uml entity relationship diagram

UML class diagram Explain UMLClass diagram: 1. first, check the rectangle of "animal". It represents a class. This type of graph is divided into three layers. The first layer displays the name of the class. If it is an abstract class, it must be displayed in italic. The second layer is the class features, usually fields and

use case diagram. composition: System boundaries. Participants. Case. Relationship. Participant: Actor is not a person, but a role to play when participating in a use case. If the action of one role is done by another role agent, establish a dependency between the role and the other role. How to identify the participants. who is providing information to the system? Who gets information from the system. Wh

directly with each other, then these two classes should not have direct interaction, and if one of the classes needs to invoke a method of another class, the call can be forwarded through a third party. The fundamental idea of this principle is to emphasize the loose coupling between classes, and the weaker the coupling between classes, the more beneficial the reuse, the more weakly coupled class is modified and does not affect the related classes. In the structure design of a class, each c

Class diagram, the British Civilization Yue: Class diagram, then the class is after how magical transformation, into a class diagram? As we all know, classes are descriptors of a set of objects with similar structures, behaviors, and relationships, classes are the most important building blocks in object-oriented systems, and class diagrams show a set of classes,

One: Time series Diagrams---> Timing diagrams are used to describe the interaction patterns between objects in chronological order. ---> It displays these objects according to the "Lifeline" of the object that participates in the interaction and the messages they send to each other. ---> Time series diagrams contain objects and lead instances, and messages that explain how they interact. ---> Time series diagrams describe the events that occur in the objects that participate in the interaction (

composite relationships. Generalization ): Dependency: for example, logwapper depends on log, The so-called dependency, the dependency program is relatively speaking, not necessarily because logwapper cannot "survive" without a log ". In the specific business logic, logwapper needs logs to assist with the completion of a specific task, which is also dependent. Class "recursion" relationship and "Triangle"

extension (Extension) use case, and then extends it from the extension point (Extension points) declared in the base use case to make the base case more concise and more focused. The extension use case adds new behavior to the base use case. An extension use case can access the properties of the base use case, so it can determine whether to execute itself based on the current state of the extension point in the base case. However, the extension use case is not visible to the base use case.Examp

Reference: http://hi.baidu.com/1987raymond/blog/item/ae2030f35223d5c70b46e041.html A component diagram, also known as a component diagram, shows the organization and dependencies between a group of parts for source code, executable release, physical database, and adjustable system modeling. This article introducesVs2010Component diagram inUML component Divisor. I

Use case diagram Structure 1Roles: Personnel roles-people and events; Roles are not necessarily limited to people. They can also be things or things. 2. Use Case: function description; Each use case describes a complete system service. 3System boundaries 4Relationship: the relationship between executors and use cases. Generalization Dependency Association Aggregation and combination Implementati

Class diagrams are the most commonly used diagrams in UML. We can see that class diagrams are very important. A class chart is a class digoal. The shape is very simple. It consists of a rectangle, two rectangles, or three rectangles. For example: The top column shown in is the class name. The second column is the class property. (A class can have one or more attributes. Of course, some classes have no attributes) the third column is the cl

Today I saw a gossip news, Zhou Xun issued a statement and formally broke up with Li Daqi (http://ent.163.com/09/0624/15/5CJ6JK3F00031H2L.html) The so-called "no follow-up or no news" Netease comments, as always, also built a building, showing the infinite wisdom of netizens, there is a comment building is quite high, as shown below: The characters in these periods are complex and difficult to clarify their clues. After reading it for a long time, I suddenly remembered that the

as an inheritance relationship. Child cases are similar to parent cases, but show more special behaviors. Child Cases inherit all structures, behaviors, and relationships of the parent case. A child use case can use a behavior of the parent use case or reload it. The parent case is usually abstract. [Arrow pointing]: pointing to the parent use case C. Include) The include relation is used to break down the Functions Represented by a complex use case

UML class Diagram Relationships (generalization, inheritance, implementation, dependencies, associations, aggregations, combinations)In UML class diagrams, the following relationships are common: generalization (generalization), implementation (realization), Association (association), Aggregation (Aggregation), composition (composition), dependency ( Dependency)1

Overview A deployment diagram (deployment divisor) is used to display the physical architecture of software and hardware in the system. From the deployment diagram, you can understand the physical relationship between software and hardware components and the component distribution of processing nodes. The deployment diagram