javascript uml diagram

I haven't studied UML for many days because of the exam, and I feel a little unfamiliar. So hurry up and make up for my inner emptiness. We have to take the test this afternoon, and there is still nearly two hours in the middle. Now I will share with you my understanding of the object diagrams in UML. Of course, I have concluded that I have never drawn any picture, in the future, we will add the picture in

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" Relationship Recursive relationships are self-contained relatio

UML class Diagram Relationships (generalization (inheritance), implementations, dependencies, associations, aggregations, combinations)650) this.width=650; "Src=" https://s2.51cto.com/wyfs02/M01/8C/88/wKioL1hvSDyAuWoyAADbhJ2FkKg898.jpg-wh_500x0-wm_ 3-wmp_4-s_4062631452.jpg "title=" main.jpg "alt=" Wkiol1hvsdyauwoyaadbhj2fkkg898.jpg-wh_50 "/>UML class

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

What is a simple Factory mode:By defining a class specifically, you are responsible for creating instances of other classes that typically have a common parent class. UML class diagram for simple Factory mode: The roles contained in the Simple factory model and the corresponding responsibilities are as follows: Factory class Creator: The core of the simple factory model, which is responsible for creating in

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 shows the structure of the runtime syst

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

Activity Diagram can be used to model the dynamic behavior of the system, mainly to refine the use case, that is, the details inside the use case can be described in the form of an activity diagram. The activity diagram describes the sequence of activities, the flow of control between the main table activities, the internal processing-driven process, which is ess

class is responsible for coordinating other jobs. After learning about classes and class diagrams, I began to draw class diagrams. This is really a headache. When I was writing a document, I felt very eager to draw a UML diagram, because it was useful at that time, but now I have a chance, and I really didn't know how to start it. I also read the class pictures drawn by others, but they said that you sho

diagram.The following fragment types can be used to change this interpretation: Fragment type Name Description Consider Consider Specifies the list of messages described by this fragment. Other messages can occur on a running system, but this is not a very meaningful description.Type the list in the Messages property. Ignore Ignore A list of messages not described in this fragment. These messages can occur in a running syst

diagram.The following fragment types can be used to change this interpretation: Fragment type Name Description Consider Consider Specifies the list of messages described by this fragment. Other messages can occur on a running system, but this is not a very meaningful description.Type the list in the Messages property. Ignore Ignore A list of messages not described in this fragment. These messages can occur in a running syst

diagram.The following fragment types can be used to change this interpretation: Fragment type Name Description Consider Consider Specifies the list of messages described by this fragment. Other messages can occur on a running system, but this is not a very meaningful description.Type the list in the Messages property. Ignore Ignore A list of messages not described in this fragment. These messages can occur in a running syst

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,

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

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 into smaller steps. [Arrow pointing]: points

multiple links1Written by one party1, Write by multiple partiesN; Multiple-to-many relationships are written in the direction of the two physical connections.N, m UML: The first use case diagram (Use Case digoal) The second type is static digraphs, including class graphs, object graphs, and packet graphs. The third type is the behavior diagra