Component model

from Wikipedia, the free encyclopedia

In software engineering , component models are understood to be concrete manifestations of the paradigm of component-based development . The following definition can be found in Gruhn & Thiel:

"A component model defines a framework for the development and execution of components , which places structural requirements in terms of linking and composition options as well as behavior-oriented requirements in terms of collaboration possibilities for the components. In addition, an infrastructure is offered by a component model that supports frequently required mechanisms such as distribution , persistence , messaging , security and versioning can be implemented. "

A component model specifies not only the exact shape and properties of the components that correspond to the model, but also how components speak to one another ( interaction standard ) and can be connected ( composition standard ). A component model can also have implementations from different manufacturers .

Concrete implementation

The various component models differ in terms of performance features, supported operating systems and the options for creating and connecting components.

The following component models are widely used:

For example, the Corba component model specified by the Object Management Group is only a standard, not an implementation. For this reason there are implementations of the Corba architecture from different manufacturers.

See also


  1. Volker Gruhn, Andreas Thiel: component models. DCOM, Javabeans, Enterprise Java Beans, CORBA Addison-Wesley, 2000, ISBN 382731724X , page 293
  • William T. Council, George T. Heineman: Component-Based Software Engineering . Addison-Wesley, 2001, ISBN 0-201-70485-4
  • Clemens Szyperski: Component Software . Addison-Wesley, 1998, ISBN 0-201-17888-5
  • Bertrand Meyer. The grand challenge of trusted components. In ICSE, pages 660-667, 2003