The presentation explores the application of the new IEEE Standard for Software Quality Assurance in the context of PMI's project management standards.

1. THE NEW IEEE STANDARD FOR SOFTWARE
QUALITY ASSURANCE PROCESSES –
AN ESSENTIAL TOOL FOR PROJECT MANAGERS
Dr. Bakul Banerjee, PMP®
Answer Technology
POB 4193, Wheaton, IL 60189
E-mail: bakulb@gmail.com
http://www.linkedin.com/in/bakulbanerjee
Complex systems are my passion.
Dr. Bakul Banerjee, October 24, 2014

2. 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
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
Dr. Bakul Banerjee, October 24, 2014
2

3. 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
• 25 years with the US Department of Energy (DOE) on
contract-based projects
• A quick view of the journey
Dr. Bakul Banerjee, October 24, 2014
3

4. NASA LANDSAT PICTURE OF CALIFORNIA
COAST ACTIVE REGION
Dr. Bakul Banerjee, October 24, 2014 4

5. BANKS OF CENTRIFUGE MACHINES
Dr. Bakul Banerjee, October 24, 2014 5

6. SPECTRUM AUTOMATIC CALL
DISTRIBUTOR
Dr. Bakul Banerjee, October 24, 2014 6

7. FUEL CYCLE FACILITIES - IDAHO FALLS
Dr. Bakul Banerjee, October 24, 2014 7

8. ADVANCED PHOTON SOURCE COMPLEX –
ARGONNE, ILLINOIS
Dr. Bakul Banerjee, October 24, 2014 8

9. COMPACT MUON SOLENOID DETECTOR FOR
LARGE HADRON COLLIDER - CERN
Dr. Bakul Banerjee, October 24, 2014 9

10. TEVATRON & MAIN INJECTOR ACCELERATOR
INSTRUMENTATION UPGRADE, FERMILAB, IL
Dr. Bakul Banerjee, October 24, 2014 10

11. LATTICE QUANTUM CHROMODYNAMIC
COMPUTING FACILITY, FERMILAB, IL
Dr. Bakul Banerjee, October 24, 2014 11

12. 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
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
Dr. Bakul Banerjee, October 24, 2014 12

13. 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
12207-2008
• IEEE Standard for Software Quality Assurance
Processes -- IEEE Std 730™-2014 (Revision of IEEE Std
730-2002)
Dr. Bakul Banerjee, October 24, 2014
13

14. 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
TIME MANAGENT
• Schedule compression implies non-linear increase of the
labor pool & possible decrease in quality
• Manage requirements
• Manage evidence-based reviews
Dr. Bakul Banerjee, October 24, 2014
14

15. 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 SQC
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)
Dr. Bakul Banerjee, October 24, 2014
15

16. 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
processes (requirements, development, &
maintenance)
Note: Software requirements are usually derived from
product requirements.
Dr. Bakul Banerjee, October 24, 2014
16

17. 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
• 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
Dr. Bakul Banerjee, October 24, 2014
17

18. 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
Relationship with agile development process
Working with very small entities
Assessing product risks
Corrective/preventive action processes & root cause analysis
Dr. Bakul Banerjee, October 24, 2014
18

19. 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
Examples of outcomes (process and product):
Software executables, training or test documents,
nonconformance reports
Dr. Bakul Banerjee, October 24, 2014
19

20. Dr. Bakul Banerjee, October 24, 2014 20

21. Dr. Bakul Banerjee, October 24, 2014 21

22. SQA RELATED PROCESSES FOR PM
PLANNING/MONITORING
• Agreement processes
• Project processes
• Technical processes
• Software implementation processes
• Software support processes
• Software verification & validation
• Software review
• Software audit
• Software reuse processes
Dr. Bakul Banerjee, October 24, 2014
22

23. 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
actions, & documentation
Dr. Bakul Banerjee, October 24, 2014
23

24. 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
• SQA schedule and cost should be in the project
plan
• Opportunities for tailoring and reuse
Dr. Bakul Banerjee, October 24, 2014
24

25. SQA PRODUCT ASSURANCE
SELECTED ITEMS - PM
• Requirements management for products
• Contractually binding rules, regulations, and laws
• Evaluation and documentation for acceptance &
conformance
• Measurement for product quality improvement
Dr. Bakul Banerjee, October 24, 2014
25