|
Subsystem design tasks:
5.3.6.1: Design subsystem
5.3.6.2: Design interfaces
5.3.6.3: Design database
5.3.6.UMP1: Design user interface
5.3.6.7: Evaluate design
References:
UMP glossary
Bibliography
Conventions & Notation
|
Task 5.3.6.1: Design Functional subsystem
UMP
 Development Process
Software
subsystem detailed design Activity |
next
task >> |
| Task
goals |
Define the design for each subsystem |
| Procedure |
- Programmer: Specifies the subsystem package
structure.
- Programmer: Develops the packages class structure
and specifies classes and relationships.
- Programmer: Incorporates Quality requirements, applicable to
the subsystem and stated in SA , into the subsystem's design.
- Programmer: Incorporates Constraints , applicable to the subsystem
and stated in SRS, into the subsystem design.
- Programmer: Analyzes task input Documents and Checklists and
makes the necessary changes in the subsystem's design.
- Development Manager and Developers: Conduct Technical Review
- Programmer: Publishes the subsystem design
|
| Inputs |
Programming
artifacts |
The Subsystem from the previous iteration |
| Model |
|
| Documents |
|
| Checklists |
SD evaluation |
| Guides |
Subsystem
design guide |
| Outputs |
Programming artifacts |
None |
| Model |
The Functional subsystem model |
| Documents |
Subsystem design
supplement document |
| Checklists |
None |
| Completion
criteria |
|
| Quality
metrics |
|
| Milestones |
|
| Task improvement opportunity events |
|
|
You
are here: Home
> Development > Detailed
design > Design Functional subsystem
