GB/T 32423-2015 English PDF
Basic dataStandard ID: GB/T 32423-2015 (GB/T32423-2015)Description (Translated English): System and software engineering -- Verification and validation Sector / Industry: National Standard (Recommended) Classification of Chinese Standard: L77 Classification of International Standard: 35.080 Word Count Estimation: 183,132 Date of Issue: 2015-12-31 Date of Implementation: 2016-07-01 Regulation (derived from): State Standard Announcement 2015 No.43 Issuing agency(ies): General Administration of Quality Supervision, Inspection and Quarantine of the People's Republic of China, Standardization Administration of the People's Republic of China GB/T 32423-2015: System and software engineering -- Verification and validation---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.System and software engineering - Verification and validation ICS 35.080 L77 National Standards of People's Republic of China Systems and Software Engineering Verification and Validation Issued on. 2015-12-31 2016-07-01 implementation Administration of Quality Supervision, Inspection and Quarantine of People's Republic of China Standardization Administration of China released Table of ContentsIntroduction Ⅲ Introduction Ⅳ 1 Scope 1 2 Compliance 1 3 Terms, Definitions and Abbreviations 1 4 V 5 Integrity Level 6 6 V7 Public V8 System V9 software V10 Hardware V 11 V 12 V Appendix A (Informative Appendix) V Appendix B (Informative Appendix) A risk-based program integrity level 131 Appendix C (Informative Appendix) IV Annex D (informative) reusable software V Appendix E (Informative Appendix) V Appendix F (Informative Appendix) V Annex G (informative) Optional V Appendix H (informative) Environmental considerations 148 Annex I (informative) systems, software and hardware integration of the three V Appendix J (informative) dangerous, confidentiality and security risk analysis 154 Examples Appendix K (informative) for "functional support system" and specify the level of system integrity and change 158 Appendix L (Informative Appendix) ISO /IEC 15288 and ISO /IEC 12207 process and the outcome of this standard V Relationship 160 References 172ForewordThis standard was drafted in accordance with GB/T 1.1-2009 given rules. Please note that some of the content of this document may involve patents. Release mechanism of the present document does not assume responsibility for the identification of these patents. This standard by the National Information Technology Standardization Technical Committee (SAC/TC28) and focal points. This standard was drafted. China Aerospace Science and Technology Corporation Software Testing Center, China Electronics Standardization Institute, the national application software Product quality supervision and inspection center, Henan Electric Power Company State Grid Electric Power Research Institute, the National Network Software Product Quality Supervision and Inspection Center (Jinan), Shanghai computer software technology development center. The main drafters of this standard. Yang Gui, Wang Ling, Zhang Gang, Wang Rui, Liang Yong, Fan Xing, phase Fumin, Wang Wei, Ren Pei, Zhang Wei, cattle frost Xia, Wei Guang Road, Lv Hongyu, Cai Lizhi, Liu Zhenyu, Zhao Yingying.Introduction0.1 Background and Overview This standard is a standard procedure, it can be seen as ISO /IEC 15288.2008 and ISO /IEC 12207.2008 concerning V Further refinement process. Verification and validation (V Product meets its intended use and user needs. Determination activities may include analysis of products and processes, evaluation, review, review, evaluate and test. a) In each life cycle process, all activities follow the demand requirements (eg, accuracy, completeness, consistency and accuracy); b) In the course of the life cycle to meet the standards, practices and conventions; c) Successful completion of each life cycle activity, and start the next step to meet all the standard life cycle activity (ie the correct production of products). The validation process provides objective evidence that the product is to achieve the following requirements. a) at the end of each life cycle activities to meet the system requirements allocated to the product; Interactive. a) Environment. determine the system correctly describes all conditions, natural phenomena, laws of nature, business rules, and the physical properties of the system is running The full scope of the environment; b) The operator/user. determine the correct state of the system to convey system operator or user/condition, correctly handle all of the operator / User input, to produce the desired results. For error operator/user input to ensure the protection system from entering the dangerous state State or out of control. Acknowledge operator/user policies and procedures (eg, privacy security, protocol interfaces, performance data, system false Set) in the consistent application and use each component interface; c) other software and hardware systems. determining hardware or software requirements and system components based on other components correct interface and determine The error does not propagate between the system components. Cheng), procedures (eg operator's guide) and facilities. Users of this standard should consider V Part of the process, such as, ISO /IEC 12207.2008, IEEEStd1074-2006 or ISO /IEC 15288.2008. In order to solve the problem of the whole system, systems, software and hardware V And other V Valuable and necessary inputs. A V Service analyzed again. Rigorous systems engineering technology V This relationship Fed) between the integrated hardware and software systems and V Early in the process improvement and potential abnormality monitoring process trend. V described in this standard Process improvement model used in combination, such as the Capability Maturity Model Integration CMU/SEI-2010-TR-033. This standard is compatible with all life cycle model (such as systems, software and hardware), but not all of the life cycle models are used in this standard The whole process of the column. 0.4 V Consistent and testing. V Users need. This determination process may include an assessment of products and processes, analysis, evaluation, review, inspection and testing. V Life cycle stages in parallel, rather than after the end of the life cycle stages. a) promoting early detection and correction of anomalies; b) to strengthen the management, risk and product discovery process; c) support life cycle processes to ensure compliance with the project implementation schedule and budget requirements; d) providing early assessment of performance; e) to provide objective evidence of compliance to support the formal certification process; f) to improve the acquisition, supply, development and maintenance of the product; g) support for process improvement activities. 0.5 standard organizational structure Introduction The use of this standard provides guidelines. Chapter 1 Scope. Chapter 2 compliance. Chapter 3 terms, definitions and abbreviations. Chapter 4 describes V The relationship between V and Chapter 5 describes the use of integrity levels to determine V Chapter 6 explained how to describe this standard V Chapter 7 describes the common V a) Table 4 contains V b) Table 5 contains for each level of integrity, common V c) Table 6 contains optional Public V d) Table 7 Summary Description Public V e) Table 8 general description V Chapter 8 describes System V a) Table 9 contains V b) contains 10 tables for each level of integrity, system V c) Table 11 contains optional system V d) Table 12 Summary description of the system V e) Table 13 Summary description of the system V Chapter 9 describes software V a) Table 14 contains V b) contains 15 tables for each level of integrity, software V c) Table 16 contains optional software V d) Table 17 Summary description of software V e) Table 18 Summary description of software V Chapter 10 describes the hardware V a) Table 19 contains V b) contains 20 tables for each level of integrity, hardware V c) Table 21 contains optional hardware V d) Table 22 Summary Description Hardware V e) Table 23 Summary Description Hardware V Chapter 11 describes V Chapter 12 describes V The standard organizational structure so that V Any combination can be accomplished as follows. System V Software V Chapter), as well as system/hardware/software V Communist; each part in order not to repeat these V Tasks can call public V Table 1 V Only system × 1) × Software only × × Only hardware × × Systems and software × × × Systems and hardware × × × Software and hardware × × × Systems, software and hardware × × × × Chapter 4 through Chapter 6 contains V Reporting requirements in combination. Chapter 12 contains a V Table 4, Table 9, Table 14 and Table 19 provides a life cycle processes each of V 15 and Table 20 lists the different levels of integrity required minimum V Task of V Table 7, Table 12, Table 17 and Table 22, for example overview of the integrity level of 4 V Services. Table 8, Table 13, Table 18 and Table 23 provides planning V 14 and Table 19, Table 5, Table 10, Table 15 and Table 20 by way of example a staged life cycle model, indicating the ISO /IEC 12207.2008 V life cycle process described in this standard Appendix A describes the ISO /IEC 12207.2008 and ISO /IEC 15288.2008 and this standard V Shoot. Appendix B provides an example of a risk-based, four integrity programs. Appendix C provides an independent verification and validation (IV Definition. Appendix D provides reusable software implementation V Other projects duties V Environmental considerations. Appendix I to discuss potential problems with the interaction between systems, software and hardware. Appendix J describes hazard analysis, safety secrecy Analysis, risk analysis, and their V example. Appendix L to the associated V 0.6 Readers The standard system includes a reader, software and hardware suppliers, the development side, the maintenance side, V Party organization managers. 1) × represents select the corresponding activities. Systems and Software Engineering Verification and Validation1 ScopeThis standard specifies include the acquisition, supply, development, operation, maintenance and decommissioning of the entire life cycle of systems, software and hardware development experience Certification and validation process. This standard applies to systems, software and hardware acquisition, development, maintenance or reuse.2 ComplianceThe word "shall" (shal) indicates compliance of this standard will not meet the requirements. The words "should" (should) and "may" (may) means a declaration is not required to follow Optional tasks of this standard. Not all V Given life cycle processes, so if all the selected items associated life cycle process executed minimum V In order to achieve this standard compliance. Any follow this statement shall identify the applicable standard life cycle processes. In all cases, the minimum Limit V Cheng, whose V Automatically generate code from the detailed design) can be deleted or development steps to develop a few steps to merge into one. Thus, allowing minimum When the existing system, software or hardware required by this standard and V The project input source with or adapted to meet the input requirements of the standard compliance. System, software or hardware, by proving that meet the following clauses in all the "should" requirements, to achieve this standard compliance. System V Software V Hardware V Waive compliance organization approval shall be subject to the acquirer, and (VVP) written verification and validation program. The required information shall include deviation and abandonment Their tasks, theoretical basis and Quality. 3 Terms, definitions and abbreviations 3.1 Terms and Definitions The following terms and definitions apply to this document. 3.1.1 Assets asset A product designed for use in different contexts (eg, design specifications, source code, documentation, test suites, manual procedure). 3.1.2 Component parts Parts of the system. Components may be hardware or software, and can be further divided into other parts. Note. The term "module (module)" "part (component)" and "unit (unit)" are often used interchangeably, or the context is defined in different ways Another sub-elements. The relationship between these terms are not standardized. ......Tips & Frequently Asked Questions:Question 1: How long will the true-PDF of GB/T 32423-2015_English be delivered?Answer: Upon your order, we will start to translate GB/T 32423-2015_English as soon as possible, and keep you informed of the progress. The lead time is typically 1 ~ 3 working days. The lengthier the document the longer the lead time.Question 2: Can I share the purchased PDF of GB/T 32423-2015_English with my colleagues?Answer: Yes. The purchased PDF of GB/T 32423-2015_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. |
