1- Problem Statement
developed by Client and can be represented by analysis.
|
Ingredients of a Problem Statement |
|
|
A good problem statement describes |
|
|
A-Current situation: |
|
|
The Problem to be solved // target of system. |
|
|
Description of one or more scenarios //have 2 or 3 scenario to be describe. |
|
|
B-Requirements |
|
|
Functional and Nonfunctional requirements |
|
|
Constraints (”pseudo requirements”) // if customer need specific tool. |
|
|
Project Schedule |
|
|
Major milestones that involve interaction with the client //what is the first deliver to Customer. |
|
|
including deadline for delivery of the system |
|
|
Deliverables expected by the client // all component of system (Training-Source code). |
|
|
Target environment |
|
|
The environment in which the delivered system has to perform a specified set of system tests. // system environment (HW, SW) |
|
|
Client Acceptance Criteria |
|
|
Criteria for the system tests. //we need to know exactly what and when is needed from system (Deliver information from system to user). //Like IBM web site Sport that have delay in result after play game |
|
1.A-Current Situation: The Problem to Be Solved
What is the problem in the current situation?
Examples:
the response time when playing letter-chess is far too slow. (Change SW for new technology-new in solution domain-)
I want to play Go, but cannot find players on my level. (Application domain)
What has changed? Why can we address the problem now?
there has been a change, either in the application domain or in the solution domain
Change in the application domain
A new function (business process) is introduced into the business
Example: We can play highly interactive games with remote people
Change in the solution domain
A new solution (technology enabler) has appeared
Example: The internet allows the creation of virtual communities.
1.B.0-Types of Requirements
No comments yet.