Designing object-oriented software
Designing object-oriented software
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
UML components: a simple process for specifying component-based software
UML components: a simple process for specifying component-based software
Making Components Contract Aware
Computer
An Architecture and a Process for Implementing Distributed Collaborations
EDOC '02 Proceedings of the 6th International Enterprise Distributed Object Computing Conference
ICSE '93 Selected papers from the Workshop on Studies of Software Design
System Design by Composing Structures of Interacting Objects
ECOOP '92 Proceedings of the European Conference on Object-Oriented Programming
COORDINATION '00 Proceedings of the 4th International Conference on Coordination Languages and Models
Acme: an architecture description interchange language
CASCON '97 Proceedings of the 1997 conference of the Centre for Advanced Studies on Collaborative research
A formal approach to software architecture
A formal approach to software architecture
Implementing a data distribution variant with a metamodel, some models and a transformation
DAIS'08 Proceedings of the 8th IFIP WG 6.1 international conference on Distributed applications and interoperable systems
Two ways of implementing software connections among distributed components
OTM'05 Proceedings of the 2005 OTM Confederated international conference on On the Move to Meaningful Internet Systems: CoopIS, COA, and ODBASE - Volume Part II
| Hi-index | 0.00 |
One of the touchstones of Object-Oriented Design is that the management of complexity is seldom located within any single object. It should instead be an emerging property of the collaborations within a society of objects, each one of these being as simple as possible. These collaborations can easily be specified using UML collaboration diagrams. We propose to reify UML collaborations as interaction components. This allows the easy handling and reusing of interaction abstractions among components at both specification and implementation levels.This paper focuses on the specification of these components. We propose criteria to define the type and the "frontier" of an interaction abstraction. We present a UML collaboration specification methodology that deals with the constraints of component specification.