uml diagram java

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. Who operating system. What external resource sy

UML Case Diagram (use cases) arrow direction:Always forget the direction of the arrows, provoke jokes.1, association, no arrows, actor connection usecase can;2, Directedassocition,actor connection UseCase, arrow by actor point to usecase (role point use case);3, generalization, inherit, I read it as " inherit in ", of course, the arrows point to the father;4, Dependency, I read " depends on", I know the dir

Symbol:+:p Ublic-:p Rovite#:p Rotected~:p ackageRelationship: Relationship Name Code relations Uml Generalization (generalization) Inherited Solid Line Triangle Arrow Implementation (Interface realization) Implementation of subclass inheritance of virtual base function Dashed triangular arrow Dependency (Dependency) One class as a function parameter or ret

This article reprint casually, Please retain the Source: http://blog.csdn.net/dylgsy/ UML class diagram relationships include association, aggregation/combination, dependency, and generalization (inheritance ). The Association is divided into two-way Association, one-way Association, and self-Association. Let's take a look at what these relationships are and what their differences are. 1. Association

, the object as a local variable, call the static method of the class. The class that is called within the parentheses of a class function is dependent on itself. Because this relationship is weakly connected, from the point of view of high cohesion and low coupling, such code is optimally organized, whether it is object-oriented or process-oriented.There is a special phenomenon in dependence, that is, interdependence. In the face of dependency interpretation, interdependence can be understood a

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 Implementation You can read books, roles, system boun

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

. Proxy modeIntent: Provides a proxy for other objects to control access to this object.21. Single case (Singleton) modeIntent: Ensure that a class has only one instance and provides a global access point to access it.22. Status (State) modeIntent: Allows an object to change its behavior when its internal state changes.23. Policy (strategy) modeIntent: Define a series of algorithms, encapsulate them one by one, and make them interchangeable with each other.24. Template Method ModeIntent: Define

consistent.Just, the class involved in the association is logically a level, such as the student teacher above, but the aggregation involves the class is not a level.Look at the following example:It can be expressed as a has a/some B, at which point B is able to separate from a and exist independently. Without a car tire or a tire.Combination compositionThe composition relationship is a bit tighter than the aggregation relationshipThe limbs and the people are die.Non-separable.As for generaliza

Class digraphs are graphs describing classes, interfaces, collaboration, and relationships between them. A class diagram is a part of a static view in the system. A static view can contain many class diagrams. Static views are used for Structural Modeling of the software system. They construct the vocabulary and relationships of the system, and the visualization of structural models is achieved through class diagrams. A class chart consists of the

The previous blog summarized the use case diagram, in which the relationship between use cases is only included, because the relationship between use cases is not particularly profound. This is also because the UML use case diagram has not passed the acceptance of the master. The relationship between use cases must be further understood. This blog will summarize

Several important grasp principles: 1. Controller mode 2. Creator mode (principle) 3. Information Expert mode (principle) 4. Cohesion Poly-low coupling The pattern described here is not a design pattern for specific events in JavaSeveral operations for the main success scenario: 1.makemewsale 2.enteritem 3.endsale 4.makepayments1) Consider the interaction diagram: Refer to the contract of operation to----Our first consideration is to select the contro

Tags: blog HTTP ar Java SP strong on art log Original Inheritance: Solid line of the hollow triangle arrow. The Child class points to the parent class. Common keywords in code are extends (Java ). Implementation: Dotted line of the hollow triangle arrow to implement class pointing interface. The implements keyword (Java) is usually used in the code ). Ass

The class diagram is learned by using examples to understand the relationship between classes and classes and the relationship between classes and interfaces.Start:Note: There is data on the representation of the interface is divided into: rectangular notation, lollipop notation, in this paper with rational Rose tool drawing,rational rose No rectangular representation of an interface.Look at the class diagram