The core workflow of the unified software development process

 

The core workflow of the unified software development process

There are nine core workflows in RUP, which are divided into six core process workflows and three core support workflows (core supporting workflows ). Although the six core process workflows may remind people of several stages in the traditional waterfall model, it should be noted that the stages in the iteration process are completely different, these workflows are accessed again and again throughout the lifecycle. Nine core workflows are used in turn in the project, and repeated with different emphasis and intensity in each iteration.
1. 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 case model and Business Object Model Based on this idea.
2. Requirements)
The goal of a requirement workflow is to describe what the system should do and reach a consensus between developers and users on this description. To achieve this goal, extract, organize, and document the required functions and constraints. The most important thing is to understand the definition and scope of the problems solved by the system.
3. Analysis & Design)
Analysis and Design workflows transform requirements into future system designs, develop a robust structure for the system, adjust the design so that it matches with the implementation environment, and optimize its performance. The analysis design result is a design model and an optional analysis model. A design model is an abstraction of source code. It consists of a design class and some descriptions. The design class is organized into a package with good interfaces and a subsystem. The description shows how the class objects work together to implement the use case function. The design activity is centered on the architecture design. The architecture is expressed by several structural views, which are the abstraction and simplification of the entire design. Some details are omitted in this view, make important features clearer. The architecture is not only a medium for good model design, but also improves the quality of the created model during system development.
4. Implementation)
The purpose of implementing a workflow is to define the code organization structure in the form of a hierarchical subsystem; To implement classes and objects in the form of components (source files, binary files, and executable files; testing the developed components as units and integrating the results produced by a single developer (or group) into an executable system.
5. Test)
The test workflow should verify the interaction between objects, verify the correct integration of all components in the software, and verify that all requirements have been correctly implemented, identify and confirm defects are raised and handled prior to software deployment. The iterative approach proposed by RUP means testing throughout the project, so as to discover defects as early as possible, fundamentally reducing the cost of modifying defects. The test is similar to a three-dimensional model, which can be carried out from the reliability, functionality, and system.
6. Deployment)
The purpose of deploying a workflow is to successfully generate a version and distribute the software to the end user. The deployment workflow describes activities related to ensuring that software products are available to end users, including software packaging, generating products other than the software itself, installing software, and helping users. In some cases, it may also include planning and beta testing, porting existing software and data, and formal acceptance.
7. Configuration and 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 evolutionary system and tracking versions during Software creation. A workflow describes how to manage parallel development, distributed development, and automate Project Creation. At the same time, it also describes the reasons for product modification, the time, and personnel maintenance audit records.
8. Project Management)
Software project management balances various conflicting goals, manages risks, overcomes various constraints, and successfully delivers products that satisfy users. Its goals include: to provide a framework for project management, practical guidelines for planning, staffing, implementation and monitoring of projects, and to provide a framework for management risks.
9. Environment (Environment)
The purpose of an environment workflow is to provide the software development environment, including processes and tools, to the software development organization. Environment workflows focus on the activities required during project configuration. They also support development project standard activities, provide a step-by-step instruction manual, and introduce how to implement the process in an organization.