“We consider C the set of components (…) and the set of links L. A link is a list composed of an event and a list of methods. (…) An assembly consists of a subset of C and L. A container component implements an API to control programmatically this assembly. It implements consequently the addition and removal of elements in C and L.”

“We believe that a design environment needs to provide various representations and design tools for programmers to work on an application. (…) A multi-designer approach allows modifying and then adapting applications using different design views.”

“Clemens Szyperski in (Component Software - Beyond OOP) : A software component is a unit of composition with contractually specified interfaces and explicit context dependencies only. A software component can be deployed independently and is subject to composition by third parties. (…) Wcomp component model is inspired from the JavaBeans model. But it has been slightly modified. A component in Wcomp is also an instance of a class. But it is not necessarily serializable. A component has a unique name. A component has an interface that is composed of a set of events and a set of methods. (…) Events are characterized by their unique name and methods as well. They are gathered in the term of 'port'.”

  • defintions.txt
  • Last modified: 2007/06/08 12:09
  • by lavirotte