In the previous article "UML System Analysis and Design 02-use case diagram and activity diagram (I)", we mainly explained the use case analysis and drawing methods and techniques in requirement analysis, however, the use case diagram only tells us what the system wants to do. As for how to do it, there is no intuitive
employee and timecard may be better represented as "compositing" rather than "associative". 5. Generalization (generalization) Generalization represents a relationship between a more generalized element and a more specific element. Generalization is a UML element that is used to model inheritance. In Java, this relationship is represented directly by the extend
In the 13 graphs of UML 2.0, class diagrams are one of the most frequently used UML diagrams. Martin Fowler in his book "UML Distilled:a Brief Guide to the Standard object Modeling Language, Third Edition" (UML Essence: A concise reference to the model language South (3rd edition)) There is a paragraph in this: "If som
software components that will run on their systems. Although the system administrator will not be able to identify physical devices or things from the graphBut they still welcome the component diagram because it provided earlier information about the component and its relationship (which promised the system administrator to easily plan the subsequent work ).SymbolCurrently, the component
device or a software system running on a hardware device.
-UML Representation -node instance: the instance form of the node. The format is instance Name:node, similar to the class instance format, preceded by a colon with an instance name or without an instance name -node type : Depending on whether the node is capable of-Processor: A node with the ability to perform software operations such as calculation and execution-Devi
connection. The constraint is represented as {}.4. Typically in UML, the name of the specific instance is underlined, and the class, not the instance, is represented if there is no underscore. Note that the rule has an exception for instances in the interaction diagram, and the instance is represented by a lifeline diagram, with no underscore in its name.Typical
modeling representation, clear graphical structure and easy to use
UML contains nine types of diagrams:
Class diagram, object diagram, use case diagram, state diagram, sequence diagram, activity
UML Construction Design Model A. Class diagram two. Package Diagram three. Assembly Diagram Four. Deployment Diagram I. Class Diagram 1. Classes: Classes are represented by dig: class names, class properties, operations of cla
and is considered an attribute in another local application.(2) The same entity does not have exactly the same attributes in different detail views, or the order of the attributes is not identical.(3) The relationships between entities render different types in different detail views. For example, the entity E1 and E2 are many-to-many links in local application A, but in the local application B is a one-to
UML-united modeling language, unified modeling language-is an object-oriented visual modeling language. UML uses a set of visualized graphical symbols (such as class diagrams) as the modeling language. These symbols can be used to visually describe all aspects of the system. UML describes a model by establishing various relationships between graphs (such as the
One: Class diagrams (Behavior classes and entity classes)---> class diagrams are used to show the classes in the system and their relationship to each other---> Conceptual layer class Diagram---> Description layer class DiagramSecond: Concept layer class Diagram---> Concept view: Class Diagrams At this level describe t
inheritance relationships between classes and interfaces. Figure H
650) This. width = 650; "src =" http://pic002.cnblogs.com/images/2012/285763/2012061315050938.gif "style =" margin: 0px; padding: 0px; Border: 0px; "/>
1.1.6 implementation (realization): Expressed by hollow arrows and dotted lines
Instance (FigureI) Link specifies a contract between two entities. In other words, one entity defines a contract, and the other
UML consists of nine diagrams, in which the core is the only---class diagram.
Here is my summary of the Class Diagram section in UML.
Class diagram is a static structure that shows the model, especially the classes that exist in the model, the internal structure of the clas
Through the previous blog: the use case diagram of UML diagrams, we have completed the division of a software system use case and function module. Now we need to know how to further improve the static structure of the system.
With the UML tool, we can obtain the static diagram of the static structure of the software s
PrefaceUML is composed of dynamic graphs and static graphs, and the state diagram is one of the most important diagrams in dynamic graphs. definitionused to describe all possible states of a particular object and the transitions between states caused by the occurrence of various events.Purposestudy the complex behavior of classes, roles, subsystems, or components.constituent elementsStatusdefinition: Refers to a condition or condition in the life cycl
first, the concept
use case diagram (Diagram): Primarily used to describe the behavior of systems and the relationships between functions, is a graph that describes the relationship between participants (Actor) and use cases, and use cases and use cases.
Use case diagram = actor + use case +
the relationships between classes
Inheritance Relationship
An inheritance relationship is the most understandable relationship. The picture is like this. The object-oriented argument is the is-a relationship. That is to say Class2 is a Class1. In C + + we say that Class2 is a derived class of Class1, or that Class1 is
within the "whole". The composition is also unshared. Therefore, although the local does not have to be destroyed with the overall destruction, but the overall responsibility to maintain a local survival, or be responsible for destroying it. Local cannot be shared with other whole. However, the whole can transfer ownership to another object, which will then assume the lifetime responsibility. The relationship between employee and timecard may be bett
Class diagrams and sequence diagrams are directly associated with program code in software system design. To be precise, program code is directly generated by class diagrams, A Sequence Chart can define a class chart method. The use case diagram is used to describe system functions and has no direct relationship with the sequence diagram.
A class
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.