ISO/IEC JTC1/SC7 Software & Systems Engineering Secretariat: CANADA (SCC) SC7_AG; JTC1 Sec.; P, O & L Members

Transcription

1 ISO/IEC JTC1/SC7 Software & Systems Engineering Secretariat: CANADA (SCC) ISO/IEC JTC1/SC7 N Doc. Type Title Source NWI Proposal New Work Item Proposal Revision of ISO/IEC Systems and Software Engineering - Software Life Cycle SC7 / WG07 Project Status NP References Resolution 849 Action ID ACT Due Date Mailing Date Distribution Medium SC7_AG; JTC1 Sec.; P, O & L Members 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. 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 secretariat@jtc1-sc7.org

2 VOTE ON A PROPOSED NEW WORK ITEM ISO/IEC JTC 1/SC7 N3260 Date of Circulation of NP: Date of Ballot Close: Please return all votes and comments directly to the JTC 1/SC 7 Secretariat (secretariat@jtc1-sc7.org) by the due date indicated. Proposal for a new work item on Revision of ISO/IEC Systems and Software Engineering - Software Life Cycle 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 . Simply type your vote (with comments where applicable) into an message and send to Secretariat@jtc1-sc7.org.

3 ISO/IEC JTC 1/SC 7/WG 7 N New Work Item Proposal May 2005 PROPOSAL FOR A NEW WORK ITEM Date of presentation of proposal: Secretariat: Standards Council of Canada (SCC) Proposer: SC 7/WG 7 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 Systems and Software Engineering Software Life Cycle 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 (and its two Amendments) in order to decrease terminological and structural differences between the standard, its Amendments and ISO/IEC Justification: 1. ISO/IEC 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 Additionally, the IEEE did not adopt the Amendments for its IEEE 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 and the revision of ISO/IEC are planned to be executed concurrently.

4 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 and its amendments, ISO/IEC 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

5 A.1 Market Requirement Essential _x Desirable Supportive A.2 Regulatory Context Essential Desirable Supportive _ x _ Not Relevant Existing and potential users are confused as to the structure and use of the standard as amended 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 E. Cultural and Linguistic Adaptability Yes No_x F. Other Justification

6 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

7 Description of scope and intent of revisions to ISO/IEC & ISO/IEC 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 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 and Proposed Process Constructs and Their Usage Increasing Level of Detail Proposed Usage Process Constructs require a purpose, outcomes and tasks. Activities are recommended as an aggregation construct for process tasks when there are numerous tasks. The activities provide 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 provide 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. = Optional process construct 12207R & 15288R Acti vities Tasks Note s PRM Annex The PRM annex gathers the purpose and outcome information. Other Documents Other documents copy or reference material from 15288R, 12207R and add activ ities, tasks and/or guidance w ithin the scope of the processes. Examples: SW Maintenance (?) Assurance Process Assessment Measurement Risk Management SW Project Management 7 Attachment 1 - NP Proposal.doc Page 1 of 11

8 Proposed Usage Activity Elaboration Increasing Level of Detail 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 R & 15288R Activities Tasks Notes The PRM annex gathers the purpose and outcome information. PRM Annex = Optional process construct 8 Proposed Usage Process Decomposition 12207R & 15288R 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. Increasing Level of Detail Activities Tasks Activities Activities Notes Tasks Tasks PRM Annex Notes Notes = Optional process construct 9 Relationship of previous process constructs in ISO/IEC and the ISO/IEC (as Amended) to the new process constructs: Attachment 1 - NP Proposal.doc Page 2 of 11

9 Relating Old to New This chart is an overview. There will be exceptions to the general cases :Amd 12207: R & R 15288:2003 = Sub- = Activities Activities New bins Tasks Tasks Activities +Tasks (Some) Lists Notes Notes (Lower-Level) PRM Annex 10 The following relationships can exist among the processes: Relationships among 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 Transition Also, 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 Development and the ISO/IEC Technical related to development. The following is the intended scope of change: 11 Attachment 1 - NP Proposal.doc Page 3 of 11

10 ** Note: If recursion is applied to a low enough level with 15288, then these are obviated. Development Oriented 15288R 12207R Notes (System Context) User would be allowed to use instead. Stakeholder requirements P [SW] Sys Requirements elicitation is-specialization-of definition Requirements analysis P [SW] Sys Requirements analysis is-specialization-of Architectural design P [SW] Sys Architectural design is-specialization-of Implementation (See P [SW] Implementation (See below) below) Integration P [SW] Sys Integration is-specialization-of Verification P [SW] Sys Qualification Testing contributes-to Transition P SW Installation contributes-to P SW acceptance support contributes-to Validation Implementation P SW Implementation is-specialization-of A SW Impl Strategy (was Process Impl). For now, these remain specific to software.* Later CP SW requirements analysis ** CP SW architectural design ** CP SW detailed design CP SW coding and testing we can rewrite them to create specialization relationships. Also, we would reverse the Amendments merger of the testing processes and the design processes. CP SW integration ** CP SW qualification testing ** Impact on Possibly some minor modifications to purposes and outcomes. Negligible normative impact. Impact on Current development process is broken into two parts. Users are allowed to use 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. 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 and ISO/IEC processes related to Operations, Maintenance and Disposal. The following is the intended scope of change: 13 Attachment 1 - NP Proposal.doc Page 4 of 11

11 Downstream or post-deployment deployment- oriented processes 15288R 12207R Notes Operation P [SW] Operation is-specialization of. User would be allowed to use instead. Maintenance P [SW] Maintenance is-specialization-of Disposal P [SW] Disposal is-specialization-of. User would be allowed to user instead. 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 Disposal needs a disposal process but the one in extends well beyond the scope of software. We probably need a simpler disposal process. Impact on Probably little impact. Impact on 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 systemlevel processes. 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 and Amendments, and add supporting process concept to ISO/IEC This includes the ISO/IEC Project Management, ISO/IEC Supporting, and ISO/IEC Project processes. The following is the intended scope of change: 16 Attachment 1 - NP Proposal.doc Page 5 of 11

12 Project Management and Support Group : Amd 1 PMBOK Approach P Management Treated in Enterprise group C Organizational alignment C Organizational management P [Project] Management C Project Management In both and 12207, five processes (or five A Initiation and scope defn Initiating activities) similar to PMBOK process groups. This Project planning A Planning Planning implies some additional processes in and A Execution and Execution some rebinning in Project control control Controlling Name processes: Project Initiation, Planning, Project assessment A Review and evaluation Execution, Assesment & Control, and Project A Closure Closing Closure. C Quality management Treated in Enterprise group Risk management C Risk management Relabel as "supporting" process and use purpose and outcomes from C Measurement Relabel as "supporting" process and use purpose and outcomes from Add to both and Will require rebinning some activities and tasks. Decision-making Change process title to "Decision Management" in Add "Decision Management" process to (Supporting processes) Information management P Documentation P Documentation Reconcile into a single supporting process Configuration management P [SW] Configuration managementp [SW] Configuration Management (Merge or leave separate?) P [SW] Quality assurance P [SW] Quality Assurance P [SW] Verification process P [SW] Verification P [SW] Validation process P [SW] Validation P Joint review process P Joint Review P Audit process P Audit P Problem resolution process P Problem Resolution P Change management For now these remain specific to software.* * Key to Lite approach Change process name to "Reviews" for and relax the requirement for "joint" participation to provide for broader application. P Usability Relabel as "supporting" process P Product evaluation Investigate Product Evaluation, Verification, and Qualification processes and remove redundancy/overlap. Impact on A new class of supporting processes A few new processes Some rebinning of existing outcomes and activ ities. Impact on 12207:1995 A few new processes. Some rebinning of existing tasks. Possibly a few changes to Documentation. 20 Attachment 1 - NP Proposal.doc Page 6 of 11

13 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 and Amendments. This includes the ISO/IEC 12207:1995 Infrastructure, Improvement, Training ; ISO/IEC 12207: Amd Infrastructure, Improvement (establishment, assessment, improvement), and Human Resources / Training plus Organizational Alignment, Organizational Management, Quality Management, Knowledge Management; ISO/IEC Enterprise processes. The following is the intended scope of change: Approach for Enterprise Oriented Add a note to state that the enterprise processes are not intended to describe complete processes, but rather the portion of the process that provides the necessary interface. Ensure definition of the minimum set of outcomes that a system or software project requires of the enterprise. Establish a common set of process names, such as: Existing enterprise process names in Infrastructure and Environment Life Cycle Process Definition and Improvement Human Resource Management and Training Financial Resource Management Quality Management (the link to 9001) Organizational Alignment Knowledge Management Impact on and Little: Existing outcomes, activities and tasks could be rebinned. 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 and ISO/IEC processes for Acquisition and Supply. The following is the intended scope of change: 23 Attachment 1 - NP Proposal.doc Page 7 of 11

14 Strategy for Agreement A single pair of processes should work for both systems and software. We should try to retain the good conversations of 12207:1995 and We should try to retain the component processes of Amd. A possible solution Harmonization Prop WD1 (with additions) Acquisition Prepare acq Advertise acq Supplier selection Contract agreement Supplier monitoring Acquirer acceptance Closure Supply (None) Supplier tendering (None) Contract agreement Contract execution Product/service delivery Closure Additional considerations are as follows: Reuse and Domain Engineering Amd has processes for systematic software reuse Domain engineering [Reuse] Asset management Reuse program management Product line management can be characterized as a distinct project with some specialized processes. Approach: Short-term: term: Include the processes in the PRM annex. Long-term: Write a distinct add-on standard that describes product line management. 25 Attachment 1 - NP Proposal.doc Page 8 of 11

15 Terminology Task/Process: Use updated SWG5 guidelines. Explain the relationship between process constructs. Customer/Acquirer: Amd uses the term customer (probably to match up with 9001) 12207:1995 and 15288:2003 use the term acquirer Alternative 1: Explain that customer and acquirer are synonymous in these standards. Alternative 2: Change customer back to acquirer in the purposes and outcomes taken from Amd. Explain that when we mean the user, we say user. Item/Element: In 12207, replace item with element or stipulate that item maps to element. Look for all other terminology mismatches. 28 General Impacts on :1995 Process preambles would be replaced and/or supplemented by purpose and outcomes. Some existing activities would be relabeled as processes, and purposes, outcomes, and tasks would be added to them. Some existing tasks would be rebinned into different activities. Additional supporting processes would be added, e.g. risk manage ment, measure ment. Most lists would be turned into notes. Verify that relationships among activities of are not brok en. Amendments Much of the content could migrate into the PRM annex, if decision that such a matrix adds value. Otherwise, relevant information would be added to processes and notes. Some processes would be added, subtracted, changed, or devolved. These will require addition of tasks. Some purposes and outcomes would be modified. 30 Attachment 1 - NP Proposal.doc Page 9 of 11

16 Near-term Investigations Verification and Validation Issues: Is verification continuous or done at end? What is the relationship of verification and evaluation to verification? Are SW V&V specializations of Sys V&V? Analyze potential redundancy between Product Evaluation and Verification or Qualification Testing Is SW CM a specialization of System CM? Additional items re specialization: Applying the recursion concept of 15288, can we permit use of processes as alternatives to some of the SW-specific component (or sub) processes of SW Implementation? Also, some of the SW-specific supporting processes? These issues will be investigated while the draft of the document revisions are generated. Solutions that are found will be incorporated. 31 Additional Tasks for Revisions The revision will include the following additional tasks: Identify and address additional instances where terminology is different between 15288, and Amd. Determine which task lists would become notes and which should remain as lists Where relationships of contributes to and is a specialization of exist, ensure there are no conflicts Make sure that project process outcomes are suitable to stimulate the enterprise to provide outcomes needed by projects. 32 Attachment 1 - NP Proposal.doc Page 10 of 11

17 Schedule Meeting Date Task Helsinki Prepare NP proposal List of changes for and Possible implementation of some (most or all) of these changes in and focused on high-risk issues Distribute as a Working Group draft Bari Discuss and agree on proposed changes to and Prepare near-fcd quality and Distribute for WG 7 and WG 10 and WG 23 review Comments due to the Project Editors and Convener Editors in consultation with HSC decide if an editing meeting is required Possible date for an editing meeting (if needed) (Subject to consideration of dates of holidays) FCD-quality and for WG 7 review Bangkok May 15, 2006 Final changes to the documents To Be Determined Submit to SC 7 Secretariat for FCD Ballot Disposition of any FCD comments Documents delivered to SC 7 Secretariat for FDIS Ballot St. Petersburg In publication Team Current Project Editors for and will be utilized: ISO/IEC Editor Terry Doran ISO/IEC Editor Stuart Arnold They will be assisted by: ISO/IEC Co-editor Anatol Kark (subject to support) ISO/IEC 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. Attachment 1 - NP Proposal.doc Page 11 of 11