UML software engineering organization

To use the same development Language (UML) effectively during application development, you must fully understand the UML elements and how these elements are allocated.

1. Characteristics of UML

Unified standards

Object-oriented. Supports object-oriented development of modeling languages

Visualization and strong performance

Independent of processes, UML does not depend on specific software development processes

The concept is clear, the modeling is concise, the graphic structure is clear, easy to grasp and use.

Views in UML

The views in UML include the use case view, logic view (design view), implementation view, process view, and deployment view. This view becomes a 4 + 1 View

 

 

Logical view: Focus on functions, including not only the functions of user courseware, but also the auxiliary function modules required to implement user functions. They may be logical layers and functional modules.

Development View: Focus on packages, including not only source programs, but also third-party sdks and thread mining and class libraries that can be directly used, and the system software or intermediate key on which the developed system runs. There may be a certain ing relationship between the development view and logic confusion. For example, the logic layer is usually mapped to multiple packages.

Processing view: focus on processes, threads, objects, and other runtime concepts. And related issues such as development, synchronization, and communication. The relationship between the view and the development view is processed. The development view focuses on the static dependency of the package during the compilation period. After these programs run, they are displayed as objects, threads, and processes, the view processing focuses on the interaction of these runtime units.

Deployment view: Focus on the runtime libraries and system software on which the target program depends, and how to install or deploy the program to a physical machine. And how to deploy machines and networks to meet software system reliability and scalability requirements. Relationship Between the deployment view and the processing view: handling the dynamic execution of the Target Program in the view, and attaching importance to the static location of the target program in the deployment view, it is an architectural view of the interaction between the integrated oven software system and the entire IT system.

Three UML Components

Common UML diagrams mainly include use case diagram, class digram, sequence daigram, and activity diagram ), statechart machine divisor and deployment divisor.

 

1. Use Case

The writing of user description articles is a reflection of the system's profound understanding of user needs. It is an important basis for later time sequence diagrams and actual development. It can also be used as a basis for project estimation and to measure the efficiency of developers Based on UC complexity and development cycle. Therefore, UC writing standards and their importance.

2 Use case diagram of the design phase

The use case diagram outlines the relationship between roles and systems in the use case, describes the functional requirements of the I system, the interaction between roles and systems, and the system response. It is a good way for customers and developers to fully understand the functions required by the project. It is also the basis and direction for subsequent functional iterations.

Relationship between Class 3 and Class

 

Common relationships between classes include association, generalization, dependency, aggregation, and combination. For detailed differentiation, see section 3.

4 UML modeling activity diagram

The activity diagram describes the rules followed by the sequence of object activities. It focuses on system behaviors rather than system amount processing. The activity diagram can represent and act. The activity diagram is object-oriented.

5 State Diagram of UML modeling

The state chart focuses on the transfer between state machines of Mo aihuisu objects. The basic elements of a status chart include status, transfer, action, self-transfer, combined transfer, power-saving access, node exit, historical status, and concurrent region. Events in status are divided into calls, change Events, events, and signal events.

6. Sequence diagram of UML modeling

A sequence chart is a graph that shows interactions between objects. These objects are arranged in chronological order. The sequence diagram shows the interaction objects and the order of message interaction between objects. The Modeling Elements in the sequence diagram mainly include objects, lifeline, control focus, and messages.

7
UML modeling-collaboration Diagram

A collaboration diagram is a graphical method used to describe the spatial structure of interactions between objects in a given language. It can be analyzed from the definition as follows: the message passing between objects reflects the logical expression of specific use context. The logic of a use scenario may be part of a use case or a control flow. Composition,

Object, message, chain, and other structures

 

8 component diagram of UML modeling

The component diagram describes the main functions of a system from the perspective of the software architecture. Such as subsystems, classes, packages, and components. The most important component to use is reuse. A component chart must be composed of components, components, interfaces, and relationships.

9 deployment diagram of UML modeling

 

The physical relationship between software and hardware components can be handed over, and the component distribution of the processing nodes can be processed. you can use the deployment diagram to display the structure of the runtime system. the configuration and deployment modes of the hardware and software elements of the application can also be communicated. deployment chart structure, nodes, components, node instances, node containers, connections, and so on.

 

Summary

Through the study of UML, I learned that UML plays an important role in software design. It involves the software framework and details, so that the software design is no longer subject to macro control.