Four Phases of Software Process in RUP
- Inception phase: Build a business model for the system and determine the project's boundaries
- Elaboration phase: Establish engineering plan and rational architecture
- Build phase: build system
- Handover Phase: Delivering the system to the end user
An evaluation is performed at the end of each stage to determine whether the goals for that stage have been met. If the assessment results are satisfactory, the project may be allowed to proceed to the next phase.
Basic Features of RUP
1. Use case-driven:
Try to describe the user's descriptive needs with use cases. (In this way, user needs can be better understood, and secondly, users can confirm the needs through use cases.) The use case description requirements are also relatively clear.
But some dependencies may not be described in the use case, which requires some other related documents to record these dependencies. In actual projects, use cases can be used as an important basis for signing summer contracts, but sometimes they cannot be used as the only basis.
1. Architecture-centric:
that is, to conduct architecture design based on baseline (that is, initially standard) requirements to form a prototype key output.
At the same time, in the architecture design, it is very important to componentize the elements in the architecture so that they can be used in future products, so the architecture is not a simple prototype product 2. Iterative development: that is, iterative
software
cycle Carry out development, each iteration, complete a part of the requirements, so that the third party and the development organization can recognize the developed product earlier, in order to prepare for changes in requirements. And help to better confirm and track the needs. At the same time, iterative development can better guarantee the quality of the product.
Note that the requirements selected for each iteration must follow certain rules, for example, select risky or unknown functional items for early iterations.
rup 4+1 view
