Which of the following activities results in change requests?

A change request is a formal proposal to modify any document, deliverable, or baseline. When a product or component fails an inspection, a defect is identified. The recommended action to fix this non-conformance is a "defect repair." This repair work must be formally proposed, approved, and tracked through the project's change control process, thus directly resulting in a change request to authorize the repair.

A. Preventive actions are proactive measures to avoid future issues and may not always require a formal change request unless they alter a project baseline.
B. Inspection is the activity that identifies defects; it is the trigger for a change request, not the resulting action itself.
D. Corrective action is a broad category for realigning project work. Defect repair is a specific, and very common, type of corrective action.

1. Carnegie Mellon University, Software Engineering Institute. (2010). CMMI for Development, Version 1.3 (CMU/SEI-2010-TR-033). Project Monitoring and Control (PMC) Process Area, SG 1, SP 1.7: "Take corrective action... Corrective actions may include replanning... and implementing defect repairs." This links defect repair to corrective actions managed under project control.

2. Fairley, R. E. (2009). Managing and Leading Software Projects. IEEE Computer Society Press. Chapter 11, Software Configuration Management. The text describes the change control process where problem reports (defects) lead to Engineering Change Proposals (change requests) to authorize fixes.

3. University of Toronto. (n.d.). CSC444H1: Software Engineering I Course Notes. Department of Computer Science. Lecture on Quality Assurance. The notes describe the process where a bug/defect report is submitted, which then enters a change management workflow to be prioritized and assigned for repair.