|
US$759.00 · In stock
Delivery: <= 6 days. True-PDF full-copy in English will be manually translated and delivered via email.
GB/T 25000.45-2018: Systems and software engineering -- Systems and software Quality Requirements and Evaluation (SQuaRE) -- Part 45: Evaluation module for recoverability
Status: Valid
| Standard ID | Contents [version] | USD | STEP2 | [PDF] delivered in | Standard Title (Description) | Status | PDF |
| GB/T 25000.45-2018 | English | 759 |
Add to Cart
|
6 days [Need to translate]
|
Systems and software engineering -- Systems and software Quality Requirements and Evaluation (SQuaRE) -- Part 45: Evaluation module for recoverability
| Valid |
GB/T 25000.45-2018
|
PDF similar to GB/T 25000.45-2018
Basic data | Standard ID | GB/T 25000.45-2018 (GB/T25000.45-2018) | | Description (Translated English) | Systems and software engineering -- Systems and software Quality Requirements and Evaluation (SQuaRE) -- Part 45: Evaluation module for recoverability | | Sector / Industry | National Standard (Recommended) | | Classification of Chinese Standard | L77 | | Classification of International Standard | 35.080 | | Word Count Estimation | 38,361 | | Date of Issue | 2018-12-28 | | Date of Implementation | 2021-01-01 | | Issuing agency(ies) | State Administration for Market Regulation, China National Standardization Administration | GB/T 25000.45-2018: Systems and software engineering -- Systems and software Quality Requirements and Evaluation (SQuaRE) -- Part 45: Evaluation module for recoverability
---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--Systems and software Quality Requirements and Evaluation (SQuaRE)--Part 45. Evaluation module for recoverability
ICS 35.080
L77
National Standards of People's Republic of China
System and software engineering
System and Software Quality Requirements and Evaluation (SQuaRE)
Part 45. Evaluation module for recoverability
andEvaluation(SQuaRE)-Part 45.Evaluationmoduleforrecoverability
[ISO /IEC 25045.2010, Systemsandsoftwareengineering-Systemsand
Moduleforrecoverability, MOD]
2018-12-28 released.2019-07-01 implementation
State market supervision and administration
China National Standardization Administration issued
Content
Foreword I
Introduction III
1 Scope 1
2 Compliance 1
3 Normative references 1
4 Terms and Definitions 1
5 inputs and measures 2
5.1 Evaluation Method 2
5.2 Evaluation input 6
5.3 Data Elements 8
5.4 Quality Measurement 9
6 Description of results 13
6.1 Measure Mapping 13
6.2 Report 13
6.3 Application Procedures 13
Appendix A (informative) Report Example 14
Reference 30
Foreword
GB/T 25000 "System and Software Engineering Systems and Software Quality Requirements and Evaluation (SQuaRE)" has been or is planned to release the following
section.
--- Part 1. SQuaRE Guide;
--- Part 2. Planning and Management;
--- Part 10. System and software quality models;
--- Part 12. Data quality model;
--- Part 20. Measurement reference models and guidelines;
--- Part 21. Quality measurement elements;
--- Part 22. Use quality measurement;
--- Part 23. System and software product quality measurement;
--- Part 24. Data quality measurement;
--- Part 30. Quality requirements;
--- Part 40. Evaluation process;
--- Part 41. Evaluation guidelines for developers, acquirers and independent reviewers;
--- Part 45. Evaluation module for easy recovery;
--- Part 51. Quality requirements and test details for Ready-to-Use Software Products (RUSP);
--- Part 62. Ease of Use Test Report Industry Common Format (CIF).
This part is the 45th part of GB/T 25000.
This part is drafted in accordance with the rules given in GB/T 1.1-2009.
This section adopts the redrafting method to modify the use of ISO /IEC 25045.2010 "system and software engineering systems and software quality requirements and
Evaluation (SQuaRE) Evaluation Module for Resiliency.
The structural differences and reasons for this part and ISO /IEC 25045.2010 are as follows.
--- Due to the required clauses in the suspension section of ISO /IEC 25045.2010, for the normative expression, 5.1 and 5.1.2
The suspension section containing the required clauses at the beginning is modified to 5.1.1 and 5.1.3.1, and the original chapters are sorted in order.
The technical differences and reasons for this part and ISO /IEC 25045.2010 are as follows.
--- Revised the SQuaRE series of standard organization chart to maintain consistency with the latest technological achievements (see Figure 1);
--- Regarding the normative reference documents, this section has made technical adjustments to maintain the national standard with GB/T 25000 series.
The quasi-coordination and adjustment are concentrated in Chapter 2, “Regulatory Citations”, and the specific adjustments are as follows.
● Replace ISO /IEC 25000 with GB/T 25000.1 equivalent to the international standard;
● Replace ISO /IEC 25010 with GB/T 25000.10 modified to international standards;
● Replace ISO /IEC 25040 with GB/T 25000.40 modified to international standards;
--- Added the term "resistance" (see 4.4);
--- For the sake of understanding, change the "throughput" to "traffic volume".
The editorial differences between this section and ISO /IEC 25045.2010 are as follows.
--- In order to coordinate with the GB/T 25000 series of national standards, the name of the international standard was revised;
--- Removed the first paragraph of the third paragraph and scope of the ISO /IEC 25045.2010 introduction, the content of which is inconsistent with this standard (see
Scope and scope);
---Modified the ISO /IEC 25045.2010 introduction in the ISO /IEC 25040, ISO /IEC 25041 name errors (see introduction);
--- Deleted the "system detection and recovery" in Figure 3, there is no "system detection and recovery" related content (see Figure 3);
--- Revised the table number and drawing number in Appendix A of ISO /IEC 25045.2010, and re-in accordance with the requirements of GB/T 1.1-2009
Sort (see Appendix A);
--- Revised the name of Table 13 of ISO /IEC 25045.2010, the original table name is "resource competition" and should be "data loss" (see
Table A.4).
Please note that some of the content in this article may involve patents. The issuing organization of this document is not responsible for identifying these patents.
This part is proposed and managed by the National Information Technology Standardization Technical Committee (SAC/TC28).
This section drafted by. Fujian Electronic Product Supervision and Inspection Institute, Shanghai Software Testing Center Co., Ltd., Shenzhen Zhongan Testing Standard
Technology Co., Ltd., Guangdong Jincheng Information Technology Co., Ltd., China Electronics Technology Standardization Research Institute, Guangxi Dayi Business Service Co., Ltd.
Company, Shanghai Computer Software Technology Development Center, National Application Software Product Quality Supervision and Inspection Center, Zhejiang Electronic Information Product Inspection
Institute, Chongqing Software Testing Center Co., Ltd., Xiamen University of Technology.
Drafters of this section. Liu Yulong, Meng Yan, Zhang Wei, Jing Guozhen, Liu Yujian, Zhang Yi, Zhang Guohua, Wu Hongdeng, Deng Ziyi, Liu Zhenyu, Wang Wei,
Zhang Lifen, Ji Yongzhen, Ding Xiaoming, Cui Jianfeng.
Introduction
As the use of information technology continues to grow, so does the number of critical computer systems. These systems include. confidentiality, life, and
Various systems for security and security. The software quality of these systems is especially important because software failure can have serious consequences.
Evaluation is a systematic determination of the extent to which an entity meets its stated criteria. Software product quality evaluation is critical to software acquisition and development
important. The relative importance of various features of software quality depends on the intended use or target of the software portion of the system; the software product needs to be evaluated
Price to determine if the relevant quality characteristics meet system requirements.
This section uses methods that involve two types of evaluation of recoverability. One is to use interference injection and operations based on common categories.
A list of disturbances of faults and events to evaluate the quality of the bearing. The other is based on defining a set of questions for each type of interference.
The evaluation system measures, analyzes, and resolves the degree of interference without human intervention to evaluate the quality measure of the autonomous recovery index.
The overall goal of the SQuaRE standard set is to develop a logically organized, rich and unified set of standards covering two main
Process. Software quality requirements specification and software quality evaluation supported by the software quality measurement process. The purpose of the SQuaRE standard set is to help
Those who develop and acquire software products with specifications and evaluations of quality requirements. The standard set establishes software product quality requirements
The specifications and their measurements, as well as the criteria for evaluation, include the use of development process attributes to match the quality model defined by the customer's quality. this
In addition, this series of standards provides recommended measures of the quality attributes of software products that can be used by developers, acquirers, and independent reviewers.
SQuaRE offers.
--- Terms and definitions;
--- Reference model;
---General guide;
--- Each division guide;
--- Standards for demand specification, planning and management, measurement and evaluation purposes.
SQuaRE includes standards for quality models and measurements as well as quality requirements and evaluations.
SQuaRE replaces the current ISO /IEC 9126 (GB/T 16260) series of standards and ISO /IEC 14598 (GB/T 18905) series
standard.
ISO /IEC 25040 "System and Software Engineering Systems and Software Quality Requirements and Evaluation (SQuaRE) Evaluation Process" will replace
ISO /IEC 14598-1 "Information Technology Software Product Evaluation Part 1. Overview".
ISO /IEC 25041 "System and Software Engineering Systems and Software Quality Requirements and Evaluation (SQuaRE) Developers, Buyers and Independents
The evaluation guide of the appraisers will replace ISO /IEC 14598-3 "Procedures for Developers in Software Engineering Product Evaluation Part 3",
ISO /IEC 14598-4 "Software Engineering Product Evaluation Part 4 Processes for Demanders" and ISO /IEC 14598-5 "Software Engineering
Product Evaluation Part 5. Process for Evaluators.
ISO /IEC 25001, System and Software Engineering Systems and Software Quality Requirements and Evaluation (SQuaRE) Planning and Management will replace
ISO /IEC 14598-2 "Software Engineering Product Evaluation Part 2. Planning and Management".
Figure 1 SQuaRE series standard organization structure
Figure 1 shows the members that make up the ISO /IEC 25000 SQuaRE family of standards, called divisions.
The divisions within the ISO /IEC 25000SQuaRE series of standards are.
a) ISO /IEC 2500n---Quality Management Division. The standards that make up this division are defined by the ISO /IEC 25000 series of standards.
All public models, terms, and definitions referenced by all other standards in . This division is also provided for managing software
Requirements and guidelines for support functions for product quality requirements specification and evaluation.
b) ISO /IEC 2501n---Quality Model Division. The standards that make up this division are given to include computer systems and software products.
Detailed quality model of quality, quality of use and data. A practical guide to using these quality models is also provided.
c) ISO /IEC 2502n---Quality Measurement Division. The standards that make up this segment include the software product quality measurement reference model,
A practical guide to the mathematical definition of mass measurement and its application. The internal quality of the software, the external quality of the software and the quality of use are given.
An example of measurement. The quality measure elements that form the basis of the subsequent measurements are defined and given.
d) ISO /IEC 2503n---Quality Requirements Division. The standards that make up this segment contribute to the foundation of quality models and quality measurements.
The quality requirements are defined on the basis. These quality requirements can be used in the quality requirements extraction process of the software product to be developed or as a review
The input of the price process.
e) ISO /IEC 2504n---Quality Evaluation Division. The criteria that make up this division are given by the appraiser, the acquirer, or
Requirements, recommendations, and guidelines for system or software product evaluation performed by the developer. Also gave quality measurement as an evaluation module
Documentation support.
f) ISO /IEC 25050~25099---Extension Division. Currently includes quality requirements for ready-to-use software and general industry
Ease of use report.
This standard is part of the Quality Evaluation Division (ISO /IEC 2504n), which includes the following criteria.
a) ISO /IEC 25040 "System and Software Engineering Systems and Software Quality Requirements and Evaluation (SQuaRE) Evaluation Process" contains
General requirements for software quality requirements specifications and evaluations, and clarify general concepts. Provided a quality evaluation software product
Process description and affirm the application requirements of the process. The evaluation process is a software product quality review for different purposes and methods.
The basis of the price. Therefore, the process can be used for product quality, external measurement of software quality, and internal measurement of software quality.
Price, as well as the quality of custom software that can be used to evaluate pre-developed software or in the development process. Software product quality review
The price can be implemented, for example, by a demander, developer organization, or independent reviewer.
b) ISO /IEC 25041 “System and Software Engineering Systems and Software Quality Requirements and Evaluation (SQuaRE) Developers, Buyers and
The Independent Evaluation Party's Evaluation Guide contains specific requirements and recommendations from the developer, the acquirer and the evaluater.
c) ISO /IEC 25045 Evaluation of System and Software Engineering Systems and Software Quality Requirements and Evaluation (SQuaRE)
The module gives an evaluation specification for the recoverability sub-character defined under the reliability characteristics of the quality model, and determines the tolerance and self.
The method of quality measurement of the primary recovery index. The software product and the system thus constituted remain acceptable for an acceptable interference time
The ability to use or recover has always been important because downtime often has economic losses and other consequences. Key points in recent years
It has been extended to the autonomy of software products, so that the system is self-management and the level of operator involvement is low. In the user field and
Industry is interested in software products and the systems thus formed that handle such interference in a manner that detects, analyzes, adjusts or recovers.
Interference can be an operational failure (eg, a sudden shutdown of an operating system process that causes the system to down) or an event (eg, a system user)
A significant increase).
System and software engineering
System and Software Quality Requirements and Evaluation (SQuaRE)
Part 45. Evaluation module for recoverability
1 Scope
This part of GB/T 25000 provides an evaluation method, process, measurement and result description of the software product's recoverability quality evaluation.
This section uses interference injection methods and interference lists based on common categories of operational faults and events to evaluate the quality of the bearing.
degree. The application is based on defining a set of problem sets for each type of disturbance, and the assessment system detects, analyzes, and solves the problem without human intervention.
The degree of disturbance is used to evaluate the quality measure of the autonomous recovery index. Applicable to software products (including intermediate work products and final products), support orders
Ease of recovery quality evaluation of one or more concurrent users' trading systems.
This section is intended for use by those responsible for software product quality evaluation and is applicable to product developers, acquirers (users) and independent reviewers.
Price side.
2 Compliance
If the resiliency evaluation of a software product follows the requirements of Chapter 5, it can be claimed to comply with this section.
3 Normative references
The following documents are indispensable for the application of this document. For dated references, only dated versions apply to this article.
Pieces. For undated references, the latest edition (including all amendments) applies to this document.
GB/T 25000.1 Software Engineering Software Product Quality Requirements and Evaluation (SQuaRE) SQuaRE Guide (GB/T 25000.1-
2010, ISO /IEC 25000.2005, IDT)
GB/T 25000.10 Systems and Software Engineering Systems and Software Quality Requirements and Evaluation (SQuaRE) Part 10. Systems and
Software quality model (GB/T 25000.10-2016, ISO /IEC 25010.2011, MOD)
GB/T 25000.40 Systems and Software Engineering Systems and Software Quality Requirements and Evaluation (SQuaRE) Part 40. Evaluation
Cheng (GB/T 25000.40-2018, ISO /IEC 25040.2011, MOD)
4 Terms and definitions
This document is defined in GB/T 25000.1 and the following terms and definitions apply.
4.1
Performance baseline performanceline
The result of the system performing a performance workload normally without performing interference injection.
4.2
Interference disturbance
Operational failures (for example, OS processes that cause the system to shut down suddenly shut down) or events (for example, a significant increase in the number of system users) or any
An event that may change the state of the system.
Note. In the context of this evaluation module, interference is limited to external faults or events, rather than internal faults that require modification of the application or OS code.
Tips & Frequently Asked Questions:Question 1: How long will the true-PDF of GB/T 25000.45-2018_English be delivered?Answer: Upon your order, we will start to translate GB/T 25000.45-2018_English as soon as possible, and keep you informed of the progress. The lead time is typically 4 ~ 6 working days. The lengthier the document the longer the lead time. Question 2: Can I share the purchased PDF of GB/T 25000.45-2018_English with my colleagues?Answer: Yes. The purchased PDF of GB/T 25000.45-2018_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 [email protected]. 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.
|