WM Software Process & QualitySPiCE - slide#1  Paul Sorenson SP i CE SPI S oftware P rocess I mprovement CE & C apability D E termination * An international collaboration to develop a standard on software process assessment ISO *Carried out under the auspices of a joint technical committee of ISO (International Standards Organization) and the International Electrotechnical Committee * Expected to culminate in a new international standard in the 1998 timeframe (ISO/IEC PDTR 15504)

WM Software Process & QualitySPiCE - slide#2  Paul Sorenson SPiCE GOALS & SCOPE goals Overall goals of the standard are to encourage organizations to employ proven, consistent and reliable methods for assessing the state of their processes and to use their assessment results as part of a coherent improvement program. scope The scope is process assessment, process improvement and capability determination. Software process domains to be assessed are: acquisition, supply development, operation, maintenance, supporting processes and service support.

WM Software Process & QualitySPiCE - slide#3  Paul Sorenson SPiCE... In the beginning June 1991 In June 1991, the 4th plenary meeting of ISO/IEC JTC1/SC7 approved a study period to investigate the needs and requirements for a standard for software assessment. June 1993 In June 1993, SPICE Project Organization was established with a mandate from JTC1/SC7 to: - assist to develop initial working drafts; - undertake user trials to gain early experience; - create market awareness and take-up.

WM Software Process & QualitySPiCE - slide#4  Paul Sorenson SPiCE... In the beginning + June 1995 In June 1995, the SPICE Project Organization completed its task of producing the set of working drafts - - form the basis of Technical Report. January 1995 In January 1995, the period of user trials commenced. User trials continue today and working drafts of the various parts of the proposed standard continue to evolve.

WM Software Process & QualitySPiCE - slide#5  Paul Sorenson SPiCE... Concepts A set of practices forms the lowest level of the standards architecture. The architecture distinguishes between: + base practices which are the essential activities of a specific process. +generic (management) practices, applicable to any process,which represent the activities necessary to manage a process and improve its capability to perform.

WM Software Process & QualitySPiCE - slide#6  Paul Sorenson SPiCE... Architecture Organization Customer - Supplier Support Management Engineering Process Categories

WM Software Process & QualitySPiCE - slide#7  Paul Sorenson SPiCE... Concepts The SPICE architecture model contains five process categories: Customer-Supplier + Customer-Supplier - processes that directly impact the customer, support development and transition of the software to the customer, and provide for its correct operation and use. (Part 5 - page 16) Engineering + Engineering - processes that directly specify, implement, or maintain a system and software product and its user documentation. (page 23)

WM Software Process & QualitySPiCE - slide#8  Paul Sorenson SPiCE... Concepts Management + Management - processes which establish the project, and coordinate and manage its resources. (page 41) Support + Support - processes which enable and support the performance of the other processes on a project. (page 32) Organization + Organization - processes which establish the business goals of the organization and develop the process, product, and resource assets necessary to achieve its goals. (page 47)