Communicating sequential processes
Communicating sequential processes
Object structure in the Emerald system
OOPLSA '86 Conference proceedings on Object-oriented programming systems, languages and applications
A semantics of multiple inheritance
Information and Computation - Semantics of Data Types
Theoretical aspects of object-oriented programming: types, semantics, and language design
Theoretical aspects of object-oriented programming: types, semantics, and language design
A behavioral notion of subtyping
ACM Transactions on Programming Languages and Systems (TOPLAS)
Specification matching of software components
SIGSOFT '95 Proceedings of the 3rd ACM SIGSOFT symposium on Foundations of software engineering
Component software: beyond object-oriented programming
Component software: beyond object-oriented programming
Objects, components, and frameworks with UML: the catalysis approach
Objects, components, and frameworks with UML: the catalysis approach
The object constraint language: precise modeling with UML
The object constraint language: precise modeling with UML
A Protocol Based Approach to Specifying Interoperability between Objects
TOOLS '98 Proceedings of the Technology of Object-Oriented Languages and Systems
Component specification model for the web services
ICCSA'06 Proceedings of the 2006 international conference on Computational Science and Its Applications - Volume Part IV
A new formal test method for networked software integration testing
ICCSA'10 Proceedings of the 2010 international conference on Computational Science and Its Applications - Volume Part II
| Hi-index | 0.00 |
Component-based development (CBD) has gained in popularity in recent years due to its promise of building applications from reusable and plug-and-playable software components. An ultimate goal of CBD is making plug-and-playable software development not only feasible, but also easy. In order to achieve this goal, techniques for clearly specifying functionality of components and for determining the degree to which two components can interoperate are needed. In this paper, we briefly review the ICM (Interoperable Component Model), and enhance the model by adding a formalism and providing a testing framework based on the formal specification. Each component is accompanied with an interface that describes the component's type and behavior. The component interactions are specified in message protocols. With the specification model, we will define the behavior type conformance rules on components.