This document provides an introduction and overview of a course on software quality management. It outlines the course information, including the lecture topics, assignments, literature, and assessment. The course aims to teach quality basics, process improvement, product and project quality management, and defect prevention. Students will complete three assignments in groups and an individual exam. The assignments focus on code reviews, quality measurement, and process improvement. Overall, the document establishes the expectations and requirements for successfully completing the software quality management course.

1. s
Software Quality Management
PA2557
Course introduction
Conny Johansson

2. Introduction
• Information about the course
• Information about the lectures
• Information about the assignments
• Expectations from you

3. Course Information
• Course information
– Web page: Canvas reference
• Course responsible
– Conny Johansson
• Email: Conny.Johansson@bth.se (best contact media)
• Marking assignments (with support/supervision from me
as an examiner)
– Xingru Chen
• Email: xingru.chen@bth.se

4. Course – Overview of Lecture content
• L1: Introduction to Quality
• L2-3: Quality basics
• L4: Process Improvement
• L5: Process Improvement and Process Maturity
• L5-6: Product and Project Quality Management
• L7: Process Improvement Processes, GQM+Strategies
• L8: GQM+Strategies
• L9-10:Defect Prevention
• L11: Quality standards, SE Code of ethics

5. Course – Content of
Assignments
A1: Impact of code reviews on Software Code Quality
(Individual assignment)
A2: Evaluating code quality through code reviews -
Group assignment (3-4 members)
A3: Improving code quality using GQM+Strategies –
Group assignment (same group as assignment 2)
Note: Reports shall be written in English (not Swedish, nor
Chinese, nor Hindi, nor any other language). Agree on
groups and sign on to the groups in Canvas.

6. Ways of Learning in the Course
• Active participation in the lectures
• Ask additional questions during lectures or after the
lectures
• Study the mandatory literature and material from the
department (Canvas)
• Read the reference literature
• The slides are complements to the course material/
literature. Not explicitly referring to the literature.

7. • Main literature:
• Basili, et al.: Aligning Organizations Through Measurement (The
GQM+Strategies approach)
• Material published at the course home page in Canvas
• Reference literature:
• Project Management Institute: A Guide to the Project Management Body of Knowledge –
PMBOK GUIDE, Seventh Edition
• Bergman/Klefsjö: Quality – From Customer Needs to Customer Satisfaction
• Jacobs, Deb: Accelerating Process Improvement Using Agile Techniques
• Zahran: Software process improvement – Practical Guidelines for Business Success
• Ronald William Day: Design Error; A human factors approach.
• Huizinga, D; Kolawa: Automated Defect Prevention.
Course literature

8. Expectations
• Attend the seminars/lectures
• Deliver mandatory assignments at the expected deadlines
• Assignments delivered late = cannot guarantee that the assignment will
be corrected this year
• You shall show your ability to extract the most important
knowledge and to present it in a clear way
• At least Pass grade (E) on all the assignments and the exam
• The requirements for passing each assignment are described in each
assignment description
• Grades for the course will be based on the assignments and
the written exam

9. Assessment and Grading
Module Credit Grading
Assignment 1 1.5 ECTS
Assignment 2 1.5 ECTS
Assignment 3 1.5 ECTS
Written Exam 3.0 ECTS
The number of credits corresponds to the weight of the grade

10. Grading
• The grade for the course will be given according
to the European grading system
– ECTS (A, B, C, D, E, FX, F)
• A, B:
– Pass with distinction/High pass
• C, D, E:
– Pass
• FX, F:
– Fail

11. Grading (ECTS)
• A: EXCELLENT
– outstanding performance with only minor errors
• B: VERY GOOD
– above the average standard but with some errors
• C: GOOD
– generally sound work with a number of notable errors
• D: SATISFACTORY
– fair but with significant shortcoming
• E: SUFFICIENT
– performance meets the minimum criteria
• F: FAIL
– considerable further work is required

12. The Written Exam
• Questions are closed. “Which alternative is true....”,
“Which alternative is NOT true...”. E.g.
i. Alternative 1
ii. Alternative 2
iii. Alternative 3
iv. Alternative 4
v. (i) and (iii) above
vi. (ii) and (iv) above
vii. All of the above (i) – (iv)
viii. None of the above (i) – (iv)

13. Assignment Requirements – Contents
• Write the reports with your own words
– Copy/paste is strongly forbidden
• Even from your assignments of other courses
• Plagiarism is not tolerated
– Automatically checked in Canvas
– Consequence: Could be Fail for the “course”
• Make clear distinction between your own opinion
and other’s work/opinion
– Proper citation and referencing

14. Myself – Conny Johansson
• MSc. Mathematics, specialized in CS, 1987
• Licentiate Software Engineering (Swedish research degree)
• At BTH since 1989
• 5 years at a small Software House. 1987-1992
• 15 years at the Ericsson Group (part time 50%). 1992-2007
• 13 years, co-owner of HLL – Software Specialists Consultants
(Quality and Architecture)
• Since 2020 – own company CQA – Continuous Quality
Assurance (previously a part of HLL)

15. Myself, interest and skills
• Quality management:
– certified ISO9001:2015 Lead Auditor
– registered Lead Auditor, TickITplus capability assessor, in
the International Register of Certified Auditors, gasq
– 15-20 customers of different size
• Dean of School, head of approximately 150 people
within telecommunication systems, software engineering
and computer science April 2009 – December 2013.

16. What is Quality?
Quality?!

17. What is Quality?

18. What is Quality? – cont.
• Which has highest quality?
– Mercedes Benz or Toyota Camry?
• more prestige?
• weighs more?
• costs less to operate and maintain?
• more reliable?
• more beautiful?
• leaves more money for other things?

20. What is Quality? – cont.

24. What is Quality? – cont.
• What is quality for a cell phone?
– Must be smart?!
– Weight?
– Prestige?
– Price?
– Camera characteristics?
– Safety?
– Soccer results?
– Social media?
– Payment?
– Screen features?
– What about making calls?

25. • Crosby: quality is conformance to
requirements
• Juran: fitness for use
• Deming: quality should be aimed at the
needs of the customer, present and future
• Shewhart: quality has one measurable
side and one subjective
What is Quality? – cont.

26. What is Quality? – cont.
• ISO9000: the degree to which a set of
inherent characteristics fulfills the
requirements, i.e. needs or expectations
that are stated, generally implied or
obligatory
• Bergman/Klefsjö: The quality of the
product is its ability to satisfy, or preferably
exceed, the needs and expectations of the
customer

27. What is Quality? – cont.
• Who establishes the requirements?
• The Stakeholders
– Sponsor: the one who pays for the product
– End user: the one who will use the product
– Sales or marketing: the ones who will sell the product
– Customer: the one who buys the product
– The Developers: the one’s who develop the product
– Subcontractors
– Stockholders
– Subject matter experts
– An Individual or a Group
• The Stakeholders differ between projects and products
• Identify the stakeholders! Stakeholder Management.

28. What is Quality? – cont.
• Functional requirements
– E.g. connect point A to point B
– Exists, or does not exist. Binary result 0 or 1.
• Quality requirements (characteristics, non-functional
requirements)
– Reliability
– Security
– Safety
– Maintainability
– Usability
– Performance
– Measured on a relative scale

29. Is the customer always right?
• NO!
– But you shall always consider the customer’s needs,
point of views
• Who is the customer for
– Standard products? (Niche market)
– Off-the-shelf products? (Mass market)
– Specialized products?
• Stakeholders – supports the organization (customers, suppliers,
product management, users, share-holders, loan givers)
• Interested parties – appr. person/group who have interest in the
performance and success of the organization

30. Is the customer always right?
• It is the suppliers responsibility to actively
and continuously ensure that the
requirements are conforming to the
stakeholder’s real needs.

31. What is Quality? – cont.

32. • Coffee could be:
• Hot or cold (or medium)
• Flavorful or tasteless
• Strong or weak
• Served in a small cup or big mug
• Saucer or no saucer
• Not too strong
• Sugar or no sugar
• Lump sugar or powdered sugar
• Raw sugar or white sugar
• Milk or no milk
• Cream or no cream
• Decaffeinated coffee?
• The amount of milk, sugar, cream?????
• Etc.!!!!!!
What is Quality? – cont.