CP4096 Software Quality Assurance Syllabus:
CP4096 Software Quality Assurance Syllabus – Anna University PG Syllabus Regulation 2021
COURSE OBJECTIVES:
Be exposed to the software quality factors, Quality Assurance (SQA) architecture and SQA components.
Understand the integration of SQA components into the project life cycle.
Be familiar with the software quality infrastructure.
Be exposed to the management components of software quality.
Be familiar with the Quality standards, certifications and assessments
UNIT I INTRODUCTION TO SOFTWARE QUALITY & ARCHITECTURE
Need for Software quality – Software quality assurance (SQA) – Software quality factors- McCall’s quality model – SQA system components – Pre project quality components – Development and quality plans.
UNIT II SQA COMPONENTS AND PROJECT LIFE CYCLE
Integrating quality activities in the project life cycle – Reviews – Software Testing – Quality of software maintenance components – Quality assurance for external participants contribution – CASE tools for software quality Management.
UNIT III SOFTWARE QUALITY INFRASTRUCTURE
Procedures and work instructions – Supporting quality devices – Staff training and certification – Corrective and preventive actions – Configuration management – Software change control – Configuration management audit -Documentation control.
UNIT IV SOFTWARE QUALITY MANAGEMENT & METRICS
Project process control – Software quality metrics – Cost of software quality – Classical quality cost model – Extended model – Application and Problems in application of Cost model
UNIT V STANDARDS, CERTIFICATIONS & ASSESSMENTS
Quality management standards – ISO 9001 and ISO 9000-3 –Capability Maturity Models – CMM and CMMI assessment methodologies – Bootstrap methodology – SPICE Project – SQA project process standards – Organization of Quality Assurance – Role of management in SQA – SQA units and other actors in SQA systems.
COURSE OUTCOMES:
CO1: Utilize the concepts of SQA in software development life cycle
CO2: Demonstrate their capability to adopt quality standards.
CO3: Assess the quality of software products.
CO4: Apply the concepts in preparing the quality plan & documents.
CO5: Ensure whether the product meets company’s quality standards and client’s expectations and demands
TOTAL: 45 PERIODS
REFERENCES
1. Daniel Galin, “Software Quality Assurance”, Pearson Publication, 2009.
2. Alan C. Gillies, “Software Quality: Theory and Management”, International Thomson Computer Press, 2011.
3. Kshirasagar Naim and Priyadarshi Tripathy,” Software Testing and Quality Assurance Theory and Practice”, John Wiley & Sons Inc., 2008
4. Mordechai Ben-Menachem “Software Quality: Producing Practical Consistent Software”, International Thompson Computer Press, 2014