WM-001 - Software Process & Quality SPiCE - slide#1 Paul Sorenson

SPSPiiCCEE SSoftware PProcess IImprovement

& CCapability DEEtermination

An international collaboration to develop a standard on software process assessment

Carried out under the auspices of a joint technical committee of ISOISO (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-001 - Software Process & Quality SPiCE - slide#2 Paul Sorenson

SPiCE GOALS & SCOPESPiCE GOALS & SCOPE

Overall goalsgoals of the standard are to encourageorganizations to employ proven, consistent and reliable methods for assessing the state of theirprocesses and to use their assessment results as part of a coherent improvement program.

The scopescope 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-001 - Software Process & Quality SPiCE - slide#3 Paul Sorenson

SPiCE . . . In the beginningSPiCE . . . In the beginning

In June 1991June 1991, the 4th plenary meeting ofISO/IEC JTC1/SC7 approved a studyperiod to investigate the needs andrequirements for a standard for softwareassessment.

In June 1993June 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-001 - Software Process & Quality SPiCE - slide#4 Paul Sorenson

SPiCE . . . In the beginning SPiCE . . . In the beginning ++

In June 1995June 1995, the SPICE Project Organization completed its task of producing the set of working drafts -- form the basis of Technical Report.

In January 1995January 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.

Paul SorensonSPiCE - slide#5WM-001 - Software Process & Quality

SPiCE . . . SPiCE . . . ConceptsConcepts

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.

Paul SorensonSPiCE - slide#6WM-001 - Software Process & Quality

SPiCE . . . SPiCE . . . ArchitectureArchitecture

Organization

Customer - Supplier

Support Management

Engineering

Process Categories

Paul SorensonSPiCE - slide#7WM-001 - Software Process & Quality

SPiCE . . . SPiCE . . . ConceptsConcepts

The SPICE architecture model contains fiveprocess categories: Customer-SupplierCustomer-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)

EngineeringEngineering - processes that directly specify, implement, or maintain a system and software product and its user documentation. (page 23)

Paul SorensonSPiCE - slide#8WM-001 - Software Process & Quality

SPiCE . . . SPiCE . . . ConceptsConcepts

ManagementManagement - processes which establish the project, and coordinate and manage its resources. (page 41) SupportSupport - processes which enable and support

the performance of the other processes on a project. (page 32)

OrganizationOrganization - processes which establish the business goals of the organization and develop the process, product, and resource assets necessary to achieve its goals. (page 47)