Scribd
Upload
19 views

Lecture 04

The document discusses approaches to project management and software quality assurance. It outlines several key practices for ensuring high quality software, including using automated estimation and planning methods, conducting formal risk analysis, and tracking defects and milestones. It also discusses the importance of a dedicated Software Quality Assurance group that reports to senior management and monitors quality-related activities. This group is responsible for quality assurance plans and audits to verify compliance with processes. Maintaining software quality involves costs but provides economic benefits like shorter development times and higher customer satisfaction.

Uploaded by

uzairaneesbhutto
Copyright
© © All Rights Reserved
Available Formats
Download as PPT, PDF, TXT or read online on Scribd
19 views

Lecture 04

The document discusses approaches to project management and software quality assurance. It outlines several key practices for ensuring high quality software, including using automated estimation and planning methods, conducting formal risk analysis, and tracking defects and milestones. It also discusses the importance of a dedicated Software Quality Assurance group that reports to senior management and monitors quality-related activities. This group is responsible for quality assurance plans and audits to verify compliance with processes. Maintaining software quality involves costs but provides economic benefits like shorter development times and higher customer satisfaction.

Uploaded by

uzairaneesbhutto
Copyright
© © All Rights Reserved
Available Formats
Download as PPT, PDF, TXT or read online on Scribd
You are on page 1/ 24

Software Quality Assurance

(ITC- 704)
Lecture 04
Project Management Approaches and software Quality

Dr. Zulfikar Ahmed Maher


Lecturer, ITC
Project Management
Approaches and High
Software Quality
 Use of automated project estimation
methods
 Use of automated project planning
methods
 Use of early and automated estimates of
software defect potentials
 Use of early and automated estimates of
software defect removal efficiency
 Formal risk-analysis
2
Project Management
Approaches and High
Software Quality
 Provision of adequate time for pre-test
inspections
 Historical quality data from similar
projects available
 Milestone tracking automated and
thorough
 Defect tracking automated and thorough
 Management focus concentrated on
achieving excellent results
3
SQA Group
 Every company, which wants to establish a
reputation for producing high quality
software, must establish a Software Quality
Assurance (SQA) Group within the company

 This groups must be funded properly and


management must pay attention to the
reports and presentations made by this group

4
SQA Group
 The SQA group report directly to the line-
management and not to the project
management

 The personnel of the SQA group must work


with the project management team, and
vice versa to produce high quality software
for the company – which is the ultimate
goal
5
 The SQA group is needed to monitor
the quality assurance-related activities
in a company

6
SQA Group’s Activities
 Preparation of an SQA plan for a project
 Participation in the development of the
project’s software process description
 Review of software engineering
activities to verify compliance with the
defined software process

7
SQA Group’s Activities - 2
 Audit of designed software work
products to verify compliance with
those defined as part of the software
process

8
SQA Group’s Activities - 3
 Ensure that deviations in software work
and work products are documented and
handled according to a documented
procedure

 Record any noncompliance and reports


to senior management

9
SQA Plan
 Evaluations to be performed

 Audits and reviews to be performed

 Standards that are applicable to the project

 Procedures for error reporting and tracking

10
SQA Plan - 2
 Documents to be produced by the SQA
group

 Amount of feedback provided to the


software project team

 (we’ll discuss SQA Plan in detail later in


the course)
11
Software Quality Personnel
 Unfortunately are under-paid
 Usually are let go first in times of crisis
 “Top-gun” SQA personnel and
managers with proven track record are
in high demand from companies that
have active QA programs

12
Costs of Software Quality

13
Costs of Software Quality

 Defects prevention costs


 User satisfaction optimization costs
 Data quality defect prevention costs
 Data quality defect removal costs
 Quality awareness/training costs
 Non-test defect removal costs
 Testing defect removal costs
14
Costs of Software Quality
 Post-release customer support costs
 Litigation and damage award costs
 Quality savings from reduced
scrap/rework
 Quality savings from reduced user
downtime
 Quality value from reduced time-to-
market intervals
15
Costs of Software Quality - 3
 Quality value from enhanced
competitiveness
 Quality value from enhanced employee
morale
 Quality return on investment

16
Economics of Software Quality

17
Economics of Software Quality
 High quality software applications have
shorter development schedules than
low quality applications because they do
not get hung up in integration and
testing due to excessive defect levels

18
Economics of Software Quality

 High quality software applications have


lower development and maintenance
costs than low quality applications. This
is because the cumulative costs of
finding and fixing bugs is often the
major cost driver for software projects

19
Economics of Software Quality
 High quality software applications have
better reliability levels and longer mean
times to failure than low quality
applications
 High quality commercial software
packages have larger market shares
than low quality commercial software
packages
20
Economics of Software Quality
 High quality software achieves better
user-satisfaction ratings than low
quality software
 High quality software projects score
better on employee morale surveys
than do low quality software projects

21
Economics of Software Quality
 High quality software produced under
contract or an outsource agreement has a
much lower probability of ending up in court
for breach of contract or malpractice litigation
than low quality software
 High quality software benefits or augments
the performance levels of users, while poor
quality tends to degrade worker performance

22
References
 Software Quality: Analysis and
Guidelines for Success by Capers Jones
 Customer-Oriented Software Quality
Assurance by Frank Ginac
 A Practitioner’s Approach to Software
Engineering by Roger Pressman

23

You might also like