Software Configuration Management (SCM)

Lecture 33 of CS605 Software Engineering - II introduces Software Configuration Management (SCM) as an essential umbrella discipline that manages the evolutionary changes software inevitably undergoes throughout its lifecycle. The lecture defines the core concepts of SCM: Software Configuration Items (SCIs)—including requirements documents, architecture models, source code files, test suites, and user manuals—and Baselines, which represent formally reviewed and agreed-upon specifications that serve as the basis for further development. Once an SCI becomes part of a baseline, changes can only be introduced through formal change control procedures. Students study the four primary operational activities of SCM: Configuration Identification, Configuration Control (governing change requests), Configuration Status Accounting (reporting what changes occurred, when, and by whom), and Configuration Audits (verifying physical and functional conformance before software delivery). The curriculum systematically aligns practical industry development workflows with formal IEEE standards and CMMI process maturity levels. Reviewing the accompanying lecture handouts and conceptual diagrams reinforces understanding of project monitoring, statistical process control, and configuration baselines. Consistent evaluation of planning templates, estimation equations, and decomposition hierarchies ensures robust preparation for academic assessments. Students investigate the role of software process engineering in synchronizing development activities across multidisciplinary engineering teams. The discussion highlights how requirements traceability matrices prevent scope creep and ensure strict adherence to customer 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 Function Point Analysis to produce reliable effort and duration forecasts. Structured decomposition methods are demonstrated using task networks and PERT charts to evaluate critical path scheduling and project float. Network diagramming techniques provide deterministic and probabilistic insights into project milestones and resource dependencies. Risk mitigation, monitoring, and management plans are formulated to identify technical, operational, and commercial 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 democratic decentralized, controlled decentralized, and controlled centralized teams, are contrasted regarding productivity.