Design
| Release Information |
|
| Project |
|
| Release Number |
|
| Attached Worksheets |
Architecture |
| |
Source Organisation and Build |
| |
User Interface |
| |
Persistent Storage and Database |
| |
Security |
| Related Documents |
Software Requirements: Use Case Suite |
| |
Sofware Requirements: Feature Set |
| |
Glossary |
Introduction
How is this design document organized?
This main page describes the system design in terms of packages, classes, relationships, and behavior. Several attached worksheets address specific aspects of the overall system design, such as user interface and database design.
What are the most important facts that a developer should know about this design
What are the prioritized goals of this design
- Correctness
- Feasibility
- Understandability
- Implementation phase guidance
- Modularity
- Extensibility
- Testability
- Efficiency
UML Structural Design
UML Behavioral Design
UML Design Checklist
Correctness: How do you know that this design is correct?
Feasibility: What indicates that this design can be implemented and tested with the planned amount of time and effort?
Understandability: What makes this design understandable?
Implementation phase guidance: Does the design suggest reasonable implementation tasks?
Modularity: How have concerns been separated and addressed in distinct modules?
Extensibility: How can new features can be easily added later?
Testability: What makes this system easy to test?
Efficiency: Does the system consume an acceptable amount of time, storage space, bandwidth, and other resources?
Has the design been communicated to the development team and other stakeholders?