new work item proposal – iso/iec 15288 and iso/iec …jtc1-sc7.logti.etsmtl.ca/n2851-n2900/07n2881...

ISO/IEC JTC1/SC7 Software & Systems Engineering Secretariat: CANADA (SCC)

ISO/IEC JTC1/SC7 N2881

2003-07-01

Doc. Type NP Ballot

Title New Work Item proposal – ISO/IEC 15288 and ISO/IEC 12207 harmonization

Source SC7 / WG07

Project

Status NP

References Resolution 721

Action ID ACT

Due Date 2003-10-01

Mailing Date 2002-07-01

Distribution SC7_AG; JTC1 Sec.; P, O & L Members

Medium PDF

No. of Pages 13

Note This ballot is also sent to JTC1 for a parallel endorsement balltot, as per new directives. Member Bodies must use the form included on the ballot and provide answers to all questions.

Address reply to: ISO/IEC JTC1/SC7 Secretariat École de technologie supérieure – Département de génie électrique

1100 Notre Dame Ouest, Montréal, Québec Canada H3C 1K3 [email protected]

www.jtc1-sc7.org

VOTE ON A PROPOSED NEW WORK ITEM ISO/IEC JTC 1/SC7 N2881

Date of Circulation of NP: 2003-07-01

Date of Ballot Close: 2003-10-01 Please return all votes and comments directly to the JTC 1/SC 7 Secretariat ([email protected]) by the due date indicated.

New Work Item proposal – ISO/IEC 15288 and ISO/IEC 12207 harmonization Any proposal to add a new item to the programme of work shall be voted on by correspondence, even if it has appeared in the agenda of a meeting.

A. Vote YES NO Comments

Q.1 Do you accept the proposal in document JTC 1 N XXXX as a sufficient definition of the new work item? (If you have responded "NO" to the above question, you are required to comment.)

____ ____ ____

Q.2 Do you support the addition of the new work item to the programme of work of the joint technical committee?

____ ____ ____

B. Participation

Q.3 Do you commit yourself to participate in the development of this new work item?

____ ____ ____

Q.4 Are you able to offer a project editor who will dedicate his/her efforts to the advancement and maintenance of this project? (If "YES," please identify .............................................................)

____ ____ ____

C. Documentation

Q.5 Do you have a major contribution or a reference document ready for submittal?

____ ____ ____

Q.6 Will you have such a contribution in ninety days?

____ ____ ____

P-member Voting:

National Body _____________________

Date:

______________

Submitted by:

Name ____________________________

NOTE: do NOT submit this form when voting by email. Simply type your vote (with comments where

applicable) into an email message and send to [email protected].

mailto:[email protected]

ISO/IEC JTC 1/SC 7/WG 7 N0714 2003-06-18

Document type NP proposal

Title New Work Item proposal – ISO/IEC 15288 and ISO/IEC 12207 harmonization

Source ISO/IEC JTC 1/SC 7/WG 7 Convener

Status Final

Reference SC 7 Resolution 721

Action ID FYI or ACT

07N2881 W07N0714 HARMONIZATION NEW WORK ITEM PROPOSAL.DOC 30 June 2003 Page 1 of 13

ISO/IEC JTC 1/SC 7/WG 7 N0714 2003-06-18

PROPOSAL FOR A NEW WORK ITEM

Date of presentation of proposal: 2003-07-01 Proposer: ISO/IEC JTC 1/SC 7

Secretariat: Standards Council of Canada (SCC) ISO/IEC JTC 1/SC7 N2881

ISO/IEC JTC 1 N XXXX

A proposal for a new work item shall be submitted to the secretariat of the ISO/IEC joint technical committee concerned with a copy to the ISO Central Secretariat.

Presentation of the proposal - to be completed by the proposer Guidelines for proposing and justifying a new work item are given in ISO Guide 26.

Title

Systems and Software engineering – Life cycle management

Scope (and field of application) The scope includes the current scope of ISO/IEC 15288 and ISO/IEC 12207 and the associated guidance documents. This International Standard establishes a common framework for describing the life cycle of systems. It defines a set of processes and associated terminology. These processes can be applied at any level in the hierarchy of a system’s structure. Selected sets of these processes can be applied throughout the life cycle for managing and performing the stages of a system's life cycle. This is accomplished through the involvement of all interested parties with the ultimate goal of achieving customer satisfaction. This International Standard includes processes that can be applied during the life cycle of a system that is software-intensive. This International Standard also provides processes that support the definition, control and improvement of the life cycle processes used within an organization or a project. Organizations and projects can use these life cycle processes when acquiring and supplying systems. This International Standard concerns those systems that are man-made and may be configured with one or more of the following: hardware, software, humans, processes (e.g. review process), procedures (e.g. operator instructions), facilities and naturally occurring entities (e.g. water, organisms, minerals).

Purpose and justification

The project is a revision of ISO/IEC 15288 to consolidate and harmonize with other related standards and guides.

ISO/IEC 12207 Software life cycle processes was published in 1995 and a lengthy Amendment was published in 2002. The standard will be easier to use if the Standard and the Amendment are combined into a single document.

ISO/IEC 15288 System life cycle processes was published in 2002. During the development of ISO/IEC 15288 it was noted that there was a need for harmonization between the two life cycle process standards and the following points were noted in this regard:

1. The differences in architectural principles in the two documents may make it difficult for concurrent usage.

2. The level of detail of the two documents needs to be revised to ensure that they are complementary.

3. The comment dispositions for ISO/IEC 15288 drafts resulted in a number of comments that were deferred to a future revision.

4. There are places where the two documents overlap, and in those areas there are perceived incompatibilities.

The harmonization project will ensure consistency in terminology, concepts, process architecture, document structure, processes, and other factors that will facilitate the joint usage of the documents. The users of ISO/IEC 15288 and ISO/IEC 12207, as well as other related JTC 1/SC 7 standards and technical reports, will benefit from having one harmonized set of documents. The need to revise other related standards and technical reports from JTC1/SC7 is identified as follows:


ISO/IEC JTC 1/SC 7/WG 7 N0714 2003-06-18

• ISO/IEC TR 15271 Guide for ISO/IEC 12207 (currently due for revision), • ISO/IEC TR 19760 Guide for ISO/IEC 15288, • ISO/IEC 15504 – part 5.

The revision may impact the following related documents:

• ISO/IEC 15939 Software measurement process • ISO/IEC 14764 Software maintenance, • ISO/IEC TR 16326 Project management, • ISO/IEC 18019 Documentation process, • ISO/IEC TR 15846 Configuration management, • ISO/IEC 90003

Current work on harmonization between ISO/IEC 15288 and IEEE 1220 may impact the revision.

Programme of work

If the proposed new work item is approved, which of the following document(s) is (are) expected to be developed? ____ a single International Standard more than one International Standard (expected number: ........ ) X a multi-part International Standard consisting of 4 parts ____ an amendment or amendments to the following International Standard(s) .................................... ____ a technical report , type ...........

Relevant documents to be considered • ISO/IEC 15288:2002 ; • ISO/IEC 12207:1995 • ISO/IEC 12207:1995/Amd 1:2002 • ISO/IEC TR 15271:1998, • ISO/IEC TR 19760, • ISO/IEC 15504, part 2 & 5 • ISO/IEC 90003 • IEEE 1220 (after alignment) • ISO/IEC 15939

Preparatory work offered with target date(s) ISO/IEC JTC 1/SC 7 N2817 Harmonization Study Group Report

Refer to the attached Project Requirements.

The draft schedule for the project is: • Requirements document baselined 2003-11 • Document architecture baselined 2004-05 • WD.1 – 2004-11 • WD.2 – 2005-05 • CD.1 – 2005-11 • CD.2 – 2006-05 • FCD – 2006-11 • FDIS – 2007-05 • Publication – 2007-11

Cooperation and liaison INCOSE (Cat A liaison), IEEE Computer Society (Cat A liaison)

Signature: Alain Abran

Will the service of a maintenance agency or registration authority be required? NO - If yes, have you identified a potential candidate? ................ - If yes, indicate name .............................................................

Are there any known requirements for coding? NO -If yes, please specify on a separate page

Does the proposed standard concern known patented items? NO - If yes, please provide full information in an annex

Comments and recommendations of the JTC 1 Secretariat - attach a separate page as an annex, if necessary

Comments with respect to the proposal in general, and recommendations thereon: It is proposed to assign this new item to JTC 1/SC 7/WG 7

Voting on the proposal - Each P-member of the ISO/IEC joint technical committee has an obligation to vote within the time limits laid down (normally three months after the date of circulation).


ISO/IEC JTC 1/SC 7/WG 7 N0714 2003-06-18

Date of circulation: 2003-07-01

Closing date for voting: 2003-10-01

Signature of JTC 1/SC7 Secretary:

Alain Abran


ISO/IEC JTC 1/SC 7/WG 7 N0714 2003-06-18

NP Acceptance Criteria Principle for NP Acceptance:

The existing JTC 1 Directives (cl. 6.2.1.3) require the commitment of five National Bodies; in addition the criteria (proforma) defined in this paper shall also be satisfied.

Assumptions:

• That the proposed NP acceptance criteria be applied at the initialization and the approval stages.

• That in accordance with existing procedures NP's may be initiated by SC's and or NB's.

• That SC's shall have a business plan, which defines and justifies their work program.

• That NP's shall fall within the scope of the JTC 1 Business Plan and where applicable the SC Business Plan.

• That when a NP is initiated the proposer shall, in addition to existing requirements, complete the new proforma and submit it along with the NP. This proforma shall be circulated along with the NP ballot.

• That NB's during the balloting stage understand that in case of serious doubt, giving a firm negative vote would be helpful to ensure relevance and utilization of critical resources within JTC1.

• That JTC 1 provide input and direction to emphasize these criteria as a new approach for NP planning and NB balloting.

• That the JTC 1 secretariat engage in modification to the JTC 1 procedures related to NP's and their balloting.

07N2881 W07N0714 HARMONIZATION NEW WORK ITEM PROPOSAL.DOC 30 June 2003 Page 5 of

ISO/IEC JTC 1/SC 7/WG 7 N0714 2003-06-18

NEW WORK ITEM PROPOSAL - PROJECT ACCEPTANCE CRITERIA

Criterion Validity Explanation

A Business Requirement

A.1 Market Requirement Essential X Desirable ___ Supportive ___

This will remedy problems relating to overlaps and inconsistencies between the two primary life cycle standards. These two standards are top-level elements in the SC 7 framework

A.2 Regulatory Context

Essential ___ Desirable ___ X Supportive ___ Not Relevant

Regulators sometimes prescribe a process model. It is helpful to have a single consistent framework as a reference.

B. Related Work

B.1 Completion/Maintenance of current standards

Yes _X_ No___

The standards being harmonized are key documents. Other SC 7 documents may be affected.

B.2 Commitment to other organization Yes X No___ IEEE-CS

B.3 Other Source of standards Yes X No___

IEEE 1220,

IEEE 12207

C. Technical Status

C.1 Mature Technology Yes X No___

Revision of existing standards and guides

C.2 Prospective Technology Yes ___ No__X_

C.3 Models/Tools Yes ___ No __X_

D. Conformity Assessment and Interoperability

D.1 Conformity Assessment Yes ___


ISO/IEC JTC 1/SC 7/WG 7 N0714 2003-06-18

No X

D.2 Interoperability Yes __ __ No ___ X __

E. Other Justification

Notes to Proforma

A. Business Relevance. That which identifies market place relevance in terms of what problem is being solved and or need being addressed.

A.1. Market Requirement. When submitting a NP, the proposer shall identify the nature of the Market Requirement, assessing the extent to which it is essential, desirable or merely supportive of some other project.

A.2 Technical Regulation. If a Regulatory requirement is deemed to exist - e.g. for an area of public concern e.g. Information Security, Data protection, potentially leading to regulatory/public interest action based on the use of this voluntary international standard - the proposer shall identify this here.

B. Related Work. Aspects of the relationship of this NP to other areas of standardization work shall be identified in this section.

B.1 Competition/Maintenance. If this NP is concerned with completing or maintaining existing standards, those concerned shall be identified here.

B.2 External Commitment. Groups, bodies, or fora external to JTC1 to which a commitment has been made by JTC for cooperation and or collaboration on this NP shall be identified here.

B.3 External Std/Specification. If other activities creating standards or specifications in this topic area are known to exist or be planned, and which might be available to JTC1 as PAS, they shall be identified here.

C. Technical Status. The proposer shall indicate here an assessment of the extent to which the proposed standard is supported by current technology.

C.1 Mature Technology. Indicate here the extent to which the technology is reasonably stable and ripe for standardization.

C.2 Prospective Technology. If the NP is anticipatory in nature based on expected or forecasted need, this shall be indicated here.

C.3 Models/Tools. If the NP relates to the creation of supportive reference models or tools, this shall be indicated here.

D. Any other aspects of background information justifying this NP shall be indicated here.

D. Conformity Assessment and Interoperability


ISO/IEC JTC 1/SC 7/WG 7 N0714 2003-06-18

D.1 Indicate here if Conformity Assessment is relevant to your project. If so, indicate how it is addressed in your project plan.

D.2 Indicate here if Interoperability is relevant to your project. If so, indicate how it is addressed in your project plan.


ISO/IEC JTC 1/SC 7/WG 7 N0xxx

2003-05-27

Project requirements - Project 07.xx

1. Title of the project Systems and Software engineering – Life cycle management.

2. Requirements based on the intended usage of the harmonized solution

2.1. Introduction

Each usage of the harmonized solution is decomposed in "Users' needs", and each user need is decomposed in a set of requirements linked to the context of the usage.

Each requirement is followed by a letter. Those letters mean the requirement can be categorized as :

U Facilitation of Use

S Structure of standards

V Validation

I Interface

O Operation of the standard in a certain context

2.2. Usage of the harmonized solution

Usage 1: Use as a common understandable set of terms within ISO/SC7 standards.

User needs:

N1: Consistent standards – ISO/IEC 15288 & ISO/IEC 12207

N2: Understandable terms

N3: Minimum vocabulary (avoid synonyms)

N4: Easy to translate

N5: Minimize discipline-specific terminology

N6: Consistency with other ISO standards, as appropriate

Requirements:

R1: The harmonized solution shall use commonly defined terms in a consistent manner. (U)

R2: The definition of a term shall include a description of the concept, including associated relationships and context of use. (U)

R3: There shall be a mechanism to manage the baseline of terms for the harmonized solution. (S)

R4: Definitions shall follow ISO rules regarding vocabulary. (S)

07N2881 W07N0714 Harmonization New Work Item proposal.doc 2003/05/27Page 9 of 13


2003-05-27

R5: Terms shall be used such that they can be translated into other languages and maintain the same meaning. (S)

R6: The context of use for any potentially ambiguous term shall be clearly specified. Example: "system" for quality system, computer system, information system ... "design" for "system design", "equipment design". (U)

Usage 2: Use as a basis for establishing the definitions of terms within an enterprise, an organization, or a project

User needs:

N7: Terms need to be able to be mapped from the standard into the terminology of the enterprise, organization, or project.

N8: Demonstrate conformance between the terms defined in the standard and an implementation (interpretation and implementation).

Requirements:

This use case is covered by the requirements in Usage 1.

Usage 3: Use as a basis for development of future versions and related standards and guides of the harmonized documents.

User needs:

N9 : Have a set of integrated standards and guides that are easy to understand, maintain, and extend over time.

Requirements:

R7: The primary harmonized standards (ISO/IEC 15288 & ISO/IEC 12207) shall have a single process architecture. (S)

R8: The standards should have associated guidance that covers various life cycle applications. (S)

R9: The harmonized standard(s) should have an individual requirement in only one document. (However, a requirement in one document may be further decomposed in another document.) (S)

Usage 4: Use as a basis for establishing and maintaining contractual requirements for integrated system and software acquisition (management, technical and legal aspects)

User needs:

N10: Provide consistent input for establishing contractual requirements across System and software acquisition.

Requirements:

R10: The harmonized solution shall contain guidance on the development and application of contractual requirements that are derived from the requirements included in the standards. (O)

R11: The harmonized solution shall contain guidance on the use of the contractual requirements for terms of acceptance of the products and services. (O)

R12: The harmonized solution shall include a single set of agreement processes. (S)



2003-05-27

Usage 5: Use as a basis to establish and maintain an integrated set of system and software processes based on business needs within an enterprise, organization, or project

User needs:

N11: Provide input for establishment of integrated system and software processes and application guidance that can address a wide range of business needs within the enterprise.

Requirements:

R13: The harmonized solution shall include process implementation guidance for integrated application to system and software development. (O)

R14: The harmonized solution shall provide a means for adaptation of requirements to business needs. (O)

Usage 6: Use as a basis to establish and maintain life-cycle models based on business needs within an enterprise, organization, or project

User needs:

N12: Provide an applicable set of life cycle models with tailoring guidance that address system and software development needs.

Requirements:

See Usage 5 and,

R15: The processes of the harmonized solution shall be defined so they are independent of any specific life-cycle model or life-cycle model stage. (S)

R16: The harmonized solution shall provide guidance on the definition, selection, application, and tailoring of life cycle models for system and software development. (O)

Usage 7: Use the harmonized documents as a basis for evaluating, such as monitoring, reviewing, auditing, assessing, or qualifying (certifying) a project, organization, or enterprise

User needs:needs:

N13: Provide an objective basis for evaluating cost, schedule, and technical performance at appropriate levels to identify findings.

Requirements:

R17: Processes shall be defined in accordance with the SC 7 process definition guidance to support use as a process reference model. (S)

R18: Each normative provision shall encapsulate only one requirement and each requirement shall be wholly contained in one sub-clause. (S)

R19: Each normative provision shall be verifiable by objective evaluation methods. (V)

R20: The elements of the harmonized solution shall be written to support integrated evaluation of system and software life cycle processes. (O)

Usage 8: Provide an agreed baseline of concepts and principles of systems and software life-cycle management

User needs:



2003-05-27

N14: Have the standard reflecting established best practices, and a broad range of technical agreement.

Requirements:

R21: The harmonized solution shall respect the integrity of the requirements of the standards being harmonized. (O)

Usage 9: Use as guidance in the development of courses and curricula

User needs:

N15: Provide notes, annexes, and supporting documents to facilitate understanding of concepts, principles, as well as technical and management content.

Requirements:

R22: The harmonized solution shall contain information (e.g., guides) to facilitate the use by stakeholders. (U)

R23: Interface mechanisms between the various parts of the harmonized solution shall be defined to facilitate their use. (U)

Usage 10: Use as a framework for developing specialty (e.g. safety, security), discipline (e.g. Electrical Engineering, software), or domain-specific standards (e.g. Space Agency, Defence version)

User needs:

N16: Provide a framework for appropriate elaboration with domain, discipline, or specialty issues, expertise, or constraints.

N17: Easy to interface with others standards, what ever the domain

N18: Consistent vocabulary and processes

Requirements:

R24: The harmonized solution shall contain guidance for application within and across domains, disciplines, and specialty areas. (O & I)

Usage 11: Use as a basis for establishing and maintaining policy within enterprises or organizations

User needs:

N19: Policy makers need a consistent, coordinated set of standards with clearly defined scopes.

Requirements:

R25: The scope (field of application) of the harmonized solution shall be defined, so that it is clear what is covered. (O)

R26: The harmonized solution shall include well-defined mechanisms for adaptation (tailoring). (O)



2003-05-27


3. Other requirements OR1. Potential cchanges should not cause major disruptions to the users of current WG 7 and SC 7 documents, and should protect the investments that countries have made in the deployment of them. As a result, a key achievement of the harmonization must be to simplify the use.

OR2. The harmonization of the documents will achieve consistency and/or compatibility in these areas: Concepts, Terminology, Readability, Level of detail and or compatibility, Processes, Document structure, Normative references

OR3. The harmonized solution will provide common interfacing mechanism with the ISO 9000 family of standards.

OR4. The harmonized solution will conform to requirements from ISO/IEC 15504-5 for process reference models as applicable.

OR5. The project will evaluate alternatives relating to the structure of the harmonized solution.

new work item proposal – iso/iec 15288 and iso/iec …jtc1-sc7.logti.etsmtl.ca/n2851-n2900/07n2881...

Documents