Software evolution in componentware using requirements/assurances contracts
Proceedings of the 22nd international conference on Software engineering
Synthesizing State-Based Object Systems from LSC Specifications
CIAA '00 Revised Papers from the 5th International Conference on Implementation and Application of Automata
Describing interactions between MSC components: the MSC connectors
Computer Networks: The International Journal of Computer and Telecommunications Networking - ITU-T system design languages (SDL)
ACM Transactions on Software Engineering and Methodology (TOSEM)
A Rich Services Approach to CoCoME
The Common Component Modeling Example
Capturing overlapping, triggered, and preemptive collaborations using MSCs
FASE'03 Proceedings of the 6th international conference on Fundamental approaches to software engineering
MSC connectors - the philosopher's stone
SAM'02 Proceedings of the 3rd international conference on Telecommunications and beyond: the broader applicability of SDL and MSC
Automatic generation of compatible interfaces from partitioned UML activities
SDL'09 Proceedings of the 14th international SDL conference on Design for motes and mobiles
Component synthesis from service specifications
SMTT'03 Proceedings of the 2003 international conference on Scenarios: models, Transformations and Tools
| Hi-index | 0.00 |
We introduce the formal notion of an interaction interface. Its purpose is to specify formally the interaction between two or more components that co-operate as subsystems of a distributed system. We suggest the use of interaction interfaces for the description not of the behaviour of a single component in isolation but of the interface, the co-operation, between two or more components that are interacting within a distributed system. Typical examples are the interaction between an embedded system and its environment or the interaction between a sender and a receiver in a communication protocol. An interaction interface can be formally described by predicates characterising sets of interaction histories. We understand the specification of interaction histories as a typical step in system development that prepares the decomposition of a system into interacting subcomponents. After fixing the distribution structure of the system, an interaction interface is worked out that describes how the introduced subcomponents interact. In a successive development step we systematically derive the individual component specifications from the interface description. We show how such an interaction interface can be decomposed systematically into component specifications.