Chapter 2. What is software quality. Please note that author slides have been significantly modified. Chapter 2. What is software quality?. Outline What is software? Software errors, faults and failures differences Classification of the causes of software errors
Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.
What is software quality?
According to the IEEE:
ISO definition (from ISO 9000-3) lists four components necessary to assure the quality of the software development process and years of maintenance:
2.1 Software - IEEE definition
2.2 Software errors, software faults
and software failures
So let’s move on to ‘exactly’ what we mean by ‘Software Quality.’
As you will see, there is no commonly-agreed to definition.
Says to plan and implementsystematically!
shows progress and instills confidence software is coming along
Refers to a software development process
a methodology; a way of doing things;
Refers to the specification of technical requirements
must have these.
Note that SQA must include not only process for development but for
(hopefully) years of maintenance. So, we need to consider quality issues
affecting not only development but also maintenance into overall SQA concept.
SQA activities must also include scheduling and budgeting.
SQA must address issues that arise when time constraints are encountered
– are features eliminated? Budget constraints may force compromise
when/if inadequate resources are allocated to development and/or maintenance.
Software quality assurance is:
A systematic, planned set of actions necessary to provide adequate confidence that the software development process or the maintenance process of a software system product conforms to established functional technical requirements as well as with the managerial requirements of keeping the schedule and operating within the budgetary confines.
regarding SQA, and corresponds to main outlines of the Capability
Maturity Model (CMM) for software.
Our book adapts the Expanded Definition of SQA.
See Table 2.2. We will be looking at these a lot later…
Table 2 compares the elements of the expanded SQA definition with the relevant sections of both the ISO-9000-3 and the software CMM.
We will discuss these in depth coming up.Comparison with ISO 9000-3 and SEI-CMM
Quality Control is defined as a designed to evaluate the quality of a set of activitiesdeveloped or manufactured product
in Software Development (Process-Oriented)
Assuring an acceptable level of confidence that the software will conform to functional technical requirements.
Assuring an acceptable level of confidence that the software will conform to managerial scheduling and budgetary requirements.
(3) Initiation and management of activities for the improvement and greater efficiency of software development and SQA activities.
in Software Maintenance (product-oriented)
Assuring an acceptable level of confidence that the software maintenance activities will conform to the functional technical requirements.
Assuring an acceptable level of confidence that the software maintenance activities will conform to managerial scheduling and budgetaryrequirements.
(3) Initiate and manage activities to improve and increase the efficiency of software maintenance and SQA activities.
You are to answer the following questions in essay format and
send to me via Blackboard Assignment Chapter 2:
Team 2 will fully discuss the following questions in our next class:
On page 34.