ISO/IEC/IEEE 12207, Systems And Software Engineering .
INTERNATIONALSTANDARDISO/IEC/IEEE12207First edition2017-11Systems and software engineering —Software life cycle processesIngénierie des systèmes et du logiciel — Processus du cycle de vie dulogicielReference numberISO/IEC/IEEE 12207:2017(E) ISO/IEC 2017 IEEE 2017Authorized licensed use limited to: Burapha University provided by UniNet. Downloaded on January 08,2018 at 04:42:14 UTC from IEEE Xplore. Restrictions apply.
ISO/IEC/IEEE 12207:2017(E) COPYRIGHT PROTECTED DOCUMENT ISO/IEC 2017, Published in Switzerland IEEE 2017All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized otherwise in any formor by any means, electronic or mechanical, including photocopying, or posting on the internet or an intranet, without priorwritten permission. Permission can be requested from either ISO or IEEE at the address below or ISO’s member body in thecountry of the requester.iiISO copyright officeCh. de Blandonnet 8 CP 401CH-1214 Vernier, Geneva, SwitzerlandTel. 41 22 749 01 11Fax 41 22 749 09 47copyright@iso.orgwww.iso.orgInstitute of Electrical and Electronics Engineers, Inc3 Park Avenue, New YorkNY 10016-5997, USAstds.ipr@ieee.orgwww.ieee.org ISO/IEC 2017 – All rights reserved IEEE 2017 – All rights reservedAuthorized licensed use limited to: Burapha University provided by UniNet. Downloaded on January 08,2018 at 04:42:14 UTC from IEEE Xplore. Restrictions apply.
ISO/IEC/IEEE 12207:2017(E)ContentsPageForeword .viIntroduction . vii11.11.21.31.4Scope . 1Overview .1Purpose . 1Field of application .1Limitations . 22Normative references .233.13.2Terms, definitions, and abbreviated terms . 2Terms and definitions . 2Abbreviated terms . 1144.14.24.2.14.2.24.3Conformance. 11Intended usage . 11Full conformance. 12Full conformance to outcomes . 12Full conformance to tasks . 12Tailored conformance . 45.6.55.75.8Key concepts and application. 13Introduction . 13Software system concepts . 13Software systems. 13Software system structure . 13Enabling systems . 15Life cycle processes for the software system . 16Organization and project concepts. 16Organizations . 16Organization and project-level adoption . 17Life cycle concepts . 17Software life cycle stages . 17Life cycle model for the software system . 17Process concepts . 19Criteria for processes. 19Description of processes . 19General characteristics of processes . 19Tailoring. 19Process groups . 19Introduction . 19Agreement processes . 21Organizational project-enabling processes . 22Technical Management processes . 22Technical processes . 22Process application . 22Process reference model . 2366.16.1.16.1.26.26.2.16.2.26.2.36.2.4Software life cycle processes . 24Agreement processes . 24Acquisition process . 24Supply process . 27Organizational Project-Enabling processes . 28Life cycle model management process . 29Infrastructure Management process . 30Portfolio Management process . 31Human Resource Management process . 33iii ISO/IEC 2017 – All rights reserved IEEE 2017 – All rights reservedAuthorized licensed use limited to: Burapha University provided by UniNet. Downloaded on January 08,2018 at 04:42:14 UTC from IEEE Xplore. Restrictions apply.
ISO/IEC/IEEE y Management process.34Knowledge Management process .36Technical Management processes.37Project Planning process .38Project assessment and control process .40Decision Management process .43Risk Management process .44Configuration Management process .46Information Management process .50Measurement process .52Quality Assurance process .53Technical processes .55Business or Mission Analysis process .56Stakeholder Needs and Requirements Definition process .59System/Software requirements definition process .63Architecture Definition process .66Design Definition process .71System Analysis process .74Implementation process .75Integration process .79Verification process .82Transition process.85Validation process .89Operation process .92Maintenance process .95Disposal process .99Annex A (normative) Tailoring process . 102A.1Introduction . 102A.2Tailoring process . 102A.2.1 Purpose . 102A.2.2 Outcomes . 102A.2.3 Activities and tasks . 102Annex B (informative) Examples of process information items . 104Annex C (informative) Process Reference Model for assessment purposes . 107C.1Introduction . 107C.2Conformance with ISO/IEC 33004. 107C.2.1 General . 107C.2.2 Requirements for process reference models . 107C.2.3 Process descriptions . 108C.3The process reference model . 108Annex D (informative) Process integration and process constructs. 109D.1Introduction . 109D.2Process constructs and their usage . 109Annex E (informative) Process views . 111E.1Introduction . 111E.2The process view concept . 111E.3Process viewpoint . 111E.4Process view for specialty engineering . 112E.5Process view for interface management . 114E.6Process view for software assurance (Information security) . 116Annex F (informative) Software system architecture modelling . 120F.1Introduction . 120F.2Views, models and model kinds used in software system architecture . 120F.2.1 Functional model . 120F.2.2 Static model . 121F.2.3 Data model . 121F.2.4 Behavioral model. 121F.2.5 Temporal model . 121F.2.6 Structural model . 121iv ISO/IEC 2017 – All rights reserved IEEE 2017 – All rights reservedAuthorized licensed use limited to: Burapha University provided by UniNet. Downloaded on January 08,2018 at 04:42:14 UTC from IEEE Xplore. Restrictions apply.
ISO/IEC/IEEE 12207:2017(E)F.2.7F.3Network model .121Other model considerations .121Annex G (informative) Application of software life cycle processes to a system of systems .123G.1Introduction .123G.2SoS characteristics and types .123G.3SE processes applied to systems of systems .124G.3.1 General .124G.3.2 Agreement processes .124G.3.3 Organizational project enabling processes .124G.3.4 Technical management processes .125G.3.5 Technical processes .125Annex H (informative) Application of Agile .127Annex I (informative) Process Mapping from ISO/IEC/IEEE 12207:2008 .129Bibliography.143List of IllustrationsFigure 1 —Software system and software system element relationship . 14Figure 2 —Example of software system-of-interest structure. 14Figure 3 —Software system-of-interest, its operational environment and enabling systems . 15Figure 4 —Software life cycle processes . 21Table B.1 — Sample information items by process .104Figure D.1 — ISO/IEC/IEEE 12207:2017 and ISO/IEC/IEEE 15288:2015 process constructs.110Table G.1 — System of Systems types .123Table I.1 — Comparison of processes in ISO/IEC/IEEE 12207:2017 and the previous edition .129Table I.2 — Comparison of process outcomes in ISO/IEC/IEEE 12207:2017 and software-relatedoutcomes in the previous edition .131v ISO/IEC 2017 – All rights reserved IEEE 2017 – All rights reservedAuthorized licensed use limited to: Burapha University provided by UniNet. Downloaded on January 08,2018 at 04:42:14 UTC from IEEE Xplore. Restrictions apply.
ISO/IEC/IEEE 12207:2017(E)ForewordISO (the International Organization for Standardization) and IEC (the International Electrotechnical Commission)form the specialized system for worldwide standardization. National bodies that are members of ISO or IECparticipate in the development of International Standards through technical committees established by therespective organization to deal with particular fields of technical activity. ISO and IEC technical committeescollaborate in fields of mutual interest. Other international organizations, governmental and non‐governmental, inliaison with ISO and IEC, also take part in the work. In the field of information technology, ISO and IEC haveestablished a joint technical committee, ISO/IEC JTC 1.IEEE Standards documents are developed within the IEEE Societies and the Standards Coordinating Committeesof the IEEE Standards Association (IEEE‐SA) Standards Board. The IEEE develops its standards through aconsensus development process, approved by the American National Standards Institute, which brings togethervolunteers representing varied viewpoints and interests to achieve the final product. Volunteers are notnecessarily members of the Institute and serve without compensation. While the IEEE administers the processand establishes rules to promote fairness in the consensus development process, the IEEE does not independentlyevaluate, test, or verify the accuracy of any of the information contained in its standards.The procedures used to develop this document and those intended for its further maintenance are described inthe ISO/IEC Directives, Part 1. In particular, the different approval criteria needed for the different types ofdocument should be noted. This document was drafted in accordance with the editorial rules of theISO/IEC Directives, Part 2 (see www.iso.org/directives).Attention is drawn to the possibility that some of the elements of this document may be the subject of patentrights. ISO, IEC, and IEEE shall not be held responsible for identifying any or all such patent rights. Details of anypatent rights identified during the development of the document will be in the Introduction and/or on the ISO listof 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 constitutean endorsement.For an explanation on the meaning of ISO specific terms and expressions related to conformity assessment, as wellas information about ISO’s adherence to the World Trade Organization (WTO) principles in the Technical Barriersto Trade (TBT) see the following URL www.iso.org/iso/foreword.html.This document was prepared by Joint Technical Committee ISO/IEC JTC 1, Information technology, SubcommitteeSC 7, Systems and software engineering, in cooperation with the IEEE Computer Society Systems and SoftwareEngineering Standards Committee, under the Partner Standards Development Organization cooperationagreement between ISO and IEEE.This first edition of ISO/IEC/IEEE 12207 cancels and replaces ISO/IEC 12207:2008 (second edition), which hasbeen technically revised.Changes in this revision of ISO/IEC/IEEE 12207 were developed in conjunction with a corresponding revision ofISO/IEC/IEEE 15288:2015, Systems and software engineering – System life cycle processes. The purpose of theserevisions is to accomplish the harmonization of the structures and contents of the two documents, whilesupporting the requirements of the engineering and assessment communities.This document was developed with the following goals:— provide a common terminology between the revision of ISO/IEC/IEEE 15288 and ISO/IEC/IEEE 12207;— where applicable, provide common process names and process structure between the revision ofISO/IEC/IEEE 15288 and ISO/IEC/IEEE 12207; and— enable the user community to evolve towards fully harmonized standards, while allowing backwardcompatibility.This revision is intended to achieve a fully harmonized view of the system and software life cycle processes.vi ISO/IEC 2017 – All rights reserved IEEE 2017 – All rights reservedAuthorized licensed use limited to: Burapha University provided by UniNet. Downloaded on January 08,2018 at 04:42:14 UTC from IEEE Xplore. Restrictions apply.
ISO/IEC/IEEE 12207:2017(E)IntroductionThe complexity of software systems has increased to an unprecedented level. This has led to new opportunities,but also to increased challenges for the organizations that create and utilize systems. These challenges existthroughout the life cycle of a system and at all levels of architectural detail. This document provides a commonprocess framework for describing the life cycle of systems created by humans, adopting a Software Engineeringapproach. Software Engineering is an interdisciplinary approach and means to enable the realization of successfulsoftware systems. It focuses on defining stakeholder needs and required functionality early in the developmentcycle, documenting requirements, and performing design synthesis and system validation while considering thecomplete problem. It integrates all the disciplines and specialty groups into a team effort forming a structureddevelopment process that proceeds from concept to production to operation and maintenance. It considers boththe business and the technical needs of all stakeholders with the goal of providing a quality pr
This first edition of ISO/IEC/IEEE 12207 cancels and replaces ISO/IEC 12207:2008 (second edition), which has been technically revised. Changes in this revision of ISO/IEC/IEEE 12207 were developed in conjunction with a corresponding revision of ISO/IEC/IEEE 15288:2015, Systems and so
IEC 61215 IEC 61730 PV Modules Manufacturer IEC 62941 IEC 62093 IEC 62109 Solar TrackerIEC 62817 PV Modules PV inverters IEC 62548 or IEC/TS 62738 Applicable Standard IEC 62446-1 IEC 61724-1 IEC 61724-2 IEC 62548 or IEC/TS 62738 IEC 62548 or IEC/TS 62738 IEC 62548 or IEC/TS 62738 IEC 62548 or IEC/
IEEE 3 Park Avenue New York, NY 10016-5997 USA 28 December 2012 IEEE Power and Energy Society IEEE Std 81 -2012 (Revision of IEEE Std 81-1983) Authorized licensed use limited to: Australian National University. Downloaded on July 27,2018 at 14:57:43 UTC from IEEE Xplore. Restrictions apply.File Size: 2MBPage Count: 86Explore furtherIEEE 81-2012 - IEEE Guide for Measuring Earth Resistivity .standards.ieee.org81-2012 - IEEE Guide for Measuring Earth Resistivity .ieeexplore.ieee.orgAn Overview Of The IEEE Standard 81 Fall-Of-Potential .www.agiusa.com(PDF) IEEE Std 80-2000 IEEE Guide for Safety in AC .www.academia.eduTesting and Evaluation of Grounding . - IEEE Web Hostingwww.ewh.ieee.orgRecommended to you b
ISO/IEC/IEEE 29148:2011 Systems and software engineering — Life cycle processes — Requirements engineering ISO/IEC/IEEE 12207:2008 Systems and software engineering — Software life cycle processes ISO/IEC/IEEE 24765:2010 Systems and software engineering — Vocabulary IEEE 1220 (ISO /IEC 26702) Systems engineering — Application
Mar 23, 2001 · IEEE/EIA 12207.0-1996 is not being followed, this standard can continue to be applied. To facilitate use with IEEE/EIA 12207 series, the standard is written using the vocabulary and style of IEEE/ EIA 12207.0-1996. Finally, this standard supports the IEEE standards that involve the management of specific categories of risk, such as IEEE Std .
IEC has formed IECRE for Renewable Energy System verification - Component quality (IEC 61215, IEC 61730, IEC 62891, IEC 62109, IEC 62093, IEC 61439, IEC 60947, IEC 60269, new?) - System: - Design (IEC TS 62548, IEC 60364-7-712, IEC 61634-9-1, IEC 62738) - Installation (IEC 62548, IEC 60364-7-712)
ISO/IEC 27011:2008 . Information security management guidelines for tele-communications organizations based on ISO/IEC 27002. ISO/IEC 27013:2015 . Guidance on the integrated implementation of ISO/IEC 27001 . and ISO/IEC 20000-1. ISO/IEC 27014:2013includes nearly 20 standards. The . Governance of information security. ISO/IEC 27015:2012
IEC 61869-9, IEC 62351 (all parts), IEC 62439-1:2010, IEC 62439-3:2010, IEC 81346 (all parts), IEC TS 62351- 1, IEC TS 62351- 2, IEC TS 62351- 4, IEC TS 62351- 5, Cigre JWG 34./35.11, IEC 60044 (all parts), IEC 60050 (all parts), IEC 60270:2000, IEC 60654-4:1987, IEC 60694:1
planned care. Mental health services are also under pressure – for example, national data published in November 2018 found that 675 patients in acute need were admitted to mental health units outside their local area (NHS Digital 2019b), a practice that the government has committed to eliminate by 2020/21. In the longer term, if substantial .
