GB/T 8566-2022 English PDFUS$1989.00 · In stock
Delivery: <= 10 days. True-PDF full-copy in English will be manually translated and delivered via email. GB/T 8566-2022: Systems and software engineering - Software life cycle processes Status: Valid GB/T 8566: Historical versions
Basic dataStandard ID: GB/T 8566-2022 (GB/T8566-2022)Description (Translated English): Systems and software engineering - Software life cycle processes Sector / Industry: National Standard (Recommended) Classification of Chinese Standard: L77 Classification of International Standard: 35.080 Word Count Estimation: 114,142 Date of Issue: 2022-10-12 Date of Implementation: 2023-05-01 Older Standard (superseded by this standard): GB/T 8566-2007 Issuing agency(ies): State Administration for Market Regulation, China National Standardization Administration GB/T 8566-2022: Systems and software engineering - Software life cycle processes---This is a DRAFT version for illustration, not a final translation. Full copy of true-PDF in English version (including equations, symbols, images, flow-chart, tables, and figures etc.) will be manually/carefully translated upon your order.Systems and software engineering - Software life cycle processes ICS 35.080 CCSL77 National Standards of People's Republic of China Replacing GB/T 8566-2007 Systems and Software Engineering Software Life Cycle Process (ISO /IEC /IEEE12207.2017, IDT) Released on 2022-10-12 2023-05-01 implementation State Administration for Market Regulation Released by the National Standardization Management Committee table of contentsPreface III Introduction IV 1 Scope 1 1.1 Overview 1 1.2 Purpose 1 1.3 Application field 1 1.4 Restrictions 2 2 Normative references 2 3 Terms and Definitions, Abbreviations 2 3.1 Terms and Definitions 2 3.2 Abbreviations 9 4 Compliance10 4.1 Intended usage 10 4.2 Fully compliant with 11 4.3 Tailoring to fit 11 5 Key concepts and applications 11 5.1 Guide 11 5.2 Software system concepts 11 5.3 Organizational and project concepts 15 5.4 Life Cycle Concept 15 5.5 Process concept 17 5.6 Process Group 17 5.7 Process application 19 5.8 Process Reference Model 20 6 Software life cycle processes 20 6.1 Agreement Process Group 20 6.2 Organizational Project Enablement Process Group 24 6.3 Technology Management Process Group 30 6.4 Technical Process Group 43 Appendix A (Normative) Tailoring process 79 Appendix B (informative) Examples of process information items 81 Annex C (informative) Process reference model for evaluation purposes85 Appendix D (Informative) Process Integration and Process Architecture 87 Appendix E (informative) Process View 89 Appendix F (Informative) Software System Architecture Modeling 96 Appendix G (informative) Applying software life cycle processes to systems of systems 98 Appendix H (Informative) Agile Applications 101 Appendix NA (informative) Differences between this document and GB/T 8566-2007 103 References 107forewordThis document is in accordance with the provisions of GB/T 1.1-2020 "Guidelines for Standardization Work Part 1.Structure and Drafting Rules for Standardization Documents" drafting. This document and GB/T 22032-2021 "System and Software Engineering System Life Cycle Process" together constitute the software and system engineering Basic standards in the field. This document replaces GB/T 8566-2007 "Information Technology Software Life Cycle Process". Compared with GB/T 8566-2007, except knot In addition to structural adjustments and editorial changes, the main technical changes are as follows. --- Terms and definitions have been adjusted and supplemented (see Chapter 3, Chapter 3 of the.2007 edition); ---The software life cycle process model has made major adjustments and changes (see Appendix NA for details). This document is equivalent to ISO /IEC /IEEE12207.2017 "System and Software Engineering Software Life Cycle Process". The following minimal editorial changes have been made to this document. ---Delete Appendix I (informative) and the process mapping of ISO /IEC /IEEE12207.2008, the.2007 version replaced by this document adopts ISO /IEC 12207.1995, this document adopts ISO /IEC /IEEE12207.2017, ISO /IEC /IEEE12207.2008 It is an intermediate version, meaningless to national standards, and does not involve changes in technical content; --- Added Appendix NA (informative). Please note that some contents of this document may refer to patents. The issuing agency of this document assumes no responsibility for identifying patents. This document is proposed and managed by the National Information Technology Standardization Technical Committee (SAC/TC28). This document was drafted by. Zhejiang Institute of Electronic Information Product Inspection, China Institute of Electronic Technology Standardization, Jiangsu Saixi Technology Development Co., Ltd. Exhibition Co., Ltd., Shenzhen Saixi Information Technology Co., Ltd., the 54th Research Institute of China Electronics Technology Group Corporation, Beijing Aerospace Automatic Control Institute, Zhejiang SUPCON Technology Co., Ltd., China Aviation Development Commercial Aviation Engine Co., Ltd., Shandong Shanke Digital Economy Research Academy Co., Ltd., China Academy of Aerospace Systems Science and Engineering, Beijing Software and Information Service Exchange Co., Ltd., Shanghai Baosight Software Co., Ltd. Co., Ltd., Dalian University of Technology, Tenth Research Institute of China Electronics Technology Group Corporation, Shandong Provincial Computing Center (National Supercomputing Jinan Center Heart), Guangdong Yian Civil Air Defense Engineering Technology Co., Ltd., Shanghai Computer Software Technology Development Center, Beijing CCID Certification Center Co., Ltd., Chengdu Sifang Weiye Software Co., Ltd., Shandong Genzon Information Technology Co., Ltd., Beijing Huayu Software Co., Ltd., Shanghai City Software Evaluation Center Co., Ltd. The main drafters of this document. Zhang Jun, Zhang Yangyang, Ji Yongwei, Li Wenpeng, Sun Jimin, Zhao Haoqiang, Guo Xiaohui, Liu Yongzhao, Zhu Qin, Li Gang, Yang Guizhi, Yu Tieqiang, Zhang Xingxing, Huang Yumei, Song Mingqiu, Dong Limei, He Chang, Sun Jinyang, Wang Gongtao, Ma Lie, Hu Yun, Yan Huaibai, Song Lihua, Qi Yuqi, Zhuangzhuang, Wang Chunxiao, Dong Guantao, Mi Kun, Meng Yan, Li Yan, Han Delong, Li Min. The release status of previous versions of this document and the documents it replaces are as follows. ---In 1988, it was first published as GB/T 8566-1988 "Computer Software Development Specification"; ---In.1992, it was first revised as GB/T 8566-1992 "Information Technology Software Life Cycle Process"; ---The second revision in.2001 was GB/T 8566-2001 "Information Technology Software Life Cycle Process", the third revision in.2007 revision; --- This is the fourth revision.IntroductionThe complexity of software systems has increased to unprecedented levels. This opens up new opportunities for organizations that create and use systems, but It also brings more challenges, these challenges exist in the whole life cycle of the software system and all the details on the architecture level. this document A common process framework is provided to describe the life cycle of artificially created systems using software engineering methods. software engineering is successful An interdisciplinary approach and approach to the development of software systems that focuses on defining the needs of stakeholders and the functionality required prior to the development cycle, It focuses on establishing requirements documents, it focuses on performing design integration and system verification, and it also considers global issues. software engineering combines all Procedures and professional groups are integrated into a team working to form a structured development process from concept to production, to operation, to maintenance, while Also consider the business and technical needs of all stakeholders, with the aim of providing high-quality products that meet the requirements of users and other stakeholders mark. This life cycle spans the entire process from conception to system decommissioning, providing a process for the acquisition and provisioning of the system, while It also helps to improve communication and cooperation among all parties who create, use, and manage modern software systems so that they can be developed in an integrated, high-level manner. Cohesive patterns work. The framework also provides for the assessment and improvement of life cycle processes. The processes in this document form a comprehensive set from which organizations can build software life cycle models appropriate for their products and services. Depending on the purpose of the organization, an appropriate subset can be selected and applied to achieve that purpose. This document can be used in one or more of the following modes. a) Organizational Use - Helps establish the context of the required process. These processes can be defined by methods, procedures, techniques, tools and trained People make up the infrastructure to support it. Organizations can then use these environments to execute and manage their own projects, and through their life cycle phases to develop a software system. In this mode, this document is used to assess whether the declared, established environment is whether it complies with its provisions. b) Project Use - Helps select, structure and use elements of an established environment to deliver products and services. in this mode , this document is used to assess whether the project conforms to the declared and established environment. c) Use by acquirers and suppliers—help develop agreements on processes and activities. By this agreement, the processes and activities in this document Selected, negotiated, agreed to and executed. In this mode, this document is used to guide the development of the protocol. d) Process evaluators use --- as a process reference model for the performance of process evaluation to support the organization's process improvement. Considering the difference between software and system scope, the "project-specific package management process" in the software life cycle process model in this document is the same as The "programme management process" in the GB/T 22302-2021 system life cycle process model refers to the same process, but there are difference. Systems and Software Engineering Software Life Cycle Process1 Scope1.1 Overview This document uses well-defined terms to establish a common framework for software life cycle processes that can be referenced by the software industry. Should A framework contains processes, activities and tasks that can be used during the acquisition, supply, development, operation, maintenance or disposal of software systems, products and services. These life cycle processes are completed through the participation of all parties related to the system, with the ultimate goal of achieving customer satisfaction. This document applies to software systems, products and services, and the acquisition, supply, development, operation, maintenance and Disposition (whether performed internally or externally to the organization). Software includes the software portion of firmware and also includes the environment that provides software products and services The required system defines those sections. This document also provides procedures that can be used within an organization or a project to define, control and improve software life cycle processes. The processes, activities and tasks in this document can also be applied during the acquisition of a system including software, where either used alone, It can also be used in combination with GB/T 22032-2021. GB/T 22032-2021 mainly focuses on man-made systems that use little or no software, and the use of GB/T 22032-2021 In contrast to environments, this document is primarily concerned with a continuum of software-manufactured systems. In reality, it is rare to meet a person without software Complex systems, and all software systems need to be run by components (hardware) of the physical system, or only as a part of the software system in focus part, or only as an enabling system or infrastructure. Therefore, whether to apply this document to the software life cycle, or to GB/T 22032-2021 applies to the software life cycle, the choice of which depends on the system concerned. The procedures in the two standards have similar have the same process purpose and process output, but differ in the activities and tasks in performing software engineering or systems engineering, respectively. 1.2 Purpose The goal of this document is to provide a defined set of processes during the system life cycle to facilitate communication between. This document is applicable to buyers, suppliers, developers, integrators, operators, maintainers, managers, quality assurance parties of software systems, products and services. certificate managers and users. It can be adopted either by a single party as a self-improvement exercise or in a multi-party situation. Parties can come from the same Organizations can also be from different organizations, and the relationship between the parties can be informal or formal. The processes in this document can be used as the basis for creating a business environment (for example, methods, procedures, techniques, tools and professionals). Appendix A Specifies the normative requirements for tailoring these software life cycle processes. 1.3 Application field This document applies to the complete life cycle of software systems, products and services, including conception, development, production, use, support and decommissioning, It also applies to their acquisition and provision, whether operating within or outside the organization. The lifecycle processes defined in this document can be used with It can be applied to software systems in time, iteratively and recursively, and can also be applied incrementally to software system elements. In terms of the purpose, application domain, complexity, scale, novelty, adaptability, quantity, location, life time and evolution of the software system, Software systems are very different. This document describes the life cycle processes for systems involving human software. Therefore, it can be applied to both production, for a wide range of commercial or public distribution, as well as customizable and adaptable software systems, and can also be applied to complete stand-alone software systems and A software system that can be embedded/integrated into a larger and more complex complete system. This document provides a process reference model represented in terms of process purpose and process output characteristics, while process purpose and process output source for the successful execution of activities and tasks. Appendix B lists examples of work products and information items related to different processes. Therefore this document ......Tips & Frequently Asked Questions:Question 1: How long will the true-PDF of GB/T 8566-2022_English be delivered?Answer: Upon your order, we will start to translate GB/T 8566-2022_English as soon as possible, and keep you informed of the progress. The lead time is typically 6 ~ 10 working days. The lengthier the document the longer the lead time.Question 2: Can I share the purchased PDF of GB/T 8566-2022_English with my colleagues?Answer: Yes. The purchased PDF of GB/T 8566-2022_English will be deemed to be sold to your employer/organization who actually pays for it, including your colleagues and your employer's intranet.Question 3: Does the price include tax/VAT?Answer: Yes. Our tax invoice, downloaded/delivered in 9 seconds, includes all tax/VAT and complies with 100+ countries' tax regulations (tax exempted in 100+ countries) -- See Avoidance of Double Taxation Agreements (DTAs): List of DTAs signed between Singapore and 100+ countriesQuestion 4: Do you accept my currency other than USD?Answer: Yes. If you need your currency to be printed on the invoice, please write an email to Sales@ChineseStandard.net. In 2 working-hours, we will create a special link for you to pay in any currencies. Otherwise, follow the normal steps: Add to Cart -- Checkout -- Select your currency to pay.Question 5: Should I purchase the latest version GB/T 8566-2022?Answer: Yes. Unless special scenarios such as technical constraints or academic study, you should always prioritize to purchase the latest version GB/T 8566-2022 even if the enforcement date is in future. Complying with the latest version means that, by default, it also complies with all the earlier versions, technically. |
