Wesley NitsckieMarlon Parker

Agenda

Background

“I’d rather have it wrong than have it late. We can always fix it later”

Background

Introduction

• Software is part of everyday life• High costs associated with poor

quality• Software quality assurance has been

given a low priority in SDLC

Introduction

Software Quality

•What is software quality?–Measures how well software is

designed (quality of design)–How well the software conforms to

that design (quality of conformance)–Fitness for use

Software Quality

• Case: Mobile messaging company– Pilot Study– Landscape

• Semi-structured interviews• Identify stakeholders, SDLC processes, organisational

flows– 2 Software development Projects

• Project A – QA at the end of SDLC process• Project B – QA throughout the SDLC process• Comparison of metrics

Research Methodology

Project A

Research Methodology

Project B

Research Methodology

• Project A:– Defects reported was 17 and took 4 days to fix.

• Project B:– Defects reported was 3 and took 3 hours to fix.

• Difference in time• Cost implications• Number of defects was reduced

Discussion of Findings

• Spend more time fixing than developing• QA early in SDLC reduces software defects and

costs• QA does not eliminate defects completely• QA should be woven through the fabric of the

SDLC

Conclusion

• Thank you

The End