jr
I.
Course code and Title
CSE302
S
OFTWAREQ
UALITYE
NGINEERINGII.
Course Prerequisites
Course Code Title
CSE291 Software Metrics
III.
Instructor’s Information
Full Name: Email:
Contact Number
Office Hours & Location Teaching Assistant (if any)
IV.
Course Composition
Credit
Hours Weekly Duration (hrs) Contact Hours
Lectures 3 2 1.5 3
Laboratories -- -- --
--V.
Course Description
This course is designed to impart an understanding of the key concepts, principles, and process of Software Quality Engineering that begins with quality planning, creating and managing quality software products, and improving software processes for better quality products. Topics covered include: Introduction to Software Quality, Software Defects, Reasons of Poor Quality, Cost of Software Quality, Quality Assurance and its activities, role of quality and QA activities throughout SDLC (i.e. from planning and requirements engineering to software deployment and maintenance), Quality improvement through software process quality, improvement models and approaches.
VI.
Text book
1. Software Quality Engineering Testing, Quality Assurance, and Quantifiable Improvement, Jeff Tian, Wiley, 2005.
2. Software quality assurance: from theory to implementation. Daniel Galin,. Pearson Education, 2004
3. Software Process Definition and Management, Münch, J., Armbrust, O., Kowalczyk, M., & Soto, M., Springer Science & Business Media, 2012.
COMSATS Institute of Information Technology
Islamabad
Department of Computer Science
VII.
Reference books & Material
1. Software Quality Engineering: A Practitioner’s Approach, Suryn, W., John Wiley & Sons, NJ, USA, 2014.
2. Software & systems requirements engineering: in practice. Brian Berenbach. McGraw-Hill, Inc., 2009.
3. Software architecture in practice. Bass, Len. Pearson Education, 2007.
4. Software testing and continuous quality improvement. Lewis, William E. CRC press, 2016.
VIII.
Course Assessment
Evaluation methods Theory Weight (%)[T] Lab Weight(%)[L]
Quizzes 15 15
Assignments 10 10
Sessional Exam(I and II) 10+15 10+15
Terminal Exam 50 50
Total 100 100
Total =T+L T=(T/100)
Nil
The course teacher may select any one of the above weightage as per the course credit hours.
IX.
Course Outline and Contents
Lectur e
CDF
Unit # Topics Covered
Textbook Section
Week 1
1. 1 Software Quality: introduction, importance and need, different definitions of software quality, dimensions of software quality
Tian: Ch02; Galin: Ch01 2. 1 Different perspectives of software quality, views of
software quality (internal view, external view), Reasons/causes of software failure
Tian: Ch02; Galin: Ch01
Week 2
3. 2 Software defects, types of software defects (errors, faults, failures), cost of defects, cost of software quality (CoSQ)
Tian: Ch02; Galin: Ch01 4. 2 Basic model of CoSQ: cost of control (prevention
and appraisal costs), cost of failure of control (internal failure cost, external failure cost), extended model of CoSQ
Galin: Ch22
Week 3
5. 3 Type of quality models: quality definition models (FURPS, McCall, etc.), quality improvement models (CMMI, Six Sigma etc.), importance and role of quality models
D. Milicic
6. 3 Quality definition models: McCalls, FURPS, ISO 9126, SPARDAT, etc.
Tian: Ch02; Galin: Ch03
Week 4
7. 4 Software Quality Engineering: definition and
concepts, process of software quality engineering Tian: Ch05; 8. 4 Software quality assurance: definition, importance,
relationship of SQA and SQE, QA activities and alternates
Week 5
9. 5 QA activities and defect management/handling: Defect prevention and associated techniques, defect detection and removal, related techniques, defect containment and related techniques
Tian: Ch02, Ch13, Ch16;
10. 5 QA activities and software development lifecycle, Comparison of QA activities with respect to software artifacts, development phases, amount of effort required, time, and cost of QA activities
Tian: Ch03, Ch04
Week 6
11. Sessional 1Week 7
12. 5 SQE redefined: activities of quality engineering (pre-QA activities, in-QA activities, post-QA activities), process of SQE in terms of QA activities
Tian: Ch05
13. 6 The SQA system, components of SQA system, pre-project components, software pre-project lifecycle components, post-project components
Galin: Ch04
Week 8
14. 6 Planning quality and selecting QA activities, objectives of quality planning, quality plans and their importance, purpose
Galin: Ch06
15. 6 Elements of quality plans, writing a quality plan Galin: Ch06
Week 9
16. 7 Performing QA activities, QA and SDLC phases (waterfall, V-model, spiral, etc.), overview of QA activities in different phases
Galin: Ch07
17. 7 Quality of software requirements; quality in requirements engineering; QA in requirements gathering, quality requirements, requirements defects
Ch. 14 K. Wiegers
Week 10
18. 7 Quality in requirements specification, defects in requirements specification, Writing quality requirements
Ch. 14 K. Wiegers 19. 7 Quality in the analysis of requirements, quality in
requirements analysis models, such as quality class diagrams, quality DFDs, etc.
Ivan Mistrik Ch. 1
Week 11
20. 8 Quality in software design and architecture, effects of different architectures on software quality, QA in software design phase
Ivan Mistrik Ch. 1 21. 8 Quality in software construction and coding, coding
standards, QA in construction phase Myers Ch. 03
Week 12
22. Sessional-2Week 13
23. 8
Quality in software verification and validation, Quality test cases, quality review and test processes
Tian: Ch14, Ch15; Galin: Ch10, Ch24 24. 8 Quality and QA activities in software deployment
and maintenance, Quality in configuration management
Galin: Ch11, Ch18, Ch19
Week 14
25. 9 Improving and maintaining software quality infrastructure, importance of continuous improvement, basic concepts and definitions
Tian: Ch13; Münch: Ch01, Ref. material 26. 9 Software product quality vs. software process
quality, role of process quality in continuous
improvement, quality attributes of software
processes material
Week 15
27. 10 Role of modeling software processes in quality improvement, goals and benefits, Introducing descriptive and prescriptive software processes
Münch: Ch01
28. 10 Prescriptive process models, classes of prescriptive
models, process standards Münch: Ch02
Week 16
29. 10 Descriptive process models, goals of descriptive models, creating a descriptive model, Gap analysis of prescriptive and descriptive models for identifying areas of improvement
Münch: Ch03
30. 11 Quality improvement models and approaches, classification of quality improvement models, model based improvement approach, continuous improvement approach
Münch: Ch05
31. 11 Model based improvement: CMMI, ISO/IEC 15504 Münch: Ch05; Galin: Ch23
32. 11 Continuous improvement approach: TQM, Kaizen, Six Sigma, etc. Role of statistical methods (cause-and-effect diagram, pareto charts, scatter diagram, etc.)
Münch: Ch05, Ref. Material Terminal Examination
X.
Course Learning Outcomes (CLO)and Program Learning Outcomes
Upon completion of the course, students will be able to:
CLO Description PLO
C1 Describe the concepts and role of Software Quality Engineering. C2 Develop a software quality plan document.
C3 Apply QA activities in any of the stage/work product in a software project lifecycle. C4
Identify areas of improvement of QA activities/processes applied as part of C3.
Program Learning Outcomes (PLOs)
PLO Description
XI.
Assessment Schedule - Tentative
Give your tentative assessment plan with submission due date.
S.
No.
1
Assignment 1
3
CLO1
2
Sessional 1
6
3
Assignment 2
8
CLO2
4
Assignment 3
10
CLO3
5
Sessional 2
12
6
Assignment 4
14
CLO4
7
Terminal Examination
The course teacher may add quizzes, project or more assignment as he/she may deemed fit
S.
No.
Artifact
Week
CLO
1
Quiz 1
2
CLO1
2
Quiz 2
5
CLO2
3
Quiz 3
9
CLO3
XII.
Policy & Procedures
Attendance Policy:
Every student must attend 80% of the lectures delivered in this
course and 80% of the practical/laboratory work prescribed for the respective courses.
The students falling short of required percentage of attendance of
lectures/seminars/practical/laboratory work, etc., shall not be allowed to appear in the
terminal examination of this course and shall be treated as having failed this course.
Grading Policy:
The minimum pass marks for each course shall be 50%. Students
obtaining less than 50% marks in any course shall be deemed to have failed in that
course. The correspondence between letter grades
,credit points
,and percentage marks at
CIIT shall be as follows:
Grade A A- B+ B B- C+ C C- D F
Marks 90 -100
85 - 89 80 - 84 75
-79
70 - 74 65 - 69 60 - 64 55
-59
50 - 54 <50
Cr. Point 4.0 3.7 3.3 3.0 2.7 2.3 2.0 1.7 1.3 0.0
Missing Exam:
No makeup exam will be given for final exam under any circumstance.
When a student misses Sessional 1 or Sessional 2 for a legitimate reason (such as medical
emergencies), his grade for this exam will be determined based on the Department policy.
Further, the student must provide an official excuse within one week of the missed exam.
Academic Integrity:
All CIIT policies regarding ethics apply to this course. The
students are advised to discuss their grievances/problems with their counsellors or course
instructor in a respectful manner.
