GB/T 40473.5-2021Banking application system—Nonfunctional requirement—Part 5: Usability (English PDF)

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 5 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.

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 this document correctly based on their professional knowledge in the field The 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 the 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, the non-functional requirements will be Demand brings greater convenience in transmission and processing.

1 Scope

This document defines the concept of ease of use of the banking application system, stipulates the level of components and elements of the ease of use, and the description method, ease of use The non-functional requirements of the identifiable family of usability, the easy-to-learn family, the easy-to-operate family, the user error defense family, and the user interface comfort family template.

This document is suitable for the description of ease-of-use non-functional requirements for 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.