WG10/N066
1995-03-31
(supercedes N002R)





ISO/IEC JTC1/SC7/WG10

SOFTWARE PROCESS ASSESSMENT

MODUS OPERANDI










VERSION 1.02


March, 1995





Table of Contents

Configuration Control
Document History
Revision History
1. PURPOSE
2. REFERENCES
3. MODUS OPERANDI
3.1 Standardisation Project
3.2 SPICE Project
3.3 Product Development
3.4 Organisation
3.5 Document Control
4. CONTACT POINT


Configuration Control

Title:         Modus Operandi 
Doc Ref:       QMS\MP\MODOP102
Created by:    Alec Dorling, January 1993 

Document History

Ver    Status     Who   Date    Saved as: 
1.01   Baselined  ad    93/06   New document, approved by SC7 and WG10 
1.02   Baselined  ad    95/03   Revised to implement JTC1/SC7 resolution 374 

Revision History

+--------+---------+--------------------------------------------------------+
|   Ver  |   Date  |                     Changes                            |
|--------+---------+--------------------------------------------------------|
|  1.01  |  06/93  | New Document developed by WG10 and approved by         |
|        |         | ISO/IEC JTC1/SC7 & WG10.                               |
|--------+---------+--------------------------------------------------------|
|  1.02  | 3/31/95 | Document updated to implement JTC1/SC7 resolution 374. |
|        |         | Also includes minor editorial changes                  |
+--------+---------+--------------------------------------------------------+


1. PURPOSE

The purpose of this document is to define the organisation and management for the development of a suite of international standards for software process assessment assigned to ISO/IEC JTC1/SC7/WG10 following acceptance of the new work item proposal (ref 2.4) by JTC1.

2. REFERENCES

2.1 ISO/IEC JTC1/SC7 N812, JTC1/SC7 Guidelines: Responsibilities

2.2 ISO/IEC Directives

Part.2, Methodology for the development of International Standards
Part.3, Drafting and presentation of International Standards

2.3 ISO/IEC Directives for JTC1: Procedures for the technical work of ISO/IEC JTC1 on Information Technology

2.4 ISO/IEC JTC1 N2104 Proposal for a New Work Item: Software Process Assessment.

2.5 Requirements Specification for a Software Process Assessment Standard (WG10/N017R)

2.6 Product Specification for a Software Process Assessment Standard (WG10/N0016R)

2.7 SPICE Project Organisation, Management and Control Procedures

2.8 SPICE Product Review Procedure

2.9 SPICE Configuration Management Procedure

3. MODUS OPERANDI

3.1 Standardisation Project

The procedures for the development of Standardisation Projects are outlined in ISO/IEC Directives for JTC1 (ref 2.3). The sequence of standardisation project STAGES through which the technical work will progress is as follows:

+-------------------------------+--------------------------------------------+
| Standardisation Project STAGE | Associated Standardisation Document        |
|-------------------------------+--------------------------------------------|
| 1 Proposal                    | New Work Proposal (NP)                     |
|-------------------------------+--------------------------------------------|
| 2 Preparatory                 | Working Draft(s) (WDs)                     |
|-------------------------------|--------------------------------------------|
| 3 Committee                   | Proposed Draft Technical Report(s) (PDTRs) |
|-------------------------------|--------------------------------------------|
| 4 Approval                    | Draft Technical Report(s) (DTRs)           |
|-------------------------------|--------------------------------------------|
| 5 Publication                 | Technical Report(s) (TRs)                  |
+-------------------------------+--------------------------------------------+

The suite of standards will initially be published as Technical Reports (Type 2). A recommendation will be made to revise the Technical Reports (Type 2) as International Standards (IS) within one year of publication following extensive field trials in the international community through the SPICE project.

3.2 SPICE Project

The SPICE project has been established in June 1993 with an organisational structure and a set of defined management and control procedures (ref 2.7) to:

SPICE, being an organisation which is making an effective technical contribution and actively participating in SC7/WG10, shall be established as a C liaison organisation in JTC1 classification terms (ref 2.3).

3.3 Product Development

The requirements for the suite of standards is documented in a Requirements Specification (ref 2.5). The Requirement Specification and any changes to it are written, reviewed and approved by WG10.

The SPICE project using the Requirements Specification shall develop a Product Specification (ref 2.6) providing a high level conceptual design for the suite of standards which can be traced back to the Requirements Specification. The Product Specification contains a product breakdown structure of the suite of standards, an outline product description for each product and a product work flow diagram. The Product Specification and any changes to it are written and proposed by the SPICE project and approved by WG10.

The SPICE project shall develop the technical products described in the Product Specification. The products having undergone product approval and release by the SPICE project, according to a documented Product Review Procedure (ref 2.8), will be consolidated and input to WG10 as initial Working Drafts. The SPICE project will use the WG10 Working Drafts for its ongoing work (i.e. user trials) through its C Liaison status. The SPICE project will NOT maintain a separate set of technical products once the C Liaison status is effected.

WG10 will progress the initial Working Drafts through SC7 and JTC1, according to ISO/IEC Directives for JTC1 (ref 2.3), as Proposed Draft Technical Reports, Draft Technical Reports and eventually as published Technical Reports (Type 2).

In order to gain experience data which will form the basis for a review of the published Technical Reports prior to revision as full International Standards, the SPICE project will undertake user trials within the international community, thereby creating market awareness and take-up of the evolving standards.

3.4 Organisation

In order to provide cohesion and coupling between the Standardisation project and the SPICE project, the SPICE project organisation shall establish a C liaison with JTC1/SC7/WG10. Additionally, the WG10 Convenor is correspondingly the SPICE Project Manager and the WG10 Project Editors are correspondingly the SPICE Product Managers.

Within the SPICE project organisation, the SPICE Project Manager is supported by a SPICE Management Board. The SPICE Management Board comprises:

The Technical Centres are responsible for coordinating the overall resources of the SPICE project within a geographical sector. Each Technical Centre has a Technical Centre Manager. The Chair of the Management Board passes to the Technical Centre Manager whose region will host the next international SPICE meeting following the conclusion of an existing meeting.

The overall project organisation is illustrated on the following diagram. The organisation, management and control procedures for the SPICE project are contained in the SPICE Project Organisation, Management and Control Procedures (ref 2.7).

3.5 Document Control

All WG10 documents are controlled according to the JTC1 rules for numbering working documents (ref 2.3) and are referenced WG10/Nnnn. WG10/N000 is the WG10 document list.

All SPICE documents are controlled under a configuration management system in both a paper and electronic filing system according to a documented Configuration Management Procedure (ref 2.9).

4. CONTACT POINT

Alec Dorling
JTC1/SC7 WG10 Convenor
IVF, Center for Software Engineering
Tel: +46 31 706 6014
Fax: +46 31 27 6130
Mobile: +46 70 780 6014
Email: dorling@qai.u-net.com