UML Weekend Crash Course™ - To Parent Directory

262
Sunday Morning
REVIEW
The purpose of the Component diagram is to define software modules and their relationships
to one another. Each component is a chunk of code that resides in memory on a piece of
hardware.
The UML groups components into three broad categories:
Deployment components, which are required to run the system
Work product components including models, source code, and data files used to
create deployment components
Execution components, which are components created while running the
application
The component icon is a rectangle with two small rectangles on the left edge. The
interface to the component may be modeled two different ways:
The lollipop notation represents the interface as a small circle connected to the
component by a solid line and with the name of the interface near the circle.
The second method uses a class with the stereotype with a realizes
relationship drawn from the component to the interface class. A component
may realize (implement) as many interfaces as it requires.
QUIZ YOURSELF
1. What is a UML component (See “Explaining the Component Diagram.”)
2. What is the icon for a UML component (See “Defining the Notation for
Components and Component Dependencies.”)
3. What notation shows that one component needs access to another component
(See “Defining the Notation for Components and Component Dependencies.”)
4. What notation is used to show that a component implements an interface (See
“Defining the Notation for Components and Component Dependencies.”)
5. True or False: Each component implements a class. (See “Mapping the Logical
Design to the Physical Implementation.”)