UP has three axiom:
Use examples and risk drive architecture center iterations and increments
The use case is that the method of capturing the needs is not therefore, we can say that UP is a demand drive.
Risk is another driver, so if you don't take the initiative to attack risks, the risk will take the initiative to attack you. UP constructs through risk analysis prediction software. However, this is the work of project managers and architects.
The UP transmission method for developing software systems is a system architecture that develops and evolves a robust system. The architecture describes the strategy: how the system is divided into components, how these components interact and deploy on hardware. Obviously, the high-quality system architecture will produce high quality systems, rather than rarely planning, the collection of source code together.
Each iteration contains all the elements of the normal software item:
Planning analysis and design construction integration and test internal or external release
In each iteration, there are five core workflows, which means what you need to do and what work skills are needed. In addition to these five core workflows, there are other workflows. Such as plans, assessments, and any work related to specific iterations. However, UP does not include these. Five workflows are:
Demand --- What should be analyzed in the capture system --- Refining and Structured Demand Design --- System Architecture Realization Realization --- Construction Software Test --- Whether to authenticate if you expect to work
The above source << UML AND The Unified Process Practical Object-Oriented Analysis & Design >> Chinese version (Machinery Industry Press)
