Top 10 elements of RUP

Recently, I began to summarize some of my experiences in system analysis. I have some understanding from others, and I am a process of improving and reviewing myself.

Prerequisites:

I. Typical software engineering ideas divide software development into the following five stages:

1. Demand Analysis (Requirements Capture) stage,

2 System Analysis and Design stage,

3. Implementation stage,

4. Test phase

5. Maintenance (Maintenance) phase.

 

2. There are 5 types of static diagrams in UML: use case diagram, class diagram, object diagram, component diagram, and configuration diagram.

There are four types of dynamic graphs: Time Sequence diagram, collaboration diagram, state diagram, and activity diagram.

 

3. Rational Unified Process is a set of software engineering methods. At the same time, it is also a documented Software Engineering Product. All the implementation details and Method Guidance of the RUP/are integrated on a single Cd as WEB documents, developed, maintained, and sold by Rational. The current version is 5.0.RUP. It is a framework of software engineering methods and can be tailored to the actual situation of each organization, and the project scale to crop and modify the RUP to work out the necessary software engineering process.
By leveraging the advantages of multiple development models, RUP is highly operable and practical. As soon as it was launched, it was quickly recognized by the industry. More and more organizations are using it as a software development model framework.

4. RUP can be described using two-dimensional coordinates. The horizontal axis is organized by time, which is a feature of the lifecycle of a process, reflecting the dynamic structure of the development process. The vertical axis is organized by content as a natural logical activity, reflecting the static structure of the development process.

Official start

 

Top 10 elements of RUP

1. Develop a prospect

A clear prospect is the key to developing a product that meets real needs.

The prospect captures the main points of the RUP requirement process: analyzing problems, understanding requirements, defining systems, and managing requirements when requirements change.

2. Make a plan
"The product quality is only as good as the product plan ."
In RUP, the software development plan (SDP) integrates the various information required to manage the project, and may include some separate content for development in the pilot phase. SDP must be maintained and updated throughout the project.

SDP defines the project schedule (including the project plan and iteration plan) and resource requirements (resources and tools), and can track the project progress based on the project schedule. It also guides the planning of other process components: project Organization, requirement Management Plan, configuration management plan, problem solving plan, QA plan, test plan, evaluation plan and product acceptance plan.

3. Identify and reduce risks

One of the main points of RUP is to identify and handle the greatest risks early in the project. Each risk identified by the project team should have a corresponding mitigation or solution plan. The risk list should be used both as a planning tool for project activities and as the basis for determining iterations.

4. Allocate and track tasks
One thing that is important in any project is that continuous analysis comes from objective data of ongoing activities and evolving products. In RUP, regular project status evaluations provide mechanisms for describing, communicating, and solving management issues, technical issues, and project risks. Once the team finds these obstacles, they designate a person in charge for all these problems and specify the resolution date. The progress should be tracked regularly. Updates should be released if necessary.

The "snapshots" of these projects highlight issues that need to be noticed by management. With time changes/although the cycle may change, regular evaluations enable managers to capture the history of the project and eliminate any obstacles or bottlenecks that limit the progress.

5. Check business reasons

Business reasons provide necessary information from a business perspective to determine whether a project is worth investing. Business reasons can also help develop an economic plan needed to achieve project prospects. It provides reasons for project implementation and establishes economic constraints. When the project continues, analysts use business reasons to correctly estimate the ROI (Return on Investment ).

6. Design component architecture
In RUP, the architecture of a software system refers to the organization or structure of key components of a system. components interact with each other through interfaces, while components are composed of smaller components and interfaces. That is, what is the main part? How are they combined?

RUP provides a system method for designing, developing, and verifying the architecture. The analysis and design process involves the following steps: defining candidate architectures, refined architectures, analyzing behavior (Case Analysis), and designing components.

7. build and test products incrementally

The main point of the implementation and testing process in the RUP is to incrementally code, build, and test system components throughout the project lifecycle, and generate executable versions after each iteration ends. In the later stage of refinement, a framework prototype can be used for evaluation. If necessary, it can include a user interface prototype. Then, in each iteration of the build phase, components are constantly integrated into executable and tested versions, constantly evolving to the final product. Dynamic and timely configuration management and review activities are also the key elements of this basic process.

8. verification and evaluation results

As the name suggests, the iterative evaluation of RUP captures the iterative results. The evaluation determines the degree to which the iteration meets the evaluation criteria, and also includes lessons learned and improvement of the implementation process.
Based on the project scale, risks, and iteration characteristics, the evaluation can be a simple record of the demonstration and its results, or a complete and formal Test Review Record.

The key here is to focus on both process issues and product issues. The sooner you discover the problem, the more trouble you have.

9. manage and control changes

The main point of the configuration and change management process of RUP is to manage and control the scale of the project when a change occurs and run through the entire lifecycle. The goal is to consider all user needs, meet as much as possible, and deliver qualified products in a timely manner.

10. provide user support
In RUP, the key aspect of the deployment process is to package and deliver products while delivering any necessary material that helps end users learn, use, and maintain the product.
The project team should provide users with at least one User Guide (maybe through online help), and there may be an installation guide and release notes.
Based on the complexity of the product, users may need training materials. Finally, a Bill of Materials (BOM) is used to clearly record the Materials to be delivered with the product.

Several core workflows during development:

1. Requirement capture Workflow

2. Analysis workflow

3. · implement workflow

4. Test the Workflow