Requirements Analysis & Traceability Matrix

Lecture 14 covers requirements analysis, prioritization frameworks, and the Requirements Traceability Matrix (RTM). Because development resources are finite, project managers must prioritize candidate requirements collaboratively with stakeholders. The lecture explores prioritization models including MoSCoW (Must have, Should have, Could have, Won't have), Kano model, and value-cost matrices. Students analyze the Requirements Traceability Matrix as a bi-directional auditing tool that links individual user requirements forward to architectural designs, source code modules, and test verification cases, ensuring full verification and preventing gold-plating. Reviewing the accompanying lecture handouts and conceptual diagrams reinforces understanding of project monitoring, earned value analysis, and quality assurance. Consistent evaluation of planning templates, estimation equations, and decomposition hierarchies ensures robust preparation for academic assessments. Students investigate the role of the Software Development Plan in synchronizing development activities across multidisciplinary engineering teams. The discussion highlights how requirements traceability matrices prevent scope creep and ensure adherence to agreed software specifications. Key concepts such as configuration item identification, version control baselines, and formal change control board procedures are thoroughly analyzed. The lecture details algorithmic cost estimation models including COCOMO and Function Point Analysis to produce reliable effort forecasts. Structured decomposition methods are demonstrated using the Work Breakdown Structure to enforce the comprehensive one hundred percent rule. Network diagramming techniques such as CPM and PERT provide deterministic and probabilistic insights into critical path float times. Risk mitigation, monitoring, and management plans are formulated to identify technical, operational, and business exposure early in the lifecycle. Software quality assurance audits and formal technical reviews are presented as indispensable instruments for defect detection and process compliance. Organizational structures, including functional, projectized, and matrix configurations, are contrasted regarding project manager authority and team accountability. Team dynamics and collaborative leadership styles are analyzed to overcome Brooks's Law and foster high-performing software development cultures. The curriculum traces the evolutionary transition from traditional linear sequential lifecycles to iterative and risk-driven development paradigms. Practical guidance on utilizing project management software tools like Microsoft Project streamlines baseline tracking and resource leveling.