Application of "UML" UML in every stage of software development

First, UML5 connected view

In UML, 5 interconnected views are often used to describe the architecture of a narrative system.

(1) Use Case view (use-case view)

It consists of a use case diagram that describes the system behavior that can be seen by users, analysts and testers.

Finally, the user uses the use case diagram-understand the function of the system to be completed, and confirm whether it meets their requirements.

The analyst uses the use case diagram--describing the user's needs.

The tester uses use-case diagrams to verify that the implemented system conforms to user requirements based on the use case diagram.

(2) Design Views (Logical view)

Includes basic design packages, subsystems, classes, and interfaces. Mainly from the software point of view to describe the narrative system to solve the problems and solutions.

(3) Process view

Primarily for system performance, scalable rows, and throughput.

(4) Implementation view (Implementation view)

The UML implementation view uses class diagrams, package diagrams, object graphs, Sequence diagrams, collaboration diagrams, State diagrams, and activity diagrams to describe the narrative.

The programmer finally implements the system based on the Design view and the process viewport.

(5) Deployment view (Deployment view)

The system hardware topology points are included in various software modules and component modules.

II. application of UML in every stage of software development

The classic software project idea divides the software development into 5 stages: requirement Analysis, system analysis and design, system implementation \ Test and maintenance five stages. There are different applications in UML at all stages. In addition to learning the detailed drawing of each diagram, you should also pay attention to the application of UML diagrams in every stage of the software development process.

Demand

-Use use case diagrams to describe the narrative needs. Analysis --using class diagrams to describe static structures
--using sequence diagram, cooperation diagram, activity diagram, state diagram to describe dynamic behavior

Design -Using class diagrams, packages, to design the interface of the class

Implement--Implement the class in a Phenomenon object language
inheritance and delivery--component diagram, package, deployment diagram
Test --unit test--Descriptions of class diagrams and classes
-- inherit test--Class diagram, package, component diagram, cooperation diagram
-- system test--Example diagram

Application of "UML" UML in every stage of software development