|
Analysis tasks:
5.3.4.UMP1 Define Product Business Specifications
5.3.4.UMP2 Collect product requirements
5.3.4.1 Specify software requirements
5.3.4.UMP3 Develop UI prototype
5.3.8.4 Develop test cases
5.3.4.2 Evaluate SRS
5.3.4.UMP4 Evaluate UI prototype
5.3.8.5b Evaluate software test case
References:
UMP glossary
Bibliography
Conventions & Notation
|
Task 5.3.4.1: Specify software requirements
| Task
goals |
To specify system Use
Case model of the External model |
| Procedure |
- Analyst: Derives Actors from the Product
context, stated in PBS.
- Analyst: Derives Use cases from the Problems & Needs, stated
in PBS.
- Analyst: Specifies the Use Case model
- Analyst: Incorporates Quality requirements,
applicable to the Use Case model and stated in PBS, into the Use
Case model.
- Analyst: Incorporates Constraints, applicable
to the Use Case model and stated in PBS, into the Use Case model.
- Analyst: Analyzes task input Documents and Checklists and makes
the necessary changes in SRS.
- Product Manager and Developers: Conduct Technical
Review.
- Analyst: Publishes SRS.
|
| Inputs |
Programming
artifacts |
None |
| Model |
The Use Case model from the previous iteration |
| Documents |
|
| Checklists |
SRS
evaluation checklist |
| Guides |
The UMP
Requirements analysis guide |
| Outputs |
Programming artifacts |
None |
| Model |
The Use Case
model |
| Documents |
|
| Checklists |
None |
| Completion
criteria |
|
| Quality
metrics |
|
| Milestones |
The beginning of the each development iteration |
| Task improvement opportunity events |
- A difficulty coming up when using SRS models and documents
in development
- SRS are not traced to PBS or a change request
|
|
You
are here: Home
> Development > Requirements
analysis > Specify requirements
Development Process