Component-Based Software Development: Case Studies

Component-Based Software Development: Case Studies......Page 4
Contents......Page 8
Preface......Page 6
1.1 Introduction......Page 10
1.2 COTS Software Components......Page 11
1.2.2 COTS Components and the Software Development Process......Page 12
1.2.3 The Maturity of COTS Products and COTS-based Systems......Page 13
1.2.4 COTS Components in Real-time and Embedded systems......Page 15
1.2.5 Risks and Benefits of COTS Components......Page 16
1.3 Components and Software Architecture......Page 17
1.3.1 Integration of Software Components......Page 18
1.3.2 Software Components and Product line Architecture......Page 20
1.4 COTS Components and Software Architecture......Page 21
1.4.1 COTS Components and Product line Architecture......Page 22
1.4.3 Desirable Properties for Component Software Architecture......Page 23
1.4.4 Patterns for the Architecture of COTS-intensive Systems......Page 25
1.4.4.1 Middleware Layers......Page 26
1.4.5 COTS Component Integration......Page 27
1.4.6 Architectural Mismatch......Page 28
1.4.7 Maintainability of Component Software Architecture......Page 29
1.4.8 Architectural Views and COTS Components......Page 30
1.4.9 UML-RT and COTS Component Integration......Page 32
1.4.10 COTS Components in the Layers Associated with the Infrastructure Module......Page 35
1.5 Discussion and Conclusions......Page 36
References......Page 39
2.1 Introduction......Page 44
2.2 Definition of Commercial Components......Page 45
2.2.2 Semantic and Protocol Levels......Page 46
2.2.4 COTS Documents......Page 47
2.3 A COTS-based Application Example......Page 50
2.4 Software Architecture......Page 53
2.5 UML Real-Time......Page 55
2.6.1 The GTS Software Architecture......Page 56
2.6.2 Mapping the UML-RT GTS Example to UML Standard......Page 58
2.6.3 Including Information into Capsules......Page 59
2.7 Integrating the Architecture into other CBD Methodologies......Page 61
References......Page 62
3.1 Introduction......Page 66
3.2 Overview of the Case......Page 67
3.3 Towards the CSCA Process – Analysis of Existing Models......Page 70
3.3.1 Overview of the Reference Models......Page 71
1. Planning......Page 73
3. Delivery and Use of the Component......Page 74
3.4.1 Main concerns Revealed by the Interviews......Page 77
Evaluation of components and suppliers......Page 79
Management of components and supplier relationships......Page 80
3.5 Illustration of the Defined CSCA Process Framework......Page 81
3.6 Evaluation of the Process Model — The Server Project......Page 84
3.6.1 Feedback from the Evaluation......Page 85
3.6.2 Conclusions – General Implications......Page 87
References......Page 88
4.1 Introduction......Page 90
4.2 KobrA Components......Page 92
4.2.1 Modeling Dimensions......Page 93
4.2.2 Containment......Page 94
4.2.2.1 Component Specification versus Realization......Page 95
4.2.2.2 Containment Trees......Page 96
4.2.3.1 Generic Components......Page 97
4.2.4 Abstraction......Page 98
4.2.4.1 Implementation......Page 99
4.3.1.3 City Library......Page 101
4.3.2 Framework Scope......Page 102
4.3.3 Context Realization......Page 103
4.3.4 Framework Structure......Page 106
4.3.5.1 Specification......Page 107
4.3.5.2 Realization......Page 109
4.3.6.1 Specification......Page 110
4.3.6.2 Realization......Page 112
4.4 A Concrete Library System......Page 113
4.4.3.1 Specification......Page 114
4.4.4.2 Realization......Page 115
References......Page 116
5.1 Introduction......Page 118
5.2 Finding Crosscutting in Component-based Systems......Page 119
5.3.1 Aspect CCM: Specification......Page 122
5.3.3 Aspect CCM: Package......Page 124
5.3.4 Aspect CCM: Assembly......Page 127
5.4.2 Example Implementation......Page 129
5.4.3.1 Extension of XML Component Descriptor......Page 131
5.4.3.2 Generation of AspectJ code......Page 132
5.4.3.3 Composition of all the Code......Page 134
5.5 Related Work......Page 135
5.6 Conclusions and Future Work......Page 136
References......Page 137
6. Properties of Software Systems Synthesized from Components......Page 138
6.1.2 Software Component Properties......Page 139
6.2 Fundamental Theory for Software......Page 140
6.3 The Software Profile Problem......Page 141
6.4 Outline of a Subdomain Solution......Page 142
6.5.1 Series Combination of Run Time Values......Page 144
6.5.2 Component Developer's Measurements......Page 145
6.5.3 System Designer's Calculations......Page 146
6.6.1 Conditional System Control Structure......Page 147
6.6.2 Iterative System Control Structure......Page 148
6.7.2 Reliability......Page 149
6.7.3 Security and Safety......Page 150
6.7.4 Functional Behavior......Page 151
6.8.1 Choosing the Right Subdomains......Page 152
6.8.2 Component Independence......Page 153
6.8.3 Exact Component Descriptions (Proofs)......Page 154
6.9.2 ‘Spikes’ in Intermediate Profiles......Page 156
6.9.4 The Problem of State......Page 157
6.10 Preliminary Validation Experiments......Page 158
6.10.1 Validating Fundamental Theory......Page 159
6.10.3 Systematic Sampling and Subdomain Experiments......Page 160
6.11.1 Proof-based and Analytical Theories......Page 161
6.11.3 Higher-level Models......Page 162
6.12 Summary and Proposed Work......Page 164
References......Page 165
7. Component-based Measurement and Control Software for Embedded Systems......Page 168
7.1 Introduction......Page 169
7.2.1 Signals......Page 172
7.2.3 M&C Components......Page 174
7.2.5 Component Framework......Page 178
7.2.6 The Overall M&C Toolset......Page 179
7.3.1 Dataflow Paradigms......Page 181
SDF components:......Page 182
BDF components:......Page 183
DDF components:......Page 186
7.4.1 Iconnect Signal Graph......Page 187
7.4.2 Interface Types......Page 188
7.4.3 Architectural Types......Page 189
7.5 Conclusion and Outlook......Page 191
References......Page 193
8.1 Introduction......Page 196
8.2 Related Work......Page 198
8.2.2 Testing Techniques based on Fault Injection......Page 199
8.3 Proposed Approach......Page 201
8.3.1 Interface Mutation......Page 202
8.3.1.1 Error Discovery using Interface Mutation......Page 204
8.3.2 Interface-based Fault Injection Testing......Page 205
8.3.3 Mechanism for Fault Injection Testing......Page 206
8.4.1.1 APP1......Page 207
8.4.1.2 APP2......Page 210
8.4.1.3 Summary of Experimental Results......Page 212
8.4.2 Interface Fault Injection Testing......Page 214
8.5 Discussion......Page 215
References......Page 216
9.1 Introduction......Page 220
9.2 Background......Page 221
9.3 The ARIFS Methodology: What is Reusable Component?......Page 224
9.3.1 Static Classification of Reusable Components......Page 225
9.3.3 Reusing Verification Efforts......Page 228
9.4 Applying the Methodology: A Case Study......Page 229
9.4.1 Starting Point......Page 230
9.4.2 Obtaining the Sender......Page 231
9.4.3 Obtaining the Receiver......Page 234
9.4.5 Reusing Verification Information......Page 236
9.5 Is it Worth Reusing these Incomplete Models?......Page 238
9.6 Related Work......Page 239
References......Page 241
10.1 Introduction......Page 244
10.2.1 Component Specifications......Page 247
10.2.2 Connector Specifications......Page 248
10.2.4 Architecture Specification......Page 249
10.3.2 Interface Adaptation......Page 251
10.3.2.1 Type Conversion......Page 252
10.3.2.2 Generalized Wrapper Specifications......Page 253
10.3.4 Tactic Composition......Page 255
10.3.5 Tactic Selection......Page 257
10.4.1 Architecture Synthesis......Page 258
10.4.2 Event-Driven Implementation......Page 261
10.5 Discussion......Page 262
10.6 Related Work......Page 266
Acknowledgements......Page 267
References......Page 268
11. A Web-enabled Component-based Architecture for Legacy Applications......Page 270
11.1 Component Software Technology and Web Technology......Page 271
11.2.1 Characteristics of Engineering Computing Portal......Page 272
11.2.2 Common Business Requirements of WECBA for Legacy Applications......Page 274
11.3 Web-Enabled Component-Based Architecture (WECBA)......Page 275
11.4.1 Lightweight High Performance CORBA......Page 277
11.4.3 Interactions Between Web Server, Integration Broker, and Computation Manager......Page 279
11.5 Related Work......Page 283
11.6 WECBA Design and Implementation Assessment, Lessons Learned......Page 284
11.7 Conclusions and Future Work......Page 286
References......Page 287
12.1 Introduction and Motivation......Page 290
12.1.1 Component Model......Page 291
12.1.2 What should a PSE Contain?......Page 293
12.2 PSE Infrastructure......Page 294
12.2.1 Wrapper Tool......Page 295
12.3.1 Molecular Dynamics......Page 296
12.3.2 Boundary Element and Computational Electromagnetics......Page 300
12.3.3 Computational Fluid Dynamics......Page 302
12.4 Common Themes and Issues......Page 303
References......Page 306
Index......Page 310