[Project management] RUP content arrangement

The relevant content of RUP is organized as follows: (continuous update and supplement)

table of Contents

definition

Key concept

Three characteristics

Core workflow

Ten elements

Related views


definition

RUP (Rational Unified Process), unified software development process, unified software process is an object-oriented and network-based program development methodology. RUP describes how to effectively use commercially reliable methods to develop and deploy software. It is a heavyweight process (also known as thick methodology), so it is especially suitable for large software teams to develop large projects.


Key concept

Roles

  • RUP predefines many roles, which describe the job functions and tasks of a person or a development team in project development.

activity

  • It is an independent module with a clear function, reflecting a certain function of the system.

Artifact

  • It is a piece of information generated, created or modified in the course of an activity, and it is also a document of project development.

Other related, check points, templates, work guides, reports, tool guides, etc.


Three characteristics

1. Software development is an iterative process

  1. Initial (Inception): The goal is to establish a business case for the system and determine the boundaries of the project
  2. Elaboration: The goal is to analyze problem areas, establish a sound system structure foundation, prepare project plans, and eliminate the most risky elements in the project.
  3. Construction: All remaining components and application functions are developed and integrated into products, and all functions are tested in detail.
  4. Delivery (Transition): Ensure that the software is available to the end user.

Second, software development is driven by Use Case

Use cases run through the entire software development life cycle. In demand analysis, customers or users describe use cases. In the process of system distribution and system design, designers analyze use cases. In the development and implementation process, developers and programmers implement use cases. During the testing process, testers Test the use case.

Third, software development is centered on Architectural Design.

  1. Framework
  2. Design of public components (Auditing system, Logging system, Exception Handling system, Security system, etc.)
  3. Extensibility
  4. Security
  5. Maintainability
  6. Scalability
  7. Reusability
  8. Operating speed (Performance)

Core workflow

  1. Business modeling (process)
  2. Demand (process)
  3. Analysis and design (process)
  4. Implementation process)
  5. Testing process)
  6. Deployment (process)
  7. Configuration and change management (support)
  8. Project management (support)
  9. Environment (support)

Ten elements

1. Development prospects

  • Prospects as one of the ways to verify future decisions
  • Answer: What are the key terms? (Glossary) What problem are we trying to solve? (Problem statement) Who are the stakeholders? Who are the users? What are their respective needs? What are the characteristics of the product? What are the functional requirements? (Use Cases) What are non-functional requirements? What are the design constraints?

2. Reach the plan

3. Identification and risk reduction

  • Identify and deal with the biggest risks early in the project.
  • Each risk identified by the project team should have a corresponding mitigation or resolution plan.

4. Assign and track tasks

  • Regular project status assessment provides a mechanism for telling, communicating and solving management issues, technical issues, and project risks.
  • Once the team found these obstacles (fences), they assigned a person in charge of all these problems and specified a date for resolution.

5. Check business reasons

  • Decide whether a project is worth investing in, ROI

6. Design component architecture

7. Build and Test

8. Verification and evaluation results

  • The sooner the problem is found, the less problematic it will be. (Original: The sooner you fall behind, the more time you will have to catch up.)

9. Manage and control changes

10. Provide user support


Related views

  • RUP is a process definition platform and a [process framework].
  • Risk-driven, architecture-centric, iterative, and configurable software development process based on Use Case technology.
  • Customize the process specified by RUP, and customize a practical software process suitable for your organization.
  • Iterative development greatly reduces the risk of project development and improves the efficiency of software development.
  • Each phase ends in a major milestone (Major Milestones); each phase is essentially the time span between two milestones. At the end of each stage, an assessment is performed to determine whether the goals of this stage have been met. If the evaluation results are satisfactory, the project can be allowed to enter the next stage.
  • The main purpose of the RUP refinement stage is to construct a working architecture prototype.

 

Guess you like

Origin blog.csdn.net/weixin_43800786/article/details/102726966