UML.PPT.pptx
- 2. 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. CONTD.. ObjectO rien te dD e signa n dA n a lys is • 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. ■ 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. ■ 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. ▪ 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. IMPLEMENTATI ON VIEW .
- 7. • • PROCESS VIEW A view showing the concurrency of the system Encompasses the threads and Processes the 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 •
- 8. • 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 DEPLOYME NT VIEW .
- 9. THANKING YOU