Today's society has entered the era of information society. Information has received widespread attention from society and is regarded as the three pillars (materials, energy, and information) of social and scientific and technological development. Information is the basis of management and the basic basis for decision-making. In an organization, information has played an important role as the fourth energy besides human, material and financial resources. However, information is a non-material, new form of resource that is different from basic resources. Information is also an object of management and must be managed and controlled. This system mainly completes account management, withdrawal management, and deposit management of bank account management. , loss report management, card application management, user query, query statistics, etc. The system has complete backend addition, management, and password modification functions. The system uses JSP as the programming language. The paper mainly introduces the development background of this topic, the functions to be completed, and the development process. It mainly explains the key points and design ideas of the system design. , difficult technologies and solutions.
Keywords : bank account management platform; JSP technology; SSM framework; MYSQL database;
SSM Bank Account Management Platform
Today's society has entered the era of information society, and information has received widespread attention from society, regarded as the three pillars of social and scientific and technological development (materials, energy, and information). Information is the foundation of management and the fundamental basis for decision-making. In an organization, information has played an important role as the fourth energy source beyond human, material, and financial resources. However; Information is a new form of resource that is non material and different from basic resources. Information is also the object of management and must be managed and controlled. This system mainly completes account management, withdrawal management, deposit management, loss reporting management, card application management, user query, query statistics, etc. for bank account management. The system has complete backend addition, management, and password modification functions. The system uses JSP as the programming language. The paper mainly introduces the development background of this project, the functions to be completed, and the development process. The focus is on explaining the key points, design ideas, difficult technologies, and solutions of the system design
Keywords: Bank account management platform; JSP technology; SSM framework; MYSQL database;
Table of contents
2 Introduction to related technologies
2.3 Introduction to JSP technology
3.2 System performance analysis
3.4.4 Deletion of information process
4.3 System sequence diagram design
4.3.1 Login module sequence diagram
4.3.2 Add information module sequence diagram
4.4.1 Database ER diagram design
Table access_token (login access duration)
Table account_cancellation_management (cancellation management)
Table account_information (account information)
Table account_opening_application (account opening application)
Table article (article: article for content management system)
Table article_type (article classification)
Table auth (user rights management)
Table branch_inquiry (branch inquiry)
Table card_application (card application)
Table change_data (change data)
Table consumption_data (consumption data)
Table deposit_information (deposit information)
Table loss_reporting_management (loss reporting management)
Table ordinary_users (ordinary users)
Table user (user account: used to save user login information)
Table user_group (user group: used for user front-end identity and authentication)
Table withdrawal_information (withdrawal information)
5.2 Ordinary user function module
1 Introduction
1.1 Development background
With the development of science and technology and social progress, especially the widespread popularization of computers, computer applications have gradually shifted from large-scale scientific computing and massive data processing to large-scale transaction processing and workflow management. This has resulted in the emergence of desktop computers as the core. , the application of management information system with database management system as the development environment in large-scale transaction processing and workflow management, especially in bank account management, has received increasing attention.
In recent years, my country's information industry has developed rapidly, and manual management methods have become incompatible in applications that require a large amount of transaction processing, such as bank account management. It is imperative to use IT technology to improve service quality and management levels. At present, the inevitable trend of opening up to the outside world has caused the banking industry to face direct challenges from foreign banking giants. Therefore, banks must improve their work efficiency and improve their working environment. In this way, the informatization of account management is imperative. In traditional bank account management, the process is often complex and cumbersome. Account management is centered on the two contents of entry and exit. The methods of statistics and inquiries are different; and there will be problems with repeated transmission of information. , so the process must be informatized. The overall task of our system development is to realize the systematization, standardization, automation and intelligence of bank account management, so as to achieve the purpose of improving the efficiency of enterprise management. The purpose of this topic is to make bank account management clear, transparent, easy to operate, and easy to manage. Different management details are realized through the optimized combination of functional modules, so that the management process can be automated and informatized to the greatest extent, and manual operation links can be automatically reviewed to minimize the accounting error rate. In traditional bank account management systems, bank account management is often very complicated and cumbersome. Account management is characterized by a relatively large amount of information processing and a wide variety of types managed. Moreover, due to the large amount of documents such as savings slips and withdrawal slips, and the large amount of related information, the methods of query and statistics are different. Repeated transmission of information often occurs during the management process, so bank account management must be computerized. The overall task of our system development is to realize the systematization, standardization, automation, informatization and intelligence of bank account management, so as to achieve the purpose of improving the efficiency of account management.
1.2 Development significance
With the progress of society and the development of computer technology, especially the rapid progress of network technology, the concept of information has become deeply rooted in people's hearts. As an important part of contemporary society, information science plays a decisive role in the national economy. Today, as China's economy is booming, the increasing number of savings users and capital circulation are severely testing the reliability of bank account management every day. Establishing and developing a bank account management system with relatively complete functions can not only serve customers, contact customers, attract customers, stabilize customers, and consolidate the foundation of banking business operations, but also shape the bank's own market image by serving the society and reflect the bank's comprehensive Strength can also increase the bank's total deposits; by providing efficient and high-quality services, it attracts more customers to the bank to handle business, thereby expanding the bank's customer base, strengthening the business relationship between the bank and customers, and also driving other businesses development of. In short, the competition and development of modern commercial banks have broken through the traditional business framework. In order to improve the bank's business competitiveness, expand its customer base, and cultivate new profit growth points, it is necessary to vigorously improve its account management system. Therefore, it is necessary to establish a fully functional A reliable account management platform has become an urgent need for banks’ current business development.
1.3 Research content
The development and design of the bank account management platform is based on the actual situation of the user. A detailed analysis of the system needs is carried out, and then the overall design of the system is carried out. Finally, through testing, the system design is made more complete and all functions in the system can be realized. Before starting to write the paper, I personally went to the library to borrow SSM framework books, MYSQL database books and other programming books. Then, for the bank account management platform I developed, I searched the Internet for many systems that others had built, and based on their design results, I Carry out more detailed system design for your own system, list all the functional results in the system one by one, then conduct demand analysis, and finally code all functional modules, and finally complete the overall system test to achieve normal operation of the system.
The paper written this time contains 6 parts, the specific contents are as follows:
Part One Introduction: The article mainly elaborates on the necessity of developing this system from the development background and development significance.
Part 2 Related Technologies: Various technologies used in system development are roughly introduced.
Part 3 System Analysis: Conduct a detailed analysis of the feasibility of the system and all functional requirements to see whether the system is possible to develop.
The fourth part, system design: functional module design and database design, are represented by special tables and pictures.
Part 5: System Implementation: Interface display of the main functional modules of the system.
Part Six System Testing: Test whether each function of the system can operate normally and meet people's needs.
2 Introduction to related technologies
2.1 SSM framework
Today's popular "SSM combination framework" is the abbreviation of Spring + SpringMVC + MyBatis, which is sought after by many. The "combination SSM framework" is a team spirit of strong alliances, each performing its own duties, and coordination and complementation. A framework for web projects, usually simpler data sources. Spring is a lightweight inversion of control framework (IoC), but it is also an surface-oriented container (AOP). SpringMVC is often used in the classified working mode of the controller, which is separated from the model object, and the function of the program object is processed with the ATM. This decoupled treatment makes it easier to personalize the entire system. MyBatis is a good sustainability framework that supports ordinary SQL queries while allowing advanced mapping of stored procedures for data optimization. Due to the high development cost, difficulty in maintenance after development, and some difficult-to-solve problems during the development process of large-scale Java web applications, the "SSM Combination Framework" is adopted, which allows the establishment of a business hierarchy and provides a good solution to this problem. .
2.2 Introduction to JAVA
Java mainly uses CORBA technology and security model to protect data in Internet applications. It also provides full support for EJB (Enterprise JavaBeans), java servlet API, SSM (java server pages), and XML technology. The JAVA language is an object-oriented language that provides the most basic methods to complete specified tasks. Developers only need to know some concepts to write some applications. Java programs are relatively small and their code can run on small machines. Java is a computer programming language with three main features: encapsulation, inheritance, and polymorphism. It is widely used in enterprise web application development and mobile application development.
The difference between the Java language and general compilers and literal translation is that Java first converts the source code into bytecode and then converts it into an executable file for the JVM, which can run on a variety of different JVMs. Therefore, its cross-platform nature is achieved. While this made Java very slow in its early days, it has improved as Java has developed.
2.3 Introduction to JSP technology
JSP JavaServer Pages is a kind of *.htm, *.6>htm1 that is initiated by Sun Microsystems and established by many companies. Scriptlet and JSP tag tag are inserted into htm1 to form a JSP file *.jsp. Web applications developed with JSP are cross-platform and can run under Linux as well as other operating systems. JSP technology uses the Java programming language to write XML-like tags and scriptlets to encapsulate the processing logic for generating dynamic web pages. Web pages can also access the application logic of resources that exist on the server through tags and scriptlets. JSP separates web page logic from web page design and display, supports reusable component-based design, and makes the development of web-based applications quick and easy. When the web server encounters a request to access a JSP web page, it first executes the program segment, and then returns the execution result to the client together with the HTML code in the JSP file. The inserted Java program segment can operate JSP and Java (1) Write once and run anywhere. At this point, Java has better multi-platform support than (2) the system. Basically, you can develop in any environment on all platforms, deploy the system in any environment, and expand in any environment. The limitations compared to JSP/PHP are obvious. 3) Powerful scalability. Support from only a small (4) diverse and powerful development tools. This is very similar to JSP. Java already has many excellent development tools, many of which are available for free, and many of them can already run smoothly on multiple platforms.
2.4 Tomcat server
Tomcat is a lightweight server, so it is not universally applicable to small and medium-sized enterprises. But when programmers need to develop or debug SSM programs, this server is usually the first choice. For a person with only basic computer knowledge, the computer system has a good Apache server and can access HTML pages very well. Although Tomcat is an extension of Apache, they can run independently and the two do not interfere with each other. When configured correctly, the Apache server provides technical support for the running of HTML pages, and Tomcat's task is to run Servle and SSM pages. Tomca also has certain HTML page processing capabilities.
2. 5 MySQL database
Databases are an integral part of the system development process. In terms of WEB applications, MySQL AB has developed a MySQL relational database management system with great advantages. MySQL can store data in different tables, which is very flexible and can also increase the speed of the system in practical applications. Database access is most commonly used in the standard SQL language, and MySQL is used in the SQL language, so it is highly compatible. Database operations are essential, including functions such as adding, deleting, modifying, and querying database tables. Nowadays, databases can be divided into relational databases and non-relational databases. Mysql is a relational database. Mysql database is a small relational database. It has its own characteristics: small size, fast speed, low cost, etc. Mysql Database is currently the most popular open source database.
In WEB application technology, the Mysql database supports different operating system platforms. Although the installation and configuration under different platforms are different, the difference is not very big. There are two installation methods for Mysql on the Windows platform, binary version and installation-free. Version. After installing the Mysql database, you need to start the service process so that the corresponding client can connect to the database. The client can log in to the database through the command line or graphical interface tool.
3 System analysis
3.1 Feasibility analysis
At the beginning of system development, system feasibility analysis must be carried out. The purpose of this is to solve the biggest problem with the minimum cost. Once the program development meets the needs of users, the benefits will be many. Next, we will consider whether this system is worth developing from technical, operational and economic aspects.
3.1.1 Technical feasibility
This bank's account management platform is developed and designed using SSM framework technology, JSP technology and MYSQL database. As a computer major student, I have been exposed to a lot of knowledge about programming during school, including various programming software. How well I understand them It is also relatively systematic, so I still have a certain degree of confidence in technology development.
3.1.2 Economic feasibility
When I designed the system, I mainly started with cost savings, and then designed the specific system. During the system design process, all the tools and technical support used were free, so there was no need to incur any cost. The system can be designed. All resources used are free and can be downloaded and used as long as there is an Internet connection. There is no need to pay corresponding fees, so the project is completely feasible in economic terms.
3.1.3 Operational feasibility
I am a student myself and have insufficient experience in program development. The interface design should not be too complicated. It should be simple and beautiful, easy to operate, and should not make users feel unsmooth. Once the user enters the operation interface, there will be corresponding prompts on the interface. Following the operation prompts, the corresponding functional operation module can be found, which can be used by the user without training.
From the feasibility analysis of the above parts, it can be concluded that the bank account management platform developed this time has no major problems in development and is worthy of development.
3.2 System performance analysis
(1) System response efficiency: The page response time should be within 3 seconds, no longer than 4 seconds, and support at least 10,000 people online at the same time on all systems.
(2) Simple and clear interface: The system interface is required to be simple and clear, easy to operate, and consistent with user operating habits.
(3) High storage: Because there is a lot of information that needs to be stored in the bank account management platform, there are great requirements for the storage capacity of the system. It requires the support of a powerful database to ensure that all information is safe and stable. for storage.
(4) Ease of learning: The system must be easy to operate and easy to use. There are not many complicated operations and only simple learning is required to operate the system.
(5) Stability requirements: The developed bank account management platform requires stable operation and no unclear interface or blurred fonts during operation.
(6) Stability: The developed bank account management platform requires stable operation and no unclear interface or blurred fonts during operation.
3.3 System function analysis
The bank's account management platform mainly includes two functional modules, namely the administrator function module and the user module.
(1) Administrator module: The core user in the system is the system administrator. After the administrator logs in, he manages the backend system through the administrator menu. The main functions are: homepage, personal information (personal information, password change), public management (carousel, announcement information) user management (administrators, ordinary users), information management (news list, news category list), account opening application, account cancellation Management, card application, loss report management, account information, deposit information, withdrawal information, branch query, change data, consumption data and other functional modules. The administrator use case diagram is shown in Figure 3-1.
Figure 3-1 Administrator use case diagram
(2) Ordinary users: Home page, announcement information, news information, account opening application, loss report management, branch inquiry, my (my account, my collection, personal center) backend home page: personal information (personal information, modified information) account opening Application, account cancellation management, card application, loss reporting management, account information, deposit information, withdrawal information and other functional modules. A common user use case diagram is shown in Figure 3-2.
Figure 3-2 Common user use case diagram
3.4 System process analysis
3.4.1 Login process
The login module mainly meets the permission login of administrators and users. The login flow chart is shown in Figure 3-3.
Figure 3-3 Login flow chart
3.4.2 Registration process
Users who do not have an account can enter the registration interface to register. The user registration flow chart is shown in Figure 3-4.
Figure 3-4 Registration flow chart
3.4.3 Add information process
When the user adds information, the information number is automatically generated. The system will verify the added information. If the verification passes, it will be added to the database. If the information is added successfully, the addition will fail. The process of adding information is shown in Figure 3-5.
Figure 3-5 Add information flow chart
3.4.4 Deletion of information process
The user can select the information to be deleted and perform the information deletion operation. When deleting the information, the system prompts whether you are sure to delete the information. If yes, the information is deleted successfully and the system database deletes the information. The flow chart of deleting information is shown in Figure 3-6.
4 System design
4.1 System outline design
The bank's account management platform chooses two modes: B/S structure (Browser/Server, browser/server structure) and Web service-based model. It is suitable for operation on the Internet. As long as the user can connect to the Internet, the system can be operated at any time and anywhere. The system working principle diagram is shown in Figure 4-1:
Figure 4-1 System working principle diagram
4.2 System structure design
The entire system is composed of multiple functional modules. All functional modules should be listed one by one, and then functional design should be carried out one by one so that each module has a corresponding functional design, and then the overall system design should be carried out. .
The structure diagram of the bank’s account management platform is shown in Figure 4-2 .
Figure 4-2 System functional structure diagram
4.3 System sequence diagram design
4.3.1 Login module sequence diagram
The login module mainly meets the permission login of administrators and users . The login module sequence diagram is shown in Figure 4-3 .
Figure 4-3 Login sequence diagram
4.3.2 Add information module sequence diagram
Administrators and users can add information after logging in. The sequence diagram of the add information module is shown in Figure 4-4 .
Figure 4-4 Sequence diagram for adding information
4.4 Database design
A good database can be related to the quality of program development. Database design is inseparable from the design of table structures, the connections between tables, and the content of data tables that need to be designed for system development. During the database design, the database should be developed and designed in a targeted manner based on the actual situation.
4.4.1 Database ER diagram design
This bank account management platform uses a MYSQL database, which is fast for data storage. Because the bank account management platform is mainly about the management of scientific and technological information, and there is a lot of information content. This requires a good database design and clear classification. When information cannot be added, the information will be too confusing. A well-designed database must first clearly express the relationship between each entity.
The ER diagram of the system is shown below:
Figure 4-5 System ER diagram
4. 4.2 Database table design
Convert ER diagram of database conceptual design into relational database. In a relational database, data relationships are composed of data tables, but the structure of the table is represented by the fields of the table.
Table access_token (login access duration)
| serial number |
name |
type of data |
length |
Decimal places |
Allow null values |
primary key |
default value |
illustrate |
| 1 |
token_id |
int |
10 |
0 |
N |
Y |
Temporary access badge ID |
|
| 2 |
token |
varchar |
64 |
0 |
Y |
N |
temporary access badge |
|
| 3 |
info |
text |
65535 |
0 |
Y |
N |
||
| 4 |
maxage |
int |
10 |
0 |
N |
N |
2 |
Maximum lifespan: Default 2 hours |
| 5 |
create_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
Creation time: |
| 6 |
update_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
Update time: |
| 7 |
user_id |
int |
10 |
0 |
N |
N |
0 |
user ID: |
Table account_cancellation_management (cancellation management)
| serial number |
name |
type of data |
length |
Decimal places |
Allow null values |
primary key |
default value |
illustrate |
| 1 |
account_cancellation_management_id |
int |
10 |
0 |
N |
Y |
Account cancellation management ID |
|
| 2 |
applicants |
int |
10 |
0 |
Y |
N |
0 |
Applicants |
| 3 |
user_name |
varchar |
64 |
0 |
Y |
N |
username |
|
| 4 |
account_cancellation |
varchar |
64 |
0 |
Y |
N |
Cancel account |
|
| 5 |
application_description |
text |
65535 |
0 |
Y |
N |
Application instructions |
|
| 6 |
examine_state |
varchar |
16 |
0 |
N |
N |
Not reviewed |
Approval Status |
| 7 |
recommend |
int |
10 |
0 |
N |
N |
0 |
Intelligent Recommendation |
| 8 |
create_time |
datetime |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
creation time |
| 9 |
update_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
Update time |
Table account_information (account information)
| serial number |
name |
type of data |
length |
Decimal places |
Allow null values |
primary key |
default value |
illustrate |
| 1 |
account_information_id |
int |
10 |
0 |
N |
Y |
Account information ID |
|
| 2 |
account_user |
int |
10 |
0 |
Y |
N |
0 |
Account user |
| 3 |
user_name |
varchar |
64 |
0 |
Y |
N |
username |
|
| 4 |
bank_account |
varchar |
64 |
0 |
N |
N |
Bank Account |
|
| 5 |
account_balance |
varchar |
64 |
0 |
Y |
N |
Account Balance |
|
| 6 |
recommend |
int |
10 |
0 |
N |
N |
0 |
Intelligent Recommendation |
| 7 |
create_time |
datetime |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
creation time |
| 8 |
update_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
Update time |
Table account_opening_application (account opening application)
| serial number |
name |
type of data |
length |
Decimal places |
Allow null values |
primary key |
default value |
illustrate |
| 1 |
account_opening_application_id |
int |
10 |
0 |
N |
Y |
Account opening application ID |
|
| 2 |
applicants |
int |
10 |
0 |
Y |
N |
0 |
Applicants |
| 3 |
user_name |
varchar |
64 |
0 |
Y |
N |
username |
|
| 4 |
user_gender |
varchar |
64 |
0 |
Y |
N |
User gender |
|
| 5 |
user_age |
varchar |
64 |
0 |
Y |
N |
User age |
|
| 6 |
date_of_birth |
varchar |
64 |
0 |
Y |
N |
date of birth |
|
| 7 |
contact_information |
varchar |
64 |
0 |
Y |
N |
Contact information |
|
| 8 |
e_mail |
varchar |
64 |
0 |
Y |
N |
|
|
| 9 |
postal_code |
varchar |
64 |
0 |
Y |
N |
postal code |
|
| 10 |
id_number |
varchar |
64 |
0 |
Y |
N |
ID number |
|
| 11 |
home_address |
varchar |
64 |
0 |
Y |
N |
Home address |
|
| 12 |
work_unit |
varchar |
64 |
0 |
Y |
N |
employer |
|
| 13 |
application_date |
date |
10 |
0 |
Y |
N |
Date of Application |
|
| 14 |
application_notes |
varchar |
64 |
0 |
Y |
N |
Application notes |
|
| 15 |
examine_state |
varchar |
16 |
0 |
N |
N |
Not reviewed |
Approval Status |
| 16 |
examine_reply |
varchar |
16 |
0 |
Y |
N |
moderation reply |
|
| 17 |
recommend |
int |
10 |
0 |
N |
N |
0 |
Intelligent Recommendation |
| 18 |
create_time |
datetime |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
creation time |
| 19 |
update_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
Update time |
Table article (article: article for content management system)
| serial number |
name |
type of data |
length |
Decimal places |
Allow null values |
primary key |
default value |
illustrate |
| 1 |
article_id |
mediumint |
8 |
0 |
N |
Y |
Article id: [0,8388607] |
|
| 2 |
title |
varchar |
125 |
0 |
N |
Y |
Title: [0,125] is used in the title tag of articles and html |
|
| 3 |
type |
varchar |
64 |
0 |
N |
N |
0 |
Article classification: [0,1000] is used to search for articles of the specified type |
| 4 |
hits |
int |
10 |
0 |
N |
N |
0 |
Number of clicks: [0,1000000000] Number of people who visited this article |
| 5 |
praise_len |
int |
10 |
0 |
N |
N |
0 |
Number of likes |
| 6 |
create_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
Creation time: |
| 7 |
update_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
Update time: |
| 8 |
source |
varchar |
255 |
0 |
Y |
N |
Source: [0,255] Source of article |
|
| 9 |
url |
varchar |
255 |
0 |
Y |
N |
Source address: [0,255] used to jump to the website where the article was published |
|
| 10 |
tag |
varchar |
255 |
0 |
Y |
N |
Tag: [0,255] is used to mark the relevant content of the article. Multiple tags are separated by spaces. |
|
| 11 |
content |
longtext |
2147483647 |
0 |
Y |
N |
Text: the main content of the article |
|
| 12 |
img |
varchar |
255 |
0 |
Y |
N |
cover picture |
|
| 13 |
description |
text |
65535 |
0 |
Y |
N |
Article description |
Table article_type (article classification)
| serial number |
name |
type of data |
length |
Decimal places |
Allow null values |
primary key |
default value |
illustrate |
| 1 |
type_id |
smallint |
5 |
0 |
N |
Y |
Category ID: [0,10000] |
|
| 2 |
display |
smallint |
5 |
0 |
N |
N |
100 |
Display order: [0,1000] determines the order in which categories are displayed. |
| 3 |
name |
varchar |
16 |
0 |
N |
N |
Category name: [2,16] |
|
| 4 |
father_id |
smallint |
5 |
0 |
N |
N |
0 |
Parent category ID: [0,32767] |
| 5 |
description |
varchar |
255 |
0 |
Y |
N |
Description: [0,255] describes the role of this classification |
|
| 6 |
icon |
text |
65535 |
0 |
Y |
N |
Category icon: |
|
| 7 |
url |
varchar |
255 |
0 |
Y |
N |
External link address: [0,255] If this category jumps to other websites, set it on the URL |
|
| 8 |
create_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
Creation time: |
| 9 |
update_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
Update time: |
Table auth (user rights management)
| serial number |
name |
type of data |
length |
Decimal places |
Allow null values |
primary key |
default value |
illustrate |
| 1 |
auth_id |
int |
10 |
0 |
N |
Y |
Authorization ID: |
|
| 2 |
user_group |
varchar |
64 |
0 |
Y |
N |
user group: |
|
| 3 |
mod_name |
varchar |
64 |
0 |
Y |
N |
Module name: |
|
| 4 |
table_name |
varchar |
64 |
0 |
Y |
N |
Table Name: |
|
| 5 |
page_title |
varchar |
255 |
0 |
Y |
N |
page title: |
|
| 6 |
path |
varchar |
255 |
0 |
Y |
N |
Routing path: |
|
| 7 |
position |
varchar |
32 |
0 |
Y |
N |
Location: |
|
| 8 |
mode |
varchar |
32 |
0 |
N |
N |
_blank |
Jump method: |
| 9 |
add |
tinyint |
3 |
0 |
N |
N |
1 |
Is it possible to add: |
| 10 |
of the |
tinyint |
3 |
0 |
N |
N |
1 |
Can it be deleted: |
| 11 |
set |
tinyint |
3 |
0 |
N |
N |
1 |
Whether it can be modified: |
| 12 |
get |
tinyint |
3 |
0 |
N |
N |
1 |
Is it possible to view: |
| 13 |
field_add |
text |
65535 |
0 |
Y |
N |
Add fields: |
|
| 14 |
field_set |
text |
65535 |
0 |
Y |
N |
Modify fields: |
|
| 15 |
field_get |
text |
65535 |
0 |
Y |
N |
Query fields: |
|
| 16 |
table_nav_name |
varchar |
500 |
0 |
Y |
N |
Cross-table navigation name: |
|
| 17 |
table_nav |
varchar |
500 |
0 |
Y |
N |
Cross-table navigation: |
|
| 18 |
option |
text |
65535 |
0 |
Y |
N |
Configuration: |
|
| 19 |
create_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
Creation time: |
| 20 |
update_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
Update time: |
Table branch_inquiry (branch inquiry)
| serial number |
name |
type of data |
length |
Decimal places |
Allow null values |
primary key |
default value |
illustrate |
| 1 |
branch_inquiry_id |
int |
10 |
0 |
N |
Y |
Network query ID |
|
| 2 |
bank_name |
varchar |
64 |
0 |
Y |
N |
Bank name |
|
| 3 |
branch_address |
varchar |
64 |
0 |
Y |
N |
Branch address |
|
| 4 |
network_image |
varchar |
255 |
0 |
Y |
N |
Network pictures |
|
| 5 |
business_hours |
varchar |
64 |
0 |
Y |
N |
Business hours |
|
| 6 |
atm |
varchar |
64 |
0 |
Y |
N |
ATM |
|
| 7 |
remarks |
text |
65535 |
0 |
Y |
N |
Remarks |
|
| 8 |
hits |
int |
10 |
0 |
N |
N |
0 |
Clicks |
| 9 |
praise_len |
int |
10 |
0 |
N |
N |
0 |
Number of likes |
| 10 |
recommend |
int |
10 |
0 |
N |
N |
0 |
Intelligent Recommendation |
| 11 |
create_time |
datetime |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
creation time |
| 12 |
update_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
Update time |
Table card_application (card application)
| serial number |
name |
type of data |
length |
Decimal places |
Allow null values |
primary key |
default value |
illustrate |
| 1 |
card_application_id |
int |
10 |
0 |
N |
Y |
Card application ID |
|
| 2 |
applicants |
int |
10 |
0 |
Y |
N |
0 |
Applicants |
| 3 |
user_name |
varchar |
64 |
0 |
Y |
N |
username |
|
| 4 |
user_gender |
varchar |
64 |
0 |
Y |
N |
User gender |
|
| 5 |
user_age |
varchar |
64 |
0 |
Y |
N |
User age |
|
| 6 |
date_of_birth |
varchar |
64 |
0 |
Y |
N |
date of birth |
|
| 7 |
contact_information |
varchar |
64 |
0 |
Y |
N |
Contact information |
|
| 8 |
e_mail |
varchar |
64 |
0 |
Y |
N |
|
|
| 9 |
postal_code |
varchar |
64 |
0 |
Y |
N |
postal code |
|
| 10 |
id_number |
varchar |
64 |
0 |
Y |
N |
ID number |
|
| 11 |
home_address |
varchar |
64 |
0 |
Y |
N |
Home address |
|
| 12 |
work_unit |
varchar |
64 |
0 |
Y |
N |
employer |
|
| 13 |
card_type |
varchar |
64 |
0 |
Y |
N |
Card application type |
|
| 14 |
application_notes |
text |
65535 |
0 |
Y |
N |
Application notes |
|
| 15 |
examine_state |
varchar |
16 |
0 |
N |
N |
Not reviewed |
Approval Status |
| 16 |
recommend |
int |
10 |
0 |
N |
N |
0 |
Intelligent Recommendation |
| 17 |
create_time |
datetime |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
creation time |
| 18 |
update_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
Update time |
Table change_data (change data)
| serial number |
name |
type of data |
length |
Decimal places |
Allow null values |
primary key |
default value |
illustrate |
| 1 |
change_data_id |
int |
10 |
0 |
N |
Y |
Change data ID |
|
| 2 |
date |
date |
10 |
0 |
Y |
N |
date |
|
| 3 |
number_of_changes |
varchar |
64 |
0 |
Y |
N |
Number of changes |
|
| 4 |
recommend |
int |
10 |
0 |
N |
N |
0 |
Intelligent Recommendation |
| 5 |
create_time |
datetime |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
creation time |
| 6 |
update_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
Update time |
table collect (collection)
| serial number |
name |
type of data |
length |
Decimal places |
Allow null values |
primary key |
default value |
illustrate |
| 1 |
collect_id |
int |
10 |
0 |
N |
Y |
收藏ID： |
|
| 2 |
user_id |
int |
10 |
0 |
N |
N |
0 |
收藏人ID： |
| 3 |
source_table |
varchar |
255 |
0 |
Y |
N |
来源表： |
|
| 4 |
source_field |
varchar |
255 |
0 |
Y |
N |
来源字段： |
|
| 5 |
source_id |
int |
10 |
0 |
N |
N |
0 |
来源ID： |
| 6 |
title |
varchar |
255 |
0 |
Y |
N |
标题： |
|
| 7 |
img |
varchar |
255 |
0 |
Y |
N |
封面： |
|
| 8 |
create_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
创建时间： |
| 9 |
update_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
更新时间： |
表comment (评论)
| 编号 |
名称 |
数据类型 |
长度 |
小数位 |
允许空值 |
主键 |
默认值 |
说明 |
| 1 |
comment_id |
int |
10 |
0 |
N |
Y |
评论ID： |
|
| 2 |
user_id |
int |
10 |
0 |
N |
N |
0 |
评论人ID： |
| 3 |
reply_to_id |
int |
10 |
0 |
N |
N |
0 |
回复评论ID：空为0 |
| 4 |
content |
longtext |
2147483647 |
0 |
Y |
N |
内容： |
|
| 5 |
nickname |
varchar |
255 |
0 |
Y |
N |
昵称： |
|
| 6 |
avatar |
varchar |
255 |
0 |
Y |
N |
头像地址：[0,255] |
|
| 7 |
create_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
创建时间： |
| 8 |
update_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
更新时间： |
| 9 |
source_table |
varchar |
255 |
0 |
Y |
N |
来源表： |
|
| 10 |
source_field |
varchar |
255 |
0 |
Y |
N |
来源字段： |
|
| 11 |
source_id |
int |
10 |
0 |
N |
N |
0 |
来源ID： |
表consumption_data (消费数据)
| 编号 |
名称 |
数据类型 |
长度 |
小数位 |
允许空值 |
主键 |
默认值 |
说明 |
| 1 |
consumption_data_id |
int |
10 |
0 |
N |
Y |
消费数据ID |
|
| 2 |
date |
date |
10 |
0 |
Y |
N |
日期 |
|
| 3 |
consumption_amount |
varchar |
64 |
0 |
Y |
N |
消费金额 |
|
| 4 |
recommend |
int |
10 |
0 |
N |
N |
0 |
智能推荐 |
| 5 |
create_time |
datetime |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
创建时间 |
| 6 |
update_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
更新时间 |
表deposit_information (存款信息)
| 编号 |
名称 |
数据类型 |
长度 |
小数位 |
允许空值 |
主键 |
默认值 |
说明 |
| 1 |
deposit_information_id |
int |
10 |
0 |
N |
Y |
存款信息ID |
|
| 2 |
account_user |
int |
10 |
0 |
Y |
N |
0 |
账户用户 |
| 3 |
user_name |
varchar |
64 |
0 |
Y |
N |
用户姓名 |
|
| 4 |
bank_account |
varchar |
64 |
0 |
Y |
N |
银行账号 |
|
| 5 |
deposit_amount |
varchar |
64 |
0 |
Y |
N |
存款金额 |
|
| 6 |
recommend |
int |
10 |
0 |
N |
N |
0 |
智能推荐 |
| 7 |
create_time |
datetime |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
创建时间 |
| 8 |
update_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
更新时间 |
表hits (用户点击)
| 编号 |
名称 |
数据类型 |
长度 |
小数位 |
允许空值 |
主键 |
默认值 |
说明 |
| 1 |
hits_id |
int |
10 |
0 |
N |
Y |
点赞ID： |
|
| 2 |
user_id |
int |
10 |
0 |
N |
N |
0 |
点赞人： |
| 3 |
create_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
创建时间： |
| 4 |
update_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
更新时间： |
| 5 |
source_table |
varchar |
255 |
0 |
Y |
N |
来源表： |
|
| 6 |
source_field |
varchar |
255 |
0 |
Y |
N |
来源字段： |
|
| 7 |
source_id |
int |
10 |
0 |
N |
N |
0 |
来源ID： |
表loss_reporting_management (挂失管理)
| 编号 |
名称 |
数据类型 |
长度 |
小数位 |
允许空值 |
主键 |
默认值 |
说明 |
| 1 |
loss_reporting_management_id |
int |
10 |
0 |
N |
Y |
挂失管理ID |
|
| 2 |
reported_loss_user |
int |
10 |
0 |
Y |
N |
0 |
挂失用户 |
| 3 |
user_name |
varchar |
64 |
0 |
Y |
N |
用户姓名 |
|
| 4 |
id_number |
varchar |
64 |
0 |
Y |
N |
身份证号 |
|
| 5 |
contact_information |
varchar |
64 |
0 |
Y |
N |
联系方式 |
|
| 6 |
home_address |
varchar |
64 |
0 |
Y |
N |
家庭住址 |
|
| 7 |
bank_card_number |
varchar |
64 |
0 |
Y |
N |
银行卡号 |
|
| 8 |
date_of_loss_reporting |
date |
10 |
0 |
Y |
N |
挂失日期 |
|
| 9 |
reason_for_reporting_loss |
text |
65535 |
0 |
Y |
N |
挂失原因 |
|
| 10 |
examine_state |
varchar |
16 |
0 |
N |
N |
未审核 |
审核状态 |
| 11 |
recommend |
int |
10 |
0 |
N |
N |
0 |
智能推荐 |
| 12 |
create_time |
datetime |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
创建时间 |
| 13 |
update_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
更新时间 |
表notice (公告)
| 编号 |
名称 |
数据类型 |
长度 |
小数位 |
允许空值 |
主键 |
默认值 |
说明 |
| 1 |
notice_id |
mediumint |
8 |
0 |
N |
Y |
公告id： |
|
| 2 |
title |
varchar |
125 |
0 |
N |
N |
标题： |
|
| 3 |
content |
longtext |
2147483647 |
0 |
Y |
N |
正文： |
|
| 4 |
create_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
创建时间： |
| 5 |
update_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
更新时间： |
表ordinary_users (普通用户)
| 编号 |
名称 |
数据类型 |
长度 |
小数位 |
允许空值 |
主键 |
默认值 |
说明 |
| 1 |
ordinary_users_id |
int |
10 |
0 |
N |
Y |
普通用户ID |
|
| 2 |
user_name |
varchar |
64 |
0 |
Y |
N |
用户姓名 |
|
| 3 |
user_gender |
varchar |
64 |
0 |
Y |
N |
用户性别 |
|
| 4 |
user_age |
varchar |
64 |
0 |
Y |
N |
用户年龄 |
|
| 5 |
user_level |
varchar |
64 |
0 |
Y |
N |
用户等级 |
|
| 6 |
examine_state |
varchar |
16 |
0 |
N |
N |
已通过 |
审核状态 |
| 7 |
recommend |
int |
10 |
0 |
N |
N |
0 |
智能推荐 |
| 8 |
user_id |
int |
10 |
0 |
N |
N |
0 |
用户ID |
| 9 |
create_time |
datetime |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
创建时间 |
| 10 |
update_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
更新时间 |
表praise (点赞)
| 编号 |
名称 |
数据类型 |
长度 |
小数位 |
允许空值 |
主键 |
默认值 |
说明 |
| 1 |
praise_id |
int |
10 |
0 |
N |
Y |
点赞ID： |
|
| 2 |
user_id |
int |
10 |
0 |
N |
N |
0 |
点赞人： |
| 3 |
create_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
创建时间： |
| 4 |
update_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
更新时间： |
| 5 |
source_table |
varchar |
255 |
0 |
Y |
N |
来源表： |
|
| 6 |
source_field |
varchar |
255 |
0 |
Y |
N |
来源字段： |
|
| 7 |
source_id |
int |
10 |
0 |
N |
N |
0 |
来源ID： |
| 8 |
status |
bit |
1 |
0 |
N |
N |
1 |
点赞状态:1为点赞，0已取消 |
表slides (轮播图)
| 编号 |
名称 |
数据类型 |
长度 |
小数位 |
允许空值 |
主键 |
默认值 |
说明 |
| 1 |
slides_id |
int |
10 |
0 |
N |
Y |
轮播图ID： |
|
| 2 |
title |
varchar |
64 |
0 |
Y |
N |
标题： |
|
| 3 |
content |
varchar |
255 |
0 |
Y |
N |
内容： |
|
| 4 |
url |
varchar |
255 |
0 |
Y |
N |
链接： |
|
| 5 |
img |
varchar |
255 |
0 |
Y |
N |
轮播图： |
|
| 6 |
hits |
int |
10 |
0 |
N |
N |
0 |
点击量： |
| 7 |
create_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
创建时间： |
| 8 |
update_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
更新时间： |
表upload (文件上传)
| 编号 |
名称 |
数据类型 |
长度 |
小数位 |
允许空值 |
主键 |
默认值 |
说明 |
| 1 |
upload_id |
int |
10 |
0 |
N |
Y |
上传ID |
|
| 2 |
name |
varchar |
64 |
0 |
Y |
N |
文件名 |
|
| 3 |
path |
varchar |
255 |
0 |
Y |
N |
访问路径 |
|
| 4 |
file |
varchar |
255 |
0 |
Y |
N |
文件路径 |
|
| 5 |
display |
varchar |
255 |
0 |
Y |
N |
显示顺序 |
|
| 6 |
father_id |
int |
10 |
0 |
Y |
N |
0 |
父级ID |
| 7 |
dir |
varchar |
255 |
0 |
Y |
N |
文件夹 |
|
| 8 |
type |
varchar |
32 |
0 |
Y |
N |
文件类型 |
表user (用户账户：用于保存用户登录信息)
| 编号 |
名称 |
数据类型 |
长度 |
小数位 |
允许空值 |
主键 |
默认值 |
说明 |
| 1 |
user_id |
mediumint |
8 |
0 |
N |
Y |
用户ID：[0,8388607]用户获取其他与用户相关的数据 |
|
| 2 |
state |
smallint |
5 |
0 |
N |
N |
1 |
账户状态：[0,10](1可用|2异常|3已冻结|4已注销) |
| 3 |
user_group |
varchar |
32 |
0 |
Y |
N |
所在用户组：[0,32767]决定用户身份和权限 |
|
| 4 |
login_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
上次登录时间： |
| 5 |
phone |
varchar |
11 |
0 |
Y |
N |
手机号码：[0,11]用户的手机号码，用于找回密码时或登录时 |
|
| 6 |
phone_state |
smallint |
5 |
0 |
N |
N |
0 |
手机认证：[0,1](0未认证|1审核中|2已认证) |
| 7 |
username |
varchar |
16 |
0 |
N |
N |
用户名：[0,16]用户登录时所用的账户名称 |
|
| 8 |
nickname |
varchar |
16 |
0 |
Y |
N |
昵称：[0,16] |
|
| 9 |
password |
varchar |
64 |
0 |
N |
N |
密码：[0,32]用户登录所需的密码，由6-16位数字或英文组成 |
|
| 10 |
|
varchar |
64 |
0 |
Y |
N |
邮箱：[0,64]用户的邮箱，用于找回密码时或登录时 |
|
| 11 |
email_state |
smallint |
5 |
0 |
N |
N |
0 |
邮箱认证：[0,1](0未认证|1审核中|2已认证) |
| 12 |
avatar |
varchar |
255 |
0 |
Y |
N |
头像地址：[0,255] |
|
| 13 |
create_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
创建时间： |
表user_group (用户组：用于用户前端身份和鉴权)
| 编号 |
名称 |
数据类型 |
长度 |
小数位 |
允许空值 |
主键 |
默认值 |
说明 |
| 1 |
group_id |
mediumint |
8 |
0 |
N |
Y |
用户组ID：[0,8388607] |
|
| 2 |
display |
smallint |
5 |
0 |
N |
N |
100 |
显示顺序：[0,1000] |
| 3 |
name |
varchar |
16 |
0 |
N |
N |
名称：[0,16] |
|
| 4 |
description |
varchar |
255 |
0 |
Y |
N |
描述：[0,255]描述该用户组的特点或权限范围 |
|
| 5 |
source_table |
varchar |
255 |
0 |
Y |
N |
来源表： |
|
| 6 |
source_field |
varchar |
255 |
0 |
Y |
N |
来源字段： |
|
| 7 |
source_id |
int |
10 |
0 |
N |
N |
0 |
来源ID： |
| 8 |
register |
smallint |
5 |
0 |
Y |
N |
0 |
注册位置: |
| 9 |
create_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
创建时间： |
| 10 |
update_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
更新时间： |
表withdrawal_information (取款信息)
| 编号 |
名称 |
数据类型 |
长度 |
小数位 |
允许空值 |
主键 |
默认值 |
说明 |
| 1 |
withdrawal_information_id |
int |
10 |
0 |
N |
Y |
取款信息ID |
|
| 2 |
account_user |
int |
10 |
0 |
Y |
N |
0 |
账户用户 |
| 3 |
user_name |
varchar |
64 |
0 |
Y |
N |
用户姓名 |
|
| 4 |
bank_account |
varchar |
64 |
0 |
Y |
N |
银行账号 |
|
| 5 |
withdrawal_amount |
varchar |
64 |
0 |
Y |
N |
取款金额 |
|
| 6 |
recommend |
int |
10 |
0 |
N |
N |
0 |
智能推荐 |
| 7 |
create_time |
datetime |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
创建时间 |
| 8 |
update_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
更新时间 |
5 系统详细设计
银行账目管理平台，在系统登录页面管理员填写账号、密码等信息滑动滑块进行验证登录，如图5-1所示。
图5-1管理员登录界面图
管理员登录进入银行账目管理平台之后，就可以对所有的信息进行查看，可以查看到主页、个人资料（个人信息、修改密码）公共管理（轮播图、公告信息）用户管理（管理员、普通用户）信息管理（新闻列表、新闻分类列表）、开户申请、销户管理、办卡申请、挂失管理、账户信息、存款信息、取款信息、网点查询、异动数据、消费数据等功能模块，并且还可以对其进行相应的操作管理，如图5-2所示。
图5-2 管理员功能页面图
银行账目管理平台中的管理员在“用户管理”这一菜单是中可以对注册普通用户以及管理员人员进行管控，如图5-3所示。
图5-3 用户管理界面图
银行账目管理平台中的管理人员在“信息管理”这一菜单下主要是对新闻列表以及新闻资讯所属的分类进行管控，如图5-4所示。
图5-4 信息管理页面图
银行账目管理平台中的管理人员在“公共管理”这一菜单下主要是对轮播图和公告信息进行发布至前台展示，还可根据需要进行增删改查等操作，如图5-5 5-6所示
图5-5轮播图管理界面图
图5-6公告信息管理界面图
异动数据，管理员在此页面可查看日期、异动数量、新增时间、更新时间等信息，专业名称进行分类管理，可根据需要进行详情、删除或新增等相应的操作，如图5-6所示。
图5-6异动数据管理界面图
消费数据，管理员在此页面可查看日期、消费金额、新增时间、更新时间等信息，可根据需要进行详情、删除或新增等相应的操作，如图5-7所示
图5-7消费数据管理界面图
不是银行账目管理平台中正式用户的是可以在线进行注册的，如果你没有本银行账目管理平台的账号的话，添加“注册”，当填写上自己的账号+密码+确认密码+昵称+邮箱+手机号+身份+用户姓名+用户性别+用户年龄等后再点击“注册”按钮后将会先验证输入的有没有空数据，再次验证密码和确认密码是否是一样的，最后验证输入的账户名和数据库表中已经注册的账户名是否重复，只有都验证没问题后即可用户注册成功。注册成功后在登录页面输入用户名、密码、图片验证进行登录，如图5-8 5-9所示。
图5-8用户注册界面图
图5-9用户登录界面图
公告信息：用户在此页面可查看管理员发布的公告信息，如图5-10所示。
图5-10公告信息界面图
新闻资讯：用户可在此页面搜索查看新闻资讯信息，对喜欢的新闻资讯可进行点赞、收藏、发表评论等操作，如图5-13所示。
图5-10新闻资讯界面图
图5-11资讯详情界面图
开户申请：用户在此页面可通过填写出生日期、联系电话、电子邮箱、邮箱编码、身份证号、家庭住址、工作单位、申请日期、申请备注等详细信息进行提交开户申请，如图5-12所示。
图5-12开户申请界面图
办卡申请：用户在此页面可通过填写出生日期、联系电话、电子邮箱、邮箱编码、身份证号、家庭住址、工作单位、办卡类型、申请备注等详细信息进行提交办卡申请，如图5-13所示。
图5-13办卡申请界面图
挂失管理：用户在此页面可通过填写挂失用户、用户姓名、联系方式、身份证号、家庭住址、银行卡号、挂失日期、挂失原因等详细信息进行提交挂失，如图5-14所示。
图5-14挂失管理界面图
网点查询：用户在此页面可通过关键字或下拉搜索查看网点信息，如：银行名称、网点地址、营业时间、取款机等信息，如图5-15所示。
图5-15网站查询界面图
银行账目管理平台，用户登录系统后台可看到个人资料、开户申请、办卡申请、挂失管理、账户信息、存款信息、取款信息等功能模块，如图5-16所示。
图5-16用户后台功能界面图
账户信息；用户在此页面可查看账户用户、用户姓名、银行账号、账户余额、新增时间、更新时间等详细信息，并且还可以对其进行存款、取款、详情等相应的操作，如图5-17所示。
图5-17账户信息管理界面图
存款信息；用户在此页面可查看账户用户、用户姓名、银行账号、存款金额、新增时间、更新时间等详细信息，并且还可以对其进行详情、重置、删除等相应的操作，如图5-18所示。
图5-18存款信息管理界面图
取款信息；用户在此页面可查看账户用户、用户姓名、银行账号、取款金额、新增时间、更新时间等详细信息，并且还可以对其进行详情、重置、删除等相应的操作，如图5-19所示。
图5-19取款信息管理界面图
个人资料：用户在此页面可对自己的个人信息和密码进行修改等操作，如图5-20 5-21所示。
图5-19个人信息界面图
图5-20修改密码界面图
6 系统测试
一个系统设计好后，就会进入测试阶段，测试的目标是检验设计好的网站是否可以正常无误的运行，尽可能的发现网站的问题，已使后期网站投入使用后网站尽少出错[12]。
6.1 测试定义
系统测试主要是判断系统是否可以正常运行，功能模块是否可以实现操作。程序代码中是否有错误出现。测试程序是开发过程中的一个主要问题。就算系统完成的再好，再进行程序测试时也会也会发现一个重来没有被发现的错误信息。
测试不仅是系统开发的开始，而且应该贯穿整个系统的整个生命周期。评估系统质量的方法不局限于系统编码和过程，应该与软件设计工作和历史需求分析密切相关。系统错误，不一定是代码错误，可能是阶段的设计摘要和设计细节存在问题，问题也可能出现在需求分析阶段。从实际情况来看，最初的问题很可能是一个小错误，根据按钮的原理，按钮后的按钮位错将是所有位错。该系统的原因也同样适用，随着后续的开发工作，误差将越来越严重。因此就应该对系统进行测试，在一开始就发现系统中存在的问题，就能保证以后系统能够正常稳定的运行。在测试系统中，开发人员应该站在客户的角度来处理测试工作，而现在主要的测试方法是黑盒测试。测试的目的可以概括为以下几点:首先，用户界面和客户需求是一致的，设置界面和设计风格统一;第二，创新设计接口规范设计标准，具有独特的审美特征;最后，人类传统的接口以满足审美需求，不能盲目地追求一种独特的，合理的规划布局，符合审美标准。
6.2 测试目的
测试的目的在于要对系统的稳定和可操作性能进行对照检查。对于软件的开发利用最终的目的在最后的测试和试用，这是一个不可缺少的重要环节。对于软件开发者而言，在对每一个单独的功能进行编排时候，都要有单独的测试，并通过测试阶段才可以研发多个功能性软件，这样既缩短了研发时间，也可以在的单个的早期测试中发现问题，以免融合后的软件，在查找问题时就很难快速解决或者急速定位问题。
SSM银行账目管理平台开发设计完成后，需要对其进行系统测试，测试的主要目的就是发现并找出系统中存在的问题，并及时的进行解决，确保系统可以正常稳定的运行下去，在进行系统测试的时候，在一定要非常的认真、仔细，切记不能粗心，不能放过一个漏洞，测试时候一定不要着急，要按照之前指定好的测试步骤一步一步进行，并且将测试的结果进行详细的记录，我们在进行测试的时候做好选择自动化的测试，这样既可以节省时间而且也能确保测试的准确性，如果采用人工测试的方法就不会这么的方便，由于人工测试有很多不确定的因素，在测试过程中很可能会出现一些问题，用机器测试就不会出现任何的问题，而且机器不会疲惫会一直二等工作下去。在测试的时候一定要非常专注，时刻关注着测试的结果，一但发现异常及时进行修改，最后，测试完之后的文档应该保存下来，方便以后测试时用到。系统测试的方法有很多，对于本银行账目管理平台的测试，我们使用了测试用得最多的黑盒测试方法来对该系统进行测试。
6.3测试方案
对测试计划的把握是测试方案的重中之重。所有的技术难点应该都被包含在这个测试计划之中。而且我们要保证能与目标形成一致性，以至于能够测试出一些主要存在的错误和一些错误的漏洞。可以完美解决这些问题就只有白盒测试或者黑盒测试。
构造测试是白盒测试的另一个名字，了解与分析程序的结构以及性能功用的，从而我们可以得到最终想要的结果并且观察出是不是每一条程序都能得到。
性能测试是黑盒测试别称，程序本身的运作通过程序的进程来观察，主要是看一下程序是不是能够像我们预期的目标那样发展，看一看我们的程序最终能不能完整的得到我们最后想要的功能和储存想得到的数据，到最后看一下我们的这个程序完整性能不能达到要求。
（1）模块测试
单元测试就是模块测试，顾名思义就是测试每个模块所承担的功能是否能够实现，这个测试就是为了找出代码在实际的设计运转中某一些小的程序所出现的偏差，很好地改正这些错误，就说明我们模块测试进行很成功过。
（2）集成测试：
集成测试就是对系统的测试以及对他子系统的一些性能测试，他检查的事系统的包装程序信息。找出其中的问题。他的优势主要有以下这几点：
软件耗费较少。
可以提前发现端口的错误。
更好的地位系统中错误的位置。
从底部往上面进行的方案针对于偏下层的结构，而中间的结构就采用折中的方法。
（3）验收测试：
终于到了结尾性的工作了。就是为了给用户看一下我们的系统功能是否达到了预期的效果。我采用了性能测试也就是黑盒测试对系统进行测试。
其结果是分别是：
有一定的差异在用户的需求。
再者就是结果与之差不了多少。
到了最后了，我们发现的问题都是与用户的需求存在一定的关联。
测试点：登录
测试的目标：输入账号密码以及验证码后系统会自动进行验证是否正确。
所用的环境：Windows10和IE浏览器。
输入信息：用户名、密码。
步骤：
（1）首先我们打来浏览器，进入该系统的登录界面。
（2）在进入页面登录部分以后可以进行对用户名、密码进行测试，具体测试输入情况如下表6.1所示。
表6.1 登录测试
| 情况 |
用户名输入 |
密码输入 |
期望结果 |
| (1) |
15546219225 |
1244566 |
提示“用户名或者密码错误，或账号未经审核” |
| (2) |
aaaaa |
123456 |
提示“用户名或密码错误，或者账号未经审核” |
| (3) |
15546219225 |
hangguowei |
登陆成功 |
6.4系统分析
本银行账目管理平台的设计要求基本都可以达到，此系统具有完整的软件功能，良好的用户界面，能够正确的处理错误信息，而且能够准确的提出错误的种类。但是系统测试时也出现了一些系统的不足和缺陷，所以在今后的日子里我会对其视觉上的不足作出修改，其次系统的代码和数据库出现了非常多的冗余现象，都是因为对编程技术的应用不够熟练，在日后我会加强自己的自身学习和能力，减少这样的冗余现象。
经过对上述的测试结果分析，本银行账目管理平台无论是在技术方面，还是操作方面，还是经济方面都是完全可以实行的，并且经过测试，该系统操作简单，所有的功能都可以实现，因此该系统可以满足人们的使用需求，值得被推广。
7 结论
通过银行账目管理平台的开发，本人巩固了之前学过的知识，如今将平时所学到的知识融合在设计中，在设计过程中，做了很多的准备，首先，在数据库系统的设计过程中，尤其是在数据库的工作原理、工作特点，对其深刻的讨论，与此同时，对于小型站点来说，最好服务器的选择，其次，利用所学的知识点分析所做的系统，并在此基础上设计。
目前本系统已经上线，正在试运行阶段，用户反馈良好，基本完成用户所需，试运行过程中没有出现阻断性问题，有一些不足和小问题也及时予以修正，系统上线后，为了保证数据的安全性，对系统进行了备份操作，系统备份是每两个月备份一次，数据库备份为每周备份一次，系统部署在租赁的云平台服务器中。
本次系统上线成功后，得到了用户的高度认可，但是在功能上和性能上还需做进一步的研究处理，使其有更高的性能和更好的用户体验。
系统在以后的升级过程中，需要解决一系列用户所提出的问题，例如打印过程中如何避免浏览器的兼容性问题，大量用户访问时，如何保持较高的响应速度，在系统今后的升级过程中将着重解决这些安全性问题。
参考文献
[1]张一鸣.基于Java语言的基础编程平台设计[J].集成电路应用,2023,40(02):254-255.DOI:10.19339/j.issn.1674-2583.2023.02.116.
[2]梁会成,王黎光.基于JSP+SSM在线领养猫咪系统的设计与实现[J].电子制作,2022,30(24):59-62+45.DOI:10.16589/j.cnki.cn11-3571/tn.2022.24.018.
[3]费东阳,王艳丽,王蒙恩,张书宁,孙智慧,张学良.基于JSP计算网络时延的实现[J].电脑知识与技术,2022,18(33):71-73.DOI:10.14004/j.cnki.ckt.2022.2116.
[4]李乐.Java语言应用研究[J].智慧中国,2022(09):80-81.
[5]杨晓波,李颖,魏子睿.基于JSP技术的高压客户业扩报装系统[J].自动化技术与应用,2022,41(09):79-82.DOI:10.20033/j.1003-7241.(2022)09-0079-04.
[6]郑戟明,董云朝,柳青.MySQL数据库数据导入导出方法的探讨[J].电脑知识与技术,2022,18(22):24-25.DOI:10.14004/j.cnki.ckt.2022.1517.
[7]宋旸.使用Java语言开发Web应用软件的知识探讨[J].中国设备工程,2022(14):121-123.
[8]狄丹. 基于MySQL协议的数据库运维代理的设计与实现[D].华北电力大学(北京),2022.DOI:10.27140/d.cnki.ghbbu.2022.001173.
[9]彭婷.基于SSM框架的客户关系管理系统的设计与实现[J].信息与电脑(理论版),2022,34(08):137-139.
[10]杨迎.Java语言异常处理机制的分析[J].电子技术,2022,51(03):42-43.
[11]曹嵩彭,王鹏宇.浅析Java语言在软件开发中的应用[J].信息记录材料,2022,23(03):114-116.DOI:10.16009/j.cnki.cn13-1295/tq.2022.03.009.
[12]刘肖. 基于JSP+MySQL的供电管理系统的设计与实现[D].电子科技大学,2021.DOI:10.27005/d.cnki.gdzku.2021.002912.
[13]. Information Technology - Data Management; Data on Data Management Reported by Researchers at Port Said University (Performance Evaluation of Iot Data Management Using Mongodb Versus Mysql Databases In Different Cloud Environments)[J]. Computer Technology Journal,2020.
[14]张猛. MySQL融合式空间数据库扩展研究与应用[D].中国地质大学(北京),2020.DOI:10.27493/d.cnki.gzdzy.2020.000758.
[15]. Design and Implementation of ERP System Based on SSM Framework[J]. ,2020,440(5).
[16]李雨金. 基于MySQL的数据库[D].南京大学,2019.DOI:10.27235/d.cnki.gnjiu.2019.002083.
[17]Fontaine Rafamantanantsoa,Paulson Ravomampiandra. Analysis and Simulink Modeling of the Performance of Dynamic Web Server Using JSP and PHP[J]. Communications and Network,2018,10(4).
[18]刘嘉鹏,王斌,王刚.基于Z/OS系统的银行账目管理系统的设计与实现[J].中国管理信息化,2017,20(08):39-40.
[19]常龙. 银行账目管理信息系统的设计与实现[D].厦门大学,2014.
[20]顾赟. 交通银行账目管理信息系统的设计与实现[D].电子科技大学,2013.
致谢
本次毕业设计圆满的结束了，通过这次毕业设计我学到了很多的知识，也提高了我软件开发的能力，在系统开发设计的过程中，出现了很多的问题，但是通过老师和同学们的帮助，最后所有的问题都得到了解决，因此我要感谢在此过程中对我帮助的老师和同学们，感谢指导老师帮助我选课题，给我做详细的讲解，给我提供设计所需要的各种设备，也经常询问我进度与成果，再有难点的时候给我解决思路，帮助我顺利完成。没有他的指导，也不会有我今天所展现出的成果。
首先我要感谢我的指导老师，指导老师在教学任务繁忙的情况下，抽出时间帮助我纠正我在设计当中出现的问题，并耐性地为我的论文作校正，是他的定期检查和指导使得我们的毕业设计高质量完成。他在我整个课题开发和设计的过程中，为程序的设计、框架的设计、代码的撰写方面以及论文框架的设计提供了很多宝贵的意见，并且为我推荐了许多有用的资料和文献，他的指导和建议使我受益匪浅，有了指导老师的辅导和指点，我论文才能够顺利完成。老师的认真负责的工作态度和治学严谨之道使我们这些即将踏入社会的毕业生受益匪浅。
然后要感谢我的同学们，感谢大家对我这次毕业设计的帮助， 也感谢大家在大学生活中对我的陪伴，使得我的大学生活过的很快乐。
另外，我还要感谢父母，感谢一直以来对我的支持，让我能够顺利的完成我的学业，没有你们也就没有我的今天，感谢你们无私的付出，未来我一定会报答你们的。
最后，感谢在座的所有参加我论文答辩的老师们，感谢大家的聆听，你们辛苦了。
请关注点赞+私信博主，免费领取项目源码