Overall design plan 1. Introduction 1.1. Purpose of writing This document is an overall outline design description of the payment platform.

The purpose of preparing the outline design specification is to explain the design considerations for the program system, including the basic processing flow of the program system, the organizational structure of the program system, module division, function allocation, interface design, operation design, data structure design and error handling design, etc.

Provide the basis for the detailed design of the program.

The readers of this document are mainly developers, but other project related personnel can also refer to it.

1.2. Definitions Refer to the Glossary.

1.3. Reference materials Main technical reference materials: 1) Spring information 2) iBatis information 3) Hessian information 4) W3C XML related specifications 2. Technical standards followed by the overall design? This system software is developed based on J2EE specifications; ? This system software

Adopt Spring architecture and iBatis database operation framework.

? Certificate application adopts a certificate application system that complies with CSP specifications; ? PKI-based security authentication and encryption specification series: PKCS#1v2, PKCS#7v1.5, SSL3.0/TLS1.0; ? Transaction messages adopt W3C XML specifications,

And related XML Schema, XML Signature and Encryption specifications; ? Use HAP2.0 as the application development technology platform; ? Use HADP2.0 as the project development process specification; ? Web customers support Microsoft IE6.0 and above, FireFox3.0 and

The above version; ? The communication between Tonglian Fund payment system and payment gateway system adopts Hessian technology; ? JAVA SUN JDK 1.4.2, J2EE 1.3.

2.1. Subsystem design This chapter mainly defines subsystems, subsystem identifiers, subsystem functions, and relationships between subsystems.

2.1.1. Subsystem description 2.1.2. Subsystem relationship description ? The APP layer uses database 1 to store data; ? The payment interaction control subsystem stores the transaction result notification content in database 2; ? Notifies the server to extract transactions from database 2

The result notification content is forwarded; ? The bank interface system uses database 3 to record bank transaction flow; ? The APP layer exchanges files with the bank interface system through the file server.

2.2. Software hierarchical architecture design 2.2.1. Software hierarchical architecture design diagram 2.2.2. Software hierarchical architecture description The overall design of the system is divided into four levels: user interface layer, processing control layer, business logic layer, and DAO layer.

Because the functional types of modules at each level of each subsystem are basically the same, this section is described in units of levels.

2.2.2.1. User interface layer The user interface provides the user interface in B/S mode and the merchant interface in C/S mode.

All user interfaces are designed in Web-Browser mode.

The user interface layer will send the operation request to the processing control layer for operation processing.

2.2.2.2. Processing control layer The main function of the program in this layer is to handle the pre-data preparation, post-data processing, return of processing results, exception handling, etc. related to the execution of operations, without performing actual business operations.

The processing control layer will be divided into two parts: ? Dispatcher class? The business control class will call the corresponding business control class after the Dispatcher obtains the function request. The business control class will then call the functional methods of the business logic layer according to different functions.

Handling of actual functions.

2.2.2.3. Business logic layer This layer contains programs for actual functional processing, such as database operation services, transaction management, public service programs, etc.

Types in this level are abstracted and encapsulated using interface-oriented programming, object-oriented analysis, and design methods.

2.2.2.4. DAO layer This layer mainly encapsulates database operation functions.

2.3. Module design This chapter explains the division of modules at each level of this system, briefly explains the identifier and function of each module, and gives the control and controlled relationships between each module in a hierarchical manner.