Software Development Methodology
Software Architecture
Lecture 8
Lecturer：罗铁坚
Email：tjluo@gucas.ac
Phone：88256308
-----------------------------------------------------------------
Class Time：Mon / Wed10:00am–11:40am
Office Hour：Friday Morning 10:00 –12:00
Office Place：玉泉路教学园区科研楼东5层511
Today’ Topics
安卓开发教程 pdf1.Motivation and Problems
2.Software Architecture Foundations
3.Architecture Frameworks, Styles ,Patterns
4.Architecture Practice
Reference
1.  D. Perry and Wolf, “ Foundations for the study of software architecture”,
ACM SIGSOFT Software Engineering Notes, 17:4 (October 1992)
2.R. Allen and D. Garlan, “ Formalizing Architecture Connection.”, Proc.
Int’l conf. Software Eng. IEEE CS Press. 1994
3.Philippe B. Krunchten, “ The 4+1 View Model of Architecture”, IEEE
Software, Nov./Dec 1995
4.David Garlan, etc ,” Architectural Mismatch: Why Reuse is So Hard”, IEEE
Software, Nov./Dec 1995
5.Jeff Tryee, etc., “Architecture Decisions: Demystifying Architecture”,
Mar./Apr. 2005
6.utexas.edu/~perry/work/swa/
The Roman Coliseum is NOT Architecture. The Roman Coliseum is the RESULT of Architecture Architecture is the set of descriptive representations that are required in order to create an object.
Descriptive representations for describing  products
•Bills of Material
–What the object is made of.
•Functional Specs
–How the object works.
•Drawings
–Where the components exist relative to one another.•Operating Instructions
–Who is responsible for operation.
•Timing Diagrams
–When do things occur.
•Design Objectives
–Why does it work the way it does.