Component (UML)
A component in the Unified Modeling Language "represents a modular part of a system, that encapsulates its content and whose manifestation is replaceable within its environment. A component defines its behavior in terms of provided and required interfaces".
A component may be replaced by another if and only if their provided and required interfaces are identical. This idea is the underpinning for the plug-and-play capability of component-based systems and promotes software reuse.
As can be seen from the above definition, UML places no restriction on the granularity of a component. Thus, a component may be as small as a figures-to-words converter, or as large as an entire document management system.
Larger pieces of a system's functionality may be assembled by reusing components as parts in an encompassing component or assembly of components, and wiring together their required and provided interfaces." Such assemblies are illustrated by means of component diagrams.
Related terms
Component
Component may refer to:
Software
Component-based software engineering
Component-based software engineering (CBSE) (also known as component-based development (CBD)) is a branch of software engineering that emphasizes the separation of concerns in respect of the wide-ranging functionality available throughout a given software system. It is a reuse-based approach to defining, implementing and composing loosely coupled independent components into systems. This practice aims to bring about an equally wide-ranging degree of benefits in both the short-term and the long-term for the software itself and for organizations that sponsor such software.
Software engineering practitioners regard components as part of the starting platform for service-orientation. Components play this role, for example, in web services, and more recently, in service-oriented architectures (SOA), whereby a component is converted by the web service into a service and subsequently inherits further characteristics beyond that of an ordinary component.
Components can produce or consume events and can be used for event-driven architectures (EDA).
Component (thermodynamics)
In thermodynamics, a component is a chemically-independent constituent of a system. The number of components represents the minimum number of independent species necessary to define the composition of all phases of the system.
Calculating the number of components in a system is necessary, for example, when applying Gibbs' phase rule in determination of the number of degrees of freedom of a system.
The number of components is equal to the number of distinct chemical species (constituents), minus the number of chemical reactions between them, minus the number of any constraints (like charge neutrality or balance of molar quantities).
Examples
Water
A system that contains water in the liquid state also contains hydronium cations and hydroxyl anions according to the reaction:
The number of components in such a system is
CaCO3 - CaO - CO2 system
This is an example of a system with several phases, which at ordinary temperatures are two solids and a gas. There are three chemical species (CaCO3, CaO and CO2) and one reaction CaCO3
CaO + CO2. The number of components is then 3 - 1 = 2.
UML
UML may refer to:
Unified Modeling Language
The Unified Modeling Language (UML) is a general-purpose, developmental, modeling language in the field of software engineering, that is intended to provide a standard way to visualize the design of a system.
UML was originally motivated by the desire to standardize the disparate notational systems and approaches to software design developed by Grady Booch, Ivar Jacobson and James Rumbaugh at Rational Software in 1994–95, with further development led by them through 1996.
In 1997 UML was adopted as a standard by the Object Management Group (OMG), and has been managed by this organization ever since. In 2005 the Unified Modeling Language was also published by the International Organization for Standardization (ISO) as an approved ISO standard. Since then it has been periodically revised to cover the latest revision of UML.
Though well-known and widely used in education and academic papers, as of 2013 UML is little-used in industry, and most such use is informal and ad hoc.
Podcasts:
