uml class diagram tool

cannot be well adjusted in a large system. The reason for this is that, as we will see in the rest of this article, UML 2 significantly enhances the symbolic set of component diagrams. While maintaining its ease of understanding, the UML 2 symbol can be better tuned and has more information.Let's build a component diagram step by step according to the

. The above UML 1.4 symbols are still supported in UML 2. However, the UML 1.4 symbolic set cannot be well adjusted in a large system. The reason for this is as follows:ArticleThe rest of the diagram will see the same, and UML 2 significantly enhances the symbolic set o

, and generalized, mainly involving components and components, between components and interfaces, and between interfaces and interfaces. implementation : The relationship between a component and an interface dependencies : The relationship between components and components If there is a dependency on two classes in two components, the relationship between the two components can be expressed as a dependency relationship generalization : between compon

Document directory Add a self-called Message Element Use the call Message Element Use auto-extended message options Use to create a message symbol Add asynchronous Link Use a combination of fragment Elements Save Graph A sequence diagram describes the interaction modes between objects in chronological order. It uses the "lifeline" of objects and the messages passed between them to show how objects participate in interaction. A sequence

state again, it can go directly into the sub-state, rather than starting again from the initial state of the combined state.Concurrency ZoneA state diagram can be divided into regions, and regions include exits or sub-states that are currently executing. Indicates that the combined state can reach multiple sub-states at a time.State Machinedescribes the sequence of states that an object or an interaction undergoes in response to an event during its l

-01This article was synchronized on: http://blog.csdn.net/sfdev/archive/2009/02/18/3906243.aspxThis is a tutorial on the basics of UML; now that we're doing a project too tight, we haven't really done a real class-level detail design, let alone using UML to implement canonical modeling; This article is mainly about the relationship between several classes that I

world to the code realization excessively. ---> such as: The attribute of the class is described in words, and the behavior functionFour: Implement Layer class Diagram---> Implementation layer views that the class is the description of the implementation code, and the classes in the

chronological and spatial order;(9) activity digraphs, which describe the activity of system elements; Based on their applications in different architecture views, nine types of graphs can be divided:(1) User Model View: use case diagram;(2) Structure Model View: class chart and object chart;(3) Behavior Model View: status chart, sequence chart, collaboration diag