revision of 12207 - jtc1-sc7.logti.etsmtl.cajtc1-sc7.logti.etsmtl.ca/n3251-n3300/07n3260...

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

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

ISO/IEC JTC1/SC7 N3260

2005-06-13

Doc. Type NWI Proposal

Title New Work Item Proposal – Revision of ISO/IEC 12207 - Systems and Software Engineering - Software Life Cycle Processes

Source SC7 / WG07

Project

Status NP

References Resolution 849

Action ID ACT

Due Date 2005-09-13

Mailing Date 2005-06-13

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

Medium PDF

No. Of Pages 15

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

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

Date of Circulation of NP: 2005-06-13

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

Proposal for a new work item on Revision of ISO/IEC 12207 - Systems and Software Engineering - Software Life Cycle Processes 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].

ISO/IEC JTC 1/SC 7/WG 7 N0861 2005-05-26

New Work Item Proposal May 2005

PROPOSAL FOR A NEW WORK ITEM

Date of presentation of proposal: 2005-05-26

Proposer: SC 7/WG 7

Secretariat: Standards Council of Canada (SCC)

ISO/IEC JTC 1 N XXXX ISO/IEC JTC 1/SC XX N XXX

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.

Title (subject to be covered and type of standard, e.g. terminology, method of test, performance requirements, etc.) ISO/IEC 12207 Systems and Software Engineering – Software Life Cycle Processes

Scope (and field of application) Same as covered by ISO/IEC 12207:1995, AMD1:2002 and AMD2:2004

Purpose and justification (attach a separate page as annex, if necessary) Purpose: Revision of ISO/IEC 12207 (and its two Amendments) in order to decrease terminological and structural differences between the standard, its Amendments and ISO/IEC 15288. Justification: 1. ISO/IEC 12207 is close to its 5-year confirmation. 2. The current set of 3 documents (the original Standard and two Amendments) is difficult to

use. Some NBs report users actually turning away from ISO/IEC 12207. Additionally, the IEEE did not adopt the Amendments for its IEEE 12207.x series.

3. The revision allows for the application of the ISO/IEC SC 7 N0829R Guidelines for Process Definition (as revised) to the standard, which will provide for greater consistency, improved usability and alignment (within the set of standards under consideration).

4. The direction of the SC 7/WG 7 Harmonization project (ISO/IEC 24748) indicates the need for an interim solution for better alignment while the more challenging effort of integration proceeds.

5. Both this revision of ISO/IEC 12207 and the revision of ISO/IEC 15288 are planned to be executed concurrently.

Programme of work If the proposed new work item is approved, which of the following document(s) is (are) expected to be developed? __x__ a single International Standard ___ more than one International Standard (expected number: ........ ) ____ a multi-part International Standard consisting of .......... parts ____ an amendment or amendments to the following International Standard(s) .................................... ____ a technical report , type ........... And which standard development track is recommended for the approved new work item? __ x __a. Default Timeframe ____b. Accelerated Timeframe ____c. Extended Timeframe

Relevant documents to be considered ISO/IEC 12207 and its amendments, ISO/IEC 15288

Co-operation and liaison IEEE Computer Society under the terms of the coordinated development process (sections 3 and 4 of SC 7 N2860).

Preparatory work offered with target date(s) See Attachment 1

Signature:

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 or SC 7 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. Schedule: Refer to Attachment 1. (The intention is to have the FCD available within 12 months.)

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).

Date of circulation: YYYY-MM-DD

Closing date for voting: YYYY-MM-DD

Signature of Secretary:

NEW WORK ITEM PROPOSAL - PROJECT ACCEPTANCE CRITERIA

Criterion Validity Explanation

A. Business Requirement

A.1 Market Requirement Essential _x__ Desirable ___ Supportive ___

Existing and potential users are confused as to the structure and use of the standard as amended

A.2 Regulatory Context Essential ___ Desirable ___ Supportive _ x _Not Relevant __

Some regulatory authorities refer to processes from this document.

B. Related Work

B.1 Completion/Maintenance of current standards

Yes _x__ No___

B.2 Commitment to other organisation Yes _ x __ No___

IEEE-CS.

B.3 Other Source of standards Yes ___ No_x__

C. Technical Status

C.1 Mature Technology Yes _x__ No___

C.2 Prospective Technology Yes ___ No_x__

C.3 Models/Tools Yes ___ No_x__

D. Conformity Assessment and Interoperability

D.1 Conformity Assessment Yes ___ No_ x __

D.2 Interoperability Yes _x__ No___

With ISO/IEC 15288

E. Cultural and Linguistic Adaptability

Yes____ No_x____

F. 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 standardisation 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 JTC 1 to which a commitment has been made by JTC for Co-operation 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 JTC 1 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 standardisation. 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. Conformity Assessment and Interoperability 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 E. Cultural and Linguistic Adaptability Indicate here if cultural and linguistic adaptability is applicable to your project. If so, indicate how it is addressed in your project plan. F. Other Justification Any other aspects of background information justifying this NP shall be indicated here

Attachment 1 – NP Proposal

Description of scope and intent of revisions to ISO/IEC 12207 & ISO/IEC 15288 Objective Perform the minimum necessary to align the existing documents, including:

1. Common terminology 2. Common process names (where applicable) 3. Adherence to Guidelines for Process Definition (SWG 5) 4. Incorporation of the two ISO/IEC 12207 Amendments 5. Annexes in each document for process reference model information (to be used for

assessment purposes), if deemed useful. Intended Benefits

1. Gives the user community a chance to gradually evolve and transition. 2. Overcome current concerns about the perceived stability of the documents. 3. Removes difficulties of trying to achieve a completely integrated solution in one pass. 4. Defers coming up with a completely integrated set of processes. 5. Defers need to determine integrated document architecture. 6. Allows leveraging current experience with 12207 and 15288.

Proposed Process Constructs and Their Usage

7

Proposed Usage Proposed Usage –– Process ConstructsProcess Constructs

Activities

Processe s

P + O

12207R & 15288R

Note s

Increasing Level of D

etail

Other Documents

Other documents copy or reference material from 15288R, 12207R and add activ ities, tasks and/or guidance within the scope of the processes.

Examples:

14764 SW Maintenance

15026 (?) Assurance

15504 Process Assessment

15939 Measurement

16085 Risk Management

16326 SW Project Management

PRM Annex

Processes require a purpose, outcomes and tasks.

_______________________________

Activ ities are recommended as an aggregation construct for process tasks when there are numerous tasks. The activ ities prov ide a means to look at related tasks within a process to improv e understanding and communication of the process.

Guideline – create activities when there are 7 or more tasks.

_______________________________

Notes are used when there is need for explanatory information to better describe the intent or mechanics of a process. Notes are useful to prov ide some insight regarding potential implementation or areas of applicability, such as lists, examples, or other considerations.

Guideline – use notes for any example list of items that are addressed by the process or task. The PRM annex gathers

the purpose and outcome information.

Tasks

= Optional process construct

Attachment 1 - NP Proposal.doc 2005-05-27 Page 1 of 11


8

Proposed Usage Proposed Usage –– Activity ElaborationActivity Elaboration

Activities

Processes

P + O

12207R & 15288R

Notes

Increasing Level of Detail

PRM Annex

An activity may be further elaborated, when necessary for implementation or assessment reasons. Since activities must have tasks (by definition), when a purpose and outcomes are defined/required, the activity becomes a process.

The PRM annex gathers the purpose and outcome information.

Tasks


9

Proposed Usage Proposed Usage –– Process DecompositionProcess Decomposition

Activities

Processes

P + O

12207R & 15288R

Notes

Increasing Level of Detail

PRM Annex

A process may be decomposed into lower level processes, when necessary for implementation or assessment reasons. The decomposed process is still required to have purpose, outcomes, and tasks. Any process that cannot be defined with meaningful activities may be decomposed as far as is reasonable.

Tasks


Activities

Processes

P + O

Notes

Tasks

Activities

Processes

P + O

Notes

Tasks

…

Relationship of previous process constructs in ISO/IEC 15288 and the ISO/IEC 12207 (as Amended) to the new process constructs:



10

Relating Old to NewRelating Old to New

(Lower-Level) Processes

Tasks

Processes

P + O

12207R & 15288 R

Notes

Activities

PRM Annex

Activities

Tasks

Processes

12207:1995

(Some) Lists

Sub-Processes

Processes

P + O

12207:Amd

P + O

Processes

P + O

15288:2003

Notes

Activities

P + O

=

=

This chart is an overview. There will be exceptions to

the general cases.

New “bins”

+Tasks

The following relationships can exist among the processes:

11

Relationships among ProcessesRelationships among Processes

Process is-part-of Process, e.g.SW Detailed Design is-part-of SW Implementation(This is the relationship between processes and lower-level processes.)Also, Activity is-part-of Process

Process is-specialization-of Process, e.g.SW Implementation is-specialization-of Implementation

Process contributes-to Process, e.g.SW Installation contributes-to TransitionAlso, Activity contributes-to Process

Changes will be made to the development-oriented processes to capture the minimal relationships necessary to make the software and system processes interoperate. This includes the ISO/IEC 12207 Development Processes and the ISO/IEC 15288 Technical Processes related to development. The following is the intended scope of change:



13

Development Oriented ProcessesDevelopment Oriented Processes15288R 12207R Notes

(System Context) User would be allowed to use 15288 instead.Stakeholder requirements definition

P [SW] Sys Requirements elicitation is-specialization-of

Requirements analysis P [SW] Sys Requirements analysis is-specialization-ofArchitectural design P [SW] Sys Architectural design is-specialization-ofImplementation (See below)

P [SW] Implementation (See below)

Integration P [SW] Sys Integration is-specialization-ofVerification P [SW] Sys Qualification Testing contributes-toTransition P SW Installation contributes-to

P SW acceptance support contributes-toValidationImplementation P SW Implementation is-specialization-of

A SW Impl Strategy (was Process Impl).CP SW requirements analysis **CP SW architectural design **CP SW detailed designCP SW coding and testingCP SW integration **CP SW qualification testing **

For now, these remain specific to software.* Later we can rewrite them to create specialization relationships. Also, we would reverse the Amendments merger of the testing processes and the design processes.

Impact on 12207• Current development process is broken into two parts.• Users are allowed to use 15288 for “System Context” if they prefer.• Current activities would become processes with stated purposes and outcomes.• Some purposes and outcomes in Amendments might have to be rephrased.• Amendment’s merger of testing and design processes would be reversed.• Negligible normative impact.

Impact on 15288• Possibly some minor

modifications to purposes and outcomes.

• Negligible normative impact.

** Note: If recursion is applied to a low enough level with 15288, then these are obviated.

Minimum changes will be made to the “downstream” or post-deployment-oriented processes to ensure compatibility and adequately address shared and unique concerns. This includes the ISO/IEC 12207 and ISO/IEC 15288 processes related to Operations, Maintenance and Disposal. The following is the intended scope of change:



16

““DownstreamDownstream”” or postor post--deploymentdeployment--oriented processesoriented processes

15288R 12207R NotesOperation P [SW] Operation is-specialization of. User would be allowed to use

15288 instead.Maintenance P [SW] Maintenance is-specialization-ofDisposal P [SW] Disposal is-specialization-of. User would be allowed to user

15288 instead.

Impact on 12207• New Disposal process• Existing tasks of the maintenance process might be

binned into different activities.• Some tasks of maintenance and operations might be

rephrased slightly to clarify that software operation and maintenance are specializations of the system-level processes.

Impact on 15288• Probably little impact.

Operation• The motivation for the additional operations processes in the Amendment is unclear. Needs additional study.Maintenance• Software maintenance should be a specialization of system maintenance. We need to maintain compatibility with

14764.Disposal• 12207 needs a disposal process but the one in 15288 extends well beyond the scope of software. We probably

need a simpler disposal process.

Minimum changes will be made to the “project management and support” oriented processes to ensure compatibility, capture the minimal relationships necessary to make the software and system processes interoperate, sort out enterprise versus project in ISO/IEC 12207 and Amendments, and add supporting process concept to ISO/IEC 15288. This includes the ISO/IEC 12207 Project Management Processes, ISO/IEC 12207 Supporting Processes, and ISO/IEC 15288 Project processes. The following is the intended scope of change:



20

Project Management and Support GroupProject Management and Support Group15288 Processes 12207:1995 12207 Amd 1 PMBOK Approach

P ManagementC Organizational alignmentC Organizational management

P [Project] Management C Project ManagementA Initiation and scope defn Initiating

Project planning A Planning PlanningA Execution and … Execution

Project control … control ControllingProject assessment A Review and evaluation

A Closure ClosingC Quality management

Treated in Enterprise group

Treated in Enterprise groupRisk management C Risk management Relabel as "supporting" process and use purpose

and outcomes from 16085.C Measurement Relabel as "supporting" process and use purpose

and outcomes from 15939. Add to both 12207 and 15288. Will require rebinning some activities and tasks.

Decision-making Change process title to "Decision Management" in 15288. Add "Decision Management" process to 12207.

(Supporting processes)Information management P Documentation P Documentation Reconcile into a single supporting processConfiguration management P [SW] Configuration managementP [SW] Configuration Management (Merge or leave separate?)

P [SW] Quality assurance P [SW] Quality AssuranceP [SW] Verification process P [SW] VerificationP [SW] Validation process P [SW] ValidationP Joint review process P Joint ReviewP Audit process P AuditP Problem resolution process P Problem Resolution

P Change managementP Usability Relabel as "supporting" processP Product evaluation Investigate Product Evaluation, Verification, and

Qualification processes and remove redundancy/overlap.

In both 15288 and 12207, five processes (or five activities) similar to PMBOK process groups. This implies some additional processes in 15288 and some rebinning in 12207. Name processes: Project Initiation, Planning, Execution, Assesment & Control, and Project Closure .

For now these remain specific to software.*

Change process name to "Reviews" for 12207 and relax the requirement for "joint" participation to provide for broader application.

* Key to “Lite” approach

Impact on 12207:1995• A few new processes.• Some rebinning of existing tasks.• Possibly a few changes to Documentation.

Impact on 15288• A new class of “supporting processes”• A few new processes• Some rebinning of existing outcomes and activ ities.


Attachment 1 – NP Proposal Minimum changes will be made to the enterprise-oriented processes to ensure compatibility, capture the minimal relationships necessary to make the software and system processes interoperate, and sort out enterprise versus project in ISO/IEC 12207 and Amendments. This includes the ISO/IEC 12207:1995 Infrastructure, Improvement, Training Processes; ISO/IEC 12207: Amd Infrastructure, Improvement (establishment, assessment, improvement), and Human Resources / Training plus Organizational Alignment, Organizational Management, Quality Management, Knowledge Management; ISO/IEC 15288 Enterprise processes. The following is the intended scope of change:

23

Approach for Enterprise Oriented ProcessesApproach for Enterprise Oriented ProcessesAdd a note to state that the enterprise processes are not Add a note to state that the enterprise processes are not intended to describe complete processes, but rather the intended to describe complete processes, but rather the portion of the process that provides the necessary interface.portion of the process that provides the necessary interface.Ensure definition of the Ensure definition of the minimum set of outcomesminimum set of outcomes that a that a system or software project requires of the enterprise.system or software project requires of the enterprise.Establish a common set of process names, such as:Establish a common set of process names, such as:

Existing enterprise process names in 15288Existing enterprise process names in 15288Infrastructure and EnvironmentInfrastructure and EnvironmentLife Cycle Process Definition and ImprovementLife Cycle Process Definition and ImprovementHuman Resource Management and TrainingHuman Resource Management and TrainingFinancial Resource ManagementFinancial Resource ManagementQuality Management (the link to 9001)Quality Management (the link to 9001)Organizational AlignmentOrganizational AlignmentKnowledge ManagementKnowledge Management

Impact on 15288 and 12207Impact on 15288 and 12207Little: Existing outcomes, activities and tasks could be Little: Existing outcomes, activities and tasks could be rebinnedrebinned..Annex could provide additional material to enable assessment.Annex could provide additional material to enable assessment.

Minimum changes will be made to the agreement-oriented processes to ensure compatibility, capture the minimal relationships necessary to make the software and system processes interoperate, and ensure adequate communication between the acquirer and supplier. This includes the ISO/IEC 12207 and ISO/IEC 15288 processes for Acquisition and Supply. The following is the intended scope of change:



24

Strategy for Agreement ProcessesStrategy for Agreement ProcessesA single pair of A single pair of processes should work processes should work for both systems and for both systems and software.software.We should try to retain We should try to retain the good the good ““conversationsconversations”” of of 12207:1995 and 15288.12207:1995 and 15288.We should try to retain We should try to retain the component the component processes of 12207 processes of 12207 AmdAmd..A possible solutionA possible solution

Acquisition SupplyPrepare acq (None)Advertise acq

(None)

Contract execution

Closure Closure

(with additions)

Supplier tenderingSupplier selectionContract agreement

Contract agreement

Supplier monitoring

Acquirer acceptance

Product/service delivery

Harmonization Prop WD1

Additional considerations are as follows:

25

Reuse and Domain EngineeringReuse and Domain Engineering12207 12207 AmdAmd has processes for systematic software has processes for systematic software reusereuse

Domain engineeringDomain engineering[Reuse] Asset management[Reuse] Asset managementReuse program managementReuse program management

Product line management can be characterized as a Product line management can be characterized as a distinct project with some specialized processes.distinct project with some specialized processes.Approach:Approach:

ShortShort--term: Include the processes in the PRM annex.term: Include the processes in the PRM annex.LongLong--term: Write a distinct term: Write a distinct ““addadd--onon”” standard that standard that describes product line management.describes product line management.



28

TerminologyTerminologyTask/Process:Task/Process:

Use updated SWG5 guidelines.Use updated SWG5 guidelines.Explain the relationship between process constructs.Explain the relationship between process constructs.

Customer/Acquirer:Customer/Acquirer:12207 12207 AmdAmd uses the term uses the term ““customercustomer”” (probably to match up with (probably to match up with 9001)9001)12207:1995 and 15288:2003 use the term 12207:1995 and 15288:2003 use the term ““acquireracquirer””Alternative 1: Explain that Alternative 1: Explain that ““customercustomer”” and and ““acquireracquirer”” are are synonymous in these standards.synonymous in these standards.Alternative 2: Change Alternative 2: Change ““customercustomer”” back to back to ““acquireracquirer”” in the in the purposes and outcomes taken from 12207 purposes and outcomes taken from 12207 AmdAmd. . Explain that when we mean the user, we say Explain that when we mean the user, we say ““useruser””..

Item/Element:Item/Element:In 12207, replace In 12207, replace ““itemitem”” with with ““elementelement”” or stipulate that 12207or stipulate that 12207--item maps to 15288item maps to 15288--element. element.

Look for all other terminology mismatches.Look for all other terminology mismatches.

30

General Impacts on 12207General Impacts on 1220712207:199512207:1995

Process preambles would be replaced and/or supplemented by Process preambles would be replaced and/or supplemented by purpose and outcomes.purpose and outcomes.Some existing activities would be relabeled as processes, and Some existing activities would be relabeled as processes, and purposes, outcomes, and tasks would be added to them. purposes, outcomes, and tasks would be added to them. Some existing tasks would be Some existing tasks would be rebinnedrebinned into different activities.into different activities.Additional supporting processes would be added, e.g. risk Additional supporting processes would be added, e.g. risk management, measurement.management, measurement.Most lists would be turned into notes.Most lists would be turned into notes.Verify that relationships among activities of 12207 are not brokVerify that relationships among activities of 12207 are not broken.en.

AmendmentsAmendmentsMuch of the content could migrate into the PRM annex, if decisioMuch of the content could migrate into the PRM annex, if decision n that such a matrix adds value. Otherwise, relevant information that such a matrix adds value. Otherwise, relevant information would be added to processes and notes. would be added to processes and notes. Some processes would be added, subtracted, changed, or Some processes would be added, subtracted, changed, or devolved. These will require addition of tasks. devolved. These will require addition of tasks. Some purposes and outcomes would be modified.Some purposes and outcomes would be modified.



31

NearNear--term Investigationsterm InvestigationsVerification and Validation Issues:Verification and Validation Issues:

Is 15288 verification continuous or done at end?Is 15288 verification continuous or done at end?What is the relationship of 12207 What is the relationship of 12207 ““verificationverification”” and and ““evaluationevaluation”” to 15288 to 15288 ““verificationverification””??Are SW V&V specializations of Sys V&V?Are SW V&V specializations of Sys V&V?Analyze potential redundancy between Product Evaluation Analyze potential redundancy between Product Evaluation and Verification or Qualification Testingand Verification or Qualification Testing

Is SW CM a specialization of System CM?Is SW CM a specialization of System CM?Additional items re specialization:Additional items re specialization:

Applying the recursion concept of 15288, can we permit use of Applying the recursion concept of 15288, can we permit use of 15288 processes as alternatives to some of the SW15288 processes as alternatives to some of the SW--specific specific component (or sub) processes of SW Implementation?component (or sub) processes of SW Implementation?Also, some of the SWAlso, some of the SW--specific supporting processes?specific supporting processes?

These issues will be investigated while the draft of the document revisions are generated. Solutions that are

found will be incorporated.

32

Additional Tasks for RevisionsAdditional Tasks for RevisionsThe revision will include the following The revision will include the following additional tasks: additional tasks:

Identify and address additional instances where Identify and address additional instances where terminology is different between 15288, 12207 terminology is different between 15288, 12207 and 12207 and 12207 AmdAmd. . Determine which 12207 task lists would become Determine which 12207 task lists would become notes and which should remain as listsnotes and which should remain as listsWhere relationships of Where relationships of ““contributes tocontributes to”” and and ““is a is a specialization ofspecialization of”” exist, ensure there are no exist, ensure there are no conflictsconflictsMake sure that project process outcomes are Make sure that project process outcomes are suitable to stimulate the enterprise to provide suitable to stimulate the enterprise to provide outcomes needed by projects.outcomes needed by projects.


Attachment 1 – NP Proposal Schedule Meeting Date Task Helsinki 2005-05-27 Prepare NP proposal 2005-09-24 List of changes for 12207 and 15288

Possible implementation of some (most or all) of these changes in 12207 and focused on high-risk issues Distribute as a Working Group draft

Bari 2005-10-24 Discuss and agree on proposed changes to 12207 and 15288 Prepare near-FCD quality 12207 and 15288 2005-12-16 Distribute for WG 7 and WG 10 and WG 23 e-mail review 2006-01-30 Comments due to the Project Editors and Convener 2006-02-20 Editors in consultation with HSC decide if an editing meeting is

required. 2006-03-20 Possible date for an editing meeting (if needed) (Subject to

consideration of dates of holidays) 2006-04-17 FCD-quality 12207 and 15288 for WG 7 review Bangkok May 15, 2006 Final changes to the documents 2006-06-02 Submit to SC 7 Secretariat for FCD Ballot To Be Determined

2006-10-30 Disposition of any FCD comments

2007-01-26 Documents delivered to SC 7 Secretariat for FDIS Ballot

St. Petersburg

2007-05-21 In publication

Team

Current Project Editors for 15288 and 12207 will be utilized: • ISO/IEC 12207 Editor – Terry Doran • ISO/IEC 15288 Editor – Stuart Arnold

They will be assisted by:

• ISO/IEC 12207 Co-editor – Anatol Kark (subject to support) • ISO/IEC 15288 Co-editor – Garry Roedler • Alignment Co-editor– Jim Moore

Note: The Project Editors have the primary roles; the Co-Editors will assist the Project Editors in the planning, resolution, and integration of the changes.
