1. Lecture 09: Software Architecture (Part I)
“Good software architecture makes the rest of the project easy.”
-- Steve McConnell
06 Jul 2006
CSE403, Summer'06, Lecture09
Valentin Razmov

2. Outline Standard notations for expressing architectural designs
Dataflow / state diagram
Class diagram (upcoming)
Sequence diagram (upcoming)
06 Jul 2006
CSE403, Summer'06, Lecture09
Valentin Razmov

3. Resources “Code Complete”, 2nd ed., by Steve McConnell
Ch. 5:
“Design Patterns Explained – A New Perspective on Object-Oriented Design”, by Alan Shalloway and James Trott
06 Jul 2006
CSE403, Summer'06, Lecture09
Valentin Razmov

4. The Basic Problem: Getting from Requirements to Code
How do you bridge the
gap between
requirements and code?
? ? ?
Code
06 Jul 2006
CSE403, Summer'06, Lecture09
Valentin Razmov

5. From Requirements to Code: One Possible Path
A Miracle Happens!
Ad hoc, requires gurus, unpredictable, COSTLY, unmaintainable – Code and Fix
Code
06 Jul 2006
CSE403, Summer'06, Lecture09
Valentin Razmov

6. From Requirements to Code: A Better Organized Answer
Provide a high-level framework to build and evolve the system
Software Architecture
Provide a high level design, an architecture, a framework, to build around and evolve with
Code
06 Jul 2006
CSE403, Summer'06, Lecture09
Valentin Razmov

7. An Architecture Helps with …
level of abstraction, vocabulary, constraints
System understanding
Reuse
Construction
Evolution
Analysis
Management
Communication
of components,
identifies commonalities
partial blueprint
organization for change, separates “what” from “how”
of components and connections
good milestone
between stakeholders
06 Jul 2006
CSE403, Summer'06, Lecture09
Valentin Razmov

8. Notations: Dataflow / State Diagram
High-level, coarse grained
Used to describe interactions between the components of a system
Example:
06 Jul 2006
CSE403, Summer'06, Lecture09
Valentin Razmov