UML Analysis and Design Overview

The use-case requirements analysis obtained, glossary, supplementary specifications drawn design model, architectural model schema document
Insert picture description here
discrimination analysis and design:
Insert picture description here
architecture:
Insert picture description here
4 + 1 views
Insert picture description here
analysis and architecture workflow
Insert picture description here
Insert picture description here
analysis and design of a case driven
by Example implemented
Insert picture description here
iterative Development

4 + 1 view
Logical view: Logical view
is mainly used to describe the functional requirements of the system, that is, the service provided by the system to the end user. In the logical view, the system is decomposed into a series of functional abstraction, functional decomposition and functional analysis Problem Definition. In object-oriented technology, through abstraction, encapsulation, and inheritance, the object model can be used to represent the logical view, and the class diagram can be used to describe the logical view.

Development view (Development / Module View) Development view is mainly used to describe the organization and management of software modules (through a library or subsystem). Serve software programmers, and facilitate subsequent design and implementation. It is described by the model diagram and subsystem diagram of the system input-output relationship. Consider the internal requirements of the software: ease of development, possibility of reuse, versatility, limitations, etc.

The process attempts to focus on the operating characteristics of the system, focusing on non-functional requirements (performance, availability). Serve system integrators to facilitate subsequent performance testing. Emphasis on concurrency, distribution, integration, robustness (fault tolerance), scalability, throughput, etc. Define in which thread (Thread) the specific operation of each class in the logical view is performed.

The physical view attempts to describe the hardware configuration. Serve system engineering personnel, solve the system topology, system installation, communication and other issues. Mainly consider how to map software to hardware, and also consider system performance, scale, reliability, etc.

The logical view and development view are mainly used to describe the static structure of the system. Process view and physical view are mainly used to describe the dynamic structure of the system. Not every system must draw 5 views, but each has its own focus

Scenes (Scenarios) Scenes are used to describe the interrelationships between components, and organically connect the four views. You can describe the component relationships in a particular view, or you can describe the component relationships between different views. Both text and graphic representations are available.

202 original articles published · Like 13 · Visitor 7427

Guess you like

Origin blog.csdn.net/qq_43410618/article/details/105571994