Design and implementation of bank account management system
Summary
Nowadays, people are increasingly aware of the need to improve account management, hoping to reduce costs, improve business process efficiency, make offices paperless, and no longer require manual intervention to reduce personnel error rates. As far as the current situation is concerned, banking companies lack an account management system that supports the next generation of new standards to help financial personnel complete account maintenance work efficiently. The bank account management system aims to solve the deficiencies of the old system in managing accounts through the application of new technical means and new management concepts, and has positive significance for the development of bank account management in my country. This not only provides convenience to the masses, but also brings more visibility to ourselves. If the bank has its own system, it can better manage users' account information and also improve the bank's image.
The design of this system aims to meet the needs of administrators and users. It conducts in-depth analysis from the aspects of requirements, structure, database, etc., and aims at implementation, demonstrating the completeness and feasibility of the design process through description, analysis, and experiments. sex. Based on the actual situation, we determined a practical development plan, using technologies such as Java programming language and MySQL database to realize all functions of the operating system, and rigorously tested it to ensure that the operating system has no loopholes and also tested user permissions, finally bringing the operating system up to expected standards. The system is divided into user terminal and administrator terminal. The user terminal has functions such as uploading personal information, viewing financial products, online lending, viewing loan review, online repayment and managing bank cards. The back-end administrator has functions such as user management, credit rating management, financial product uploading, loan information management, and system management.
Keywords: bank account management, Java, MySQL
1.3 Research plan
The system adopts the B/S architecture model and concentrates the core part of the system function implementation on the server. The browser uses the Tomcat server to interact with the database through the Web Server. When developing the system, IDEA is used as a development tool to define various classes and Methods are used to write business logic and connect to the database. The Java language and MySQL database are used to design this system, and the Java spring boot framework is used for development. In order to realize the separation of front and backend, the system adopts the MVC design concept and divides the backend structural design of the entire bank account management system into three layers: presentation layer, business logic layer and data persistence layer. The Spring Boot framework used in the coding process can greatly reduce the difficulty of development. Combined with the HTML, CSS style web interface and JavaScript and the dynamic effects of JQuery and AJAX it contains, the page is designed to layout the page and implement animation response effects. At the same time, the Ajax code is used to interact with the backend, and the bank account management is generally simulated. system . There are two types of roles designed in the system: user and administrator.
1.4 Summary of this chapter
The full text is divided into seven chapters.
The first chapter is the introduction, which mainly introduces the research background of this topic. First, it analyzes the development status of domestic and foreign bank account management systems . Next, it explains the main content of the research on this topic, and briefly describes the research significance of the topic.
Chapter 2 mainly describes the relevant tools and technologies used to develop the system, including a brief introduction to the Java development language, springboot framework, and MySQL database.
Chapter 3 is about system demand analysis, including system functional demand analysis and non-functional demand analysis, system data flow diagram, feasibility analysis, etc.
Chapter 4 is system design. This chapter mainly describes and explains the system structure design, functional module design and database in detail.
Chapter 5 is the implementation of the system. Through the display of results diagrams, key code displays and text descriptions, the implementation process of the main functional modules in the system is described in detail, and the difficult issues in the system implementation process are described.
Chapter 6 is the testing of the system. It conducts black box testing on the main functional modules involved in the system and writes the relevant test case diagrams.
Chapter seven is summary and outlook. This chapter is a rough summary of this design, analyzes the main functions implemented by the system, and finally gives a brief explanation of the focus of the next step based on the shortcomings in the current system.
2.2 System function analysis
After the system overview part, we have a general understanding of the functions that the system needs to have. The ultimate goal of the requirements analysis is to determine the functions that the system needs to have. After preliminary market research and background understanding, we have a rough understanding of the functions that the system needs to have. Have a clear understanding of the functions that the system needs to have. The specific functions are as follows.
The functions required by this system are roughly as follows:
user
1. Register, upload personal information, and modify personal information after logging in, including username, name, gender, mobile phone, and credit rating
2. Bank card management, add, modify and delete bank card information
3. Financial product management, view financial product information, including product number, product name, investment type, sale time, annual return, risk level, issuing institution, etc.
4. Financial instrument management, view financial instrument information, borrow and repay
5. Loan information management, check loan information, review status
6. Repayment information management, check repayment information
administrator
1. User management, add, modify and delete user information
2. Bank card management, add, modify and delete bank card information, including bank card number, type, bank, name, card issuance date, code
3. Credit rating, add, modify and delete credit rating information
4. Financial product management, add, modify and delete financial products, including product number, product name, investment type, sale time, annual return, risk level, issuing institution, etc.
5. Financial instrument management, view product number, name, type, amount, etc., can be modified and deleted
6. Loan information management, view user loan information, review loan information, can modify and delete
7. Repayment information management, view user repayment information, which can be modified or deleted
2.5.5 Personal information management use cases
The use case description of the personal information management function is shown in Table 2-7.
Table 2-7 Personal information management use case description
| use case entry |
describe |
| Use case name |
Personal information management |
| Main business participants |
user |
| other participants |
none |
| describe |
Users view and modify personal information |
| Preconditions |
User completes login |
| Postcondition |
View and modify personal information |
| basic event flow |
1Enter modification information 2 The system checks the basic information 3 Return the modification results |
| alternative event flow |
1a When modifying the user name and password to be empty, the prompt cannot be empty. 2a A prompt box will pop up when the necessary information is empty. 3a If the modification is successful, the information will be returned to the page. |
3.2 Overall functional structure diagram of the system
Based on the analysis of each function of the system, design the overall functional structure diagram of the system.
The functional structure diagram of the bank account management system is shown in Figure 3.2 .
Figure 3.2 System functional structure diagram
The user login interface is shown in Figure 4.13.
Figure 4.13 User login interface
4.3.2 Bank card management
When users enter the bank card management interface, they can view bank card information including bank card number, type, bank to which they belong, name, card issuance date, serial number, etc., as shown in Figure 4.14.
Figure 4.14 Bank card management interface
Figure 4.20 Administrator login interface
1.1 Background and purpose of the study
1.2 Development status at home and abroad
1.2.1 Domestic development status
1.2.2 Foreign development status
2.1 Analysis of social reality
2.4 System requirements analysis
2.4.1 Determine business participants
2.5 Use case description of each module
2.5.3 Bank card management use cases
2.5.4 Financial product display use cases
2.5.5 Personal information management use cases
2.5.6 View repayment information use case
3.1 Overall system structure diagram
3.2 Overall functional structure diagram of the system
3.3.1 Database conceptual structure design
3.3.2 System database table design
4 System detailed design and implementation
4.1 Detailed design of system functions
4.1.5 Financial product search
4.1.6 Financial product information management
4.2.1 User registration collaboration diagram
4.2.2 Financial product search collaboration diagram
4.2.3 Repayment collaboration diagram
4.2.4 Collaboration diagram for listing financial products
4.3.5 Modification of personal information
4.3.7 Administrator user management
4.3.8 Financial product information management
4.3.9 Financial instrument management
4.3.9 Credit rating management
5.1.1 User registration function test
5.1.2 User login function test
5.1.3 Upload personal information function test
5.1.4 Modify personal information function test
5.1.5 Upload financial product function test
5.1.6 Repayment information function test
5.1.7 Test environment assessment