UML Component Diagram. Design Elements

"A credit card is a payment card issued to users as a system of payment. It allows the cardholder to pay for goods and services based on the holder's promise to pay for them. The issuer of the card creates a revolving account and grants a line of credit to the consumer (or the user) from which the user can borrow money for payment to a merchant or as a cash advance to the user." [Credit card. Wikipedia]
The UML component diagram example "Credit card agency" was created using the ConceptDraw PRO diagramming and vector drawing software extended with the Rapid UML solution from the Software Development area of ConceptDraw Solution Park.

The vector stencils library "UML component diagrams" contains 36 symbols for the ConceptDraw PRO diagramming and vector drawing software.
"In the Unified Modeling Language, a component diagram depicts how components are wired together to form larger components and or software systems. They are used to illustrate the structure of arbitrarily complex systems. ...
Symbols.
This may have a visual stereotype in the top right of the rectangle of a small rectangle with two even smaller rectangles jutting out on the left.
The lollipop, a small circle on a stick represents an implemented or provided interface. The socket symbol is a semicircle on a stick that can fit around the lollipop. This socket is a dependency or needed interface." [Component diagram. Wikipedia]
The example "Design elements - UML component diagrams" is included in the Rapid UML solution from the Software Development area of ConceptDraw Solution Park.

The vector stencils library "Bank UML component diagram" contains 13 shapes for drawing UML component diagrams.
Use it for object-oriented modeling of your bank information system.
"A component is something required to execute a stereotype function. Examples of stereotypes in components include executables, documents, database tables, files, and library files.
Components are wired together by using an assembly connector to connect the required interface of one component with the provided interface of another component. This illustrates the service consumer - service provider relationship between the two components. ...
When using a component diagram to show the internal structure of a component, the provided and required interfaces of the encompassing component can delegate to the corresponding interfaces of the contained components. ...
Symbols.
This may have a visual stereotype in the top right of the rectangle of a small rectangle with two even smaller rectangles jutting out on the left.
The lollipop, a small circle on a stick represents an implemented or provided interface. The socket symbol is a semicircle on a stick that can fit around the lollipop. This socket is a dependency or needed interface." [Component diagram. Wikipedia]
This example of UML component diagram symbols for the ConceptDraw PRO diagramming and vector drawing software is included in the ATM UML Diagrams solution from the Software Development area of ConceptDraw Solution Park.

"Component diagram shows components, provided and required interfaces, ports, and relationships between them. This type of diagrams is used in Component-Based Development (CBD) to describe systems with Service-Oriented Architecture (SOA).
Component-based development is based on assumptions that previously constructed components could be reused and that components could be replaced by some other "equivalent" or "conformant" components, if needed.
The artifacts that implement component are intended to be capable of being deployed and re-deployed independently, for instance to update an existing system.
Components in UML could represent:
(1) logical components (e.g., business components, process components), and
(2) physical components (e.g., CORBA components, EJB components, COM+ and .NET components, WSDL components, etc.),
along with the artifacts that implement them and the nodes on which they are deployed and executed. It is anticipated that profiles based around components will be developed for specific component technologies and associated hardware and software environments." [uml-diagrams.org/ component-diagrams.html]
The template "UML component diagram" for the ConceptDraw PRO diagramming and vector drawing software is included in the Rapid UML solution from the Software Development area of ConceptDraw Solution Park.
www.conceptdraw.com/ solution-park/ software-uml

"RT-middleware (Robotics Technology Middleware) is a common platform standards for Robots based on the distributed object technology. RT-middleware supports the construction of various networked robotic systems by the integration of various network enabled robotic elements called RT-Components. The specification standard of the RT-component is discussed / defined by the Object Management Group (OMG). ...
In the RT-middleware, robotics elements, such as actuators, are regarded as RT-components, and the whole robotic system is constructed by connecting those RT-components. This distributed architecture helps developers to re-use the robotic elements, and boosts the reliability of the robotic system.
Each RT-component has port as an endpoint for communicating other RT-components. Every port has its type and the ports which have the same type can be connected each other.
RT-components also has its state, so the RT-components behaves as state machines. The states that RT-components can have are CREATED, INACTIVE, ACTIVE, and ERROR, and the states and behaviors are controlled by the execution-context. If developers want to change the behavior of their RT-components, the execution-context can be replaced at run-time." [RT middleware. Wikipedia]
The UML state machine diagram example "State transitions of RT-component" was created using the ConceptDraw PRO diagramming and vector drawing software extended with the Rapid UML solution from the Software Development area of ConceptDraw Solution Park.