4 + 1 views of a System
The 4 + 1 notation represents four distinct views of a system and one overview of how everything fits together.
The four views are:
Design view (Logical):
1. The design view captures the classes, interfaces, and patterns that describe the representation of the problem domain and how the software will be built to address it.
2. The design view uses class, object, composite structure, activity and sequence diagrams to convey the design of the system. The design view doesn't address how the system will be implemented or executed.
3. It addresses end users, developers and represents the functional requirements and maps them onto classes in a platform independent manner.
Deployment view (physical view):
1. The deployment view captures how a system is configured, installed and executed.
2. It consists of component, deployment and interaction diagrams. The deployment view captures the physical layout.
3. It addresses system engineers and non-functional requirements.
Implementation view (development view):
1. The implementation view focuses on the configuration management of a system; what components depend on what, what source files implement what classes, etc.
2. It consists of component, interaction, statechart, composite structure diagrams.
3. Layered pattern could be used to describe the implementation view.
Process view:
1. The process view of a system is intended to capture concurrency, performance and scalability information. It consists of activity, interaction diagrams.
2. It addresses the concerns of system integrators.
The four distinct views of a system are brought together with the final view:
Use case view (scenarios) -
1. The use case view captures the functionality required by the end users.
2. The use case view is often broken down into collaborations that link a use case with one or more of the four basic views.
3. The use case view includes use case diagrams and typically uses several interaction diagrams to show use case details.
The 4 + 1 notation represents four distinct views of a system and one overview of how everything fits together.
The four views are:
Design view (Logical):
1. The design view captures the classes, interfaces, and patterns that describe the representation of the problem domain and how the software will be built to address it.
2. The design view uses class, object, composite structure, activity and sequence diagrams to convey the design of the system. The design view doesn't address how the system will be implemented or executed.
3. It addresses end users, developers and represents the functional requirements and maps them onto classes in a platform independent manner.
Deployment view (physical view):
1. The deployment view captures how a system is configured, installed and executed.
2. It consists of component, deployment and interaction diagrams. The deployment view captures the physical layout.
3. It addresses system engineers and non-functional requirements.
Implementation view (development view):
1. The implementation view focuses on the configuration management of a system; what components depend on what, what source files implement what classes, etc.
2. It consists of component, interaction, statechart, composite structure diagrams.
3. Layered pattern could be used to describe the implementation view.
Process view:
1. The process view of a system is intended to capture concurrency, performance and scalability information. It consists of activity, interaction diagrams.
2. It addresses the concerns of system integrators.
The four distinct views of a system are brought together with the final view:
Use case view (scenarios) -
1. The use case view captures the functionality required by the end users.
2. The use case view is often broken down into collaborations that link a use case with one or more of the four basic views.
3. The use case view includes use case diagrams and typically uses several interaction diagrams to show use case details.
No comments:
Post a Comment