Requirements Management and CMM Integration

Lecture 36 of CS605 Software Engineering - II examines the Requirements Management Key Process Area (KPA) within the Capability Maturity Model (CMM) Level 2 framework. Requirements management establishes an ongoing, disciplined commitment between the software engineering team and customer stakeholders, ensuring that changes to agreed specifications are systematically reflected in project plans and work products. Students explore the construction of Bidirectional Requirements Traceability Matrices (RTM), which map requirements forward into architectural design components, code modules, and test cases, as well as backward to original business use cases. The lecture illustrates how the RTM enables instant impact analysis when a customer requests a feature modification, allowing managers to identify every affected line of code and test case. The institutionalization of requirements baselines within CMM Level 2 is thoroughly examined. Scholars examine how mistake-proofing mechanisms such as Poka-Yoke can be adapted to software design to eliminate defect injection at the source. System maintenance challenges in legacy enterprise environments are evaluated alongside forward engineering and reverse engineering workflows. The lesson explores Martin Fowler refactoring patterns, demonstrating how code smells are methodically removed while preserving observable behavior. Extract method, move method, and replace temp with query are examined through concrete code refactoring demonstrations. Students study process maturity assessment frameworks, distinguishing between staged and continuous CMMI representations. Key process areas spanning requirements management, project planning, and quantitative process management are systematically demystified. By engaging with solved past papers by Moaaz and Waqar Siddhu, learners gain actionable insights into recurrent university exam questions. Interactive quiz assessments on VU SIGMA facilitate rapid knowledge verification and retention of critical software engineering terminology. Comprehensive coverage of IEEE terminology ensures learners communicate with technical precision across global software engineering organizations. Detailed analysis of software safety hazards highlights the imperative of building fail-safe mechanisms into safety-critical digital infrastructure. Software configuration auditing guarantees that delivered releases conform precisely to authorized engineering specifications and baselines. The strategic role of business process reengineering is evaluated as an instrument for achieving breakthrough improvements in cost and performance.