|
|
|
|
|
|
Component Diagrams
Component diagrams fall under the category of an implementation diagram, a kind
of diagram that models the implementation and deployment of the system. A
Component Diagram, in particular, is used to describe the dependencies between
various software components such as the dependency between executable files and
source files. This information is similar to that within makefiles, which
describe source code dependencies and can be used to properly compile an
application.
Notation
| Component |
A component represents a software entity in a system. Examples include source
code files, programs, documents, and resource files. A component is represented
using a rectangular box, with two rectangles protruding from the left side, as
seen in the image to the right.
|
 |
| Dependency |
A Dependency is used to model the relationship between two components. The
notation for a dependency relationship is a dotted arrow, pointing from a
component to the component it depends on.
|
 |
For example, the following Component diagram identifies the MyWebComps assembly
as being dependent on the BaseDB and SiteConfig source files.
If would like to use different icons, you can use stereotyped icons for
components instead of the standard icon. For instance, you may be modeling a
web application, and would like to graphically differentiate ASP pages,
Javascript files, and Images. Here is an example of a component diagram using
stereotyped icons to model the dependencies of an ASP Registration Form:
|
|