| Task: Define System Architecture |
| |
 |
| In this task, the elements that compose the system are identified and their structural dependencies are determined. |
|
Relationships
| Parent Practices |
|
| Roles | Primary Performer:
| Additional Performers:
|
| Inputs | Mandatory:
| Optional:
|
| Outputs |
|
Steps
|
Determine the elements that become part of the system architecture
| Elements are agents identified during requirements elecitation, supporting infrastructure, or elements from the system
environment that have to be interacted with. |
Identify interfaces between agents and system components
| Identify which components interact with each other and thus have to provide interfaces. |
|
Key Considerations
| The abstract system architecture can be captured in a UML component diagram, where each agent type, supporting
infrastructure, and external unit is a component. The different types of elements can be identified by using
suitable stereotypes, e.g., taken from PosoMAS Auxiliary UML Profile. |
|