...
Below table is a sample for use case description.
Use case ID {Add anchor} | |
Use Case | Use case name |
|---|---|
Use Case Description |
Actors | |
Pre-Condition | |
Post-Condition | |
Main Scenarios |
|---|
Basic Path |
| Alternative Path |
| Exception Path |
5. Requirements
This chapter shows functional and Non-functional requirements to be designed.
If there are any constraints to design, please describe them as well.
...
- Which design options are considered and/or chosen? why?
- What quality attributes are relevant/important for the design?
- How such attributes are exhibited in the design?
...
| Anchor | ||
|---|---|---|
|
...
...
|
...
6.2. External view
Component under design should be seen as a black-box in diagram. Logical and process views should explain how the component is interacting with the rest of the system.
- Logical view shows the static aspects of the architecture, such as the following diagram
- component structure diagram, class diagram, object diagram
- Process view shows the dynamic aspects of the architecture, such as the following diagram
- inter-component sequence, generic activity diagram, state machine diagram.
...
- .
7. Interface definition
Interface, that includes data and function/method, provided by this component to be used by other components is described here.
...
8.2.2 Logical view
Please refer Section 6.2
8.2.3 Process view
Please refer Section 6.2
8.3 Deployment view
Component may have sub-parts and these sub-parts are packaged as different distributable units. Explain them here.
...