Component composition

This paper depicts a novel approach to document components in a uniform and abstract way. Every use of component is expressed with a specific type of message sequence chart (MSG), using a limited set of standard primitives with predefined semantics. These primitives are mapped on the actual API of the component(s). This documentation is used to find compatible components and to detect conflicts when composing components. Because of the standard set of primitives, components from different sources can be matched and developers do not have to rely on the concrete API. The behavioural flavour of MSCs is suited to document, as a set of usage scenarios, how a component expects to interact with other components when configured in an application. This complements existing documentation techniques