Architecture is the first artifact that can be analyzed to determine how well its quality attributes are being achieved, and it also serves as the project blueprint. An architecture serves as the vehicle for communication, is the manifestation of the earliest design decisions, and is a re-usable abstraction that can be transferred to new systems. Software architecture of a program or computing system is the structure or structures of the system, which comprise: software components, the externally visible properties of those components, and the relationships between them. When you model a system’s architecture, you capture decisions about the system’s requirements of the system elements that shape these views:
- logical elements
- physical elements
- structural aspects of the system
- behavioral aspects of the systems
- and patterns
Learning Objective:
This cosurse teach you how to organize software architecture using idifferent views which addresses a specific set of concerns. This Course shows you how software architecture should be captured and what UML notation can support for documenting those decisions you made on your design of the systems architecture.
Architectural Modeling contains three Parts so far:The Architectural Modeling I, II & III.It covers various aspects and techniques involves in building software Architecture using:
Part I: Architectural Analysis I - Architectural Modeling Using Package Diagram
Part II: Architectural Analysis II: Architectural Modeling Using Implementation Diagram
(Component diagram & Deployment Diagram)
Part III: Architectural Analysis III: MVC Using Robustness Analysis Diagram
Course Content:
