UML 9 Diagram of the component diagram and deployment diagram

A component diagram (Component diagram) is one of the diagrams used in the physical aspect of an object-oriented system to show the organization and dependencies between a set of artifacts. The idea of using component diagrams is reuse. It is like we build a house, when the general framework of the House is built, the rest of the door and window furniture, such as directly to the installation can be, do not need to re-production, directly take the idea of the use of. These doors and windows are equivalent to a component.

The previous class diagram use case diagram defines the system's problem domain vocabulary and system expected behavior, and sequence diagrams and state diagrams describe how things work together to accomplish this behavior in the problem domain. All that is done is a blueprint for logic, and the component diagram is to transform these blueprints into things that exist in the bit events, to be real physical, touchable things, to visualize the static aspects of these physical components and their relationships with component diagrams.

Some concepts:

1. component:(Component) is the physical, replaceable part of the system that complies with the same set of interfaces and provides its implementation. Each component can realize certain functions for other components to provide the use of interfaces, convenient software reuse. such as object libraries, executables, COM +, Enterprise Java beans.

2. Component type:

Source Code widget: source code files

Binary components: Target code file, static link library, dynamic link library

Executable Artifacts: Actionable programs

Data file or document

3, component Diagram composition:

Component diagrams include artifacts, interfaces, and four relationships, and can include annotations and constraints, as well as some packages or subsystems.

4. For Example:

To construct a good component diagram must meet a number of requirements:

1. Focus on describing a level of the system rather than the global

2. To include model elements that are necessary to understand this aspect, and to grasp only the subject rather than the secondary

3, graphics can not be too simplified, so that readers will not be misunderstood

4, for the component diagram to take a name that can indicate the intention

5, the space is placed on the rational organization of elements, making semantically close to the physical location of things closer

6, use the stereotype elements carefully, for your project or organization to choose the least use of common icons, so that they remain consistent

The component diagram is one of the more laborious diagrams I've seen in 9 diagrams, and I've watched the video without any impression of the component diagram. So the understanding is still not in place. The component diagram can be used to model the static implementation view of the system to support the configuration management of the system components. To achieve the effect of reuse, saving some unnecessary manpower.

The deployment diagram (Deployment Diagram), also called the implementation diagram, describes the structure of the system runtime, showing how the hardware is configured and how its software is deployed to the network architecture. You can understand the physical relationships between software and hardware and the distribution of components that handle nodes, conveying the configuration and deployment of the hardware and software elements that make up your application. A deployment diagram describes a run-time hardware node and a static view of the software components running on those nodes.

Some concepts:

1. node:

A node is a physical element that exists at run time, represents a computable resource, usually consumes some memory, can be hardware or a software system running on it, such as a 64 host, a Windows Server 2008 operating system, a firewall, and so on.

2. Examples of deployment diagrams:

differences and linkages between deployment diagrams and component diagrams:

The main objective of component drawing is to describe what components are in the system, and the components and the dependencies between them. The deployment diagram describes node completion, describes how the software is mapped on hardware, and the topology of the network.

In the component diagram, the relationship can be four kinds, namely association, dependency, implementation and generalization. The relationship between the nodes in the deployment diagram is only related and dependent.