C

CEE:   Component execution environment.

Closed layer:   The term closed layer indicates a "separation layer" or "hiding layer."

Closured dependency list:   A versioned dependency list that includes all indirect dependencies.

Component:   A self-contained piece of software that can be independently deployed and plugged into an environment that provides a compatible socket. It has well-defined and network-addressable run-time interfaces, and it can cooperate out of the box with other components.

Component-based development:   A software development approach where all aspects and phases of the development lifecycle, including requirements analysis, architecture, design, construction, testing, deployment, the supporting technical infrastructure, and the project management are based on components.

Component diagram:   A graphical representation of the components in a system, implicitly representing the dependencies among them.

Component execution environment:    The run-time technical infrastructure, services, and facilities required to provide the appropriate separation layer for distributed components and to enable business components to collaborate. A major objective of the component execution environment is to hide low-level technology issues from the functional developer.

Component implementation technology:    A commercially-available component middleware technology and its associated connectivity capabilities. Examples are an implementation of the CORBA Components specification, EJB (Enterprise Java Beans), Microsoft’s COM and DCOM, MOM (Message-Oriented Middleware) products, and transaction management products such as BEA’s M3.

Component instance:   The run-time instantiation of a distributed component (DC).

Component-level dependency list:    A dependency list used to identify only the required components, and no other software artifacts.

Consistency set:   A closured dependency list whose components are known to work with each other and thus constitute a consistent set.

CORBA:    Common Object Request Broker Architecture.

CORBA  IOR:   CORBA Interoperable Object Reference—the name given to a network-addressable reference as defined by CORBA.

COTS:   Commercial Off-The-Shelf. For example, "COTS software" is software available on the market and maintained by the supplier.

COSM:   COSM is the new, trademarked name for what was previously known as Business Component Approach.  COSM stands for Component-Oriented Software Manufacturing.

CSL:   Component specification language.