Shulou(Shulou.com)06/02 Report--

Editor to share with you what are the components of UML, I believe most people do not know much about it, so share this article for your reference, I hope you can learn a lot after reading this article, let's go to know it!

Overview of 1.1UML

What ◆ UML can do:

Visualization, elaboration, construction, and documentation.

Conceptual Model of 1.2UML

Building blocks in the composition of ◆ UML

① things

⑴ structured things (structuralthing)

⒈ class (class): pick up a description of a set of objects that have the same properties, operations, relationships, and semantics.

⒉ interface (interface): describes a collection of operations for a service of a class or component.

⒊ collaboration (collaboration): defines an interaction that is a group of roles and other elements that work together to provide a collaborative behavior.

⒋ use case (usecase): a description of a sequence of actions that the system performs to produce a result that is valuable and observable to a particular actor.

⒌ active class (activeclass): the object of the active class has at least one process or thread, so it can start control activities.

⒍ component (component): a physical, replaceable component of a system that follows and provides an implementation of a set of interfaces.

⒎ node (node): a physical element that exists at run time. It represents a computable resource that usually has at least some memory and processing power.

⑵ behavior thing (behavioralthing)

⒈ interaction (interaction): an act that consists of messages exchanged between a group of objects that work together to accomplish a task in a particular context.

⒉ state machine (statemachine): it describes the sequence of states experienced by an object or an interaction during the life cycle of the corresponding event.

⑶ grouped things (groupingthing)

⒈ package (package): a mechanism for organizing elements into groups that can be used for many purposes.

⑷ Notes things (annotationalthing)

⒈ comment (note): a simple symbol that is attached to an element or group of elements and constrains or interprets it.

The relationship in the composition of ② UML

⑴ association (dependency): a structural relationship that describes a set of chains, which are connections between objects. Aggregation () is a special type of association, which describes the structural relationship between the whole and the part.

⑵ association: the semantic relationship between two things, in which the change of one independent thing will affect the semantics of the other dependent thing.

⑶ generalization (generalization): a special / general relationship in which objects of special elements (that is, child elements) can replace objects of general elements (that is, parent elements).

⑷ implementation (realization): is a semantic definition between classes, where one class specifies a contract guaranteed by the other class. Implementations are used in two places: between interfaces and the classes or artifacts that implement them, and between use cases and collaboration that implements them.

Diagrams in the composition of ③ UML

⑴ Class Diagram (classdiagram):

Shows a set of objects, interfaces, collaboration, and the relationships between them. The most common diagram established in the modeling of object-oriented systems is the class diagram. The class diagram shows the static design view of the system. The class diagram containing the active class gives a static process view of the system.

Together name: ClassDiagram.

Together objects: Package, Class, Interface, Enum, ClassByTemplate, AssociationClass, Generalization/ImplementationLink, AssociationLink, LinkByTemplate, DependencyLink, AssociationEnd, Object, Note, NoteLink.

⑵ object Graph (objectdiagram):

The object graph in the composition of UML shows a set of objects and their relationships. An object diagram describes a static snapshot of an instance of something created in a class diagram. Like class diagrams, these diagrams give a static design view or static process view of the system, but they are built from the perspective of a real or prototype case.

Together name: none.

Together object: none.

⑶ use case diagram (usecasediagram):

Shows a set of use cases, actors (a special class), and the relationship between them. The use case diagram gives a static use case view of the system. These diagrams are very important for organizing and modeling the behavior of the system.

Together name: UseCaseDiagram.

Together objects: Actor, UseCase, GeneralizationLink, CommunicatesLink, ExtendLink,IncludeLink, SystemBoundary, Note, NoteLink.

⑷ sequence diagram (sequencediagram):

A sequence diagram in UML composition is an interaction diagram that emphasizes the chronological order of messages.

Together name: SequenceDiagram.

Together objects: Actor, Object, Message, MessagewithDeliveryTime, Self-Message, Return, Note, NoteLink.

⑸ collaboration Diagram (collaborationdiagram):

An interaction diagram that emphasizes the structure and organization of the objects that send and receive messages. Sequence diagrams and collaboration diagrams are isomorphic, which means that they can be converted into each other.

Together name: CollaborationDiagram.

Together objects: Object, Actor, Message, AssociationLink, AggregationLink, Note, NoteLink.

⑹ state diagram (statechartdiagram):

The state diagram in the UML composition shows a state machine, which consists of states, transitions, events, and activities. The state diagram focuses on the dynamic view of the system. He is particularly important for modeling the behavior of interfaces, classes, or collaborations, and he emphasizes the order of events of object behavior, which is very helpful in modeling reactive systems.

Together name: StateDiagram.

Together objects: State, StartState, EndState, History, Object, HorizontalFork/Join, VerticalFork/Join, Transition, Note, NoteLink.

⑺ activity Diagram (activitydiagram):

Is a special state diagram that shows the process of moving from one activity to another within the system. The activity diagram focuses on the dynamic view of the system. He is particularly important for functional modeling of the system and emphasizes the control flow between objects.

Together name: ActivityDiagram.

Together objects: Activity, Decision/Merge, SignalReceipt, SignalSending, State, History, Object, StartState, EndState, HorizontalFork/Join, VerticalFork/Join, Swimlane, Transition, ObjectFlow, Note, NoteLink.

⑻ component diagram (componentdiagram):

The component diagram in the composition of UML shows the organization and dependency between a set of components. Focus on static views, related to class diagrams, and usually map component diagrams to one or more classes, interfaces, or collaborations.

Together name: ComponentDiagram.

Together objects: Subsystem, Component, Interface, SupportsLink, DependencyLink, Note, NoteLink.

⑼ implementation diagram (deploymentdiagram):

Shows the configuration of the runtime processing node and its artifacts. He gives a static implementation view of the system. Related to component diagrams, usually a node contains one or more components.

Together name: DeploymentDiagram.

Together objects: Node, Component, Interface, SupportsLink, AssociationLink, AggregationLink, Object, DependencyLink, Note, NoteLink.

Rules in the composition of ◆ UML

① is named after things, relationships, and graphs

The ② scope gives the context of a name a specific meaning.

How ③ visibility allows others to use or see names

How ④ Integrity things relate to each other correctly and consistently

What is the meaning of running or simulating a dynamic model by ⑤

⑥ omits to hide some elements to simplify the view

⑦ incompleteness can leave out some elements.

⑧ inconsistency does not guarantee the integrity of the model

Common mechanisms in the composition of ◆ UML

① specification

② modification

③ general partition

⑴ 's division of classes and objects. That is, the division of abstractions and instances, such as classes and objects, use cases and use case instances

The division of ⑵ interface and implementation. Examples include use cases and ways to implement their collaboration, operations, and implementation.

④ extension mechanism, which mainly includes:

⑴ stereotype (stereotype)

⑵ tag value (taggedvalue)

⑶ constraint (constraint)

The above is all the contents of the article "what are the components of UML?" Thank you for reading! I believe we all have a certain understanding, hope to share the content to help you, if you want to learn more knowledge, welcome to follow the industry information channel!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.