In component and deployment diagrams, a component is a distributable unit of implementation in a system. For example, a component can represent a physical module of code (source, binary, or executable) or it can be a logical component that represents a business document in a human system.
In a deployment diagram, a component instance represents an implementation unit that has identity at run time and can contain objects. A node instance can contain a component.
Note: Creating and editing UML diagrams on Visio for the web requires a Visio Plan 1 or Visio Plan 2 license, which is purchased separately from Microsoft 365. For more information, contact your Microsoft 365 admin. If your admin has turned on "self-service purchasing," you can buy a license for Visio yourself. For more details, see Self-service purchase FAQ.
A component's behavior is defined in terms of provided interfaces and required interfaces. Interfaces are model elements that define sets of operations that other model elements, such as classes or components, must implement.
There are two kinds of interfaces:
|
Name |
Description |
|
|---|---|---|
|
|
Provided interface |
Produces information that's used by a required interface of another component. |
|
|
Required interface |
Is dependent for information on another class or interface in order to perform its proper function. |
