4+1 View Model
Learned in SE464.
If you try to model everything about a system in one diagram, it becomes a mess. System architecture needs to express:
- Decomposition into subsystems (how code depends on each other)
- Process interactions (how code dynamically calls each other)
- Distribution across networked devices (where to put things)
The 4 + 1 view model splits this into five complementary views:
- Logical view: key abstractions as objects or object classes
- Process view: how the system is composed of interacting processes at run-time
- Development view: how the software is decomposed for development
- Physical view: the system hardware and how software components are distributed across processors
- +1: use cases or scenarios that tie the other four views together