Writers' First Review Draft (2V04)
Term (2V05)
Component (2V06)
Origin/Source for Inclusion of the Term (2V07)
OMB Enterprise Architecture Assessment Framework Version 1.5 SCBA v2 (2V08)
OMB Context Definition (2V09)
Reference/URL OMB Context Definition (2V0A)
Business Definition (2V0B)
One of the individual entities contributing to a whole (2V0C)
Reference/URL for Business Definition (2V0D)
Available from http://www.answers.com/component&r=67; Accessed June 22 2005 (2V0E)
Technical Definition (2V0F)
"A component is a reusable program building block that can be combined with other components across a distributed network to form an application." (2V0G)
Reference/URL Technical Definition (2V0H)
A C O N I T E T E C H N O L O G Y e-business Technology Fundamentals www.aconite.co.uk (2V0I)
Context Definition 1 (2V0J)
A small binary object or program that performs a specific function and is designed in such a way to easily operate with other components and applications. The term is sometimes used interchangeably with applet. (2V0K)
Reference/URL Context Definition 1 (2V0L)
Available from http://www.webopedia.com/TERM/c/component.html; Accessed June 22 2005 (2V0M)
Context Definition 2 (2V0N)
A self-contained business process or service with pre-determined functionality exposed through a business or technology interface. Independently deployable unit of software that exposes its functionality through a set of services accessed via well-defined interfaces. A component is based on a component standard, is described by a specification, and has an implementation. Components can be assembled to create applications or larger-grained components. (2V0O)
Reference/URL for Context Definition 2 (2V0P)
OMB Enterprise Architecture Assessment Framework Version 1.5 SCBA v2 (2V0Q)
Context Definition 3 (2V0R)
(General) any software (sub)system that can be factored out and has a potentially standardizable or reusable exposed interface. Components in a SW 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. For example, viewing an architecture at one level of abstraction, object services may be identified as components. Viewing the same architecture at a more detailed level, a given service may be implemented by several distinct software modules, which may be individually identified as components. (2V0S)
Reference/URL for Context Definition 3 (2V0T)
Craig Thompson and Frank Manola "Component Software Glossary"; Available from http://www.objs.com/survey/ComponentwareGlossary.htm#Component; Accessed June 22 2005 (2V0U)
See Also Related Terms (2V0V)
building block, constituent, element, factor, ingredient, integrant, part. See part/whole. (2V0W)