UML Architecture and Views
Download as PPT, PDF9 likes11,567 views
The document discusses object oriented design and analysis, specifically focusing on UML views. It states that a system can best be described using five interlocking views: the use case view, design view, implementation view, process view, and deployment view. Each view provides a different perspective and projection of the system's organization, structure, and functionality for various stakeholders.
UML Architecture and Views
- 1. Object Oriented Design and Analysis UML Views
- 2. Object Oriented Design and Analysis Software Architecture • Visualizing, specifying, constructing, and documenting a software- intensive system demands – system be viewed from a number of perspectives • Different stakeholders, end users, analysts, developers, system integrators, testers, technical writers, and project managers – each bring different agendas to a project – each looks at the system in different ways at different times over the project's life • The most important artifact that can be used to manage these different viewpoints and so control development of a system throughout its life cycle • Concerned with structure, behavior, usage, functionality, performance, resilience, reuse, comprehensibility, economic and technology constraints and trade-offs, and aesthetic concern
- 3. Object Oriented Design and Analysis Contd.. • the architecture of a software-intensive system can best be described by five interlocking views • each view is a projection into the organization and structure of the system, focused on a particular aspect of that system
- 4. Object Oriented Design and Analysis A view showing the functionality of the system as perceived by the external actors It exposes the requirements of the system With UML, The static aspects of this view are captured in use case diagrams The dynamic aspects of this view are captured in interaction diagrams, statechart diagrams, and activity diagrams. Use-Case View
- 5. Object Oriented Design and Analysis A view showing how the functionality is designed inside the system, in terms of the static structure and dynamic behaviour. It captures the vocabulary of the problem space and solution space. With UML, The static aspects of this view are captured in class and object diagrams The dynamic aspects of this view are captured in interaction diagrams, statechart diagrams, and activity diagrams. Design View
- 6. Object Oriented Design and Analysis A view showing the organization of the core components and files primarily addresses the configuration management of the system's releases With UML, The static aspects of this view are captured in component diagrams The dynamic aspects of this view are captured in interaction diagrams, statechart diagrams, and activity diagrams. Implementation View
- 7. Object Oriented Design and Analysis • A view showing the concurrency of the system • encompasses the threads and processes that form the system's concurrency and synchronization mechanisms • primarily addresses the performance, scalability, and throughput of the system • With UML, the static and dynamic aspects of this view are captured in same way as design view, but with a focus on the active classes that represent these threads and processes Process View
- 8. Object Oriented Design and Analysis • A view showing the deployment of the system in terms of the physical architecture • encompasses the nodes that form the system's hardware topology on which the system executes • primarily addresses the distribution, delivery, and installation of the parts that make up the physical system Deployment View