|
Architecture design tasks:
5.3.5.1 Map SRS to architecture
5.3.5.2 Develop external interface
5.3.5.3 Develop general db design
5.3.5.6 Evaluate architecture
References:
UMP glossary
Bibliography
Conventions & Notation
|
Task 5.3.5.1: Map SRS to the software architecture
UMP
 Development Process
Software architecture design Activity |
next task >> |
| Task
goals |
To develop the software subsystem
structure and map the SRS to these subsystems.
Here SRS means Actor, Use Case or numbered PBS statement. |
| Procedure |
- Architect: Groups SRSs into subsystems.
- Architect: Develops subsystem package and class
structure if necessary.
- Architect: Incorporates Quality requirements,
applicable to the Architecture model and stated in PBS and SRS,
into the Architecture
model.
- Architect: Incorporates Constraints, applicable
to the Architecture model and stated in PBS and SRS, into the Architecture
model.
- Architect: Analyzes task input Documents and
Checklists and makes necessary changes in the Architecture.
- Development Manager and Developers: Conduct
Technical Review.
- Architect: Publishes the Architecture model.
|
| Inputs |
Programming
artifacts |
None |
| Model |
|
| Documents |
|
| Checklists |
SAD Evaluation |
| Guides |
The Software architecture design guide |
| Outputs |
Programming artifacts |
None |
| Model |
The Architecture model |
| Documents |
SAD
supplement document |
| Checklists |
None |
| Completion
criteria |
|
| Quality
metrics |
|
| Milestones |
|
| Task improvement opportunity events |
|
|
You
are here: Home
> Development > Architecture
design > Map SRS to architecture
