What software architecture is and what it is not; Architectural Structures andviews; Architectural patterns; What makes a “good” architecture? Why is softwareimportant?
Technical Context; Project life-cycle context; Business context; Professional context;Stake holders; How is Architecture influenced? What Do Architecture influence?
Architecture & Requirements; Functionality; quality attribute considerations; Specifyingand achieving Quality attribute requirements; Guiding quality design decisions;Availability; Interoperability; Modifiability; Performance; Security; Testability; Usability
Modeling Architecture to enable quality attribute analysis; Quality attribute check lists;Through experiments and Back-of-the envelope analysis; Experiments; Simulations andprototypes; Analysis at different stages of the life cycle
Gathering ASRs from requirements documents; ASRs by interviewing stake holders;ASRs by understanding the business; capturing ASRs in a utility tree; Typing the methodstogether
Design strategy; the attribute driven design methods; the steps of ADD
Uses and Audiences for architecture documentation; Notations, View and Behavior;Documentation and quality attributes
Architecture and implementation; Architecture and testing
Introduction to patterns; From Mud to structure; Layers; Pipes and filters; Blackboard;Distributed systems; Brocker; Interactive systems; Model-view-control; Presentationabstraction-control; Adaptable systems; Microkernel