GB/T 22032-2021 English PDFUS$1864.00 · In stock
Delivery: <= 10 days. True-PDF full-copy in English will be manually translated and delivered via email. GB/T 22032-2021: Systems and software engineering - System life cycle processes Status: Valid GB/T 22032: Historical versions
Basic dataStandard ID: GB/T 22032-2021 (GB/T22032-2021)Description (Translated English): Systems and software engineering - System life cycle processes Sector / Industry: National Standard (Recommended) Classification of Chinese Standard: L77 Word Count Estimation: 98,927 Issuing agency(ies): State Administration for Market Regulation, China National Standardization Administration GB/T 22032-2021: Systems and software engineering - System 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-System life cycle processes ICS 35.080 L77 National Standards of People's Republic of China Replace GB/T 22032-2008 System and Software Engineering System Life Cycle Process (ISO /IEC /IEEE15288.2015, IDT) Released on 2021-04-30 2021-11-01 implementation State Administration of Market Supervision and Administration Issued by the National Standardization Management Committee Table of contentsForeword Ⅲ Introduction Ⅴ 1 Overview 1 1.1 Scope 1 1.2 Objective 1 1.3 Application area 1 1.4 Limitation 1 2 Compliance 2 2.1 Intended usage 2 2.2 Fully compliant with 2 2.3 Tailoring conforms to 3 3 Normative references 3 4 Terms, definitions and abbreviations 3 4.1 Terms and definitions 3 4.2 Abbreviations 9 5 Key concepts and applications of this standard 9 5.1 Overview 9 5.2 Concept of system 9 5.3 Concept of organization and project 11 5.4 The concept of life cycle 12 5.5 Concept of process 13 5.6 Processes in this standard 13 5.7 Application of the process 15 5.8 Process Reference Model 16 6 System life cycle process 16 6.1 Agreement Process Group 16 6.2 The organization's project enabling process group 19 6.3 Technology Management Process Group 25 6.4 Technical Process Group 37 Appendix A (Normative Appendix) Tailoring Process 66 Appendix B (informative appendix) Examples of process information items 68 Appendix C (informative appendix) Process reference model for evaluation purposes 71 Appendix D (informative appendix) Process integration and process construction 73 Appendix E (informative appendix) Process view 75 Appendix F (Informative Appendix) Architecture Modeling 80 Appendix G (Informative Appendix) Application of System Life Cycle Process in SoS 82 Appendix NA (informative appendix) Comparison of the old and new standard structure 85 References 88 System and Software Engineering System Life Cycle Process1 Overview1.1 Scope This standard establishes a general framework for describing the life cycle of artificial systems, and defines a set of processes and related processes from an engineering perspective. the term. These processes can be applied to all levels of the system structure. Throughout the life cycle, the selected process set can be applied to the management Management and operation of the various stages of the system life cycle. This is through the participation of all parties related to the system to achieve customer satisfaction as the ultimate goal To complete it. This standard also provides some processes to support the definition, control and improvement of life cycle processes used in organizations or projects. When to obtain and provide When applying the system, organizations and projects can use these life cycle processes. This standard involves one or more manual systems that can be configured by the following elements. hardware, software, data, personnel, processes (e.g. The process of providing services), procedures (such as operating instructions), facilities, materials, and naturally-occurring entities. When the system element is software, ISO /IEC /IEEE12207.2015 can be used to implement this system element. The two standards are mutually coordinated Tuning can be used simultaneously in a single project or a single organization. 1.2 Purpose The goal of this standard is to provide a set of defined processes in the life cycle of the system to promote demand-side, supplier-side and other stakeholders Communication between. This standard applies to organizations that are demanders and suppliers. It can be used by a single party as self-improvement work, or it can be used in a multi-party situation. condition. The parties can come from the same organization or different organizations, and the relationship between the parties can range from informal agreement to formal contract. The process of this standard can be used as a basis for creating a business environment (such as methods, procedures, technologies, tools, and professionals). To these The normative requirements for tailoring the system life cycle process are shown in Appendix A. 1.3 Application areas This standard applies to the complete system life cycle, including the concept, development, production, use, support and decommissioning of the system, and also applies to The acquisition and supply of the system, whether it is running inside or outside the organization. The life cycle process of this standard can be simultaneously, iteratively, and recursively The ground is applied to the system, and it can also be applied to the system elements incrementally. In terms of the purpose, application field, complexity, scale, novelty, adaptability, quantity, location, survival time and evolution of the system, the system It's very different. This standard describes the life cycle process involving artificial systems. It can be applied to single-piece production, mass production or customizable An adaptable system can also be applied to a complete stand-alone system or a system that can be embedded/integrated into a larger and more complex complete system. This standard provides a process reference model based on the process purpose and process output characteristics, and the process purpose and process output are derived from activities And the successful execution of the task. See Appendix B for examples of products and information items related to different processes. This standard serves as a reference model for supporting Support process assessment (see ISO /IEC 15504-2.2003). As a process reference model and information about the use of the system life cycle see Appendix C. Refer to Appendix D for the process structure using the process reference model. 1.4 Restrictions This standard does not specify a specific system cycle model, development methodology, method, model or technology. Users of this standard are responsible for selecting the life cycle model of the project and mapping the processes, activities and tasks of this standard to the model. Users are also negative Responsible for selecting and applying appropriate methodology, methods, models and technologies suitable for the project. Although this standard does not have a management system, it is in line with the quality management system specified by ISO 19001 and ISO /IEC.20000-1. The service management system specified in.2011 (IEEEStd20000-1-2013), the information security and confidentiality management system specified in ISO /IEC 27000 Compatible. This standard does not detail the information items about naming, format, clear content, and recording medium. For the content of life cycle process information items, see ISO /IEC /IEEE15289.2 Compliance2.1 Intended usage The requirements of this standard are contained in Chapter 6 and Appendix A. In the system or product life cycle process, this standard is suitable for use The process provides the requirements. Special projects or organizations may not need to use all the processes provided by this standard. Therefore, the implementation of this standard It usually involves selecting and declaring a collection of processes suitable for the organization or project. There are two ways to declare compliance with this standard, that is, full compliance Hehe tailoring meets. There are two criteria to declare full compliance. Although the selected criteria (or principles) are stated in the statement, these two criteria are met All are sufficient to meet compliance requirements. The full compliance of the declared task indicates that all the activities and tasks of the declared process set have been obtained. The declared output is in full compliance with the requirement that all the outputs required by the declared process set have been obtained. The output is in full compliance with the allowable There are greater degrees of freedom in the compliance process, which may be useful in the process of implementing models for the innovation life cycle. Note 1.The optionality of compliance provides the flexibility required when applying this standard. Each process has a set of goals (called "outputs") and a set of acquisition goals Way (referred to as "activities and tasks"). Note 2.The user who has realized the activities and tasks of the declared process set can be determined to be fully consistent with the tasks of the selected process. However, some users may have The process has made certain innovations, and can achieve the goal (ie output) of the stated process set without completing all the activities and tasks. These use The user can be sure that the output of the set of procedures is fully consistent with the statement. Task compliance and output compliance with these two criteria are not necessarily equivalent, because in some cases The execution of specific activities and tasks may require a higher ability than achieving output compliance. Note 3.When this standard is used to promote the agreement between the supplier and the demander, the terms of this standard can be incorporated into the agreement with or without any modification. This sentiment Under the circumstances, compliance with the agreement between the buyer and the supplier is more suitable than compliance with this standard. Note 4.An organization (e.g., country, industry association, company) that regards this standard as its terms of trade can specify and disclose the required processes, outputs, activities, and tasks. The lowest limit of the business, to make a commitment to the supplier’s trade-off conditions. Note 5.This standard uses the verb "should" to mark requirements, the use of the verb "yi" to mark suggestions, and the use of the verb "可" to mark permission. Xu. But despite the use of these marked verbs, it is still necessary to meet the above requirements first. 2.2 Fully compliant 2.2.1 The output fully complies with The full compliance statement gives a set of procedures that comply with this standard. By proving that all the inputs of the stated set of processes have been achieved Out, the complete conformity to the output is realized. In this case, regardless of whether it is “should”, “should” or “may” in this clause, the The tasks and activities of the process are recommendations, not requirements. Note. An intended use of this standard is to facilitate process evaluation and improvement. For this purpose, the target of each process is written in the form of output compatible In the provisions of ISO /IEC 15504-2 and ISO /IEC 33002.These standards provide the basis for the evaluation and improvement of the process of this standard. Want process Evaluation and promotion users will use the process output written in this standard as a process reference for ISO /IEC 15504-2 and ISO /IEC 33002 model. 2.2.2 The task is fully compliant The full compliance statement gives a set of procedures that comply with this standard. By proving that all the activities of the stated set of processes have been achieved The requirements of activities and tasks have fully met the tasks. In this case, regardless of whether it is “shall”, “should” or “may” in this clause, the right The stated output of a set of procedures are recommendations, not requirements. Note. Under the circumstances (contract or contractual agreement in the legal sense) required by the buyer or the regulatory agency to understand the supply process in detail, it is declared that the task is fully compliant. He is more suitable. 2.3 Tailoring conforms When the process set established on the basis of this standard is not enough to meet the requirements of full compliance, it is necessary to comply with the tailoring procedures specified in Appendix A. Cheng selects or modifies the terms of this standard, and gives a statement of tailoring compliance. By proving that the tailored output, activities and tasks have been achieved To achieve tailoring compliance.3 Normative referencesThere are no normative references in this document. 4 Terms, definitions and abbreviations 4.1 Terms and definitions The following terms and definitions apply to this document. Note. See ISO /IEC /IEEE24765 for other terms and definitions. 4.1.1 Acquirer A stakeholder who obtains or purchases a product or service from a supplier. Note. Synonymous terms for demand-side, commonly used are buyer, customer, owner, purchaser or internal/organization sponsor. 4.1.2 Get acquisition The process of obtaining a system, product, or service. 4.1.3 Activity A collection of tasks combined in a certain process. 4.1.4 Agreement Terms and conditions on which to maintain the working relationship and obtain mutual confirmation. Examples. contract, memorandum of agreement. 4.1.5 Architecture Architecture < System> The basic concepts or attributes of a system in its environment are embodied in its elements, relationships, and principles of design and evolution. [ISO /IEC /IEEE42010.2011, definition 3.2] 4.1.6 Architectureframework Architecture framework The conventions, principles and practices established to describe the architecture in specific application fields and stakeholder groups. Example 1.(in ISO 15704) General Enterprise Reference Architecture, Methodology (GERAM) is an architectural framework. Example 2.(in ISO /IEC 10746) The Open Distributed Processing Reference Model (RM-ODP) is an architectural framework. [ISO /IEC /IEEE42010.2011, definition 3.4] 4.1.7 Architectureview Express the artifacts of a certain system architecture from the perspective of specific system concerns. [ISO /IEC /IEEE42010.2011, definition 3.5] 4.1.8 Architectureviewpoint In order to lay down a framework for the concerns of a particular system, a contractual product is established for the construction, interpretation and use of architectural views. [ISO /IEC /IEEE42010.2011, definition 3.6] 4.1.9 Audit An independent inspection to assess whether a product or collection of products meets specifications, standards, contractual agreements, or other criteria. [ISO 24765.2010, definition 3.213] 4.1.10 Baseline The officially approved version of the technical status item. It has nothing to do with the medium, it is a specific time node in the life cycle of the technical state item Determined and cured. [IEEE828-2012, definition 2.1] 4.1.11 Conceptofoperations A general description of the idea or intention of an organization's one or a series of actions in words and/or graphics. Note 1.Operating concepts are usually reflected in long-term strategic planning and annual operating plans. In the annual operation plan, the operation concept covers simultaneously or successively A series of related actions. The operation concept is to describe the overall picture of the organization's operation. See 4.1.25 Operation Concept. Note 2.The operating concept provides the basis for determining the operating space, system capabilities, interface and operating environment boundaries. [ANSI/AIAAG-043A-2012e, definition 1.3.1] 4.1.12 Follow concern < System> The interest of one or more stakeholders in a certain system. Note. Concerns involve various impacts on a system in terms of its environment, including development, technology, business, operation, organization, policy, economic, Legal, regulatory, ecological and social impacts. [ISO /IEC /IEEE42010.2011, definition 3.7] 4.1.13 Technical status item configurationitem Configuration item Designated for technical status management, hardware, software, or hardware and software treated as a single entity in the process of technical status management Pieces of integrated items or aggregates. [ISO /IEC /IEEE24765.2010, definition 3.777] 4.1.14 Customer An organization or individual that accepts a certain product or service. Examples. consumers, customers, users, demanders, buyers, purchasers. Note 1.Customers can be internal or external to the organization. Note 2.Rewrite GB/T 19000-2008, definition 3.3.5. 4.1.15 Design (verb) design < Process> defines the architecture, system elements, interfaces, and other characteristics of a system or system elements. 4.1.16 Design (noun) design The result of the design (4.1.15) process. Note 1.Including the specification of system elements and their relationships, sufficient information is sufficient to support the implementation of compatible architecture. Note 2.The design provides a detailed implementation-level physical structure, behavior, time relationship and other attributes of the system elements. 4.1.17 Designcharacteristic A measurable description of design attributes or unique attributes that belong to a product or service. 4.1.18 Enabling system A system that provides support for the concerned system in its life cycle stage, but does not have to directly perform its functions during its operation. Example. When the concerned system enters the production stage, an enabling system to help production is needed. Note. Each enabling system has its own life cycle. When the enabling system is also treated as a system of concern for its own needs, this standard applies Used in every enabling system. 4.1.19 Environment < System> determines the settings and surroundings of all influences on a system. [ISO /IEC /IEEE42010.2011, definition 3.8] 4.1.20 Facility Physical means or equipment that facilitate the execution of actions, such as plant buildings, instruments, and tools. 4.1.21 Incident Abnormalities, unexpected events, or events, conditions, or circumstances that occur at any time in the life cycle of a project, product, service, or system set. 4.1.22 Informationitem A single identifiable entity of information produced, stored, and transmitted for human use. [ISO /IEC /IEEE15289.2011, definition 3.1.13] 4.1.23 Lifecycle The evolution of systems, products, services, projects, or other human entities from concept to retirement. 4.1.24 Lifecycle model The framework of processes and activities related to the life cycle can be organized into multiple stages, and can also be used as a general reference for communication and understanding. 4.1.25 Operationalconcept For an organization, the text and intentions or intentions of a system or a group of related systems of a kind of operation or a series of operations. Graphical representation. Note. The operating concept uses one or more specific systems or a group of related systems, from the perspective of users and operators, gives an overall description of the operation. See 4.1.11. [ANSI/AIAAG-043A-2012e, definition 1.3.2] 4.1.26 Operator operator An individual or organization that performs system operations. Note 1.The roles of operator and user can be granted to the same person or organization at the same time or sequentially. Note 2.Every operator integrated with knowledge, skills and procedures can be considered as an element of the system. Note 3.The operator can perform different operations on the system according to whether the operating instructions are within the system boundary. 4.1.27 Organization A group of people and facilities whose responsibilities, authorities, and relationships are arranged. Examples. companies, groups, businesses, enterprises, institutions, research institutions, charities, agents, associations, or parts or combinations of the above organizations. Note. A part of a designated organization (as small as one person) or a designated organization group can be regarded as a group as long as it has responsibilities,......Tips & Frequently Asked Questions:Question 1: How long will the true-PDF of GB/T 22032-2021_English be delivered?Answer: Upon your order, we will start to translate GB/T 22032-2021_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 22032-2021_English with my colleagues?Answer: Yes. The purchased PDF of GB/T 22032-2021_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 22032-2021?Answer: Yes. Unless special scenarios such as technical constraints or academic study, you should always prioritize to purchase the latest version GB/T 22032-2021 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. |
