Introduction to the core workflows in Rup

There are 9 core workflows in Rup, divided into 6 core process workflows (core processes workflows) and 3 core support workflows (cores supporting workflows). Although the 6 core process workflows may be reminiscent of several phases of the traditional waterfall model, it should be noted that the phases in the iteration are completely different, and that these workflows are accessed again and again throughout the lifecycle. 9 Core workflows are used alternately in the project, repeating each iteration with different emphasis and intensity.

1. Business Modeling (Business modeling)

Business modeling workflows Describe how to develop an idea for a new target organization and define the process, roles, and responsibilities of the organization in the business use case model and the business object model.

2. Demand (Requirements)

The goal of the requirements workflow is to describe what the system should do and to enable developers and users to agree on this description. In order to achieve this goal, it is necessary to extract, organize and document the required functions and constraints, and the most important thing is to understand the definition and scope of the problem solved by the system.

3. Analysis and Design (analyzing & Designing)

The analysis and design workflow transforms the requirement into the future system design, develops a robust structure for the system and adjusts the design to match the implementation environment, optimizes its performance. The result of the analysis design is a design model and an optional analysis model. The design model is the abstraction of the source code, which consists of a design class and some descriptions. The design class is organized into design packages (Package) and design subsystems (subsystem) with good interfaces, while the description shows how the objects of the class work together to implement the function of the use case. The design activity takes the architecture design as the center, the architecture is expressed by several structural views, the structure view is the abstraction and simplification of the whole design, the view omits some details, and makes the important features more clear. Architecture is not only the bearer medium of good design model, but also can improve the quality of the created model in the development of the system.

4. Implementation (Implementation)

The purpose of implementing workflow is to define the organization structure of code in the form of hierarchical subsystem; Implement classes and objects in the form of components (source files, binaries, executables), test the developed components as units, and integrate the results produced by a single developer (or team) into an executable system.

5. Tests (Test)

Test workflows Verify the interaction between objects, validate the correct integration of all components in the software, verify that all requirements are properly implemented, identify and verify that defects are presented and processed before the software is deployed. RUP proposes an iterative approach that means testing throughout the project to detect defects as early as possible, fundamentally reducing the cost of modifying defects. Tests are similar to three-dimensional models, ranging from reliability, functionality, and system performance.

6. Deployment (Deployment)

The purpose of the deployment workflow is to build the version successfully and distribute the software to end users. Deployment workflows describe activities that are relevant to ensuring that software products are available to end users, including: software packaging, generating products outside the software itself, installing software, and providing assistance to users. In some cases, it may also include planning and conducting beta test releases, porting existing software and data, and formal acceptance.

7. Configuration and changes management (Configuration & Change Management)

The configuration and Change management workflow depicts how to control a large number of products in a project composed of multiple members. The configuration and Change Management workflow provides guidelines for managing multiple variants in an evolving system and tracking versions during software creation. Workflows describe how to manage concurrent development, distributed development, and how to automate the creation of projects. At the same time, it also expounds the reasons for the product modification, the time, the personnel maintain audit records.

8. Projects Management (Project Management)

Software project management balances all possible conflicting goals, manages risks, overcomes constraints, and delivers successful products to users. Its objectives include providing a framework for project management, providing practical guidelines for planning, staffing, implementation, and monitoring projects, and providing a framework for managing risk.

9. Environment (Environment)

The purpose of the environmental workflow is to provide a software development environment, including processes and tools, to software development organizations. The environmental workflow focuses on the activities required to configure the project, as well as the activities that develop project specifications, providing step-by-step instructions and information on how to implement the process in your organization.