After reading the UML video, I want to start drawing documents. I don't know how to start! Let's summarize the nine types of diagrams and relationships in UML, and then start with the document. First.
The nine types of UML diagrams are: use case diagram, class
One. UML OverviewThe role of 1.UML: a complex problem decomposition B realizes the visualizationUML is created by rational company 2.UML is what: is a language, has its own standard expression rules, is an analytical design language, is also a modeling language 3.UML including five large views, 13 kinds of Figure five
. "When" is the answer, that is, how the development work is scheduled;
4. "Who" means that some development (or maintenance) work is intended to be done by "who? "·
5. "How" means how certain requirements are met;
6. Why?
The above is the relevant content of the soft work document. Let's take a look at the relationship between the UML diagram and the document below:
First, the
the sequence diagram. The direction of the arrow pointing to the edge indicates the direction of the message being passed, what message is identified above the forward edge, the time sequence in which the message is sent, and the number appended to each message, and it is clear that the collaboration diagram makes it easy to describe the collaboration between objects. There is no need for a sequence
Tags: font public service Ted Python simple folder reason nesting history Brief introduction Package diagrams is a description of the relationship between packages and packages, showing the dependencies between modules and modules in the system. A package diagram can consist of any UML diagram that can hold elements such as classes, interfaces, components, use c
name that differs from the other package. The name of the model package is a string that can be divided into simple names and path names .Simple name: refers to a package that contains only a simple name.pathname : Refers to the name of the outer package that the package is located in as a prefix.3, the role of package diagrams:Package diagrams can describe the requirements, the design of the high-level overview, package diagram through the rational
team and the team (as shown in ).
The "employee" and "employer" on the two sides of the Association indicate the relationship between the two, while the number indicates the restriction of the relationship between the two, which is the multiple correlation between the two. There are usually "*" (indicating all, not limited), "1" (indicating there is only one), "0... "(0 or more)," 0, 1 "(0 or one)," n... m "(meaning n to m)," m... * "(at least m ).
• Association is the most common relationshi
This article from: http://www.iteye.com/topic/979557
After summing up Ubuntu, we will continue to integrate UML. In the previous article, we introduced the Relationship Between the use case diagram and the use case. Let's talk about it now.Relationship between class diagrams and classes in UML.
When drawing a
Team
member
Participation
Contribution ratio
031602406 Cheng (temporary leader)
Entity Relationship Diagram Design
11
031602501 CAI Aerospace
Entity Relationship Diagram Design
8
051501124 Wang Bin
Class diagram
cases.The object graph shows the set of objects and the relationships between them. The object graph shows the static images of the instances, which are derived from the components established in the class diagram. The object graph deals with the static Design view or static process view of the system as if it were a class d
software tools available to help software engineers to do the work, either forward engineering or reverse engineering .
Forward Engineering is a traditional process of high-level abstraction, logic and independence design for a system physical structure implementation.
Reverse engineering is the analysis and processing of an existing system to identify its components and their intrinsic relations, so as to build a framework of a system with high-level abstraction. In mos
initiated by the participant.(5) Generalization. Generalization is the same as the generalization concept in a class, where the child use case inherits the behavior and meaning of the parent use case, and can also increase or overwrite the behavior of the parent use case, and the child use case can appear where any parent use case occurs (both parent and child have concrete instances). Here are two illustrations illustrating the concept and meaning o
One: Dynamic View---> Dynamic view is a description of the dynamic behavior of things. ---> Note that a dynamic view cannot exist independently, it must refer to a static view of a live uml element, explaining their dynamic behavior under the structure of things defined by static views. ---> Dynamic view: Activity diagram, state diagram, timing
than highlighting the chronological order in which these messages are sent. is a collaboration diagram corresponding to the above sequence diagram, the message arrows between objects indicate the flow of messages between them, and the labels on the message indicate the timing of the messages being sent.State DiagramA state diagram complements a
Most of the models in UML describe the logic and design information:
Use Case chart to understand expectations
Class diagrams can understand the Vocabulary (class and object) of the problem domain)
The status chart, InterAction diagram, and activity diagram can be used to un
The following is a Library management system state diagram, very typical, covering the use of all the elements of the state diagram, because the state diagram is relatively simple, directly from the view of the picture can be very well mastered. Suppose you want to understand the concept of the element rigor of the state diag
a common understanding that developers and users have agreed upon. Use case models are described in several use case diagrams. A use case diagram must include a description of the function, a role, and a role and function correspondence.Role (actor):A role in a software system is the idealization of an external person, process, or thing that interacts with a system, subsystem, or class. An activity this ca
Transferred from: http://www.cnblogs.com/alexlee73/archive/2011/11/05/2237294.htmlAttached: http://download.csdn.net/download/tiancen2001/15293911.UML is divided into:1) Static Modeling: System Foundation and system fixed frame structure, these graphs are often "static".
Class Diagram: Commonly used to analyze business concepts
Use case
ObjectiveIn my work, the most used is the time series diagram. Probably because of the work, I also like to draw time series diagram, very clear, very clearly, when to send what message, to what state, all of a sudden on the display in your mind, for the message-driven program, is no better.Introduction to timing diagramsFirst, time series diagrams are used to denote the order of behavior in a use case, whe
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 diagram is a model used to describe how object groups collaborate in certain behavior aspects over time. A sequence diagram captures the behavi
The content source of this page is from Internet, which doesn't represent Alibaba Cloud's opinion;
products and services mentioned on that page don't have any relationship with Alibaba Cloud. If the
content of the page makes you feel confusing, please write us an email, we will handle the problem
within 5 days after receiving your email.
If you find any instances of plagiarism from the community, please send an email to:
info-contact@alibabacloud.com
and provide relevant evidence. A staff member will contact you within 5 working days.