|
US$439.00 · In stock
Delivery: <= 5 days. True-PDF full-copy in English will be manually translated and delivered via email.
GB/T 40473.1-2021: Banking application system - Nonfunctional requirement - Part 1: Framework for description
Status: Valid
| Standard ID | Contents [version] | USD | STEP2 | [PDF] delivered in | Standard Title (Description) | Status | PDF |
| GB/T 40473.1-2021 | English | 439 |
Add to Cart
|
5 days [Need to translate]
|
Banking application system - Nonfunctional requirement - Part 1: Framework for description
| Valid |
GB/T 40473.1-2021
|
PDF similar to GB/T 40473.1-2021
Basic data | Standard ID | GB/T 40473.1-2021 (GB/T40473.1-2021) | | Description (Translated English) | Banking application system - Nonfunctional requirement - Part 1: Framework for description | | Sector / Industry | National Standard (Recommended) | | Classification of Chinese Standard | A11 | | Word Count Estimation | 22,215 | | Issuing agency(ies) | State Administration for Market Regulation, China National Standardization Administration | GB/T 40473.1-2021: Banking application system - Nonfunctional requirement - Part 1: Framework for description
---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 1.Framework for description
ICS 35.240.40
CCSA11
National Standards of People's Republic of China
Non-functional requirements for banking application systems
Part 1.Describe the framework
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
3.1 Application system and requirements 1
3.2 Organizational hierarchy of non-functional requirements 2
4 The scope of the application system 2
5 Non-functional requirements framework 3
5.1 Hierarchy 3
5.2 Top-level classification 3
6 Identification of non-functional requirements 4
7 Description of non-functional requirements 5
7.1 General requirements 5
7.2 Judgment of suitability 5
7.3 Instantiation of non-functional requirements 6
7.3.1 Operation of element content 6
7.3.2 Repeat operation 6
7.3.3 Assignment operation 6
7.3.4 Select operation 6
7.3.5 Refinement operation 7
7.3.6 Nested relationship of operations 7
7.3.7 The value of the column item in the operation 7
7.3.8 Applicability of the items in the operation 7
7.4 Note 7
7.5 Extension of classes, families, components and elements 7
8 Custom packages and custom contours for non-functional requirements 8
8.1 Customized packages for non-functional requirements 8
8.2 Custom profile for non-functional requirements 8
9 Technical management and evaluation of non-functional requirements 8
9.1 Technical management of non-functional requirements 8
9.2 Evaluation of non-functional requirements 8
10 XML description of non-functional requirements 9
Appendix A (informative) The degree of concern of each stakeholder on non-functional requirements 10
Appendix B (normative) XML description of non-functional requirements 12
B.1 Overview 12
B.2 Identification of the application system 12
B.3 Non-functional requirements version 12
B.4 Classes, families, components, elements 12
B.5 Description of element values 12
B.6 Non-functional requirements description framework 13
Reference 15
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 the first part 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
The application system has become an infrastructure that supports the normal service of customers and internal operation and management of the banking industry. In addition to the application system
In addition to the business functions required by the business department, there are also non-functional requirements. In the development, design and development process of application system requirements, these non-functional requirements
Requests often attract insufficient attention. With the expansion of the application system, the increase of users and transaction volume and other factors, these non-functional requirements
It will have a greater impact on the normal functioning of the application system, and even cause the application system to fail to play its predetermined role, thereby affecting the business production.
Have a negative impact.
In ISO /IEC 24765.2017 "System and Software Engineering Vocabulary", the concept of software quality is clarified, that is, "software products are
The ability to meet declared or implied requirements when used under the conditions of “(capabilityofsoftwareproducttosatisfystated
andimpliedneedswhenusedunderspecifiedconditions). Therefore, taking the software quality model as the starting point is a certainty
An effective way to apply the non-functional requirements of the system.
ISO and IEC formulated the software quality model standard ISO /IEC 9126.1991 "Software Engineering Product Quality" 30 years ago.
And since.2005, a new series of software product quality requirements and evaluation (SQuaRE) standards have been introduced. This document is based on SQuaRE.
The quality of software products in the series of standards proposes non-functional requirements. In fact, the software quality definition given by ISO /IEC 24765.2017 is
From ISO /IEC 25000.2014 "System and Software Engineering System and Software Quality Requirements and Evaluation (SQuaRE)-SQuaRE Guide
South".
In terms of the description of requirements, ISO /IEC 15408 "Information Engineering Security Technology Assessment Conditions for IT Security" series of standards
(I.e. "CommonCriteriaforInformationTechnologySecurityEvaluation", referred to as the CC standard)
A semi-formal method has been widely recognized by the industry. Therefore, in this document, a similar organization and description is adopted for non-functional requirements.
Method, and introduced the calculation between the elements consistent with the series of standards.
XML is currently a widely used information representation method. Compared with plain text, it has better structure.
XML is used as a logical statement of non-functional requirements, so that information technology can be used for further processing when possible.
Based on the integration of these standards, GB/T 40473 provides a description framework of the non-functional requirements of banking application systems and various types of banking
The template for the non-functional requirements of the industry application system is designed to improve the quality and efficiency of the compilation of the non-functional requirements of the banking application system, and reduce the compilation of the bank.
The threshold and cost of non-functional requirements of industry application systems 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.
Non-functional requirements for banking application systems
Part 1.Describe the framework
1 Scope
This document gives the scope of the banking application system, stipulates the non-functional requirement framework, non-functional requirement identification, non-functional requirement description,
Customized packages and customized outlines for non-functional requirements, technical management and evaluation requirements for non-functional requirements, and XML descriptions of non-functional requirements
The way.
This document is suitable for the description of non-functional requirements of various application systems in the banking industry. Application for information exchange with banking application system
System, can refer to use according to need.
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 18336.1-2015 Information Technology Security Technology Information Technology Security Assessment Criteria Part 1.Introduction and General
Model
GB/T 18793-2002 Information Technology Extensible Markup Language (XML) 1.0
GB/T 25000.10-2016 System and Software Engineering System and Software Quality Requirements and Evaluation (SQuaRE) Part 10.
System and software quality model
ISO /IEC 9899.2018 Information Technology Programming Language C (Informationtechnology-Programminglan-
guages-C)
ISO /IEC 15288.2015 System and Software Engineering System Life Cycle Process (Systemsandsoftware
engineering-Systemlifecycleprocesses)
3 Terms and definitions
The following terms and definitions apply to this document.
3.1 Application system and requirements
3.1.1
Application
Applicationsystem
A system for collecting, storing, processing and presenting data through a computer.
Note. The term "application" is generally used to indicate an executable software component, which consists of one or more components, modules or subsystems.
[Source. ISO /IEC 24765.2017, 3.167]
3.1.2
Requirement
Translate or express a statement of a certain need and related constraints and conditions.
Tips & Frequently Asked Questions:Question 1: How long will the true-PDF of GB/T 40473.1-2021_English be delivered?Answer: Upon your order, we will start to translate GB/T 40473.1-2021_English as soon as possible, and keep you informed of the progress. The lead time is typically 3 ~ 5 working days. The lengthier the document the longer the lead time. Question 2: Can I share the purchased PDF of GB/T 40473.1-2021_English with my colleagues?Answer: Yes. The purchased PDF of GB/T 40473.1-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 [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.
|