- System structure – system interrelated components. A key structural issue is minimizing dependencies between these components. This makes it possible to change one component without requiring changes in others.
- System behaviour – Somplete behaviour and life-cycle of the actions. From simple (and measurable) items like timings (latency, response etc) to more complex system behaviour such as auditing, logging, replication etc.
- An abstract representation of the data flows, inputs and outputs of the system.
- Includes entity-relationship model diagram
- The actual input and output processes of the system. This is explained in terms of how data is input into a system, verified, processed, and displayed.
- In physical design, the following requirements about the system are decided:
- Input requirements
- Output requirements
- Storage requirements
- Processing requirements
- System control and backup or recovery