General Software Project Development Process Specification (IV)-control and end stage

 

Control phase 

 

Figure 6-1 tasks and artifacts in the control phase

 

• Risk Management

Risks should be monitored during development, and the risk list should be regularly checked, updated, and released.

 

• Quality Management

1) Review

Review is an important part of quality assurance. In principle, each important task or stage must be reviewed before it ends, such as Scheme Review, Plan Review, Requirement Review, design review andCodeThe review result determines whether the work is approved, whether the work needs to be modified or redone. The review result is published in the form of the review report.

The review report includes:

 

Basic Information	Review subject, time, submitted by, reviewer, etc.
Review content	Review content list and description
Q & A records	Important Q & A records during review
Conclusion	The overall review results, such: Completely passed, no modification required Basically passed. A small amount of modifications are required, but no review is required. Generally passed. Some modifications are required before review. If the application fails, a major modification is required. You must review the application later.
Review comments	Comments and suggestions based on the review conclusions

Table 7-1 Review Report

 

2) test

Testing is the most direct and effective quality assurance measure for constructed products. After testing, you must submit the test report.

 

• Change management

There are often many changes in the development process, such as requirement changes, design changes, or personnel changes. These changes usually affect the development progress. Therefore, we need to track the changes and their handling processes, and finally report the handling results of the changes.

The Change Handling report includes:

 

Basic Information	Change subject, occurrence time, etc.
Details	Detailed description of a change
Change Handling	Change Handling Methods and Procedures
Processing result	Change Handling result
Change Impact	Impact of changes on projects

Table 7-2 Change Handling report

 

• Progress Monitoring

The project progress meeting is an effective measure to understand the actual progress of the project. It reviews the work report, solves the problems encountered, and plans the next step:

The work report includes:

1. 1. Basic information:Reporter, reporting time, and working hours
   2. Work Condition:Finished work and unfinished work
   3. Problems:Obstacles encountered at work
   4. Work plan:Next work plan

 

Another important topic of the project progress meeting is to review the progress table to understand the differences between the actual progress of the project and the planned progress. It provides an important basis for schedule adjustment and resource allocation.

 

• Measurement

In the project development process, collecting some key measurements is helpful for understanding the project status and making project decisions. It also provides historical data reference for future projects. Each measurement must generate and archive a measurement report.

The content of the measurement report includes:

1. Basic information, including measurement subject, measurement time, surveyors, etc.
2. Measurement content and measurement value
3. Measurement Analysis

 

End Stage

Figure 7-1 tasks and artifacts in the control phase

 

• Product Testing

Because the product is about to be accepted and released, the product must be fully tested. The product test is stricter than other tests. The product can be released only when the product quality meets the release requirements. The product quality is reflected in the test report.

 

• RCRelease

The release of RC allows users to experience and collect feedback to prepare for product acceptance. After the RC version is released, there should be no major changes to the product. Generally, this is only a partial adjustment of the interface.

 

• Compile user documents

For different user roles, prepare the corresponding user documents, provide the "installation and maintenance Guide" for managers, and compile the "product user manual" for common users.

The installation and maintenance Guide includes:

1. 1. Product components
   2. Product deployment architecture
   3. Installation, configuration, and uninstallation steps
   4. Start, stop, and restart
   5. Other operations: log, backup, and Restoration

 

The product user manual includes:

1. Product Introduction
2. Introduction to various functions
3. Use Cases to describe the usage and operation steps of each function

 

• Product usage training

For software products developed for specific customers, users must be trained on product usage before release. Before training, you must deploy the operating environment, compile training materials, and organize training meetings.

 

• Product acceptance

For software products developed for specific customers, they are generally accepted one by one according to the signed development contract, product plan, and other terms. During the acceptance, users usually perform acceptance test cases.

 

• Final revision

After the product acceptance is passed, make the final revision to the product before it is officially released, which may include:

1. 1. Development document revision
   2. User document revision
   3. Code sorting

 

• Official version released

The release of the official version marks the end of the development phase. The product enters the maintenance phase from now on. Some preparations may be made before the official release, such as data migration and environment configuration.

• Project Summary

After the project is completed, the work of the entire project development stage should be summarized, exchanged experiences, learned experiences and lessons, and archived as the project summary report.

The project summary report includes:

1. 1. Overall rating
   2. Cost and Benefit Summary
   3. Important experiences
   4. Management Summary
   5. Technical Summary

 

Coming soon:General Software Project Development Process Specification (5) -- Conclusion

 

Codeproject