System Structure Using UML planning software

To plan an excellent system, the most important step is to complete the "systemarchitecture" of the system to be designed, especially when using the latest components and distributed system structure analysis, the system structure analysis is excellent or not, which determines the success or failure of the system 90%. It can be seen how important the system structure is. Based on actual experience, a set of good "System Structure" must at least implement the following five important development strategies:
A. Software System Organization: including the overall system organization and component organization
B. selection and analysis of structural elements and interfaces in the system
C. Behavior Model Based on Structural Elements
D. Large subsystems designed based on the progressive composition of basic structural elements and behavior Elements
E. Organization of software application structures exported from structural styles: Cooperation and composition of static and dynamic elements and interfaces, static and dynamic elements, etc.

Therefore, the excellent system software structure is particularly important in the development of components (comatrix) and the Internet era. Simply put, a well-planned design blueprint is built on the building's taste to be extraordinary. The same is true for software development. The structure design of an excellent system blueprint allows the ever-changing software development technology to be used in system development, rather than chasing technology forever.

Therefore, the original design company Rational Software of UML proposed a set of standard software structure concepts: "4 + 1" View (4 + 1 view)

This structure has become an indispensable concept in software development. The so-called "4 + 1" View (4 + 1 View) refers to the "logical view) "," Implementation View "," process view "," deployment View ", and" usecase View )",.
(1) logical view: express the results of software design with the concept of object-oriented. The logical view mainly describes the detailed design for implementing the internal functional work of the system. These designs include static structures and dynamic behaviors.
(2) Implementation view: displays in which module or component the logically designed object is implemented using modules or components.
(3) process view: a typical distributed system generally contains many processes or threads. The process view is a program that describes the overall operation of components in a system.
(4) Deployment view: Deployment view refers to the actual status of a process or thread mapped to a host or device in a network environment. That is, to describe the connection between system hardware or devices and the configuration of software programs.
(5) usecase view: usecase view is the core of UML and mainly used to describe the functional requirements of the system, find the use case and role in the system, and use the use case model to fully express the needs of software functions.

When we enter the new era of Object/component Wizard software planning, the software development process is no longer like the traditional waterfall process (waterfall ). Instead, it is converted to an iterative process ).

This is a big change in the structure analysis of software systems, because waterfall software development has been followed by most system analysts and software designers for more than two decades.
However, after years of practical experience, many people have found that waterfall software development cannot fully meet the design requirements. Therefore, iterative processes are increasingly adopted, especially for large software projects. To put it simply, the main planning method of "iterative process" can be described in 16 words:
Analysis, Design, practice, and execution

That is, the entire software development process is divided into several cycles, and each cycle can be considered as a small waterfall process, in addition, the "iterative process" emphasizes that executable results should be generated at the end of each cycle.
Each cycle is based on the results of the previous cycle, and other new requirements are added until all software requirements are met, this effectively reduces project risks.

UML itself implies iterative and progressive processes. Because UML is the use case wizard, you can plan the execution cycle of the system project based on the use case, so that the difficult use cases can be completed at an earlier execution cycle, design the main structure of the software system as soon as possible.