TAILIEUCHUNG - Lecture Software design and architecture – Chapter 6

After this chapter the student should have acquired the following knowledge and skills: Introduction to software architecture, architecture vs design, architect’s responsibilities, architecture business cycle, architectural representation, using UML, using ADL. | SOFTWARE DESIGN AND ARCHITECTURE LECTURE 06 Review Introduction to software architecture Architecture vs Design Architect’s responsibilities Architecture Business Cycle Outline Architectural Representation Using UML Using ADL Architectural Representations Software architecture specifies a high level of software system abstraction by employing decomposition, composition, architecture styles, and quality attributes. Architectural Representations Every software architecture must describe its collection of components and the connections and interactions among these components. It must also specify the deployment configuration of all components and connections. Additionally, a software architecture design must conform to the project's functional and nonfunctional requirements. Architectural Representations – Box diagrams Box-and-line diagrams are often used to describe the business concepts and processes during the analysis phase of the software development lifecycle. Box diagrams These diagrams come with descriptions of components and connectors, as well as other descriptions that provide common intuitive interpretations. Unified modeling language UML for Software Architecture The Unified Modeling Language (UML) is a graphical language for visualizing, specifying, constructing, and documenting the artifacts of a software-intensive system. UML offers a standard way to draw a system's blueprints. Architecture View Models a model is a complete, simplified description of a system from a particular perspective or viewpoint. There is no single view that can present all aspects of complex software to stakeholders!!! View Model View models provide partial representations of the software architecture to specific stakeholders such as the system users, the analyst/designer, the developer/programmer, the system integrator, and the system engineer. View Model Software designers can organize the description of their architecture decisions in different views. The 4 +1 View Model The

• Đồ họa - Thiết kế - Flash
• Software design
• Software design and architecture
• Software architecture
• Software architectural design
• Object oriented design
• Software development
• Software design methods
• Distributed software architecture
• Data flow software architecture
• Software requirement specification
• Software development activities
• Component based software engineering