Software Architecture & Design

Notes from Software Architecture and Design Course. These contain links to Piazza forums, and private Google Drive. If you are not a student of this course during this duration, you won’t be able to access them.

If you find some link is exposed, which should not be, please report it.

• Introduction
  • Learning Objectives
  • Course Structure
• Text Browser Exercise (Analysis)
  • Problem Statement
  • Components
  • Use Cases
  • Analysis Model
  • Relationships
    • LinesVisible Association
    • Displays Association
    • HandleProportion Association
  • Modeling Benefits
• Design Concepts
  • Definitions
  • Programming vs. Software Design
  • Software Design
  • Approaches to Software Design
  • Design Validation
  • Design Documentation
  • Coupling and Cohesion
  • Information Hiding
  • Abstraction and Refinement
  • Aesthetics in Design
  • Design Philosophy
• Review of UML
  • History and Origins
  • Diagram Types Overview
  • Structural Diagrams
    • Class Model Diagram
    • Object Diagram
    • Composite Structure Diagram
    • Component Diagram
    • Deployment Diagram
    • Package Diagram
    • Profile Diagram
  • Behavioral Diagrams
    • Use Case Diagram
    • Context Diagram
    • Sequence Diagram
    • Communication Diagram
    • Activity Diagram
    • Interaction Overview Diagram
    • Timing Diagram
    • State Diagram (State Chart)
  • Object Constraint Language (OCL)
  • UML Metamodel
• Clock Radio Exercise
  • Modeling with Statecharts
  • Clock Radio Description
  • Percepts
  • Percept States and Finite State Machines
  • Events and External Controls
  • Outermost Statechart Layer
  • Setting the Time
  • Stimulus-Response Table
  • Timer Events and Internal States
  • Coordination Mechanisms
  • Validation
  • Statechart Modeling Method Summary
  • Conclusion
• Object Oriented Analysis Exercise
  • Object-Oriented Analysis (OOA)
  • Why Objects over Functions
  • The OOA Technique
    • Steps
  • Example: Counting Tree Leaves
    • Candidate Classes
    • Attributes (from Adjectives)
    • Operations (from Action Verbs)
  • Relationships
    • Generalization
    • Aggregation
    • Association
  • Caveats
• UML Class Models
  • Overview
  • Classes
    • Name Compartment
    • Attributes Compartment
    • Operations Compartment
  • Advanced Class Features
  • Relationships
  • Associations
    • Association Classes
    • Links
  • Aggregation and Composition
  • Generalization
    • Superclass/subclass subtlety
  • Key Takeaway
• Design Studies
  • Design Studies
  • Design Studies as Experiments
  • Report Structure
  • Deliverables
• Library Exercise (UML)
  • Analyzing Requirements
  • Refining Classes and Attributes
  • Adding Attributes
  • Identifying Operations
  • Adding Relationships
  • Refining Relationships
  • Final Considerations
• Formal Specification Exercise
  • Formal Specification
  • The Specification Process
    • SQRT Example
    • SORT Example
  • Specifying ORDERED
  • Specifying Permutation
  • OCL Version of ORDERED
  • Takeaway
• OCL
  • Overview
  • Why OCL
  • Uses of OCL
  • Syntax
  • Invariants
  • Pre and Postconditions
  • Attribute Changes and @pre
  • Built-in Types and Operations
  • Keywords
    • Let Clause
  • Navigation
  • Collections
  • Other Features
• Library Exercise (OCL)
  • Purpose
  • Invariants
  • Query Operations
  • Operations with Side Effects
  • Derived Data
  • Missing Pieces
  • Observations
• Behavior Modeling
  • States and Events
  • Modeling Approaches
  • Combinatorial Modeling
  • Sequential Systems
  • Statecharts
    • Statechart Icons
    • Synchronization
    • Additional Features
  • Relationship to Class Diagrams
  • Beyond Statecharts
• KWIC Exercise
  • Introduction
  • KWIC Index Definition
  • Four Architectural Solutions
    • Shared Data Decomposition
    • Pipe and Filter
    • Abstract Data Type (ADT)
    • Implicit Invocation
  • Comparative Evaluation
  • Resilience to Change
  • Lessons
• Guest Interview- LayerBlox
  • Background
  • LayerBlox
  • Feature-Based Design
  • Assembly Specifications
  • Supporting Tools
  • Lessons Learned
• Overview of Architectural Styles
  • Introduction
  • Informal Definition
  • Analysis Models vs. Architecture
  • Definitions of Software Architecture
  • Components
  • APIs
  • Connectors
  • Configuration
  • Terminology
  • Architectural Styles
  • Catalog of Architectural Styles
  • Style Issues
  • Architecture Description Languages
  • Architectural Evaluation
  • Summary
• Architectural Views
  • Introduction
  • Kruchten’s 4+1 Views
    • Logical View
    • Development View
    • Process View
    • Physical View
    • Use Case View (+1)
  • Context View
  • Individual Use Cases
  • Feature View
  • Non-Functional View
  • Bug Reporting View
  • Utility Views
  • Conclusion
• Text Browser Exercise (Arch)
  • Overview
  • Phase 0 — Preparation (Context Diagram)
  • Phase 1 — Decomposition
  • Phase 2 — Architectural Style Selection
    • Layer Assignment
    • OCL Updates
  • Phase 3 — Invariant Maintenance
    • Three Strategies
    • Trade-offs
  • Process Summary
  • Conclusion
• Non-Functional Reqs & Arch Styles
  • Introduction
  • Functional vs. Non-Functional Requirements
  • Quality Catalog
    • Performance
    • Maintainability
    • Reliability
    • Safety
    • Security
  • Architectural Styles Reviewed
  • Quality × Style Matrix
    • Pipe and Filter
    • Layered
    • Blackboard
    • Object-Oriented
    • Implicit Invocation
  • Negative Side Effects
  • Summary
• Connectors
  • Overview
  • Atomic Elements
  • Service Categories
  • Procedure Call Connectors
  • Event Connectors
  • Data Access Connectors
  • Linkage Connectors
  • Stream Connectors
  • Arbitrator Connectors
  • Adaptor Connectors
  • Distributor Connectors
  • Composite Connectors
  • Connector Design
  • Validation Rules
  • Linux Case Study
  • Summary
• Acme
  • Architectural Description Languages
  • ACME Overview
  • Architecture Vocabulary
  • Simple Client-Server Example
  • Decomposition
    • Representations and Rep-Maps
  • Extending ACME
    • Property Sublanguage
    • Families (Architectural Styles)
    • Open Semantic Framework
  • ACME Limitations
• Refinement
  • Complexity and Abstraction
  • Decomposition
    • Horizontal Decomposition
    • Vertical Decomposition
  • Three Properties of Proper Refinement
  • Property 1 — Requirements Satisfaction
  • Notation
  • Property 2 — Internal Consistency
  • Property 3 — Faithful Representation
    • Criterion 1: Adequacy
    • Criterion 2: Totality
    • Criterion 3: Modeling (Inputs and Outputs)
  • Bank Account Example
  • Summary
• Middleware
  • Distributed Systems Architecture
  • Context
  • Characteristic Issues
    • Network Communication
    • Data Transportability
    • ACID Transactions
    • Coordination
    • Reliability
    • Scalability
    • Heterogeneity
  • Kinds of Middleware
    • Transactional Middleware
    • Message-Oriented Middleware (MOM)
    • Procedural Middleware
    • Object/Component Middleware
  • Software Engineering Issues
  • Web Services
  • Service-Oriented Architecture (SOA)
  • Summary
• Components
  • Bottom-Up Design
  • Buy vs. Build
  • Component Characteristics
  • Component Life Cycle
  • Component Models
  • Component Issues
    • Configuration
    • Versioning
    • Extensions
    • Callbacks
    • Contracts and Guarantees
    • Objects as Components
    • Industry Scaling
    • Domain Standards
  • Component Frameworks
  • Future Directions
  • Summary
• Coffee Maker Exercise
  • The Mark IV Special Coffee Maker
  • Traditional OOA Approach
  • Use-Case-Driven Approach
  • Role-Based Design
  • Dependency Inversion Principle
  • Summary
• Object Design
  • Intermodel Consistency
  • From Analysis to Design
  • System Design Considerations
  • Abstraction Mechanisms
  • Collaboration-Based Design
  • Sources for Methods
  • New Classes in Design
  • Implementing Generalization
  • Implementing Associations
  • Implementing Dependencies
  • Implementing Control (StateCharts)
  • Abstract Classes and Interfaces
  • Summary
• Design Patterns
  • Origins and the Gang of Four
  • GoF Pattern Documentation Structure
  • Pattern Categories
    • Creational Patterns
    • Structural Patterns
    • Behavioral Patterns
  • Composite Pattern (Structural, Detail)
  • Singleton Pattern (Creational, Detail)
  • Visitor Pattern (Behavioral, Detail)
  • Problems with Patterns
  • Summary
• Design Principles
  • Foundational Concepts
  • Design Principles Catalog
    • Liskov Substitution Principle (LSP)
    • Law of Demeter
    • Hollywood Principle (Inversion of Control)
    • Dependency Inversion Principle (DIP)
    • Open-Closed Principle (OCP)
    • Interface Segregation Principle (ISP)
    • Reuse Principles
    • Acyclic Dependency Principle
    • Stable Dependency Principle
    • Bad Smells (Refactoring Principles)
    • Riel’s Design Heuristics
    • Single Choice Principle
    • Transparency
    • Intentionality
  • Summary
• Design Reviews
  • Purpose and Scope
  • The Review Process
    • Step 1: Planning
    • Step 2: Preparation
    • Step 3: Review Meeting
    • Step 4: Rework
    • Step 5: Follow-Up
  • Participant Roles
  • Review Meeting Structure
    • Severity Classification
  • Ensuring Thoroughness
  • Metrics
    • Process Improvement Data
  • Alternative Review Styles
  • Guidelines
  • Effectiveness
    • Other Benefits and Costs
  • Summary
• Geeks in Black- The Code Review
  • Code Review Roles
  • Code Review Process Observations
  • Defect Classification
    • Defect Types
    • Severity Levels
  • Defect Catalog from the Review
  • Key Takeaways