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

This article mainly shows you "Why to use UML modeling", the content is easy to understand, clear, hope to help you solve your doubts, the following let the editor lead you to study and learn "Why to use UML modeling" this article.

A brief introduction to UML object-oriented Modeling

Why use UML to model?

What is the model? The model is the abstract simulation and simplification of the shape or state of the real world. the model provides the skeleton and blueprint of the system.

The ◆ model helps to visualize the system according to the actual situation or according to the desired style.

The ◆ model can specify the structure or behavior of the system.

The ◆ model gives a template to guide the construction of the system.

For system users, the software development model describes to them the software developer's understanding of software system requirements. Allowing system users to view the software object model and find the problems in it can prevent developers from making mistakes in the first place.

For software development, the software object model helps them to communicate the requirements of the software and the architecture and function of the system.

For software maintenance and technical supporters, for a long time after the software system starts running, the software object model can help them understand the architecture and function of the program and quickly fix the problems in the software.

Modeling is not only for large software systems, but even a small notebook can benefit from the modeling process.

To

The software life cycle can be divided into planning, requirements analysis, design, coding, testing, operation and maintenance. The software development mode is the framework of the system development, operation and maintenance that spans the whole software life cycle, and gives the relationship between the various stages of the software development activities. Four common development modes are introduced here.

(1) Waterfall model

The waterfall model is also soft as the life cycle model, and its core idea is to simplify the problem according to the corresponding process and separate the implementation of the system function from the design work of the system, so as to facilitate the division of labor and collaboration among projects. that is, structured analysis and design methods are used to separate logical implementation from physical implementation. The waterfall model divides the software life cycle into six stages: project planning, requirements analysis, software design, software implementation, software testing, software operation and maintenance. And set their top-down order, each stage is connected in turn.

The UML waterfall model of UML object-oriented modeling provides a checkpoint for the project to be divided into stages, which is beneficial to the organization and management of personnel in the process of software development. The waterfall model does not pay attention to the subsequent phase until the current phase is completed, which is beneficial to the development of large-scale projects. Then there are some defects. For example, when the development results have not been tested, users can not see the software effect and can not get timely feedback in the development process, which increases the risk of the project development process. Lack of sufficient flexibility for projects with unstable requirements. It is also quite difficult to fully determine all the needs of the system users in the requirements analysis stage.

(2) Fountain model

The fountain model of UML object-oriented modeling is object-driven and user-driven. Used to describe the object-oriented software development process. The fountain model holds that the software development process is from bottom to top, and each stage is overlapped and repeated many times. There are no specific sequence requirements for each development phase and can be carried out interactively. You can supplement any omission in any other development phase at any time during one development phase.

Unlike the waterfall model, the UML fountain model does not start the design activity until the end of the analysis activity. Coding does not begin until the end of the design activity. There is no clear boundary between the various stages of the model. Developers can develop synchronously, which has the advantage of improving the efficiency of software project development and saving development time. However, it also requires a large number of developers in the development process, so it is not conducive to project management. This model requires strict management of documents, which increases the accuracy of audit, especially in the case that all kinds of information, requirements and materials may be added at any time.

(3) component-based development model

The open model based on component in UML object-oriented modeling uses modularization method to modularize the whole system, and reuses one or more components in the component library with the support of certain component model, and constructs the process of application software system development with high speed and high quality by means of combination.

UML component-based development method makes software development easier, and component assembly model leads to software reuse and improves the efficiency of software development. The component assembly model allows multiple projects to be developed simultaneously, reduces the cost, improves maintainability, and can submit software products step by step. However, due to the adoption of self-defined assembly structure standards and the lack of general assembly structure standards, soft risks are introduced. Reusability and software efficiency are difficult to coordinate, and because they rely too much on components, the quality of the component library affects the quality of the product.

(4) XP method

Agile methods. It is a lightweight development method that has sprung up in recent years, which emphasizes adaptability rather than predictability, people-centered rather than process-centered, and attention to change adaptation and human nature.

The XP (eXtremeProgramming) method is one of the most compelling agile methods. It defines a set of core values and methods, eliminates most unnecessary products in the heavy development process, and establishes a progressive development process. This method mixes four activities (analysis, design, coding and testing) in the development phase, and adopts iterative incremental development, feedback correction and repeated testing in the whole process.

The use of simple planning strategy, no need for long-term planning and complex models, short development cycle. Iterative incremental development, feedback correction and repeated testing are used in the whole process. The quality of the software is guaranteed. Can adapt to the ever-changing needs of users and provide users with satisfactory high-quality software.

The above is all the content of the article "Why use UML Modeling". 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.