BS PD ISO IEC TS 30103-2015 Software and Systems Engineering Lifecycle Processes Framework for Product Quality Achievement《软件和系统工程 生命周期过程 产品质量成就框架》.pdf

1、BSI Standards Publication Software and Systems Engineering Lifecycle Processes Framework for Product Quality Achievement PD ISO/IEC TS 30103:2015National foreword This Published Document is the UK implementation of ISO/IEC TS 30103:2015. The UK participation in its preparation was entrusted to Techn

2、ical Committee IST/15, Software and systems engineering. A list of organizations represented on this committee can be obtained on request to its secretary. This publication does not purport to include all the necessary provisions of a contract. Users are responsible for its correct application. The

3、British Standards Institution 2015. Published by BSI Standards Limited 2015 ISBN 978 0 580 78374 6 ICS 35.080 Compliance with a British Standard cannot confer immunity from legal obligations. This Published Document was published under the authority of the Standards Policy and Strategy Committee on

4、31 October 2015. Amendments/corrigenda issued since publication Date Text affected PUBLISHED DOCUMENT PD ISO/IEC TS 30103:2015Software and Systems Engineering Lifecycle Processes Framework for Product Quality Achievement Ingnierie du logiciel et des systmes Processus du cycle de vie Cadre pour la ra

5、lisation de la qualit du produit ISO/IEC TS 30103 First edition 2015-09-15 Reference number ISO/IEC TS 30103:2015(E) TECHNICAL SPECIFICATION ISO/IEC 2015 PD ISO/IEC TS 30103:2015 ii ISO/IEC 2015 All rights reserved COPYRIGHT PROTECTED DOCUMENT ISO/IEC 2015, Published in Switzerland All rights reserv

6、ed. Unless otherwise specified, no part of this publication may be reproduced or utilized otherwise in any form or by any means, electronic or mechanical, including photocopying, or posting on the internet or an intranet, without prior written permission. Permission can be requested from either ISO

7、at the address below or ISOs member body in the country of the requester. ISO copyright office Ch. de Blandonnet 8 CP 401 CH-1214 Vernier, Geneva, Switzerland Tel. +41 22 749 01 11 Fax +41 22 749 09 47 copyrightiso.org www.iso.org ISO/IEC TS 30103:2015(E) PD ISO/IEC TS 30103:2015 ISO/IEC TS 30103:20

8、15(E)Foreword v Introduction vi 1 Scope . 1 1.1 Application . 1 1.2 Audience . 2 1.3 Limitations 2 2 Motivation 2 3 T erms, definitions and abbr e viat ed t erms 3 4 Quality achievement concepts 4 4.1 Overview of quality achievement . 4 4.2 Guiding principles and approach 5 4.3 Localization of quali

9、ty responsibility 6 4.3.1 Establishing system element requirements . 6 4.3.2 Identification of process instances . 8 4.4 Creation of process instance descriptions 8 4.4.1 Establishment of success criteria 8 4.4.2 Identification of detailed activities and tasks . 9 4.4.3 Process instance descriptions

10、 .10 4.5 Consistency with institutional knowledge .11 4.6 Maintenance of content consistency .12 5 R equir ed back gr ound c onc epts .13 5.1 System and Software Concepts 13 5.2 Life cycle concepts 13 5.3 Process concepts 14 5.4 Organizational concepts 14 5.5 Information Item Concepts .14 5.6 Notion

11、 of technical management .14 6 Context of application 14 6.1 Relationship to other standards14 6.2 Organizational context 16 6.3 Stakeholder context .16 6.4 Stage context 16 6.5 Process context 16 6.6 Information item context 17 7 Potential process augmentations .17 7.1 Project planning process .17

12、7.2 Project assessment and control process 17 8 Guidelines for process augmentations .17 8.1 Project planning process .17 8.2 Project assessment and control process 18 9 Potential information item augmentations .18 9.1 Process Instance Descriptions 18 9.2 Consistency tracker 18 10 Guidelines for inf

13、ormation item augmentations .19 10.1 Process instance descriptions .19 10.2 Consistency tracker 19 Annex A (informative) Ex ample: Establishing S y st em Element R equir ements.20 Annex B (informative) Example: Creation of Process Instance Descriptions23 Annex C (informative) Example: Consistency Tr

14、acker 27 ISO/IEC 2015 All rights reserved iii Contents Page PD ISO/IEC TS 30103:2015 ISO/IEC TS 30103:2015(E)Annex D (informative) Ex ample: Pr oc ess V ie w for Specific R equir ement28 Annex E (informative) Theoretical Foundations .34 Annex F (informative) Example Set of Mutual Consistency Relatio

15、nships .37 Bibliogr aph y .38 iv ISO/IEC 2015 All rights reserved PD ISO/IEC TS 30103:2015 ISO/IEC TS 30103:2015(E) Foreword ISO (the International Organization for Standardization) and IEC (the International Electrotechnical Commission) form the specialized system for worldwide standardization. Nat

16、ional bodies that are members of ISO or IEC participate in the development of International Standards through technical committees established by the respective organization to deal with particular fields of technical activity. ISO and IEC technical committees collaborate in fields of mutual interes

17、t. Other international organizations, governmental and non-governmental, in liaison with ISO and IEC, also take part in the work. In the field of information technology, ISO and IEC have established a joint technical committee, ISO/IEC JTC 1. The procedures used to develop this document and those in

18、tended for its further maintenance are described in the ISO/IEC Directives, Part 1. In particular the different approval criteria needed for the different types of document should be noted. This document was drafted in accordance with the editorial rules of the ISO/IEC Directives, Part 2 (see www.is

19、o.org/directives). Attention is drawn to the possibility that some of the elements of this document may be the subject of patent rights. ISO and IEC shall not be held responsible for identifying any or all such patent rights. Details of any patent rights identified during the development of the docu

20、ment will be in the Introduction and/or on the ISO list of patent declarations received (see www.iso.org/patents). Any trade name used in this document is information given for the convenience of users and does not constitute an endorsement. For an explanation on the meaning of ISO specific terms an

21、d expressions related to conformity assessment, as well as information about ISOs adherence to the WTO principles in the Technical Barriers to Trade (TBT) see the following URL: Foreword - Supplementary information The committee responsible for this document is ISO/IEC JTC 1, Information technology,

22、 SC 7, Software and Systems Engineering. ISO/IEC 2015 All rights reserved v PD ISO/IEC TS 30103:2015 ISO/IEC TS 30103:2015(E) Introduction This Technical Specification provides guidance on the application of ISO/IEC/IEEE 15288:2008 1life cycle processes with specific reference to addressing quality

23、in projects that deliver systems and software products and services. It focuses on a systematic approach to achieving quality, involving the development of certain information items, the inter-relationships between these information items and the maintenance and mutual consistency management of thes

24、e information items. In particular, it describes how to develop detailed specifications of the collection of process instances needed to produce a specific product or system and achieve its quality goals. It describes how the guidance in life cycle process standards may be applied in conjunction wit

25、h other standards (such as the ISO/IEC 25000 12SQuaRE series of standards that address the specification, measurement and evaluation of product quality) to achieve quality during the development of a specific system. Application of life cycle processes to develop a system involves the production of,

26、 among others, a collection of information items such as stakeholder requirements, system requirements, designs, plans, and technical strategies, as well as a collection of artefacts including the various system elements and enabling systems. The guidance in this Technical Specification is based on

27、the following principles: Lo c a liz a t i o n o f q ua li t y re sp o nsi b ili t y: Requirements should be established for each system element and enabling system, derived from the overall system requirements; the set of process instances needed to develop each system element or enabling system sh

28、ould be identified; their responsibilities towards quality are demarcated by the outcomes defined for the corresponding life cycle process in ISO/IEC/IEEE 15288; Creation of process instance descriptions: For each process instance, success criteria should be established based on the outcomes defined

29、 for the corresponding life cycle process, the characteristics and requirements of the particular system element, and requirements and constraints arising from product decisions made in other process instances; the set of specific tasks and associated competencies needed to achieve these success cri

30、teria should be identified, particularly for system elements with significant quality risk; Consistency with institutional knowledge: Achievement of quality ultimately depends on correct technical decisions. Relevant institutional knowledge should be systematically identified and deployed for making

31、 product and process decisions, and the resulting information items and artefacts should be checked for consistency with the applicable bodies of institutional knowledge; Maintenance of content consistency: All the information items, including the process instance specifications themselves, may evol

32、ve concurrently throughout the development life cycle. Content consistency relationships among the various information items and artefacts should be tracked and managed as these information items and artefacts evolve concurrently. The Technical Specification is applicable to any project involving th

33、e development, enhancement or re-engineering of systems with hardware, software and human elements. It is particularly useful to project organizations that operate in multiple application domains where the set of critical quality characteristics varies widely across projects, requiring a more system

34、atic and detailed approach to planning the achievement of quality during the development stage of the system life cycle. This Technical Specification is intended to provide guidance for two-party situations and may be equally applied where the two parties are from the same organization. This Technic

35、al Specification can also be used by a single party as self-imposed tasks. This Technical Specification can also serve as guidance in multi-party situations, where high risks are inherent in the supply and integration of complex systems, and procurement can involve several suppliers, organizations o

36、r contracting parties.vi ISO/IEC 2015 All rights reserved PD ISO/IEC TS 30103:2015 Software and Systems Engineering Lifecycle Processes Framework for Product Quality Achievement 1 Scope 1.1 Application This Technical Specification provides guidance on applying processes from ISO/IEC/IEEE 15288:2008

37、1in conjunction with other standards to contribute to achieving quality of systems and software products and services during the development stage of the life cycle (6.4), the information items that should be produced through the implementation of the relevant processes (6.5), and the new informatio

38、n items (Clauses 9 and 10). The scope of this Technical Specification is to indicate how to apply the life cycle processes in ISO/IEC/ IEEE 15288:2008 to achieve quality in the context of a specific product. It is independent of any tailoring that may be made to modify the generic process descriptio

39、ns to suit the needs of a particular context. Even after any applicable tailoring, there is a need to apply the resulting process guidance and determine the specific detailed activities, tasks and associated success criteria for each of the process instances needed to deliver the target system. That

40、 is the focus of the framework described in this Technical Specification. This Technical Specification is applicable to those who use or plan to use ISO/IEC/IEEE 15288:2008 on projects dealing with man-made systems, software-intensive systems, software products, and services related to those systems

41、 and products, regardless of project scope, product(s), service(s), methodology, size or complexity, those who use or plan to use ISO/IEC/IEEE 15289 5on projects dealing with man-made systems, software-intensive systems, software products, and services related to those systems and products, regardle

42、ss of project scope, product(s), methodology, size or complexity, anyone performing technical processes and tasks, those who are responsible for the technical management of projects concerned with the development of systems, those responsible for performing ISO/IEC/IEEE 15288:2008 life cycle process

43、es at a project level, organizations and individuals subcontracting a project management effort, anyone developing systems engineering management documentation to complete technical planning aspects of their project processes, anyone performing systems engineering activities, project managers respon

44、sible for staffing projects and identifying competency development needs, anyone developing information items during the application of project and technical processes, and anyone performing project and technical processes to aid in ensuring that the information items developed during these processe

45、s conform to ISO/IEC/IEEE 15289. TECHNICAL SPECIFICATION ISO/IEC TS 30103:2015(E) ISO/IEC 2015 All rights reserved 1 PD ISO/IEC TS 30103:2015 ISO/IEC TS 30103:2015(E) 1.2 Audience The guidance in this Technical Specification is intended to be used in the development and maintenance stages of the lif

46、e cycle by all organizations and projects that develop or maintain systems and software products and services. It is of particular value to organizations that work in a variety of application domains, where the set of critical quality characteristics and approaches to achieve them vary widely across

47、 projects. 1.3 Limitations The achievement of quality ultimately depends on the competent performance of technical and management tasks. While this Technical Specification provides guidance on a systematic approach to quality achievement, including identification of needed competencies, the use of t

48、he approach alone is not sufficient to guarantee achievement of quality. This Technical Specification provides guidance on developing detailed specifications of the collection of process instances needed to develop the product or service including the artefact-specific tasks within each process inst

49、ance, but it does not address sequencing and information flow issues among these tasks and processes. The area of situational method engineering 8addresses the problem of organizing the collection of tasks into a network with defined information flow patterns. Tradeoffs among quality attributes are intentionally not addressed. Tradeoffs are part of the enactment of requirements, design, planning and other processes. Any iteration needed to address tradeoffs is part of concurrent elaboration