|
US$279.00 · In stock
Delivery: <= 3 days. True-PDF full-copy in English will be manually translated and delivered via email.
GB/T 40473.6-2021: Banking application system - Nonfunctional requirement - Part 6: Reliability
Status: Valid
| Standard ID | Contents [version] | USD | STEP2 | [PDF] delivered in | Standard Title (Description) | Status | PDF |
| GB/T 40473.6-2021 | English | 279 |
Add to Cart
|
3 days [Need to translate]
|
Banking application system - Nonfunctional requirement - Part 6: Reliability
| Valid |
GB/T 40473.6-2021
|
PDF similar to GB/T 40473.6-2021
Basic data | Standard ID | GB/T 40473.6-2021 (GB/T40473.6-2021) | | Description (Translated English) | Banking application system - Nonfunctional requirement - Part 6: Reliability | | Sector / Industry | National Standard (Recommended) | | Classification of Chinese Standard | A11 | | Word Count Estimation | 14,114 | | Issuing agency(ies) | State Administration for Market Regulation, China National Standardization Administration | GB/T 40473.6-2021: Banking application system - Nonfunctional requirement - Part 6: Reliability---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.
Banking application system - Nonfunctional requirement - Part 6.Reliability
ICS 35.240.40
CCSA11
National Standards of People's Republic of China
Non-functional requirements for banking application systems
Part 6.Reliability
Part 6.Reliability
Released on 2021-07-20
2022-02-01 implementation
State Administration of Market Supervision and Administration
Issued by the National Standardization Management Committee
Table of contents
Foreword Ⅲ
Introduction Ⅳ
1 Scope 1
2 Normative references 1
3 Terms and definitions 1
4 Levels and description methods of reliability elements and components 2
4.1 Level 2
4.2 Description Method 5
5 Mature sex family (RL_MAT) 5
5.1 Internal non-functional requirements (NFIR) 5
5.2 External non-functional requirements (NFOR) 5
6 Availability Family (RL_AVL) 5
6.1 Internal non-functional requirements (NFIR) 5
6.1.1 Service Level (IRL_AVL.1) 5
6.1.2 Function availability (IRL_AVL.2) 5
6.1.3 Data Availability (IRL_AVL.3) 6
6.2 External non-functional requirements (NFOR) 6
6.2.1 Operating platform availability (ORL_AVL.1) 6
6.2.2 Network Availability (ORL_AVL.2) 6
7 Fault tolerance family (RL_FTR) 6
7.1 Internal non-functional requirements (NFIR) 6
7.1.1 Functional fault tolerance (IRL_FTR.1) 6
7.1.2 Role fault tolerance (IRL_FTR.2) 7
7.2 External non-functional requirements (NFOR) 7
7.2.1 External system fault tolerance (ORL_FTR.1) 7
7.2.2 Host application system fault tolerance (ORL_FTR.2) 7
7.2.3 Software fault tolerance (ORL_FTR.3) 7
7.2.4 Network fault tolerance (ORL_FTR.4) 7
8 Recoverable family (RL_RCV) 8
8.1 Internal non-functional requirements (NFIR) 8
8.1.1 Scope of business impact (IRL_RCV.1) 8
8.1.2 System Architecture (IRL_RCV.2) 8
8.1.3 Data backup (IRL_RCV.3) 8
8.1.4 Data loss processing (IRL_RCV.4) 8
8.1.5 Status automatic protection (IRL_RCV.5) 8
8.2 External non-functional requirements (NFOR) 8
8.2.1 Data backup and save (ORL_RCV.1) 8
8.2.2 Recovery time objective RTO (ORL_RCV.2) 9
8.2.3 Recovery point objective RPO (ORL_RCV.3) 9
8.2.4 Restore data source (ORL_RCV.4) 9
8.2.5 Recovery involving external systems (ORL_RCV.5) 9
Reference 10
Foreword
This document is in accordance with the provisions of GB/T 1.1-2020 "Guidelines for Standardization Work Part 1.Structure and Drafting Rules of Standardization Documents"
Drafting.
This document is Part 6 of GB/T 40473 "Non-functional Requirements for Banking Application Systems". GB/T 40473 has been released
Lower part.
---Part 1.Description framework;
---Part 2.Functional suitability;
---Part 3.Performance efficiency;
---Part 4.Compatibility;
---Part 5.Ease of use;
---Part 6.Reliability;
---Part 7.Security;
---Part 8.Maintainability;
---Part 9.Portability.
Please note that some of the contents of this document may involve patents. The issuing agency of this document is not responsible for identifying patents.
This document was submitted by the People's Bank of China.
This document is under the jurisdiction of the National Financial Standardization Technical Committee (SAC/TC180).
Drafting organizations of this document. Science and Technology Department of the People's Bank of China, Agricultural Bank of China Co., Ltd., China Foreign Exchange Trading Center and National Bank of China
Interbank Funding Center, People’s Bank of China Clearing Center, China Construction Bank Co., Ltd., Bank of Communications Co., Ltd.,
Rural Credit Bank Fund Clearing Center Co., Ltd., China Financial Electronics Corporation.
The main drafters of this document. Li Wei, Yang Fuyu, Qu Weimin, Li Kuan, Wang Peng, Ma Jun, Wang Feng, Yang Mingying, Ge Honghui, Cui Wanmin, Zhao Liutao,
Ye Min, Liang Jun, Jing Yun, Wang Canyong, Lu Yuanpeng, Yang Qian, Xie Yanli, Liu Shuyuan, Wang Siyuan.
Introduction
GB/T 40473 gives the description framework of the non-functional requirements of banking application systems and the description of the non-functional requirements of various banking application systems.
The template is designed to improve the quality and efficiency of the compilation of non-functional requirements of the banking application system, and reduce the compilation of non-functional requirements of the banking application system.
The threshold and cost are composed of nine parts.
---Part 1.Describe the framework. The purpose is to clarify the scope of the banking application system and establish the non-functional requirements of the banking application system
The description framework of the banking industry clarifies the identification and description of the non-functional requirements of the banking application system, and gives the non-functional requirements of the banking application system
The customized package and customized profile of the bank, propose the technical management and evaluation of the non-functional requirements of the banking application system, and give the banking application
The method of using the XML description of the system's non-functional requirements is the basis for the reading and application of the rest of the parts.
---Part 2.Functional suitability. The purpose is to provide functional fitness including functional completeness, functional correctness and functional suitability
Sexual requirements, these requirements can be seen as functional requirements from the rigorous classification of requirements, but in the research and development of banking application systems,
It is often regarded as a non-functional requirement.
---Part 3.Performance efficiency. The purpose is to give performance efficiency requirements including time characteristics, resource utilization, and capacity.
---Part 4.Compatibility. The purpose is to provide compatibility including coexistence and interoperability.
---Part 5.Ease of use. The purpose is to provide information including identifiability, ease of learning, ease of operation, user error defense, user community
Face comfort and ease of accessibility.
---Part 6.Reliability. The purpose is to provide reliability including maturity, availability, fault tolerance and easy recovery.
---Part 7.Security. The purpose is to provide security including confidentiality, integrity, non-repudiation, verifiability and authenticity.
Fullness.
---Part 8.Maintainability. The purpose is to provide the information including modularity, reusability, easy analysis, easy modification and easy testability.
Maintainability.
---Part 9.Portability. The purpose is to provide portability including adaptability, easy installation and easy replacement.
When the meaning of abbreviations and numbers are not considered, those skilled in the art can basically understand the contents of this document correctly based on their professional knowledge in the field.
Substantive content. However, in the following typical situations, users of this document should first read and understand GB/T 40473.1-2021.
---Prepare the non-functional requirements of the application system;
---Review the non-functional requirements of the application system;
---Verify and confirm the application system developed in accordance with non-functional requirements;
---Static and dynamic testing of the application system developed in accordance with non-functional requirements.
For non-functional requirements prepared in accordance with this document, if they are described in the form of XML given in GB/T 40473.1-2021, they will be given to non-functional requirements.
Demand brings greater convenience in transmission and processing.
Non-functional requirements for banking application systems
Part 6.Reliability
1 Scope
This document defines the concept of the reliability of the banking application system, and specifies the components and element levels of the reliability category and the description method,
Non-functional requirement templates of the maturity family, availability family, fault tolerance family, and recoverability family of the reliability class.
This document is suitable for the description of reliability non-functional requirements of various application systems in the banking industry. Information exchange with banking application systems
The changed application system can be used as a reference as needed.
2 Normative references
The contents of the following documents constitute the indispensable clauses of this document through normative references in the text. Among them, dated quotations
Only the version corresponding to that date is applicable to this document; for undated reference documents, the latest version (including all amendments) is applicable to
This document.
GB/T 40473.1-2021 Banking industry application system non-functional requirements Part 1.Description framework
3 Terms and definitions
The following terms and definitions defined in GB/T 40473.1-2021 apply to this document.
3.1
Reliability
The extent to which a system, product or component performs a specified function under specified conditions and within a specified time.
Note. No loss will occur in the software. Reliability limitations are caused by failures in requirements, design, and implementation, or changes in the surrounding environment.
[Source. GB/T 25000.10-2016, 4.3.2.5, with modification]
3.2
Maturity
The degree to which a system, product, or component meets reliability requirements during normal operation.
Note. The concept of maturity can be used in other quality characteristics to show the degree to which they meet requirements during normal operation.
[Source. GB/T 25000.10-2016, 4.3.2.5.1]
3.3
Availability
The degree to which a system, product, or component can be operated and accessed when needed.
Note. Availability can be externally evaluated by the percentage of the system, product, or component that is available in the total time. Therefore, availability is maturity
(Control the frequency of failure), fault tolerance and easy recovery (control the length of downtime after each failure).
[Source. GB/T 25000.10-2016, 4.3.2.5.2]
|