Software Engineering Notes – Part 2
Software Quality Assurance (SQA)
Software Quality Assurance is a set of planned and systematic activities to ensure that the
developed software meets the required quality standards. It focuses on preventing defects rather
than only detecting them. SQA ensures processes are followed properly so that the final software
becomes reliable, maintainable and efficient.
Objectives of SQA
• Ensure software meets requirements
• Improve software development process
• Minimize defects and failures
• Increase customer satisfaction
• Reduce maintenance cost
SQA Activities
1. Quality Planning – deciding standards and quality policies.
2. Process Definition – defining SDLC, standards and guidelines.
3. Reviews & Audits – formal reviews, walkthroughs and audits.
4. Testing Process Monitoring – ensuring proper testing execution.
5. Defect Tracking – logging, analyzing and preventing issues.
6. Training – educating team on quality practices.
7. Documentation Control – maintaining correct project documents.
Formal Technical Review (FTR)
FTR is a formal review process used to detect errors early in requirements, design, code or testing
documents. It improves quality, reduces cost and enhances team understanding.
FTR Process
1. Preparation – reviewers study documents and prepare checklist.
2. Review Meeting – author presents work and reviewers identify issues.
3. Recording – defects and improvement suggestions are documented.
4. Follow Up – author corrects mistakes and ensures closure.
Software Configuration Management (SCM)
SCM is the process of identifying, organizing and controlling changes in software to maintain
integrity and consistency throughout its lifecycle. It ensures that the right version of software and
documents are always available.
Configuration Items (CI)
CIs are components that need to be controlled and managed. Examples include: SRS, design
documents, source code, test cases, user manuals and project plans.
Baseline
A baseline is an officially approved version of a software or document that becomes a reference
point. Once baselined, changes can only be made through formal change control.
Version Control
Version control manages multiple versions of software and documents. It helps track changes,
prevent conflicts, restore previous versions and support teamwork. Tools include Git and SVN.
Change Control Process (Very Important)
1. Change Request Submission – raised by user or developer.
2. Impact Analysis – analyze cost, risk, effort and affected modules.
3. Review by Change Control Board (CCB) – approve or reject.
4. Implementation – apply approved changes.
5. Testing – perform regression testing.
6. Version Update – release new controlled version.
Software Maintenance
Software maintenance refers to all activities performed after software delivery to fix defects,
improve performance or adapt to new environments. It consumes around 60–70% of total software
cost.
Types of Maintenance
1. Corrective Maintenance: Fixing defects and errors found after delivery.
2. Adaptive Maintenance: Modifying software due to environmental changes like OS upgrades,
new hardware or database changes.
3. Perfective Maintenance: Improving system performance, adding features or enhancing
usability.
4. Preventive Maintenance: Improving software structure, refactoring code and reducing
complexity to prevent future problems.