软件体系结构

1 IntrOduction to Software Architecture
1.1 A BriefHistory of Software Development
1.1.1 The Evolution of Programming Language-Abstract Level
1.1.2 The Evolution of Software Development Concerns
1.1.3 The Origin and Growth of Software Architecture
1.2 Introduction to Software Architecture
1.2.1 Basic Terminologies
1.2.2 Understanding IEEE 1471-2000
1.2.3 Views Used in Software Architecture
1.2.4 Why We Need Software Architecture
1.2.5Where Is Software Architecture in SOftware Life Cycle
1.3 Summary
References
2 Architectural Styles and Patterns
2.1 Fundamentals of Architectural Sty les and Patterns
2.2 Pipes Filters
2.2.1 Style Description
2.2.2 Study Case
2.3 Obiect oriented
2.3.1 Style Description
2.3.2 Study Case
2.4 Event-driven
2.4.1 style Description
2.4.2 Study Case
2.5 Hierarchical Layer
2.5.1 Style Description
2.5.2 Study Case
2.6 Data Sharing
2.6.1 style Description
2.6.2 Study Case2.7 Virtual Machine
2.7.1 Stvle Description
2.7.2 Study Case
2.8 Feedback Loop
2.8.1 Style Description
2.8.2 Study Case
2.9 Comparison among Styles
2.10 Integration ofHeterogeneous Styles
2.11 Summary
References
3 Application and Analysis of Architectural Styles
3.1 IntrOductiOn tO SMCSP
3.1.1 Program Background
3.1.2 Technical Routes
3.1.3 Function Design
3.2 SVstem Realization
3.2.1 The Pattern Choice
3.2.2 Interaction Mechanism
3.2.3 Realization ofMobile Collaboration
3.2.4 Knowledge-based Design
3.3 Summary
References
4 Software Architecture Description
4.1 Formal Descrio tion of Software Architecture
4.1.1 Problems in Informal Description
4.1.2 Why Are Formal Methods Necessary
4.2 Architectural Description Language
4.2.1 Introduction to ADL
4.2.2 Comparing among Typical ADLs
4.2.3 Describing Architectural Behaviors
4.3 Study Case：WRIGHT Svstem
4.3.1 Description of Component and Connector
4.3.2 Description of Configuration
4.3.3 Description of Style
4.3.4 CSP-Semantic Basis of Formal Behavior Description
4.4 FEAL：An Infrastructure to Construct ADLs
4.4.1 Design Purpose
4.4.2 FEC
4.4.3 FEAL Structure
4.4.4 FEAL MaDper
4.4.5 Examples of FEAL Application
4.5 Summary
References
5 Design Strategies in Architecture Level
5.1 From Reuse to Architecture Design
5.2 Architectural Design Space and Rules
5.3 SADPBA
5.3.1 Overview
5.3.2 split Design Process with Design Space
5.3.3 Trace Mechanism in SADPBA
5.3.4 Life Cycle Model of Software Architecture
5.3.5 SADPBA in Practice
5.4 Study Case：MEECS
5.4.1 IntrOductiOn tO MEECS
5.4.2 Applying SADPBA in MEECS
5.5 Summary
References
6 Software Architecture IDE
6.1 What Can Software Architecture IDE DO
6.1.1 A Comparison with Formalized Description Approach
6.1.2 Important Roles of Architecture IDE
6.2 Prototype
6.2.1 Uset Interface Layer
6.2.2 Model Layer
6.2.3 Foundational Layer
6.2.4 IDE Design Tactics
6.3 ArchStudio 4 System
6.3.1 IntrOduction
6.3.2 InstallingArchStudio 4
6.3.3 ArchStudio 4 Overview
6.3.4 Using ArchStudio 4
6.4 Summary
References
7 Evaluating Software Architecture
7.1 Whal Is Software Architecture Evaluation
7.1.1 Quality Attribute
7.1.2 Why Is Evaluation Necessary
7.1.3 Scenario-based Evaluation Methods
7.2 SAAM
7.2.1 General StepS of SAAM
7.2.2 Scenario Develooment
7.2.3 Architecture Description
7.2.4 Scenario Classitication and Prioritization
7.2.5 Individual Evaluation of lndirect Scenarios
7.2.6 Assessment of Scenario Interaction
7.2.7 Creation ofOverall Evaluation
7.3 ATAM
7.3.1 Initial ATAM
7.3.2 ATAM Inaprovement
7.3.3 General Process of ATAM
7.3.4 Presentation
7.3.5 Investigation and Analysis
7.3.6 Testing
7.3.7 Present the Results
7.4 Comparison among Evaluation Methods
7.4.1 Comparison Framework
7.4.2 Overview and Comparison of Evaluation Methods
7.5 Summary
References
8 Flexible Software Architecture
8.1 What Is Flexibility for
8.2 Dynamic S0flware Architecture
8.2.1 ：A Behavior Perspective
8.2.2 MARMOL：A Reflection Perspective
8.2.3 LIME：A Coordination Perspective
8.3 Flexibility：Beyond the Dynamism
8.3.1 Concept of Fiexible Software Architecture
8.3.2 Trade-off of Flexibility
8.4 Study Cases
8.4.1 Rainbow
8.4.2 MADAM
8.5Summary
References
9 A Vision on Software Architecture
9.1 S0flware Architecture in M odern Software Industry
9.1.1 Categorizing Software
9.1.2 Soflware Product Line
9.2 Soflware Architecture Used in Other Fields
9.2.1 The Outline of Software Architecture Application Practice
9.2.2 The Development Trends of Domain-Specific Software
9.3 Software Architectures Future Research
9.4 Summary
References
Index

components，hence，it supports the function modular level reuse．Exasted tilters inthe system can be easily applied to new systems which are to be designed．Second，the system composed by pipes and filters can be easily maintained and extended．The maintenance is mainly incarnated in a system’s evolution．The filter only needsto consider components’input，output and inner implementation，and not needs toconsider the filter’s maintenance and modification．If we want to replace a certainfilter。we only need to design a filter that has the same input，output with theoriginal one．The extension mainly incarnate on the system functions’expanslon．For instance．if we want to add a new function to the original sy stern,add new dataoutput，we can finish it by adding new output port to the original filter．Third，inthe Pipes Filters style，the independence of filter component provides conveniencefor system’s performance analysis，such as data throughout，deadlock analysis andcomputing accuracy，etc．Fourth，it supports concurrency computing．Systems basedon Pipes-Filters style may have many Parallel filters；these filters can runconcurrently．so that the whole performance of the system is improved．
M eanwhile，the Pipes-Filters sty le has some disadvantage：
Filters may have some restrictions to the input and output data，so this style isnot proper for interactive systems．In fact，when the pipes filters style is broughtforward，the application does not have high interactive requirement．In the earlydays of computer design，this type of style met the requirement of processmgmultiple tasks．For some application design that needs sharing much data，it is notproper to use this type of style．The exchanging of data between filters needs largedata access space．and the transinl‘ssion of data will occupy much system runningtime．2．2．2 Study CaseIn this part，we will give a typical example about digital communication system，andintroduce in detail how to organize each component using Pipes-Filters style．Fromthis，we can obviously know that software architecture is production producedwhen system analysis，creation and management technologies have got manyresearch results．Software architecture does not limit itself to computer software orother concrete subjects，it has strong general utility．
The goal of communication is transferring information．Messages have a varietyof forms，such as symbols，text，voice，music，graph，image，etc.，according to thedifference of messages．We carl classify the communication operation into telegraph，telephone．fax,data transferring and visible telephone，etc．In fact，the basic peer topeer communication is always transferring data form one point to another point．
……

Building software nowaday s is far more difficult than it Can be done several decadesago．At that time，software engineers focused on how to manipulate the computer towork and then solve problems correctly．The organization of data andimplementation of algorithm were the crucial process of software designing then?However．more and more tasks in low level，such as memory manag：ment andnetwork communication，have been antomatized or at least can be reused with littleeffort and cost．Programmers and designers，with the help of high level programminglanguages and wieldy development tools，can P ay more attention to problems，ratherthan bury themselves into the machine code manuals．However，the side effect ofthese utilities iS that more complicated problems are gwen according to therequirements from military，enterprise and SO on，in which the comp lexlty grows rap idly day by day．We believe that software architecture is a key to deal with it．

Many people become aware of the existence of software architecture Justrecently．Nevertheless，it in fact has a long history，which may surprise you．Be~~rethe invention of C++or even C，some computer scientists had begun to notice the concept of software structure and its influence to software development．In the1990s，software architecture started its journey of bloom，when several communities，workshops and conferences were held with a great amount of published articles，books and tools．Today，software architect，the job of taking software designing