UML - Architecture - Lecture 1 - 3
UML - Architecture - Lecture 1 - 3
Chapter
Contents
o UML- Architecture
1. Use case view
2. Design view
3. Implementation view
4. Process view
5. Development view
Software architecture provides a basic design of a complete software system. It defines the elements included in
the system, the functions each element has, and how each element relates to one another. In short, it is a big
picture or overall structure of the whole system, how everything works together.
The architect plans the structure of the system to meet the needs like these. It is essential to have proper software
architecture, mainly for a large software system. Having a clear design of a complete system as a starting point
provides a solid basis for developers to follow.
It is a view that shows the functionality of the system as perceived by external actors.
It reveals the requirements of the system.
With UML, it is easy to capture the static aspects of this view in the use case diagrams, whereas ? its
dynamic aspects are captured in interaction diagrams, state chart diagrams, and activity diagrams.
2. Design View
It is a view that shows how the functionality is designed inside the system in terms of static structure and
dynamic behavior.
It captures the vocabulary of the problem space and solution space.
With UML, it represents the static aspects of this view in class and object diagrams, whereas its dynamic
aspects are captured in interaction diagrams, state chart diagrams, and activity diagrams.
It is the view that represents the organization of the core components and files.
It primarily addresses the configuration management of the system?s releases.
With UML, its static aspects are expressed in component diagrams, and the dynamic aspects are captured
in interaction diagrams, state chart diagrams, and activity diagrams.
4. Process View