1 / 8

SP i CE

S oftware P rocess I mprovement & C apability D E termination. SP i CE. An international collaboration to develop a standard on software process assessment.

coen
Download Presentation

SP i CE

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Software Process Improvement & Capability DEtermination SPiCE • An international collaboration to develop a • standard on software process assessment • 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) SPiCE - slide#1

  2. SPiCE GOALS & SCOPE 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. The scope is process assessment, process improvement and capability determination. Software process domains to be assessed are: acquisition, supply development, operation, maintenance, supporting processesandservice support. SPiCE - slide#2

  3. SPiCE . . . In the beginning 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. 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. SPiCE - slide#3

  4. SPiCE . . . In the beginning + 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. In June 1995, the SPICE Project Organization completed its task of producing the set of working drafts -- form the basis of Technical Report. SPiCE - slide#4

  5. 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. SPiCE - slide#5

  6. SPiCE . . . Architecture Organization Customer - Supplier Management Engineering Support Process Categories SPiCE - slide#6

  7. SPiCE . . . Concepts The SPICE architecture model contains five process categories: • 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 - processes that directly specify, implement, or maintain a system and software product and its user documentation. (page 23) SPiCE - slide#7

  8. SPiCE . . . Concepts • Management - processes which establish the project, and coordinate and manage its resources. (page 41) • Support - processes which enable and support the performance of the other processes on a project. (page 32) • 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) SPiCE - slide#8

More Related