Component-based Software Development : Case Studies.
- 1st ed.
- 1 online resource (312 pages)
- Series On Component-based Software Development ; v.1 .
- Series On Component-based Software Development .
Intro -- Component-Based Software Development: Case Studies -- Contents -- Preface -- 1. A Survey of Proposals for Architecting Component Software -- 1.1 Introduction -- 1.2 COTS Software Components -- 1.2.1 Component Models -- 1.2.2 COTS Components and the Software Development Process -- 1.2.3 The Maturity of COTS Products and COTS-based Systems -- 1.2.4 COTS Components in Real-time and Embedded systems -- 1.2.5 Risks and Benefits of COTS Components -- 1.3 Components and Software Architecture -- 1.3.1 Integration of Software Components -- 1.3.2 Software Components and Product line Architecture -- 1.4 COTS Components and Software Architecture -- 1.4.1 COTS Components and Product line Architecture -- 1.4.2 MOTS Frameworks and COTS Components -- 1.4.3 Desirable Properties for Component Software Architecture -- 1.4.4 Patterns for the Architecture of COTS-intensive Systems -- 1.4.4.1 Middleware Layers -- 1.4.5 COTS Component Integration -- 1.4.6 Architectural Mismatch -- 1.4.7 Maintainability of Component Software Architecture -- 1.4.8 Architectural Views and COTS Components -- 1.4.9 UML-RT and COTS Component Integration -- 1.4.10 COTS Components in the Layers Associated with the Infrastructure Module -- 1.5 Discussion and Conclusions -- References -- 2. Describing Specifications and Architectural Requirements of COTS Components -- 2.1 Introduction -- 2.2 Definition of Commercial Components -- 2.2.1 Component Interfaces -- 2.2.2 Semantic and Protocol Levels -- 2.2.3 Interface Notation -- 2.2.4 COTS Documents -- 2.3 A COTS-based Application Example -- 2.4 Software Architecture -- 2.5 UML Real-Time -- 2.6 Composing the Software Architecture -- 2.6.1 The GTS Software Architecture -- 2.6.2 Mapping the UML-RT GTS Example to UML Standard -- 2.6.3 Including Information into Capsules -- 2.7 Integrating the Architecture into other CBD Methodologies. 2.8 Concluding Remarks -- References -- 3. Definition of COTS Software Component Acquisition Process - The Case of a Telecommunication Company -- 3.1 Introduction -- 3.2 Overview of the Case -- 3.3 Towards the CSCA Process - Analysis of Existing Models -- 3.3.1 Overview of the Reference Models -- 3.3.2 Acquisition Process Framework based on the Existing Models -- 1. Planning -- 2. Contracting -- 3. Delivery and Use of the Component -- 3.4 Requirements for the CSCA Process - the Purchaser's Perspective -- 3.4.1 Main concerns Revealed by the Interviews -- Contracting and negotiation -- Evaluation of components and suppliers -- Management of components and supplier relationships -- 3.5 Illustration of the Defined CSCA Process Framework -- 3.6 Evaluation of the Process Model - The Server Project -- 3.6.1 Feedback from the Evaluation -- 3.6.2 Conclusions - General Implications -- References -- 4. The Library Systems Product Line: A Case Study Demonstrating the KobrA Method -- 4.1 Introduction -- 4.2 KobrA Components -- 4.2.1 Modeling Dimensions -- 4.2.2 Containment -- 4.2.2.1 Component Specification versus Realization -- 4.2.2.2 Containment Trees -- 4.2.3 Genericity -- 4.2.3.1 Generic Components -- 4.2.3.2 Frameworks versus Applications -- 4.2.4 Abstraction -- 4.2.4.1 Implementation -- 4.2.4.2 Reuse -- 4.3 Framework for Library System Product Line -- 4.3.1 Product Line Members -- 4.3.1.1 Research Library -- 4.3.1.2 University Library -- 4.3.1.3 City Library -- 4.3.2 Framework Scope -- 4.3.3 Context Realization -- 4.3.4 Framework Structure -- 4.3.5 Library System -- 4.3.5.1 Specification -- 4.3.5.2 Realization -- 4.3.6 Loan Manager -- 4.3.6.1 Specification -- 4.3.6.2 Realization -- 4.3.7 Reservation Manager -- 4.4 A Concrete Library System -- 4.4.1 Concrete Product Line Member -- 4.4.2 Context Realization -- 4.4.3 Library System -- 4.4.3.1 Specification. 4.4.3.2 Realization -- 4.4.4 Loan Manager -- 4.4.4.1 Specification -- 4.4.4.2 Realization -- 4.5 Conclusions -- References -- 5. Component-based System Design and Composition: An Aspect-oriented Approach -- 5.1 Introduction -- 5.2 Finding Crosscutting in Component-based Systems -- 5.3 AspectCCM: CCM Components through AOP -- 5.3.1 Aspect CCM: Specification -- 5.3.2 Aspect CCM: Components Implementation -- 5.3.3 Aspect CCM: Package -- 5.3.4 Aspect CCM: Assembly -- 5.4 Example of Use -- 5.4.1 Example Specification -- 5.4.2 Example Implementation -- 5.4.3 Example Package -- 5.4.3.1 Extension of XML Component Descriptor -- 5.4.3.2 Generation of AspectJ code -- 5.4.3.3 Composition of all the Code -- 5.4.4 Example Assembly -- 5.5 Related Work -- 5.6 Conclusions and Future Work -- References -- 6. Properties of Software Systems Synthesized from Components -- 6.1 Components in Engineering -- 6.1.1 Software Components? -- 6.1.2 Software Component Properties -- 6.2 Fundamental Theory for Software -- 6.3 The Software Profile Problem -- 6.4 Outline of a Subdomain Solution -- 6.5 Details of Series System Calculation -- 6.5.1 Series Combination of Run Time Values -- 6.5.2 Component Developer's Measurements -- 6.5.3 System Designer's Calculations -- 6.6 Other System Control Structures -- 6.6.1 Conditional System Control Structure -- 6.6.2 Iterative System Control Structure -- 6.7 Applications of the Paradigm -- 6.7.1 Performance -- 6.7.2 Reliability -- 6.7.3 Security and Safety -- 6.7.4 Functional Behavior -- 6.8 Theoretical Issues -- 6.8.1 Choosing the Right Subdomains -- 6.8.2 Component Independence -- 6.8.3 Exact Component Descriptions (Proofs) -- 6.9 Deficiencies of the Theory -- 6.9.1 Problems of Scale -- 6.9.2 'Spikes' in Intermediate Profiles -- 6.9.3 Incorrect Components -- 6.9.4 The Problem of State -- 6.10 Preliminary Validation Experiments. 6.10.1 Validating Fundamental Theory -- 6.10.2 First Manual Experiments -- 6.10.3 Systematic Sampling and Subdomain Experiments -- 6.10.4 Components Constructed to Order -- 6.11 Related Work -- 6.11.1 Proof-based and Analytical Theories -- 6.11.2 Component Frameworks -- 6.11.3 Higher-level Models -- 6.11.4 Component-based Software Engineering Workshops -- 6.12 Summary and Proposed Work -- Acknowledgements -- References -- 7. Component-based Measurement and Control Software for Embedded Systems -- 7.1 Introduction -- 7.2 A Novel Concept for M& -- C Systems -- 7.2.1 Signals -- 7.2.2 Communication between M& -- C Components -- 7.2.3 M& -- C Components -- 7.2.4 Component System -- 7.2.5 Component Framework -- 7.2.6 The Overall M& -- C Toolset -- 7.3 Dataflow Model -- 7.3.1 Dataflow Paradigms -- 7.3.2 M& -- C Component Models -- SDF components: -- BDF components: -- DDF components: -- Component assembly -- 7.4 Application Example -- 7.4.1 Iconnect Signal Graph -- 7.4.2 Interface Types -- 7.4.3 Architectural Types -- 7.5 Conclusion and Outlook -- References -- 8. Fault-based Testing of CORBA Component Software -- 8.1 Introduction -- 8.2 Related Work -- 8.2.1 Test Techniques based on Mutation -- 8.2.2 Testing Techniques based on Fault Injection -- 8.2.2.1 Interface-based Fault Injection Testing -- 8.3 Proposed Approach -- 8.3.1 Interface Mutation -- 8.3.1.1 Error Discovery using Interface Mutation -- 8.3.1.2 Interface Mutation Adequacy Criterion -- 8.3.2 Interface-based Fault Injection Testing -- 8.3.3 Mechanism for Fault Injection Testing -- 8.4 Experimental Evaluation -- 8.4.1 Mutation Testing -- 8.4.1.1 APP1 -- 8.4.1.2 APP2 -- 8.4.1.3 Summary of Experimental Results -- 8.4.2 Interface Fault Injection Testing -- 8.5 Discussion -- 8.6 Conclusion -- References -- 9. ARIFS Methodology: A Case Study -- 9.1 Introduction -- 9.2 Background. 9.3 The ARIFS Methodology: What is Reusable Component? -- 9.3.1 Static Classification of Reusable Components -- 9.3.2 Retrieval Process -- 9.3.3 Reusing Verification Efforts -- 9.4 Applying the Methodology: A Case Study -- 9.4.1 Starting Point -- 9.4.2 Obtaining the Sender -- 9.4.3 Obtaining the Receiver -- 9.4.4 Obtaining the Whole System -- 9.4.5 Reusing Verification Information -- 9.5 Is it Worth Reusing these Incomplete Models? -- 9.6 Related Work -- 9.7 Summary and Future Work -- References -- 10. REBOUND: A Framework for Automated Component Adaptation -- 10.1 Introduction -- 10.2 Architecture Specifications -- 10.2.1 Component Specifications -- 10.2.2 Connector Specifications -- 10.2.3 Interface Binding -- 10.2.4 Architecture Specification -- 10.3 Adaptation Tactics -- 10.3.1 Type Adaptation -- 10.3.2 Interface Adaptation -- 10.3.2.1 Type Conversion -- 10.3.2.2 Generalized Wrapper Specifications -- 10.3.3 Behavior Adaptation -- 10.3.4 Tactic Composition -- 10.3.5 Tactic Selection -- 10.4 Case Study: KWIC -- 10.4.1 Architecture Synthesis -- 10.4.2 Event-Driven Implementation -- 10.5 Discussion -- 10.6 Related Work -- 10.7 Conclusion -- Acknowledgements -- References -- 11. A Web-enabled Component-based Architecture for Legacy Applications -- 11.1 Component Software Technology and Web Technology -- 11.2 Characteristics of Engineering Computing Portal and Common Business Requirements of WECBA for Legacy Applications -- 11.2.1 Characteristics of Engineering Computing Portal -- 11.2.2 Common Business Requirements of WECBA for Legacy Applications -- 11.3 Web-Enabled Component-Based Architecture (WECBA) -- 11.4 Technology Choices and System Implementation of the WECBA -- 11.4.1 Lightweight High Performance CORBA -- 11.4.2 Implementing Broker and Computation Manager based on Lightweight High Performance CORBA. 11.4.3 Interactions Between Web Server, Integration Broker, and Computation Manager.