A notion in object-oriented programming where “components” of a program are completely generic. Instead of having a specialised set of methods and fields they have generic methods through which the component can advertise the functionality it supports to the system into which it is loaded. This enables completely dynamic loading of objects. JavaBeans is an example of a component architecture.
See also design pattern.
- Component based development
programming (CBD) The creation, integration, and re-use of components of program code, each of which has a common interface for use by multiple systems. (1999-08-23)
[kuh m-poh-nuh nt, kom-] /kəmˈpoʊ nənt, kɒm-/ noun 1. a constituent part; element; ingredient. 2. a part of a mechanical or electrical system: hi-fi components. 3. Physics. the projection of a vector quantity, as force or velocity, along an axis. 4. Physical Chemistry. one of the set of the minimum number of chemical constituents by […]
noun, Linguistics. 1. the analysis of a set of related linguistic items, especially word meanings, into combinations of features in terms of which each item may be compared with every other, as in the analysis of man into the semantic features “male,” “mature,” and “human,” woman into “female,” “mature,” and “human,” girl into “female,” “immature,” […]
- Component integration laboratories
project (CIL) An effort to create a common framework for interoperability between application programs on desktop platforms, formed by Apple Computer, Inc., IBM, Novell, Oracle, Taligent, WordPerfect and Xerox. [When? What happened?] (1994-10-24)