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

This article mainly introduces what the basic concept of UML is, and it has certain reference value. Interested friends can refer to it. I hope you will gain a lot after reading this article.

Basic concepts of UML:

UMl is a standard graphical modeling language, which is a standard representation of object-oriented analysis and design. The most commonly used tools are MicrosoftOfficeVisio2007.

View

The views of UML in the process of object-oriented software development can be roughly divided into the following five categories:

1. Use case view. The use case view emphasizes the system functionality seen or required from the point of view of external participants (mainly users) of the system.

2. Logical view. The logical view shows how to realize the function of the system from the point of view of static structure and dynamic behavior of the system.

3. Component view. The component view shows the organizational structure of the code components.

4. Concurrent view. The concurrent view shows the concurrency of the system and solves the problems of communication and synchronization in the concurrent system.

5. Configuration view. The configuration view shows the specific deployment of the system. Deployment refers to configuring the system to a physical structure made up of computers and devices.

UML object-oriented software development process:

Unified process (up) has become a popular software development process for constructing object-oriented systems. RUP is a detailed refinement of UP. The following describes which diagrams of UML are used for modeling in business modeling, requirements, design, implementation and testing processes.

1. Business modeling

The object diagram and class diagram of UML are used to represent the concepts and the relationship between concepts in the application field on which the target software system is based. These interrelated concepts make up the domain model. On the one hand, the domain model can help the software project team understand the business background and communicate effectively with business experts; on the other hand, with the continuous progress of the software development phase, the domain model will become the main basis of the software structure. If there is an obvious process processing part in the domain, you can consider using the activity diagram of UML to describe the workflow in the domain and identify the characteristics of concurrency and synchronization in the business process.

two。 Demand

UML's use case view is user-centric and models the functional requirements of the system. By identifying the actors outside the boundaries of the system and their goals, the system determines what functions the system wants to provide to users and describes them with use cases. Use cases can be described in text form or UML activity diagrams, and UML use case diagrams can be used to represent the relationship between actors and use cases, and between use cases and use cases. UML sequence diagram is used to describe the system events between the participant and the system. The system operation contract is used to describe the changes in the internal state of the system caused by the occurrence of system events. If the target system is large and there are many use cases, you can use packages to manage and organize these use cases, organize closely related use cases into the same package, and use UML package diagrams to describe these packages and their relationships.

3. Design

In the process of object-oriented software development, UML expands the results of the analysis phase into technical solutions, including software architecture design and effort implementation design. UML package diagram is used to design the software architecture to depict the hierarchical and block ideas of the system. Use UML collaboration diagrams or sequence diagrams to find the classes and their responsibilities that participate in the use case implementation, one of which comes from the domain model, and the other is the new classes added by the software implementation, which provide basic services for the software, such as the classes responsible for database persistence. Use UML class diagrams to describe these classes and their relationships, which belong to different packages of the architecture. Use UML state diagrams to describe classes with complex lifecycle behavior. UML activity diagrams are used to describe complex algorithm processes and business processes involving multiple objects, and activity diagrams are especially suitable for describing concurrency and synchronization in the process. In addition, UML component diagrams can be used to describe the static structure and management of software code. The UML deployment diagram describes the topology of the hardware and the mapping of software and hardware.

4. Realize

Code that converts the designed class into some kind of object-oriented programming language.

5. test

Impenetrable test teams use different UML diagrams as the basis for their work: unit tests use class diagrams and class specifications, integration tests typically use component diagrams and collaboration diagrams, and validation tests use use case diagrams and use case text descriptions to verify that the behavior of the system meets the definitions in these diagrams.

Thank you for reading this article carefully. I hope the article "what is the basic concept of UML" shared by the editor will be helpful to you. At the same time, I also hope you will support us and pay attention to the industry information channel. More related knowledge is waiting for you to learn!

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.