1

S2ESCQuality Management Planning Group

John WalzQuality Management Planning Group Chair

P730 Vice-Chair

S2ESC ExCom30-Jul-08

Melbourne, FL

2

S2E Quality Mgmt. Topics

• Where is Quality? - Information

• P90003 Status - Information

• Revised S2E Standards inclusion - Discussion

• P730 PAR Revision – Decision

• Working with SEI to validate S2E Standards mapping - Opportunity

• Next S2ESC Steps - Discussion

3

S2ESC Mission• To develop and maintain a family of software and systems

engineering standards that is authoritative, relevant, integrated, comprehensive, and effective in use by practitioners, organizations, and educators;

• To improve communications among stakeholders of software and systems engineering services and products;

• To aid the community in improving the quality of delivered software and systems containing software;

• To support improvements in the effectiveness and efficiency of software and systems engineering processes;

• To promote the professions of software and systems engineering through support for the knowledge base and practices, and the public recognition of professional competency;

• To develop supporting knowledge products that aid practitioners, organizations, and educators in understanding and applying our standards.

4

IEEE SA

S2ESC

ISO IEC

TC176 JTC1

SC7

IEEE CS

IEEE / ANSI

Related SDOs on Quality

ISO 9001,ISO 9004ISO 100xx

IS 90003:2004IEEE 90003:2008IS 90005:2008

5

S2E Quality

6

S2E Quality

7

Life Cycle Processes for Quality

• IS 12207 Software Engineering Life Cycle– 18 processes, including Software Quality

Assurance• IS 15288 System Engineering Life Cycle

– 25 processes, including Quality Management• IS 20000 Service Management

– 11 processes, including Supplier management• Control Objectives for Information and

related Technology (CobiT) – 34 processes, including PO8 Manage Quality

• CMMI-DEV Process Areas (PA)– 22 processes, including Product & Process

Quality Assurance

8

Life cycle processes

9

IT Service Management

• “I am still herding cats here during the summer at IBM. There are many many process models out there- most are derivatives of ITIL, eTOM or COBIT. This is from ITIL. They want to avoid the stiff royalties to OGC so they build there own. Its typical. We had to go through the exercise of looking at these and determining what was common to them all because it is really a pain in the neck having all these pseudo reference models. Agreement on one set would allow the industry to move on to value add topics like service innovation rather than what does incident management look like.. Bill Powell”, Tuesday, July 29, 2008

10

SP-07 Relationship to Quality Management

• S2ESC commits that ISO 9000:2000 and ISO 9001:2000 will provide the principles and concepts for a quality program in future updates of the IEEE software and systems engineering standards

• S2ESC commits that ISO/IEC 90003:2004 will be recognized as the primary document for guidance for organizations in the application of ISO 9001:2000 to the acquisition, supply, development, operation and maintenance of computer software - S2ESC ExCom 9-Aug-05

11

Quality Management Status

• P90003 Draft balloted & comment resolved• S2ESC will submit the final P90003 draft to RevCom, which uses

ISO/IEC 90003:2004

• ISO/IEC Status:– IS 12207 was revised this year to IS 12207:2008 with SQA process– IS 15288 was revised this year to IS 12207:2008 with Quality Management

process– IS TR 90005:2008 Systems engineering -- Guidelines for the application of

ISO 9001 to system life cycle processes– TC 176 will publish ISO 9001:2008 this fall with no new requirements; only

clarifications to avoid misuse– JTC1 SC7 has a NWIP for Revision of IS TR 90003 for both the new ISO

9001 and IS 12207:2008– JTC1 SC7 has a NWIP for Guidelines for the application of ISO 9001:2000

to IS 20000 IT service management

12

Future updates to IEEE S2E Standards

• Alignment to IS 12207:2008 & IS 15288:2008 process descriptions– “1996 type” project at add addendum pages

for every S2E standard?

• Alignment to ISO 9001:2008– Updates to IEEE P90003 & P90005

• Relationship to CMMI-DEV – Appendix in every for every S2E standard?

13

Example: IEEE 1074IEEE Standard 1074 for Developing a Software Project Life Cycle Process

1. OVERVIEW

1.6 RELATIONSHIP TO OTHER KEY STANDARDSNo standard lives isolated from its associated standards. This standard is related to ISO

9001:2000 and IEEE 12207.

1.6.1 RELATIONSHIP TO ISO 9001The ISO 9001:2000 family of standards recommends organizing a software development

project in accordance with a selected life cycle model. It is intended that a conforming application of this standard would satisfy this recommendation; however, it would be the responsibility of the applier to assure that the developed SPLCPs satisfy specific requirements of applicable clauses. Application of SPLCP to ISO 9001 can be facilitated through the usage of ISO/IEC 90003 ‘Guidelines for the application of ISO 9001:2000 to computer software’ (2004).

1.6.2 RELATIONSHIP TO IEEE 12207

1.6.3 RELATIONSHIP TO SEI CMMI-DEV

14

PAR for P730 Software Quality Assurance Planning

• Relevance issues, as PAR scope is a subset of:– IS 12207 SQA– CMMI-DEV PPQA– SQA professional job scope

• Monster.com job ads:– 369 "Software Quality Assurance" – 0 "Software Quality Assurance Plan"– 0 "Software Quality Assurance Planning"

15

S2ESC Guidance to P730

1. from a "product" standard (QA plan) to a "process" standard (QA planning)

2. Information products SQAP3. Terminology: IS 122074. Process architecture: IS 122075. Relationship to ISO 9001 6. Anticipated revisions, IS 152897. Relationships explained 8. CMMI-DEV Goals and Practices 9. S2ESC Executive Committee reviews

16

IS 12207:2008 7.2.3 Software Quality Assurance ProcessPurpose• The purpose of the Software Quality Assurance Process is to provide

assurance that work products and processes comply with predefined provisions and plans

Outcomes• As a result of successful implementation of the Software Quality Assurance

Process:– a strategy for conducting quality assurance is developed;– evidence of software quality assurance is produced and maintained;– problems and/or non-conformance with requirements are identified and recorded;

and– adherence of products, processes and activities to the applicable standards,

procedures and requirements are verified.Process activities

– . . . and adhere to their established plans.• Process implementation

– A plan for conducting the quality assurance process activities and tasks shall be developed, documented, implemented, and maintained for the life of the contract

• Product assurance– . . . plans required by the contract are documented

• Process assurance• Assurance of quality systems

17

CMMI-DEV Process & Product Quality Assurance

(PPQA)SG 1 Objectively Evaluate Processes and Work Products• Adherence of the performed process and associated work products and services to

applicable process descriptions, standards, and procedures is objectively evaluated. SP 1.1-1 Objectively Evaluate Processes• Objectively evaluate the designated performed processes against the applicable

process descriptions, standards, and procedures. SP 1.2-1 Objectively Evaluate Work Products and Services• Objectively evaluate the designated work products and services against the

applicable process descriptions, standards, and procedures.

SG 2 Provide Objective Insight• Noncompliance issues are objectively tracked and communicated, and resolution is

ensured SP 2.1-1 Communicate and Ensure Resolution of Noncompliance Issues• Communicate quality issues and ensure resolution of noncompliance issues with the

staff and managers. SP 2.2-1 Establish Records• Establish and maintain records of the quality assurance activities.

18

P730 PAR 5.4 Purpose

• The purpose of this standard is to provide uniform, minimum acceptable requirements for Software Quality Assurance activities in support of a software project.

• In considering adoption of this standard, regulatory bodies should be aware that specific application of this standard may already be covered by one or more IEEE or ANSI standards documents relating to quality assurance, definitions, or other matters. It is not the purpose of this document to supersede, revise, or amend existing standards directed to specific industries or applications.

19

P730 PAR 5.2 Scope:

• This standard establishes the requirements for planning Software Quality Assurance activities in support of a software project. It is directed toward the development and maintenance of software. The orientation is toward planning the systematic actions on a particular project that would provide adequate confidence that the software product conforms to established technical requirements. The standard also provides a means of satisfying the planning requirements of an organization's Quality Manual for a software project. It has been harmonized with the requirements of the Quality Assurance process of IEEE/EIA 12207.0 and the documentation content requirements of ISO/IEC 15289.

20

SEI Rope Bridge for CMMI & ISO 9001

Organizations which are implementing both ISO 9001 and CMMI for Developmentwill benefit from an understanding of areas which are covered well by both bodiesof knowledge as well as areas which are not covered by both; this can lead toefficiencies of operation as well as less confusion for those responsible forimplementation and operations.

21

CMMI & IEEE S2E Standards

IEEE Software and Systems Standards collection

22

Next Steps• Revise P730 PAR for Software Quality Assurance• Refresh S2ESC CD-ROM collection with

IEEE 90003, IS 12207, IS 15288• Request WG Chairs to include typical paragraph

on supporting ISO 9001 relevant clauses • Create PAR P90005 to map S2E Standards • Revised IEEE 90003 when IS 90003 is revised• Work with SEI to validate & publish mappings from

Land/Walz book