UML/rose learning notes Series 1: modeling principles and concepts

I. modeling principles

1. Choosing what model to create has a profound impact on how to solve the problem and how to form a solution.

2. Each model can be expressed at different precision levels.

3. The best model is associated with reality.

4. A single model is inadequate. It is best to process each important system with a set of almost independent models.

 

Ii. Concepts

1. Unified Modeling Language (UML) is a standard language for Drawing Software blueprints.

You can use UML to visualize, detail, construct, and document the products of software-intensive systems.

2. From enterprise information systems to web-based distributed applications, even strict embedded systems are suitable for UML modeling.

3. UML is a visual constructor language that can be used to describe in detail.

4. There are four stages in the software development lifecycle:

A. Initial Stage: After developing the development idea, we must at least lay a sufficient foundation internally to ensure that the development can enter the refinement stage.

B. refinement: Define an imaginary product and its architecture.

C. Construction: In this case, the software is developed from an executable architecture baseline to a device handed over to the user.

D. Hand over: At this time, the software should be interacted with the user. At this stage, the software development process rarely ends, and we need to continue to improve the system, eradicate errors, and increase the number early.

Features that cannot be implemented during release.