NATIONAL UNIVERSITY
of Computer & Emerging Sciences, Lahore
FAST School of Computing
SE3002 – Software Quality Engineering
FALL 2024
Instructor Name: Dr. Ali Afzal Malik TA Name: Tayyab Anees
Email address: [Link]@[Link] Email address: l215756@[Link]
Office Location/Number: C-145 (GF, CE Building) Office Location: Library Class Room
Office Hours: Wednesdays 1130 - 1230 Office Hours: Tuesdays 1130 - 1230
Course Information
Program: BS (SE)
Credit Hours: 3
Type: Core
Pre-requisite: SE1001 Introduction to Software Engineering
Course Website: Google Classroom
Class Meeting Days: Wednesday and Friday
Class Meeting Time: 0830 – 0950 (BSE-5A); 1000 – 1120 (BSE-5B)
Class Venue: F/NB-311
Course Objectives
This course provides a comprehensive coverage of different aspects of software quality assurance
(SQA). Apart from the conventional discussion on SQA activities during the project life-cycle (e.g.
reviews, testing, etc.), it includes a discussion about pre-project components (e.g. contract review),
infrastructure components (e.g. configuration management), and management components (e.g.
quality metrics).
1
Course Learning Outcomes (CLOs)
CLO # CLO description BT Cognitive Level PLO #
Explain different views of quality
CLO 1 2 (Understanding) PLO 1
Describe the fundamentals of measurement theory
CLO 2 2 (Understanding) PLO 1
Understand the use of software quality related metrics in
CLO 3 2 (Understanding) PLO 2
Software Quality Engineering
Use quality management tools
CLO 4 3 (Applying) PLO 5
Relevant Program Learning Outcomes (PLOs)
PLO # PLO Name PLO Description
To apply knowledge of mathematics, science, engineering fundamentals and
PLO 1 Software
an engineering specialization to the solution of complex Software Engineering
Engineering
problems.
Knowledge
Identify, formulate, research literature, and analyze complex computational
PLO 2 Problem Analysis
problems, reaching substantiated conclusions using first principles of
mathematics, natural sciences, computing, and Software Engineering.
Create, select, and apply appropriate techniques, resources and modern
PLO 5 Modern Tool Usage
Computer-Aided Software Engineering (CASE) tools, including prediction and
modelling for complex computing problems.
2
Reference Material
1. Software Quality Assurance: From Theory to Implementation, Daniel Galin, 1st Edition,
Pearson Education, 2004.
2. Software Quality Engineering: Testing, Quality Assurance, and Quantifiable Improvement,
Jeff Tian, 1st Edition, Wiley-IEEE Computer Society Press, 2005.
3. Software Engineering: A Practitioner’s Approach, Roger S. Pressman, 6th Edition, McGraw-
Hill, 2005.
4. Software Metrics: A Rigorous & Practical Approach, Norman E. Fenton and Shari Lawrence
Pfleeger, 2nd Edition, PWS Publishing Company, 1997.
Course Grading (Tentative)
● Assignments 10%
● Quizzes: 10%
● Project: 10%
● Midterm Exams: 30%
● Final Exam: 40%
Absolute grading scheme will be used for this course.
3
Tentative Course Schedule
1
S# Topic Week(s) Readings
1 INTRODUCTION AND OVERVIEW 1 [1] Chapter 1
Definitions of Software, Quality, and
Engineering
History of SE
Role of Software
Importance of Software Quality
2 BASIC SOFTWARE QUALITY 2 [1] Chapter 2
CONCEPTS
[3] Chapter 26 (26.1)
Software Quality
Software Quality Problems & Causes
Software Quality Assurance
Software Quality Control
3 SOFTWARE QUALITY FACTORS 2, 3 [1] Chapter 3
McCall’s Factor Model - Operation
Factors, Revision Factors, Transition
Factors
Alternative Factor Models
4 COMPONENTS OF SQA SYSTEM 3 [1] Chapter 4
SQA Architecture
Pre-project Components
Life-cycle Components
Infrastructure Components
Management Components
Standards-related Components
Human Components
Considerations Affecting Use of SQA
System Components
5 INTEGRATION OF SQA ACTIVITIES 4, 5 [1] Chapter 7
Software Processes [3] Chapters 3 and 4
1Numbers in square brackets correspond to books numbered in the “Reference Material”
section.
4
Factors Affecting Intensity of SQA
Activities
Verification, Validation, and
Qualification
Software Defect Removal
Effectiveness and Cost Model
6 PRE-PROJECT COMPONENTS 5 [1] Chapter 5
Contract Review
MIDTERM EXAM 1 6
7 REVIEWS 6 [1] Chapter 8
Formal Technical Reviews [2] Chapter 14
Peer Reviews – Inspections and [3] Chapter 26 (26.4)
Walkthroughs
Expert Opinions
8A SOFTWARE TESTING – BASIC 7 [1] Chapter 9
CONCEPTS & STRATEGIES
[3] Chapter 13
Definition and Objectives
Unit Testing
Integration Testing – Big Bang,
Incremental (Bottom-up, Top-down)
Validation Testing
System Testing
Regression Testing
Smoke Testing
Alpha and Beta Testing
UAT
8B SOFTWARE TESTING – TEST 8 [1] Chapter 9
CLASSIFICATIONS
W. R. T. Testing Concept – BB, WB
W. R. T. Quality Factors – Operation
(Correctness, Reliability, Efficiency,
Integrity, Usability), Revision
(Maintainability, Flexibility, Testability),
Transition (Portability, Reusability,
Interoperability)
5
8C SOFTWARE TESTING – 8, 9, 10 [1] Chapter 9
TECHNIQUES
[3] Chapter 14
White Box – Code Coverage (Line,
Branch, Path) Basis Path Testing
(Control Flow Graph, Cyclomatic
Complexity), Loop Testing, Condition
Testing, Qualification Testing
Black Box – ECP, BVA
Advantages and Disadvantages
8D SOFTWARE TESTING – 11, 12 [1] Chapter 10
IMPLEMENTATION
Testing Process
Test Case Design
Automated Testing
Debugging
MIDTERM EXAM 2 12
9 SOFTWARE CONFIGURATION 13 [1] Chapter 18
MANAGEMENT
[3] Chapter 27
Terminology
SCM Tasks
Change Control
Release Management
10 MEASUREMENT THEORY 13 [4] Chapters 1 and 2
Importance of Measurement
Measurement Scales
11 SOFTWARE QUALITY METRICS 14 [1] Chapter 21
Size Metrics
Process Metrics
Product Metrics
Implementation
Limitations
PROJECT PRESENTATIONS 15, 16
ADVANCED TOPICS (May Be
6
Covered if Time Permits)
Statistical SQA (Six Sigma)
Formal Approaches to SQA
Test Driven Development
FINAL EXAM
7
Course Policies
1. Announcements related to different aspects of this course (e.g. lectures, quizzes, exams,
etc.) may be posted on Google Classroom. Students are expected to view the Google
Classroom Stream regularly.
2. All students are expected to attend all lectures from beginning to end. Partial or full absence
from a lecture without a valid reason may hamper chances for securing good grades.
University’s attendance requirements must be met in order to appear in the final exam.
3. Exams will be closed-book and closed-notes. Syllabus for the final exam will be
comprehensive.
4. Students are encouraged to take full advantage of instructor’s office hours. Any doubts
regarding concepts covered in class or any questions regarding quizzes, projects, etc. may
be clarified during office hours. In case a student is not able to make it during office hours,
he/she may schedule an appointment with the instructor for another time slot.
5. Quizzes may be announced or unannounced. A quiz will usually be about 5 – 15 minutes
long and it may be given anytime during the lecture. Students missing a quiz will NOT be
given a make-up quiz.
6. Students are encouraged to finish the assigned readings BEFORE the lecture. This is likely to
improve lecture comprehension and class participation.
7. Students can contest their grades on quizzes, assignments, and project ONLY within a week
of the release of grades. Exams will be available for review according to university policies.
8. Students are expected to demonstrate the highest degree of moral and ethical conduct. Any
student caught cheating, copying, plagiarizing, or using any other unfair means will be
strictly dealt-with in accordance with university policies.