1.Architectural requirements
[This section describes the requirements which are important for developing the software architecture.]
1.1Non-functional requirements
[Describe the architecturally relevant non-functional requirements, i.e. those which are important for developing the software architecture. Think of security, privacy, third-party products, system dependencies, distribution and reuse. Also environmental factors such as context, design, implementation strategy, team composition, development tools, time to market, use of legacy code may be addressed.
Usually, the non-functional requirements are already in place and can be referenced here. This document is not meant to be the source of non-functional requirements, but to address them. Provide a reference per requirement, and where the requirement is addressed.]
|
Source |
Name |
Architectural relevance |
Addressed in: |
|
[The source usually is the Vision, the Product Acceptance Plan or a stakeholder.] |
[Provide the name of the requirement] |
[Describe why this requirement is relevant with respect to the software architecture.] |
[Provide the section number in the SAD where this requirement is addressed.] |
1.2Use Case View (functional requirements)
[Refer to Use Cases or Use Case scenarios which are relevant with respect to the software architecture. The Use Cases referred to should contain central functionality, many architectural elements or specific delicate parts of the architecture.]
The overview below refers to architecturally relevant Use Cases from the Use Case Model (see references).
|
Source |
Name |
Architectural relevance |
Addressed in: |
|
[The source is a Use Case or scenario.] |
[Provide the name of the Use Case or Use Case scenario.] |
[Describe what makes this Use Case or scenario relevant in the envisioned software architecture.] |
[Provide the section number in which the Use Case is treated.] |
0 comments