S 2 ESC Quality Management Planning Group John

S 2 ESC Quality Management Planning Group John Walz Quality Management Planning Group Chair P 730 Vice-Chair S 2 ESC Ex. Com 30 -Jul-08 Melbourne, FL 1

S 2 E Quality Mgmt. Topics • • • Where is Quality? - Information P 90003 Status - Information Revised S 2 E Standards inclusion - Discussion P 730 PAR Revision – Decision Working with SEI to validate S 2 E Standards mapping - Opportunity • Next S 2 ESC Steps - Discussion 2

S 2 ESC 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. 3

Related SDOs on Quality IEEE / ANSI IEEE SA IEEE CS ISO IEC JTC 176 ISO 9001, ISO 9004 ISO 100 xx S 2 ESC IEEE 90003: 2008 SC 7 IS 90003: 2004 IS 90005: 2008 4

S 2 E Quality 5

S 2 E Quality 6

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 (Cobi. T) – 34 processes, including PO 8 Manage Quality • CMMI-DEV Process Areas (PA) – 22 processes, including Product & Process Quality Assurance 7

Life cycle processes 8

IT Service Management • “I am still herding cats here during the summer at IBM. There are many process models out there- most are derivatives of ITIL, e. TOM 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 9

SP-07 Relationship to Quality Management • S 2 ESC 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 • S 2 ESC 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 - S 2 ESC Ex. Com 9 -Aug 05 10

Quality Management Status • P 90003 Draft balloted & comment resolved • S 2 ESC will submit the final P 90003 draft to Rev. Com, 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 – JTC 1 SC 7 has a NWIP for Revision of IS TR 90003 for both the new ISO 9001 and IS 12207: 2008 – JTC 1 SC 7 has a NWIP for Guidelines for the application of ISO 9001: 2000 to IS 20000 IT service management 11

Future updates to IEEE S 2 E Standards • Alignment to IS 12207: 2008 & IS 15288: 2008 process descriptions – “ 1996 type” project at addendum pages for every S 2 E standard? • Alignment to ISO 9001: 2008 – Updates to IEEE P 90003 & P 90005 • Relationship to CMMI-DEV – Appendix in every for every S 2 E standard? 12

Example: IEEE 1074 IEEE Standard 1074 for Developing a Software Project Life Cycle Process 1. OVERVIEW 1. 6 RELATIONSHIP TO OTHER KEY STANDARDS No standard lives isolated from its associated standards. This standard is related to ISO 9001: 2000 and IEEE 12207. 1. 6. 1 RELATIONSHIP TO ISO 9001 The 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 13

PAR for P 730 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 Planning" 14

S 2 ESC Guidance to P 730 1. from a "product" standard (QA plan) to a "process" standard (QA planning) 2. Information products SQAP 3. Terminology: IS 12207 4. Process architecture: IS 12207 5. Relationship to ISO 9001 6. Anticipated revisions, IS 15289 7. Relationships explained 8. CMMI-DEV Goals and Practices 9. S 2 ESC Executive Committee reviews 15

IS 12207: 2008 7. 2. 3 Software Quality Assurance Process Purpose • 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 16

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. 17

P 730 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. 18

P 730 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. 19

SEI Rope Bridge for CMMI & ISO 9001 Organizations which are implementing both ISO 9001 and CMMI for Development will benefit from an understanding of areas which are covered well by both bodies of knowledge as well as areas which are not covered by both; this can lead to efficiencies of operation as well as less confusion for those responsible for implementation and operations. 20

CMMI & IEEE S 2 E Standards IEEE Software and Systems Standards collection 21

Next Steps • Revise P 730 PAR for Software Quality Assurance • Refresh S 2 ESC 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 P 90005 to map S 2 E Standards • Revised IEEE 90003 when IS 90003 is revised • Work with SEI to validate & publish mappings from Land/Walz book 22