the new ieee standard for software quality assurance processes – an essential tool for project...

THE NEW IEEE STANDARD FOR SOFTWARE

QUALITY ASSURANCE PROCESSES –

AN ESSENTIAL TOOL FOR PROJECT MANAGERS

Dr. Bakul Banerjee, October 24, 2014

Dr. Bakul Banerjee, PMP®

Answer TechnologyPOB 4193, Wheaton, IL 60189

E-mail: [email protected]

http://www.linkedin.com/in/bakulbanerjee

Complex systems are my passion.

LEARNING OBJECTIVES

• Identify key software quality assurance (SQA)

processes associated with a software (IT or

engineering) development project

• Map SQA tasks to the overall framework of the


Map SQA tasks to the overall framework of the

project as described in the Software Extension to the

PMBOK Guide Fifth Edition

• Understand how to implement SQA process in a

project to maximize ROI using tailoring

2

BACKGROUND

• Decades of volunteering with IEEE Software &

Systems Engineering Standards Committee as WG

member and balloter

• Working Group Member of IEEE 730-2014

• Review captain of IEEE SWEBOK 2004


• Review captain of IEEE SWEBOK 2004

• 25 years with the US Department of Energy (DOE) on

contract-based projects

• A quick view of the journey

3

NASA LANDSAT PICTURE OF CALIFORNIA

COAST ACTIVE REGION

Dr. Bakul Banerjee, October 24, 2014 4

BANKS OF CENTRIFUGE MACHINES


SPECTRUM AUTOMATIC CALL

DISTRIBUTOR


FUEL CYCLE FACILITIES - IDAHO FALLS


ADVANCED PHOTON SOURCE COMPLEX –

ARGONNE, ILLINOIS


COMPACT MUON SOLENOID DETECTOR FOR

LARGE HADRON COLLIDER - CERN


TEVATRON & MAIN INJECTOR ACCELERATOR

INSTRUMENTATION UPGRADE, FERMILAB, IL


LATTICE QUANTUM CHROMODYNAMIC

COMPUTING FACILITY, FERMILAB, IL


A BRIEF HISTORY OF SOFTWARE QUALITY

ASSURANCE (SQA) STANDARDS

•2014: IEEE Std. 730 Software Quality Assurance Processes

(Working Group Member)

•2004 - IEEE Guide Adoption of ISO/IEC 90003: Software

Engineering—Guidelines for the Application of ISO


Engineering—Guidelines for the Application of ISO

9001:2000 to Computer Software

•1995: IEEE std. 730.1 IEEE Guide to Software Quality

Assurance

•1989: IEEE Std. 730.1 IEEE Software Quality Assurance

•Various versions of NQA-1

REFERENCES

• Software Extension to the PMBOK Guide Fifth

Edition, IEEE Computer Society/PMI

• ISO/IEC Systems and software engineering —

Software Life Cycle Processes, ISO/IEC IEEE Std


Software Life Cycle Processes, ISO/IEC IEEE Std

12207-2008

• IEEE Standard for Software Quality Assurance

Processes -- IEEE Std 730™-2014 (Revision of IEEE Std

730-2002)

13

HIGHLIGHTS OF SOFTWARE EXTENTION TO

PMBOK GUIDE (5TH ED.)

QUALITY MANAGEMENT

Software quality considerations for planning

– Stakeholders: Safety, Security, Reliability, Resilience …

– Developers: Testability, Maintainability, Portability,

Extensibility, and Reusability


Extensibility, and Reusability

TIME MANAGENT

• Schedule compression implies non-linear increase of the

labor pool & possible decrease in quality

• Manage requirements

• Manage evidence-based reviews

14

HIGHLIGHTS OF SOFTWARE EXTENTION TO

PMBOK GUIDE (5TH ED.) – CONTD.

8.0 PROJECT QUALITY MANAGEMENT A. Plan Quality Management (QM)

B. Perform Quality Assurance (SQA)

C. Control Quality (SQC)

Levels of SQA and SQC1. Internal – development organization (project)


1. Internal – development organization (project)

2. External – to the project team, but within the organization

3. Independent – assessment done by teams outside of the organization

Other topics of interest:Cost Benefit Analysis (CBA)

Cost of Quality (COQ)

15

SQA IS:

For all software processes, requirements elicitations,

development, & maintenance, SQA is

• Assessing the software development process

• Evaluating the conformance to software processes

• Evaluating the effectiveness of the software


• Evaluating the effectiveness of the software

processes (requirements, development, &

maintenance)

Note: Software requirements are usually derived from

product requirements.

16

IEEE 730 SCOPE, USE & EXCLUSIONS

• Only a brief overview of a (very) large knowledge-base

• The IEEE 730 standard and other IEEE standards are designed to be comprehensive

• Conformance

– Full conformance claim

– Tailored (per IEEE) conformance for certain deliverables


– Tailored (per IEEE) conformance for certain deliverables

• May also be used as good practice guidance

• This presentation is limited to the normative sections of 730, not the informative sections:

• This presentation is agnostic of any particular life-cycle model and any particular industry

17

OUTLINE OF IEEE 730 - A PM PERSPECTIVE

Normative sections describe SQA processes, activities, and

expectations

Informative sections contain, among others,

Guidance for creating SQA Plans

Industry specific application guidance


Industry specific application guidance

Relationship with agile development process

Working with very small entities

Assessing product risks

Corrective/preventive action processes & root cause analysis

18

CLAUSE 5: DESCRIPTION OF CORE ACTIVITIES

• SQA plan is the key document for implementation

• Each activity has four sections:

– Reference to IEEE12207

– Purpose, Outcomes, & Tasks


– Purpose, Outcomes, & Tasks

Examples of outcomes (process and product):

Software executables, training or test documents,

nonconformance reports

19

SQA RELATED PROCESSES FOR PM

PLANNING/MONITORING

• Agreement processes

• Project processes

• Technical processes

• Software implementation processes

• Software support processes


• Software support processes

• Software verification & validation

• Software review

• Software audit

• Software reuse processes

22

SQA PROCESS OUTCOMES

• Process Implementation: Evidence-based

• Product Assurance: Adherence to product

requirements/plans; non-conformance, corrective

actions, & documentation



• Process Assurance: Adherence to process

requirements/plans; non-conformance, corrective


23

SQA PROCESS IMPLEMENTATION

SELECTED ITEMS - PM

• Planning for SQAP

– Good plans do not have to be complicated

• An established culture of SQA is cost effective

• Simplifying record keeping reduces cost


• Simplifying record keeping reduces cost

• SQA schedule and cost should be in the project plan

• Opportunities for tailoring and reuse

24

SQA PRODUCT ASSURANCE

SELECTED ITEMS - PM

• Requirements management for products

• Contractually binding rules, regulations, and laws

• Evaluation and documentation for acceptance &


• Evaluation and documentation for acceptance &

conformance

• Measurement for product quality improvement

25