4+1 view model addresses large and challenging architectures using several concurrent views or perspectives, with different notations each one addressing one specific set for concerns.
The diagrammatic representation is showed below:
.
Logical View: (Object-oriented Decomposition)
Viewer: End-user
Consideration: Functional requirements like what the system should provide in terms of services to its users.
Notation: the object and dynamic models are involved
Tool: Rational Rose
Process View: (The process decomposition)
Viewer: Integrators
Consideration: Non - functional requirements (concurrency, performance, scalability)
Style: Several styles would fit in this view
It uses multiple levels of abstractions- a logical network of processes at the highest level.
A process is a grouping of tasks that form an executable unit:
- Major Tasks: Architecture relevant tasks
- Minor Tasks: Helper tasks. (Buffering)
Deployment View (Subsystem decomposition)
Viewer: Programmers and Software Managers
Consideration: software module organization (Hierarchy of layers, software management, reuse, constraints of tools)
Style: layered style
Notation: module, subsystem, layers are involved
Physical View: (Mapping the software to the Hardware)
Viewer: System Engineers
Considers: Non-functional req. regarding to underlying hardware (Topology, Communication)
Notation: It may have several forms and may be tightly connected to the process view
There may be two architectures:
- Test and development
- Deployment
Scenarios: (Putting it all together)
Viewer: All users of other views and Evaluators.
Considers: System consistency, validity
Notation: almost similar to logical view
Tool: Rational Rose
It helps illustrate and validate the document and also helps architect during the architecture design
and 2 others joined a min ago.
teamques10
★ 68k