Component Model 

Definition

By dividing software projects into components, you can organize them right from the start into comprehensible and reusable units. Components can use other components in a well-defined and controlled manner, can encapsulate child components, and can publish their functions in a set of public interfaces called public parts. These features are applied in the component model.

The component model consists of the following elements:

●     Software components (SCs) are delivery and installation units; they group development components without overlapping.  For more information, see Software Components.

○     Products – these are the overlapping selections of software components. One software component can be part of several products.

●     Development components (DCs) are development and build units; they group development objects without overlapping. For more information, see Development Components (DCs).

○     Development objects created in the context of development components; they are stored as versioned files in the Design Time Repository (DTR).

Use

You must work with components to be able to use all types of development projects including Web Dynpro. With NWDI you can:

●     Create development components (DCs) of all existing types.

○     Explicitly define dependencies between components

○     Nest development components

○     Define public parts

○     Build on DC level

●     Handle software components (SCs)

Integration

The component model is independent of the technology used and can easily be integrated into different languages and platforms. In contrast to other techniques such as COM/DCOM, it is based on dividing the sources of a software into components, which makes it platform-independent.

NWDI and SAP NetWeaver Developer Studio offer unrestricted support to the development with components.

For more information about the Developer Studio, see Getting Involved.