search for books and compare prices
Tables of Contents for Software Architecture
Chapter/Section Title
Page #
Page Count
Foreword
xv
List of Contributors
xvii
An Introduction and History of Software Architectures, Components, and Reuse
1
12
Introduction
1
1
Software Architecture
1
2
Reusable Components
3
3
Setting a Context for Component Reuse
6
1
Components and How to Use Them
7
1
Current and Future Developments
7
6
Components, Scripts and Glue
13
14
Introduction
13
1
Motivation and State-of-the-Art
14
2
A Conceptual Framework for Software Composition
16
4
Terminology
16
2
Concepts in Practice
18
1
Other Aspects of the Conceptual Framework
19
1
Piccola --- a Small Composition Language
20
2
Discussion
22
1
Conclusions
23
4
Business Component Development
27
34
Introduction
27
1
Business Needs
27
1
Software Components
28
1
Business Components
28
1
Structure
28
1
Business Component Concepts
28
13
The Business Component Vision
28
1
Terminology
29
1
Component Granularity
30
8
Distribution Models
38
3
Business Component Run-time Concerns
41
4
The Business Object Facility
42
1
BOF Transparencies
43
1
BOF Services
43
1
BOF Frameworks
44
1
Technologies and Initiatives
44
1
Business Component Development Process Concerns
45
13
An Approach to Business Component Development
46
4
Business Component Patterns
50
7
Standards
57
1
Summary
58
3
Designing Component Kits and Architectures with Catalysis
61
26
Introduction
61
1
What is a Component?
61
1
Families of Product from Kits of Components
62
5
Larger Components
65
1
Component Strategies
66
1
Catalysis: Modelling Component Behaviour
67
7
Actions
68
2
Refinement and Traceability
70
3
Refinement from Domain to Components
73
1
Modelling for Component-Based Development
74
10
Domain Modelling
74
1
Specifying Component Behaviour
75
2
Designing Components
77
2
Defining Components Connectors
79
4
Component Partitioning
83
1
Processes for Component-Based Development
84
1
Summary
84
3
Reuse Requires Architecture
87
14
Introduction
87
1
What do we Mean by Software Architecture?
88
5
Architectural Choice
89
2
Architecture-Driven Design
91
2
Case Study in Reuse --- Matra Cap C3 Systems
93
1
Architecture-Based Reuse
93
2
Organisation and Technology
95
1
Case Study --- ``Diagonal'' Inc.
96
1
Managing the Technology
96
1
Case Study --- ``Vertical'' Ltd
97
1
Components and Reuse
97
1
Summary
98
3
Recommendations
98
3
Designing Software Architectures Through Evaluation and Transformation
101
20
Introduction
101
1
Requirements Terminology
102
1
Example
103
1
Overview of the Method
104
1
Functionality-Based Architectural Design
105
2
Assessing Quality Attributes
107
5
Scenario-Based Assessment
107
1
Simulation
108
2
Mathematical Modelling
110
1
The Role of Experience
111
1
Architecture Transformation
112
5
Impose Architectural Style
113
1
Impose Architectural Pattern
114
1
Apply Design Pattern
115
1
Convert Quality Requirements to Functionality
116
1
Distribution of Requirements
116
1
Related Work
117
1
Conclusions
118
3
An Architecture for Internet Business Applications with Business Components
121
24
Introduction
121
2
Example
123
1
Database Access
124
1
A One-Layer Two-Tier Internet Business Application Architecture
125
3
Vision for Internet Business Applications
128
2
Internet Object Server for Business Entities with RMI
130
5
Business Entities Versus Business Processes
135
1
Five-Layer Architecture
136
1
Providing Layers of Business Objects as Components
137
3
Business Components
140
2
Conclusions
142
1
Acknowledgments
143
2
Lean Product-Line Architectures for Client-Server Systems --- Concepts & Experience
145
14
Introduction
145
1
The CACS System: an End User Perspective
146
1
Rearchitecting Client-Server Systems
147
2
Framework Technology and Reflection as a Basis of Self-Configuring Product-Line Architectures
149
2
Framelets --- Small is Beautiful
150
1
Reflection Versus Abstract Classes and Interfaces
150
1
A Sample Framelet Family
151
4
List Handling Framelet
151
2
RPC Framelet
153
2
Framelet Coupling
155
1
Discussion and Conclusions
155
4
Java Evaluation
155
1
Quantitative Data
155
1
Software Engineering Challenges
156
3
Issues in Industrial Product-Line Architectures
159
20
Introduction
159
1
The Case Study
160
5
Method
160
5
Product-Line Architectures and Reusable Assets
165
2
Issues in Product-Line Architectures
167
8
Organisation
168
2
Process
170
2
Technology
172
3
Related Work
175
1
Conclusion
176
3
Architectural Standards, Processes and Patterns for Enterprise Systems
179
12
Today's Enterprises Face Increasing Competitive Challenges
179
1
Distributed Components Offer a Route Forward
179
1
``Reuse'' Really Means Achieving Economies of Scale
180
2
A Component-Capable Organisation Must be Mature
182
2
There are Several Synergistic Standards for Enterprise Components
184
3
CORBA --- Common Object Request Broker Architecture
184
1
UML --- Unified Modeling Language
185
1
XMI --- XML Metadata Interchange
186
1
Java --- a Standard Programming Language
186
1
Enterprise Java Beans --- a Standard Programming Model for Enterprise Componentry
186
1
TCP/IP, HTML, HTTP, SSL, etc. --- Standards for the Internet
187
1
Enterprise Components Require a New Generation of Middleware
187
1
Architecture Patterns are Encapsulated Solutions to the Distributed Application Design Problem
188
1
Conclusion
189
2
How Not to Reinvent Some Wheels: Lessons from Interactive System Architectures
191
22
Lessons from Another Place
191
2
Boxes and Arrows are Not Enough
193
1
Properties, Not Topologies
194
3
Domain Decompositions are Essential
197
5
Machine-Centered Decomposition Rationales
198
1
User-Centred Decomposition Rationales
199
1
Function Specificity
200
1
Abstraction Independence
200
1
Evolvability
201
1
Summary
201
1
Interactions Between Quality Attributes and Software Architectures
202
4
Trade-Offs are Unavoidable
206
1
Tools are Essential, but Virtually No Good Ones Exist
207
2
Conclusions
209
1
Acknowledgements
210
3
An Industrial Perspective
213
12
The Current Situation
213
3
What We Do
213
1
Sharing Common Solutions
214
1
Information Overload and Management
214
1
Addressing Change: the Impact of Architecture
214
2
Tools and Standards
216
1
Architectural Approaches to Software Engineering in Industry
216
6
How Does Software Architecture Fit ``Industry'' Software Development?
216
4
How are Frameworks and Patterns Used in Industry?
220
1
What is the Impact of These New Approaches on Traditional Software Development Methodologies?
220
1
Conclusions
221
1
Software Architectures and Component Engineering in Philips
222
3
Introduction
222
1
Why Components?
222
1
Approaches to Component-Based Development
223
1
Conclusions
224
1
Bibliography
225
37
Index
262