scispace - formally typeset
Search or ask a question
Topic

Common Component Architecture

About: Common Component Architecture is a research topic. Over the lifetime, 1068 publications have been published within this topic receiving 18209 citations.


Papers
More filters
Journal ArticleDOI
TL;DR: The Palladio component model (PCM) is used to specify component-based software architectures in a parametric way to enable the prediction of extra-functional properties, and the resulting prediction accuracy is sufficient to support the evaluation of architectural design decisions.

749 citations

Journal ArticleDOI
TL;DR: In this article the authors define a general model of sofware contracts and show how existing mechanisms could be used to turn traditional components into contract-aware ones.
Abstract: Components have long promised to encapsulate data and programs into a box that operates predictably without requiring that users know the specifics of how it does so. Many advocates have predicted that components will bring about widespread software reuse, spawning a market for components usable with such mainstream software buses as the Common Object Request Broker Architecture (CORBA) and the Distributed Component Object Model (DCOM). In the Windows world, at least, this prediction is becoming a reality. Yet recent reports indicate mixed results when using and reusing components in mission-critical settings. Such results raise disturbing questions. How can you trust a component? What if the component behaves unexpectedly, either because it is faulty or simply because you misused it? Before we can trust a component in mission-critical applications, we must be able to determine, reliably and in advance, how it will behave. In this article the authors define a general model of sofware contracts and show how existing mechanisms could be used to turn traditional components into contract-aware ones.

617 citations

Book
01 Jan 2000
TL;DR: This chapter discusses UML Modeling Techniques, which aims to extend UML with Stereotypes, and its application to Component Systems, a system of Components and System Architectures that was developed in the 1990s and still exists today.
Abstract: Foreword. 1. Component Systems. Component Goals. Component Principles. Component Forms. Example: Microsoft Word. What a Component Isn't. Component and System Architectures. System Architectures. Component Architectures. Specifying Contracts. Usage Contracts. Realization Contracts. Interfaces versus Component Specifications. Model Levels. Summary. 2. The Development Process. Workflows. The Impact of the Management Process. The Evolution of Software Processes. Accommodating Change. Workflow Artifacts. The Specification Workflow. Component Identification. Component Interaction. Component Specification. Summary. 3. Applying UML. Why Do We Need This Chapter at All? Tools. Extending UML with Stereotypes. Precision, Accuracy, and Completeness. UML Modeling Techniques. Business Concept Model. Use Case Model. Use Case Diagrams. Use Case Descriptions. Use Case Instances. Inclusions, Extensions, and Variations. Business Type Model. Types. Structured Data Types. Interface Type. Invariants. Interface Specification. Interface Specification Package. Information Model. Operation Specification. Component Specification. Component Object Interaction. Specification, Not Implementation. Component Architectures. Summary. 4. Requirements Definition. Business Processes. Business Concept Model. System Envisioning. Use Cases. Actors and Roles. Use Case Identification. Use Case Descriptions. Quality of Service. Summary. 5. Component Identification. Identifying Interfaces. Identifying System Interfaces and Operations. Make a Reservation. Take Up Reservation. Identifying Business Interfaces. Create the Business Type Model. Refine the Business Type Model. Define Business Rules. Identify Core Types. Create Business Interfaces and Assign Responsibilities. Allocating Responsibility for Associations. Creating Initial Interface Specifications. Existing Interfaces and Systems. Component Specification Architecture. System Component Specifications. Business Component Specifications. An Initial Architecture. Summary. 6. Component Interaction. Discovering Business Operations. Some Simple Interactions. Breaking Dependencies. Maintaining Referential Integrity. Component Object Architecture. Controlling Intercomponent References. Completing the Picture. Refining the Interfaces. Factoring Interfaces and Operations. Summary. 7. Component Specification. Specifying Interfaces. Operation Specification. Interface Information Models. Pre- and Postconditions. A Systematic Process. From Business Type Model to Interface Information Model. Invariants. Snapshots. Exactly What Does a Postcondition Guarantee? Specifying System Interfaces. Business Rule Location. Specifying Components. Offered and Used Interfaces. Component Interaction Constraints. Inter-Interface Constraints. Factoring Interfaces. Summary. 8. Provisioning and Assembly. What Do We Mean by Target Technology? Components Realize Component Specifications. Realization Mappings and Restrictions. Operation Parameters. Error and Exception Handling Mechanisms. Interface Inheritance and Interface Support. Operation Sequence. Interface Properties. Object Creation. Raising Events. Application Architecture Correspondence. Business Components. Subcomponents. Integrating Existing Systems. Purchasing Components. Assembly. Summary. A Final Thought. References. Index. 0201708515T04062001

512 citations

Proceedings ArticleDOI
03 Aug 1999
TL;DR: This research stems from the growing recognition that the scientific community needs to better manage the complexity of multidisciplinary simulations and better address scalable performance issues on parallel and distributed architectures.
Abstract: Describes work in progress to develop a standard for interoperability among high-performance scientific components. This research stems from the growing recognition that the scientific community needs to better manage the complexity of multidisciplinary simulations and better address scalable performance issues on parallel and distributed architectures. The driving force for this is the need for fast connections among components that perform numerically intensive work and for parallel collective interactions among components that use multiple processes or threads. This paper focuses on the areas we believe are most crucial in this context, namely an interface definition language that supports scientific abstractions for specifying component interfaces and a port connection model for specifying component interactions.

433 citations

Journal ArticleDOI
TL;DR: Using the definitions of bounded component behavior and protocol conformance relation, the designer can verify the adherence of a component's implementation to its specification at runtime, while the correctness of refining the specification can be verified at design time.
Abstract: In this paper, we propose a means to enhance an architecture description language with a description of component behavior. A notation used for this purpose should be able to express the "interplay" on the component's interfaces and reflect step-by-step refinement of the component's specification during its design. In addition, the notation should be easy to comprehend and allow for formal reasoning about the correctness of the specification refinement and also about the correctness of an implementation in terms of whether it adheres to the specification. Targeting all these requirements together, the paper proposes employing behavior protocols which are based on a notation similar to regular expressions. As proof of the concept, the behavior protocols are used in the SOFA architecture description language at three levels: interface, frame, and architecture. Key achievements of this paper include the definitions of bounded component behavior and protocol conformance relation. Using these concepts, the designer can verify the adherence of a component's implementation to its specification at runtime, while the correctness of refining the specification can be verified at design time.

395 citations


Network Information
Related Topics (5)
Software development
73.8K papers, 1.4M citations
87% related
Software system
50.7K papers, 935K citations
87% related
Software construction
36.2K papers, 743.8K citations
86% related
Web service
57.6K papers, 989K citations
81% related
Data structure
28.1K papers, 608.6K citations
80% related
Performance
Metrics
No. of papers in the topic in previous years
YearPapers
20231
20221
20181
20171
201610
201519