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.

  1. Does the (senior) management have a mechanism for the regular review of the status of the software projects?

  2. Is the project plan updated each time the status of the project deviates from the plan?

  3. Is a mechanism used for periodically assessing the software engineering process and implementing indicated improvements?

  4. Is a mechanism used for regular technical interchanges with the customer?

  5. Is a mechanism used for ensuring compliance with the software engineering standards?

  6. Do project managers sign off on their schedule and cost estimates?

  7. Is a mechanism used for ensuring traceability between the software requirements and top-level design?

  8. Is a mechanism used for controlling changes to the software requirements?

  9. Is a mechanism used for ensuring traceability between the top-level and detailed design?

  10. Are internal software design reviews conducted?

  11. Is a mechanism used for controlling changes to software design?

  12. Is a mechanism used for ensuring traceability between the software detailed design and the code?

  13. Are formal records maintained of unit (module) development progress?

  14. Are software code reviews conducted?

  15. Is a mechanism used for controlling changes to the code? Who can make changes and under which conditions?

  16. Is a mechanism used for verifying that the samples examined by quality assurance are truly representative of the work performed?

  17. Is there a mechanism for assuring that regression testing is routinely performed?

  18. Are formal test case reviews conducted?


Literature:

Boehm, B.W.: Verifying and Validating Software Requirements and Design Specifications. IEEE Software, January 1984.