Reusable objects that you can place on a page or template to perform a certain task. For example, an ImageLink component uses a GIF or JPG image as an anchor for an HTML hypertext link. The behavior and appearance of components are determined by their properties. See the Component Reference for definitions of each component.
component is a locus of computation or data storage. Component is one of our fundamental architectural types. Connectors are usually represented as boxes or other compact shapes in our environments.
a piece of a software system, for example, module, module user interface, model, pre/post-processor, or framework user interface.
A unit of work that encapsulates business logic. It publishes an interface available to all foreign applications or components enabling easy integration.
A self-contained, re-usable object, in programming or architecture
A special kind of (persistent) Adapter that works with a twisted.python.components.Componentized. See also Interfaces and Adapters.
A component is a replaceable, tangible part of a system that realizes of a set of interfaces, including software code, scripts, or command files, run-time objects, documents, databases, etc. The new UML 2.0 notation for a component is a simple box with either the component text stereotype or the graphical stereotype depicting the old notation (not supported in this release of Poseidon).
An object adhering to a component architecture. Component technology is a blend of object-oriented and Internet technologies. In a component-based architecture, the components of a system have generic interfaces through which they advertise their functionalities, enabling the dynamic loading of the components. See architecture and interoperability.
An encapsulated software object, described by its class interface, that may be reused as a whole in a software system. The dual of a framework.
A piece of a distributed application. Often a component is the implementation of a tier. However, if an application includes two different graphical interfaces then each interface is a separate component of the presentation tier.
(in the context of the DoD Enterprise Architecture Service Component Reference Model). A self contained business process or service with predetermined functionality that may be exposed through a business or technology interface. (Federal Enterprise Architecture SRM v1.0, 12 June 2003)
A modular unit of functionality accessed through one or more interfaces.
Any software (sub)system that can be factored out and has a potentially standardizable or reusable exposed interface. Components in a software architecture can be identified at different levels of abstraction, and the components identified at these different levels may not be in one-to-one correspondence.(issues with components) least common denominator component interfaces so that resulting implementations do not meet anyone's needs portmanteau standards (that become increasingly complex, overloaded, heavyweight) that include features anyone wanted but few implement or include but not by reference other standards and are not further decomposable. interface versus implementation factoring and composition. implementations that expose additional interfaces beyond standard ones (special features) that some users want or find useful and take advantage of - use of these features means the resulting system cannot be ported (as easily), a pay-me-now or pay-me-later tradeoff where the more expedient possibly more expensive pay-me-later usually wins. APIs with many, many user accessible interfaces
a general category of items that can appear on a user interface. These items can include containers, buttons, labels, text input fields, check boxes, listboxes, lines, etc.
A physical and replaceable part of a system that conforms to and provides a realization of a set of interfaces.
A reusable object or program that performs a specific function and is designed to work with other components and applications.
The fundamental unit within a system. A component encapsulates behavior and structure. Modules and models can represent a single component, or a component with many subcomponents.
An object of the WOComponent class that represents a web page or a reusable portion of one.
A unit of code that provides a set of services through well-defined interfaces and is specifically designed and packaged to be reusable. A component acts like a "black box" that hides or encapsulates the details of how the services are actually implemented. Components can be mixed and matched to form larger systems. "For most of the industry, components are synonymous with encapsulated binary objects, most notably Java Beans and ActiveX controls. Support for inheritance and polymorphism is not critical for the definition of components." 5
Reusable piece of code or reusable subnet
servlet, Enterprise JavaBean (EJB), or JavaServer Page (JSP).
A basic part of a system or program. A chunk of reusable code.
An implementation of a set of interfaces identified by a CLSID
an implementation in final form, modulo bound labels, that provides an interface for third-party composition and is a unit of independent deployment
A subclass of java.awt.component or, by extension, the interface element implemented by that subclass. Most components--for example, menus and toolbars--enable a user to control an application.
An object type in the AWT for visible user interface elements (such as a button, list box, or scrollbar).
A unit of application logic that delivers a set of specified services that can be accessed only through a published interface or interface contract.
Software that packages the client or server implementation of a service and can provide the realization of a set of interfaces. A component consists of software code (source, binary or executable) or other equivalents such as scripts or command files.
A component is a software object, meant to interact with other components, encapsulating certain functionality or a set of functionalities. A component has a clearly defined interface and conforms to a prescribed behavior common to all components within an architecture. [CCA T&D] A component is an abstract unit of software instructions and internal state that provides a transformation of data via its interface. [Fielding] A component is a unit of architecture with defined boundaries.
A module or library containing one or more POE sessions. Components can be divided into three types, based on their interfaces: servlets, libraries, and hybrids. "Servlet" components set up stand-alone sessions that interact with the rest of the program through events. Client sessions post requests at servelets, and the servlets post responses back. Library components present a more traditional call and callback interface. Programs call functions within the component that in turn interact with its underlying session. Events occurring within the session are passed back to the program through callbacks. It's possible to completely hide POE this way. Hybrid components provide some mix of the other two interfaces. To date, nobody has written a hybrid component. see: callback, nfa session, session
An executable software module with identity and a well-defined interface. Contrast: component [OMA].
A component is traditionally a reusable, self-contained set of methods, properties, and interfaces that can be added to an application to extend its functionality. A component may or may not have a visual interface. For example, a command button on a window is a component.
An item such as a clickable button or scrollbar that can be manipulated by a user in a program.
An object that encapsulates both data and code, and provides a well-specified set of publicly available services.
Any of the GUI primitives implemented in the java.awt package as subclasses of Component. The classes Button, Choice, and TextField (among many others) are components.
(1) In the context of graphical user interfaces, a component is an object within the interface. It will usually have some visual apperance, and it will usually be something with which the user can interact (e.g. using the mouse). (2) In software engineering in general, components are replaceable units within an implementation of a system (e.g. run-time objects), implementing certain interfaces.
Any hardware or software product that is part of or attached to a desktop system or server. For example, a modem, a printer, a network interface card, a spreadsheet program, and an operating system could all be considered components.
A subclass of java.awt.component or, by extension, the interface element implemented by that subclass. See also control, object, Swing classes.
The atomic unit of Component Oriented Programming. It made up of an interface which defines the service it provides (the API) and one or more implementations of that interface. The implementations can also provide lifecycle methods (configuration, start, stop, etc.)
A piece of code or, by extension, the interface element implemented by that code. See also Swing classes.
Restlet managing a set of Clients, Servers and other Restlets. "A component is an abstract unit of software instructions and internal state that provides a transformation of data via its interface." Roy T. Fielding Component managing a set of VirtualHosts and Applications. Applications are expected to be directly attached to VirtualHosts. Components are also exposing a number of services in order to control several operational features in a portable way, like access log and status setting.
A unit of functionality that may be amortized across multiple implementations. A software object that exposes one or more interfaces and that implements logic.