Hello, dear friend, you can consult us at any time if you have any questions, add WeChat: THEend8_
SWEN90016
Software Processes & Project Management
Quality Management
SWEN90016 Software Processes and Project Management Quality Management
Learning Outcomes
Quality Management
1. Understand the fundamentals of quality management
2. Understand the quality management process
3. Understand the following quality management activities:
– Quality Assurance
– Quality Planning
– Quality Control and Monitoring
-3-
SWEN90016 Software Processes and Project Management Quality Management
Project Quality
-4-
Today’s lecture
SWEN90016 Software Processes and Project Management Quality Management-5-
SWEN90016 Software Processes and Project Management Quality Management
Learning Outcomes
1. Understand the fundamentals of quality management
2. Understand the quality management process
3. Understand the following quality management activities:
– Quality Assurance
– Quality Planning
– Quality Control and Monitoring
-6-
SWEN90016 Software Processes and Project Management Quality Management
What is quality?
Quality is not an act, it is a habit — Aristotle
• Evidence shows that we cannot simply fix up our software
post-hoc and add in quality attributes after building the system
• Quality must be built into the software from the beginning
• In this topic you will learn how to built quality into the software
through a range of Quality Management activities
-7-
SWEN90016 Software Processes and Project Management Quality Management
What is software quality?
• We define quality from two broad perspectives:
– End-user’s Perspective:
Typically, end-users judge the quality of a product by their interaction with it.
For users, a system has quality if it is fit for purpose, is reliable, has
reasonable performance, is easy to learn and use, and helps the users in
achieving their goals. Sometimes, if the functionality is hard to learn but is
extremely important and worth the trouble of learning, then users will still
judge the system to have high quality. These are termed external quality
characteristics, because they are typically associated with the external
behaviour of the system.
– Developer’s Perspective:
The developer’s perspective typically also includes the number of faults that
the system has, ease of modifying the system, ease of testing the system, the
ease of understanding the system design, the re-usability of components,
conformance to requirements, resource usage, and performance. These are
mainly internal quality characteristics, because they are concerned with the
quality of the internal structure of the system.