jgs CSE 460 Software Analysis and Design Lecture 21: Software Architecture Dr. Javier Gonzalez-Sanchez [email protected] javiergs.engineering.asu.edu | javiergs.com PERALTA 230U Office Hours: By appointment 

jgs 00010000 Announcement § Assignment 05 (Patterns) is due March 29. It opens at the end of the lecture 

jgs Next Software Architecture 

jgs 00010000 Software Design 

jgs 00010000 Software Architecture Java.util javax.swing java.awt 

jgs 00010000 Definition § Software design It is responsible for the code level design: what each class is doing, its relationships, and scope. § Software architecture It is responsible for the skeleton and the high-level organization of a software. It identifies the main structural modules (or components) in a system and the relationships between them. 

jgs 00010000 Architecture Goals § Define separate branches for each major function § Coordinate communication between modules § Limit propagation of side effects § Facilitate extensibility, modifiability and reuse 

jgs 00010000 Architecture Representation § The most frequently used method for documenting software architectures are simple, informal block diagrams § They show entities and relationships § They lack semantics, do not show the types of relationships between entities nor the visible properties of entities in the architecture. 

jgs 00010000 Architectural Decisions Is there a generic application architecture that can act as a template for the system that is being designed? How will the system be distributed across hardware cores or processors? What architectural patterns or styles might be used? What will be the fundamental approach used to structure the system? How will the structural components in the system be decomposed into sub-components? What strategy will be used to control the operation of the components in the system? What architectural organization is best for delivering the non-functional requirements of the system? How should the architecture of the system be documented? ? 

jgs 00010000 Architectural Patterns 1. Model-View-Controller (MVC) 2. Layered Architecture 3. Repository Architecture (Blackboard) 4. Client-Server architecture 

jgs Model-View-Controller 

jgs 00010000 Model-View-Controller 

jgs 00010000 Model-View-Controller 

jgs 00010000 Model-View-Controller 

jgs 00010000 Model-View-Controller Description Separates presentation and interaction from the system data into three logical components: 1. Model manages the system data and operations. 2. View defines and manages how the data is presented to the user. 3. Controller manages user interaction (e.g., key presses, mouse clicks, etc.) and passes these interactions to the View and the Model. When Used • Used when there are multiple ways to view and interact with data. • Also, used when the future requirements for interaction and presentation of data are unknown. Advantages • Allows the data to change independently of its representation and vice versa. • Supports presentation of the same data in different ways with changes made in one representation shown in all of them. Disadvantages • Additional code and complexity when the data model and interactions are simple. 

jgs 00010000 Drafting an Implementation 

jgs 00010000 Example Main Factory Controller View Model Gift Ball Box Envelop 

jgs 00010000 Implementation :: View 

jgs 00010000 Implementation :: Controller 

jgs To be Continued… 

jgs CSE 460 Software Analysis and Design Javier Gonzalez-Sanchez [email protected] Fall 2020 Disclaimer. These slides can only be used as study material for the class CSE460 at ASU. They cannot be distributed or used for another purpose.