Checklist for Project Control
The process control questions concern the definition of the development process and the mechanisms for identifying process problems, correcting process deficiencies, and preventing their recurrence.
- Does the (senior) management have a mechanism for the regular review of the status of the software projects?
- Is the project plan updated each time the status of the project deviates from the plan?
- Is a mechanism used for periodically assessing the software engineering process and implementing indicated improvements?
- Is a mechanism used for regular technical interchanges with the customer?
- Is a mechanism used for ensuring compliance with the software engineering standards?
- Do project managers sign off on their schedule and cost estimates?
- Is a mechanism used for ensuring traceability between the software requirements and top-level design?
- Is a mechanism used for controlling changes to the software requirements?
- Is a mechanism used for ensuring traceability between the top-level and detailed design?
- Are internal software design reviews conducted?
- Is a mechanism used for controlling changes to software design?
- Is a mechanism used for ensuring traceability between the software detailed design and the code?
- Are formal records maintained of unit (module) development progress?
- Are software code reviews conducted?
- Is a mechanism used for controlling changes to the code? Who can make changes and under which conditions?
- Is a mechanism used for verifying that the samples examined by quality assurance are truly representative of the work performed?
- Is there a mechanism for assuring that regression testing is routinely performed?
- Are formal test case reviews conducted?
Boehm, B.W.: Verifying and Validating Software Requirements and Design Specifications. IEEE Software, January 1984.