Eiffel: the language
Architectural mismatch or why it's hard to build systems out of existing parts
Proceedings of the 17th international conference on Software engineering
Protocol specifications and component adaptors
ACM Transactions on Programming Languages and Systems (TOPLAS)
A formal basis for architectural connection
ACM Transactions on Software Engineering and Methodology (TOSEM)
Adding more “DL” to IDL: towards more knowledgeable component inter-operability
Proceedings of the 21st international conference on Software engineering
Object-Oriented Software Construction
Object-Oriented Software Construction
Behavior Protocols for Software Components
IEEE Transactions on Software Engineering
Formal Specification and Prototyping of CORBA Systems
ECOOP '99 Proceedings of the 13th European Conference on Object-Oriented Programming
Techniques for Embedding Executable Specifications in Software Component Interfaces
ICCBSS '03 Proceedings of the Second International Conference on COTS-Based Software Systems
A Comprehensive Interface Definition Framework for Software Components
APSEC '98 Proceedings of the Fifth Asia Pacific Software Engineering Conference
iContract - The Java(tm) Design by Contract(tm) Tool
TOOLS '98 Proceedings of the Technology of Object-Oriented Languages and Systems
Ensuring Compatible Interactions within Component-based Software Systems
APSEC '03 Proceedings of the Tenth Asia-Pacific Software Engineering Conference Software Engineering Conference
Runtime Validation of Behavioural Contracts for Component Software
QSIC '05 Proceedings of the Fifth International Conference on Quality Software
Supporting high interoperability of components by adopting an agent-based approach
Software Quality Control
Pattern-Based specification and validation of web services interaction properties
ICSOC'05 Proceedings of the Third international conference on Service-Oriented Computing
Hi-index | 0.00 |
A vital issue in the correct use of commercial-off-the-shelf (COTS) components is the proper understanding of their functionality, quality attributes and ways of operation. Traditionally, COTS component vendors provide some of this information in accompanying documentation. However, the documentation is often informal and likely contains ambiguous and inconsistent statements. Even equipped with interface descriptions clearly defining the basic aspects of component use, such as operation signatures and operating platforms, this documentation does not provide a mathematically sound means for addressing the behavioural interoperability issues in component-based system design. In this paper, we propose a formal but user-friendly component specification approach which augments commercial IDLs with the capability of capturing component interoperability requirements. This approach uses unambiguous temporal operators to define sequencing and concurrency constraints between component operation invocations. Accordingly, it enables precise specifications of how a component provides its services and the correct way in which its services should be used.