UML knowledge aggregation

I. Meanings and functions of the Unified Modeling Language (UML:

A: uniied modeling language: Unified Modeling Language, simple

Simply put, it is a language with special purposes.

UML (Unified Modeling Language) is a tool for analyzing and designing software using object-oriented methods. UML is a language used for Visual Modeling of software systems.

UML is a standard language used to describe, visualize, and document products of object-oriented development systems.

The definition of UML consists of UML Semantics and UML notation.

UML Semantics

UML Semantics provides precise metadata definition based on UML. The meta-model provides simple, consistent, and general definitions for all UML elements in terms of syntax and semantics, enabling developers to achieve semantic consistency, this eliminates the impact of different representation methods. UML also supports the extended definition of the metadata model.

UML notation

UML notation defines the representation of UML Symbols and provides a standard for System Modeling by developers and development tools using these image symbols and text syntax. These graphical symbols and texts represent application-level models. In terms of semantics, they are examples of UML meta-models.

Ii. Case Modeling: composition elements and modeling process

Definition of a use case diagram: a dynamic view that consists of actors, use cases, and their relationships to describe system functions is called a use case diagram.

Iii. Class Graph Modeling: various relationships of class graphs (semantics and modeling methods)

Class diagram: it is mainly used to describe the relationship between people and things (classes) and between them. It is a diagram describing classes, collaboration (collaboration between classes or objects), interfaces and their relationships.

The relationships in a class diagram include: dependency, generalization, association, and realization ).

4. Modeling of activity and sequence graphs (modeling graphs based on text descriptions ):

1. Activity diagram definition:

Is a diagram composed of the active node and the conversion process. It describes the control flow formed by a series of activities of a system or business. It describes the entire process from one activity to another, that is, the activity change process of a transaction or object. The activity diagram is used to model the system workflow.

Function of activity diagram

2. Role of the activity diagram:

It is often used to describe the activity track of the business or software system, and describe the activity control flow of the system. We often use activity diagrams to model business processes, workflows, and use cases.

3. The sequence diagram (sequence digoal) is also known as the sequence diagram and sequence diagram. It describes the interaction between objects in the system through messages and emphasizes the order of messages on the timeline.

Role of Sequence Chart

4. sequence diagrams are often used to describe the implementation of use cases. They indicate the objects that implement the use cases through mutual message collaboration. In sequence diagrams, they indicate the order in which messages interact.

Supplement:

1. The prototype is a visual presentation of a product. It mainly conveys the information architecture, content, functions, and interaction modes of a product.

Object-oriented = Object + class + inheritance + Communication

Object-oriented core elements:

2. Object encapsulation message class inheritance polymorphism structure and Connection

3. The object model usually consists of five layers:

4. Category and Object layer attribute layer service layer Layer topic Layer

4. software processes are a series of software engineering activities implemented by software engineers with the support of software and tools to obtain software products.

5. four basic activities of the software process:

Specification Description: defines software functions and restrictions on their use

Software Development: Design and implement software that meets specifications

Software validation: verifies the software to ensure it meets customer requirements

Software Evolution: improving software to meet changing needs

6. Software Process Model: waterfall model, rapid prototyping model, incremental model, spiral model, and formal method model

Component-Based Development Model

7. Define a domain model (OOA): identifies a concept in a problem. It visualizes the concept and imagination in a real world and has nothing to do with the specific software technology.

8. diagrams in UML are divided into two types: Structure Diagram (static diagram) and behavior diagram (dynamic diagram ). A structure diagram depicts the static structure between system elements. A behavior diagram depicts the dynamic behavior of system elements.

1. The structure diagram has the following types:

(1) class diagram

Class diagrams are the most commonly used diagrams for UML modeling. It shows static objects in the system, their structures, and their relationships. A typical use of this image is to describe the logical design and physical design of the system.

(2) object graph

An object graph shows a group of objects in the system. It is a snapshot of the system at a certain time point. An object chart is a snapshot of a class chart at a certain time point.

(3) component diagram (Component diagram)

A component diagram shows the organization of a group of components and their dependencies. The construction diagram shows how the system is implemented and how the components in the software system work collaboratively.

(4) Deployment Diagram

The deployment diagram shows the architecture of the physical system during running. The deployment diagram describes the hardware and software that reside on the system.

(5) package diagram

A package diagram depicts the dependencies between packages (a package is a common model element used to organize other model elements ).

2. The behavior diagram contains the following types:

(1) use case diagram

The use case describes how the system works and the services that the system can provide. The use case diagram describes how external participants of the system use the services provided by the system.

(2) activity diagram

The activity diagram shows the activity streams in the system. The activity diagram is usually used to describe different business processes.

(3) status chart

The status chart shows the transition between the status and status of an object. Status charts include status, transition, events, and activities. A status chart is a dynamic view that is especially important for event-driven behavior modeling. In uml2.0, a state chart is called a state machine diagram ).

(4) Cooperation Diagram

A collaboration diagram is a type of interaction diagram, which also includes a sequence diagram. The cooperation diagram highlights the cooperation and interaction between objects. In uml2.0, the cooperation diagram is replaced by the communication diagram (collaboration diagram.

(5) Sequence Chart

A Sequence Chart is an interactive chart. The sequence diagram emphasizes the time sequence in which messages are transmitted between different elements in a system.

9. The main content of the standard modeling language UML can also be summarized into two categories: Static Modeling Mechanism and dynamic modeling mechanism.