Software Quality Assurance (SQA)

Lecture 27 of CS605 Software Engineering - II demystifies Software Quality Assurance (SQA) as an umbrella discipline that ensures software conforms to established organizational standards and customer requirements. The lecture contrasts Quality Control (QC)—the tactical, operational activities such as testing aimed at finding defects—with Quality Assurance (QA)—the strategic, process-oriented governance aimed at preventing defects through structured methodologies and continuous process improvement. Students examine the role of an independent SQA team, which operates outside direct project management reporting lines to guarantee unbiased compliance monitoring. The components of an SQA Plan aligned with IEEE 730 standards are explored, including standards definition, audit schedules, record-keeping, problem reporting, and management escalation protocols. Special attention is given to quality cost models, categorizing quality expenditures into prevention costs, appraisal costs, internal failure costs, and catastrophic external failure costs. 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. Team dynamics and collaborative leadership styles are analyzed to overcome communication bottlenecks and foster high-performing development cultures.