Objective
Most of the UML describes the logic and design of the information. The implementation diagram is used to describe the realization of the narrative information. The implementation diagram contains a deployment diagram and a component diagram.
Component diagram
1. Concept
Component diagram describes the main functions of a system from the perspective of software architecture. such as subsystems, classes, packages, components. Used to show the relationship between the organization and dependencies of a set of builds.
2. Composition
components, interfaces, relationships
3. Types of components
Source artifacts, binary components, operational artifacts, data files, or documents
4. Relationship of components and classes
(1) Classes represent logical abstractions and artifacts represent physical abstractions
(2) component is the physical implementation of other elements
(3) Classes can have properties and operations directly, and members generally only have access to the interface via interfaces.
5. Features of the component
Physical, replaceable, part of a system, from a set of interfaces and providing implementations of a set of interfaces
6. Component-to-interface relationships
Realization, dependence, indication, entry
7. The following is a component diagram of my room charge. Now feel understanding is not thorough enough, first draw out after learning deep and then improve
Deployment diagram
1. Concept
Used to display the physical architecture of software and hardware in the system.
A system has only one deployment diagram.
2. Deployment diagram elements
Nodes, node instances, objects, relationships, node containers
3. Conditions of Use
Using deployment diagrams for complex distributed software
4. Strengths
deployment diagram to determine the required processor for the software and the topology of the device
5. A good deployment diagram:
(1) Each implementation diagram is an aspect of the system
(2) One aspect of side weight
(3) Include only necessary elements and necessary modifications
(4) Avoid cross, name can summarize your function
6. The following is the deployment diagram of my computer room charges, the shortcomings welcome everyone to correct
UML Still on the road (epilogue)
through the above continuous five blog, the UML in the 9+1 (package diagram) A graph combined before knocking the room charge system to do a summary. The first five blogs will close the links closely to the 22 to put together more helpful to understand these diagrams in comparison.
UML language makes system modeling process standardized and unified. Standardization. UML uses the same concepts and representations throughout the software development process
Method. There is no need to transform concepts and representations at different stages of development. Avoids the two gaps in traditional software development methodologies. UML uses a graphical
Representation. The resulting model is easy to understand. Easy communication between developers and users. So that users can get feedback information in time. Use
The modeling artifacts obtained by UML for system modeling include not only a variety of model diagrams, but also a wealth of documentation. These documents give the system a later dimension
The protection work brings convenience.
UML uses class diagram and component diagram to judge the structure of software, using sequence diagram, activity diagram, collaboration diagram, State diagram to describe the behavior of software, deployment diagram
Determine the required processor and device topology for the software.
The above blog is a summary of the completion of UML. UML temporary tall paragraph, but still understand is not very clear, UML diagram will always
Use, personal ability is limited, hope and everyone together probe.
Copyright notice: This article Bo Master original article. Blog, not reproduced without consent.
UML deployment diagram and Figure nine component diagram