|
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.UMP2: Collect product requirements
| Task
goals |
To collect and analyze product
Change Requests |
| Procedure |
- Product manager: Establishes Change requesting procedure.
- Product manager: Manages Change requests tracking.
- Product manager: Analyzes changes in cost,
benefits and the overall impact on the current development
plan.
- Product manager: Prioritizes the requested changes
and proposes ensuing changes in the plan.
- Project Manager: Incorporates the accepted requests into the current plan for subsequent implementation.
- Project Manager: If necessary, agrees with
the customers (sponsors, investors) on the changes in the development
plan.
- Project Manager: Publishes the
updated development plan.
|
| Inputs |
Programming
artifacts |
- Previous product iterations
- Previous product version
- Analogous product
- Competitive product
|
| Model |
None |
| Documents |
Change request |
| Checklists |
Change request evaluation checklist |
| Guides |
None |
| Outputs |
Programming artifacts |
None |
| Model |
None |
| Documents |
|
| Checklists |
None |
| Completion
criteria |
|
| Quality
metrics |
|
| Milestones |
|
| Task improvement opportunity events |
- Change requests are not collected
- Change requests are not prioritized
- Change requests cannot be accessed by project participants
- Change requests are not traced to PBS
|
|
You
are here: Home
> Development > Requirements
analysis > Collect requirements
Development Process