ssm love donation material maintenance system
With the rapid development of information technology, computer applications have entered thousands of families. As the quantity of materials increases, there are also many problems in material inventory management. The amount of material data processed is increasing rapidly, and the original manual management model is not suitable for this form. The use of computers can complete data collection, processing and analysis, reducing the waste of manpower and material resources. It is necessary to establish a love donation material maintenance system to provide information management and dynamic management for material management and improve the quality and efficiency of material management.
In the design of the love donation material maintenance system, the Java programming language and SSM technology are used, under the MVVM mode, and MySQL is used as the database of the system. The system is designed with powerful functional modules, taking into account all aspects of material management. These main functional modules are the home page, system user (administrator, registered user) module management (material warehouse, material type, material warehousing, material application, warehouse confirmation, material application, user signature, detailed announcement) and other functions module. Finally, through system requirements analysis and system design method verification, the results show that the design has practical value, so from the perspective of software design, the research theory, foundation, overall system layout and specific system design are studied in detail.
Keywords: java programming language; SSM technology; software design
Ssm caring donation material maintenance system Events
ABSTRACT
With the rapid development of information technology, computer applications have entered thousands of households. With the increase of material quantity, there are many problems in material inventory management. The processing volume of material data is rapidly increasing, and the original manual management mode is not suitable for this form. Using computers can complete data collection, processing, and analysis, reducing the waste of human and material resources. It is necessary to establish a caring donation material maintenance system to provide information management and dynamic management for material management, and improve the quality and efficiency of material management.
In the design of the charity donation material maintenance system, the Java programming language and SSM technology are used, under the MVVM mode, and MySQL is used as the system database. The system has designed powerful functional modules that take into account all aspects of material management. These main functional modules are the home page, system user (administrator, registered user) module management (material warehouse, material type, material warehousing, applying for materials, confirming outbound delivery, applying for materials, user signing in, detailed announcement), and other functional modules. Finally, through system requirements analysis and system design method validation, the results show that the design has practical value. Therefore, from the perspective of software design, the research theory, foundation, overall system layout, and specific system design were studied in detail.
Key words: Java programming language; SSM technology; software design
Table of contents
1.1 Development background and significance
1.2 Research status at home and abroad
1.3 The structure of the thesis
Chapter 2 Introduction to Development Tools and Related Technologies
2.3 Introduction to MVVM pattern
2.4.2 Introduction to ssm framework
4.1 Principles of system design
4.3.2 Logical structure design
Chapter 5 System Implementation
5.1 Implementation of user management function module
5.2 Implementation of user management function module
5.3 Implementation of material management function module
Chapter 1 Introduction
1.1 Development background and significance
With the development of the market economy, market competition pressure has increased. To survive and develop, charity donations must strengthen management in all aspects, and require higher information integration of charity donations to enable integrated management of the overall resources of charity donations. . The competition among charity donations is a competition of comprehensive strength, which requires charity donations to have stronger financial strength and faster market response speed. This requires unified planning among various departments of charity donation, coordination of production steps, summary of information, and realization of resource sharing management that is both independent and unified. With the development of information technology, in order to improve the management efficiency of charity donation warehouse management and speed up the operation of charity donation pipes, it was decided to develop a "love donation material maintenance system".
1.2 Research status at home and abroad
Maintaining the donation system is a complex and necessary task. Supervisors need to process large amounts of documents and data every day. In order to settle each business account in a timely manner, check the inventory quantity and the entry and exit of goods, and ensure normal operations and property safety, managers need to spend a lot of manpower, material resources and time to record data and make statistics.
In developed countries, the level of computerized inventory management is very high, and the automated management model has been realized. Although there is strong domestic awareness and great progress in this regard, including material management, there are still some problems in management. In some, inventory management remains manual and semi-manual. From the beginning of material purchase registration to the end of material delivery, all operations are basically recorded in writing. Inventory management is written by inventory managers and statistics are done using calculators. This method not only has complex management and low efficiency, but also lacks some basic inventory management tools, such as inventory status statistics, query calculation of economic order quantity, etc. This has also led to backward management, backward competition and loss of economic benefits to a certain extent.
1. 3 Thesis structure
The paper is divided into six chapters: the introduction introduces the research background and significance, the second chapter mainly introduces the related technologies used and the development methods used, the third chapter describes the preliminary investigation and analysis, and the fourth chapter is the systematic Functional and other design, Chapter 5 is mainly about the implementation process and key codes of the entire system, and the last chapter is about the system testing methods and the recording and description of the test results.
Chapter 2 Introduction to Development Tools and Related Technologies
The development environment mainly includes the following types:
1. Operating system: Microsoft Windows10Pro1709;
2. Development tools: Pycharm;
3. Server: Tomcat7.0;
4. Database: MySQL5.6, MySQL For Navicat (visual interface management client)
2.2 Operating system
Windows 10 and Windows Beyond Regarding Windows 10, Microsoft announced that it will update Windows at a faster pace than before, and there will be no official "Windows 11"; instead, Windows Update (or another servicing model) will update existing Windows 10 for the new version. At the time of writing, there have been two such updates, in November 2015 (also known as version 1511, referring to the year and month of service) and in July 2016 (version 1607, also known by the marketing name of the Anniversary Update ) [5] .
Windows 10 and "One Kernel" Several different types of Windows have evolved over the years. In addition to mainstream Windows running on PCs, there is the Xbox 360 game console, which runs a fork of Windows 2000. Windows Phone 7 is based on a variant of Windows CE (Microsoft's real-time operating system) [6] . Maintaining and extending all these code bases is obviously difficult. Therefore, Microsoft decided to aggregate the kernel and base platform supported binaries into one. This started with Windows 8 and Windows Phone 8, where the kernel was shared (Windows 8.1 and Windows Phone 8.1 had a converged Windows Runtime API). With Windows 10, the convergence is complete. This shared platform is called Onecore and it runs on PCs, phones, Xbox One game consoles, holographic screens, and Internet of Things (IoT) devices such as the Raspberry Pi2 [7 ] .
2.3 Introduction to MVVM pattern
MVVM is the abbreviation of Model-View-ViewModel. It is essentially an improved version of MVC. MVVM abstracts the state and behavior of the View, allowing us to separate the view UI and business logic. Of course, ViewModel has already done these things for us. It can take out the data of the Model and help handle the business logic involved in the View due to the need to display content. Microsoft's WPF brings new technical experiences, such as Silverlight, audio , video , 3D , animation ..., which results in the software UI layer being more detailed and customizable. At the same time, at the technical level, WPF also brings new features such as Binding, Dependency Property, Routed Events, Command, DataTemplate, ControlTemplate and so on. The origin of the MVVM (Model-View-ViewModel) framework is a new architectural framework that evolved from the application method of combining the MVP (Model-View-Presenter) pattern with WPF . It is based on the original MVP framework and incorporates the new features of WPF to cope with increasingly complex changes in customer needs.
The love donation material maintenance system is written using the MVC model. MVC in English is Model-View-Controller, which separates the input, processing, and output processes of an application according to Model, View, and Controller. In this way, an application is divided into three layers, namely, model layer, view layer, and control layer [ 11] .
View represents the user interaction interface. In a Web application, it can be said to be an HTML interface, which may also include XML, XHTML, or Applet, etc. As technology and needs develop, the complexity and scale of Web applications are also increasing, so the difficulty of processing is also increasing. A Web application may have many interfaces. In the MVC model, the view only handles data collection and processing, as well as user requests, and does not include the processing of business processes. Business processes are handled by the model (Model).
Model is the processing of business processes/states and the formulation of business rules. The process of the model processing the business process cannot be seen by other layers. It is like a black box. After accepting the data requested by the view, it then returns the final processing result. The main core of MVC is the design of the business model. A typical application example is the currently popular EJB model, which further divides the model from the perspective of application technology implementation in order to make full use of existing components, but it cannot be used as A framework for applying design models.
The controller can be understood as receiving the user's request, and then the view and model are matched together to complete the user's request. It has a very obvious role in dividing the control layer. It can clearly tell you that it is a distributor, what kind of model and view can be selected, and what kind of user's request can be completed. The control layer does not do all data processing. For example, if the user clicks a connection, after the control layer receives the request, it does not process the business information. It only transmits the user's information to the model, tells the model what to do, and then selects the one that meets the needs. The view is returned to the user [12][13] .
2.4.2 Introduction to ssm framework
The SSM (Spring+SpringMVC+MyBatis) framework set is integrated by the two open source frameworks Spring and MyBatis (SpringMVC is part of Spring). It is often used as a framework for web projects with relatively simple data sources.
1.6.1 Spring
Spring is like a big factory that assembles beans in the entire project. In the configuration file, you can specify the use of specific parameters to call the constructor method of the entity class to instantiate the object. It can also be called the glue in the project.
The core idea of Spring is IoC (Inversion of Control), which means that programmers no longer need to explicitly `new` an object, but let the Spring framework do it all for you.
1.6.2 SpringMVC
SpringMVC intercepts user requests in the project. Its core Servlet, DispatcherServlet, assumes the responsibilities of intermediary or front desk, and matches user requests to the Controller through HandlerMapping. The Controller is the specific operation performed in response to the request. SpringMVC is equivalent to struts in the SSH framework.
1.6.3 mybatis
mybatis is an encapsulation of jdbc, which makes the underlying operations of the database transparent. The operations of mybatis are centered around a sqlSessionFactory instance. Mybatis is associated to the Mapper file of each entity class through the configuration file. The Mapper file is configured with the SQL statement mapping required for each class to the database. Every time you interact with the database, get a sqlSession through sqlSessionFactory, and then execute the sql command.
The page sends a request to the controller, the controller calls the business layer processing logic, the logic layer sends a request to the persistence layer, the persistence layer interacts with the database, and then returns the result to the business layer, the business layer sends the processing logic to the controller, and the controller then Call the view to display the data.
Feasibility analysis is an important part of the early stage evaluation of project development. It is usually carried out at the beginning of project development and mainly analyzes whether the project development is feasible from multiple perspectives.
The economic feasibility analysis mainly considers the costs involved in the system development process. From an all-round perspective, the costs mainly involve human capital costs, related equipment costs, and maintenance costs. The overall scale of this system development is relatively small, and the costs involved are low and affordable for individuals. For this reason, economic feasibility analysis is also feasible.
Technical feasibility analysis mainly predicts whether the actual development of the system is possible by judging the existing technology. It is the most critical link in the entire analysis process and determines the actual success rate of the system. Therefore, a detailed analysis of the technical feasibility of the system was conducted. First of all, the system uses SSM development technology. This technology is relatively comprehensive, widely practical, and has no functional requirements that cannot be realized. Secondly, the database uses MySQL as the data storage. This kind of database is extremely stable and is also a practical database for the public. ; Finally, the development tool uses Pycharm, which has framework functions, etc., which can be directly quoted; through more than three years of study and practice, I have become proficient in the use of this system and have a certain understanding of the corresponding technology types. , the main language used is java.
This system is operated using a Web browser, and the browser is a familiar browsing method. The Web browser is mainly used to implement client requests and manage server port components, process database data, and return results. The database is established to organize and store data, thereby ensuring the integrity of the data. Once relevant operations on the data are required, the work will become easier and the workload will be reduced. All operations are controlled by the system itself. It liberates productivity and speeds up work efficiency while also reducing the error rate and ensuring the stability of the system. In order to make the overall operation easier and more convenient, this system uses JS dynamic interaction technology. The operator does not need to understand the relevant database and other information during the operation, ensuring the security of the core data. The entire system is a visual operation that can be completed by clicking the mouse and does not require much data processing. Therefore, the operational feasibility is feasible.
Through the above analysis, it can be determined that the system has the value and possibility of actual development.
Through the investigation and understanding of user needs, the main functions provided by the system are as follows:
1. Basic information management of administrator accounts. It mainly provides basic information entry, deletion, maintenance and query functions for administrator accounts, including:
The administrator enters the basic information of the administrator account;
The administrator updates, adds and deletes the basic information of the administrator account;
Users query basic information based on the administrator account ID;
System administrator changes personal password;
2. Basic information management of users. It mainly provides users with basic information entry, deletion, maintenance and query functions, including:
The administrator enters basic user information;
Administrators update, add and delete basic user information;
The administrator queries basic information based on user ID;
User User changes personal password;
3. Basic information management of materials. Mainly provides basic information entry, modification and query functions for materials, including:
The administrator enters basic material information;
Administrators update, add and delete basic material information;
The administrator queries basic information based on the material ID;
4. Basic information management of warehouse. It mainly provides basic information entry, maintenance and query functions for the warehouse, including:
The administrator enters the basic information of the warehouse;
Administrators update, add and delete basic warehouse information;
The administrator queries the basic information of the warehouse based on the warehouse ID;
5. Basic information management of warehousing. It mainly provides basic information entry, deletion, maintenance and query functions for warehousing, including:
The administrator enters material storage information;
The administrator updates and adds basic information on material storage;
The administrator queries the basic information of material storage according to the material ID;
Users can query personal storage information according to the personal information navigation bar;
6. Basic information management of outbound shipments. It mainly provides basic information entry, deletion, maintenance and query functions for outgoing warehouses, including:
The administrator enters the material outbound information;
The administrator updates and adds basic information on material delivery;
The administrator can query the basic information of materials out of the warehouse based on the material ID;
Users can query personal outbound information based on the personal information navigation bar;
The main components of the love donation material maintenance system are divided into two parts, one is the warehousing management operation of materials, and the other is the material outgoing management operation. Around these two parts, all functions of the love donation material maintenance system will be launched. As described in the traditional business process diagram in the figure below, the operator performs warehousing and then classification and summary. When the material inventory meets the requirements, normal outbound processing is carried out; when the material inventory is lower than the outbound amount, a shortage form is filled in to put the materials into storage, thus carrying out the normal inventory management business process in a traditional scale.
The system business flow chart is shown below.
Figure 3-1 System business flow chart
1. Data Flow Diagram Layer 0 The data flow diagram at Layer 0 is composed of ordinary users, administrators, and the donation maintenance system. Users can provide inbound information, outbound information, and distribution information to the system; administrators can provide inbound information to the system. Library information, statistical information, material information; the administrator passes the material information to the system, and the system will provide the material information to the user.
The data flow diagram layer 0 of this system is shown in the figure below.
Figure 3-2 Layer 0 data flow diagram of the system
2. The administrator at layer 1 of the data flow diagram can manage the inventory, generate an inventory information table, transfer the inventory information to material information management, generate a material information table, and then transfer the material information to statistical management, perform statistics on the information, and also compile statistics The information is passed to the administrator, and users can also view material inventory information through material information management.
The data flow diagram of the system at layer 1 is shown in the figure below.
Figure 3-3 System layer 1 data flow diagram
3. Inventory management data flow diagram Layer 2 administrator can manage the warehousing and generate the warehousing information table. The material information table can also provide information to the warehousing management. The warehousing information table can pass the information to the outbound management. The administrator can handle the outbound management. The warehouse is managed and an outbound information table is generated. The inventory management decomposition 2-layer data flow diagram is shown in the figure below.
Figure 3-4 Inventory management decomposition 2-layer data flow diagram
4.1 Principles of system design
System design principles include:
- Modular. Modularization means dividing the entire program into multiple modules, each module has its own name and can be accessed independently. The functions of all modules can be combined to meet user needs.
- abstract. Abstraction is to temporarily ignore the details of the software and concentrate on extracting the essential features of the software.
- Gradually refine. The overall design needs to solve the main problems first, and then refine the problems step by step.
- Localization and information hiding. Information between different modules cannot be accessed from each other; and closely related software elements should be placed at similar physical addresses.
- Modules are independent. Modules should follow the principles of high cohesion and low coupling.
From the perspective of practical application, the love donation material maintenance system can be divided into three major modules: user management module, system module, and main function module.
1. The system user management module can be divided into user management, personal information management and rights management modules. User management is the process of checking, modifying, deleting and other operations related to users. Personal information management can add, modify, delete, modify and query personal information.
2. The main functional management module includes home page and module management (material warehouse, material application, warehouse confirmation, user signature, detailed announcement).
3. System management module The system management module is divided into data backup.
The functional module diagram of the system is shown in the figure below.
Figure 4-1 System functional structure diagram
4.3 Database design
Database design (DatabaseDesign) refers to constructing a good database model and establishing a database system for a given environment so that it can store data most effectively and meet the needs of various users, that is, processing requirements and information requirements. Within the scope of database applications, systems that use databases are often called database application systems.
4. 3.1 Concept model design
The ER design method is a DB design method that describes the real-world information structure through ER diagrams. The ER diagram consists of three parts: entities, attributes, and relationships. It has two advantages: it is close to human thinking and easy to understand; it has nothing to do with computers and is easy for users to accept.
The ER diagram of the relationship between the main entities of the system is shown in the figure below:
Figure 4-2 System ER Diagram
Certain relationships can be established between entities, which can be roughly divided into three types: (1) one-to-one relationships between entities, which can be independent or combined with others; (2) one-to-many relationships between entities, where entities are An n-terminal entity is contacted; (3) There is a many-to-many relationship between entities, and there is a certain relationship between the two entities. The attributes of each entity code are relationship attributes, and the combination of entity codes is the relationship code.
Based on the above principles, the graph can be converted into a relational model.
Material information table: {material name, classification, number of pictures, warehouse location}; warehouse-in information table: {material number, name, classification, warehouse-in date, quantity, remarks, account number, name}; warehouse-out information table: {materials Number, name, classification, delivery date, quantity, remarks, account name}; distribution information table: {warehouse name, material name, material quantity, branch warehouse name, deployment date, account number, name}.
4.3.2 Logic structure design
According to the ER model, the love donation material maintenance system has established the following logical data structure. The following is a detailed description of each data table.
Table access_token (login access duration)
| serial number |
name |
type of data |
length |
Decimal places |
Allow null values |
primary key |
Defaults |
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 apply_for_materials (apply for materials)
| serial number |
name |
type of data |
length |
Decimal places |
Allow null values |
primary key |
Defaults |
illustrate |
| 1 |
apply_for_materials_id |
int |
10 |
0 |
N |
Y |
Apply for material ID |
|
| 2 |
application_no |
varchar |
64 |
0 |
Y |
N |
Application number |
|
| 3 |
item_no |
varchar |
64 |
0 |
Y |
N |
Material serial number |
|
| 4 |
item_name |
varchar |
64 |
0 |
Y |
N |
Material name |
|
| 5 |
material_type |
varchar |
64 |
0 |
Y |
N |
Material type |
|
| 6 |
material_specifications |
varchar |
64 |
0 |
Y |
N |
Material specifications |
|
| 7 |
material_unit |
varchar |
64 |
0 |
Y |
N |
material unit |
|
| 8 |
ordinary_users |
int |
10 |
0 |
Y |
N |
0 |
general user |
| 9 |
user_name |
varchar |
64 |
0 |
Y |
N |
username |
|
| 10 |
application_quantity |
int |
10 |
0 |
Y |
N |
0 |
Quantity claimed |
| 11 |
application_date |
date |
10 |
0 |
Y |
N |
Claim date |
|
| 12 |
reason_for_application |
longtext |
2147483647 |
0 |
Y |
N |
Reason for claim |
|
| 13 |
examine_state |
varchar |
16 |
0 |
N |
N |
Not reviewed |
Approval Status |
| 14 |
examine_reply |
varchar |
16 |
0 |
Y |
N |
moderation reply |
|
| 15 |
recommend |
int |
10 |
0 |
N |
N |
0 |
Intelligent Recommendation |
| 16 |
create_time |
datetime |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
creation time |
| 17 |
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 |
Defaults |
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 confirm_delivery (confirm delivery)
| serial number |
name |
type of data |
length |
Decimal places |
Allow null values |
primary key |
Defaults |
illustrate |
| 1 |
confirm_delivery_id |
int |
10 |
0 |
N |
Y |
Confirm delivery ID |
|
| 2 |
application_no |
varchar |
64 |
0 |
N |
N |
Application number |
|
| 3 |
item_no |
varchar |
64 |
0 |
Y |
N |
Material serial number |
|
| 4 |
item_name |
varchar |
64 |
0 |
Y |
N |
Material name |
|
| 5 |
material_type |
varchar |
64 |
0 |
Y |
N |
Material type |
|
| 6 |
material_specifications |
varchar |
64 |
0 |
Y |
N |
Material specifications |
|
| 7 |
material_unit |
varchar |
64 |
0 |
Y |
N |
material unit |
|
| 8 |
ordinary_users |
int |
10 |
0 |
Y |
N |
0 |
general user |
| 9 |
user_name |
varchar |
64 |
0 |
Y |
N |
username |
|
| 10 |
application_quantity |
int |
10 |
0 |
Y |
N |
0 |
Quantity claimed |
| 11 |
application_date |
date |
10 |
0 |
Y |
N |
Claim date |
|
| 12 |
recommend |
int |
10 |
0 |
N |
N |
0 |
Intelligent Recommendation |
| 13 |
create_time |
datetime |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
creation time |
| 14 |
update_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
Update time |
Table detailed_announcement (detailed announcement)
| serial number |
name |
type of data |
length |
Decimal places |
Allow null values |
primary key |
Defaults |
illustrate |
| 1 |
detailed_announcement_id |
int |
10 |
0 |
N |
Y |
Detailed announcement ID |
|
| 2 |
application_no |
varchar |
64 |
0 |
N |
N |
Application number |
|
| 3 |
item_no |
varchar |
64 |
0 |
Y |
N |
Material serial number |
|
| 4 |
item_name |
varchar |
64 |
0 |
Y |
N |
Material name |
|
| 5 |
material_type |
varchar |
64 |
0 |
Y |
N |
Material type |
|
| 6 |
material_specifications |
varchar |
64 |
0 |
Y |
N |
Material specifications |
|
| 7 |
material_unit |
varchar |
64 |
0 |
Y |
N |
material unit |
|
| 8 |
user_name |
varchar |
64 |
0 |
Y |
N |
username |
|
| 9 |
application_quantity |
int |
10 |
0 |
Y |
N |
0 |
Quantity claimed |
| 10 |
date_of_publication |
date |
10 |
0 |
Y |
N |
公布日期 |
|
| 11 |
announcement_content |
longtext |
2147483647 |
0 |
Y |
N |
公布内容 |
|
| 12 |
recommend |
int |
10 |
0 |
N |
N |
0 |
智能推荐 |
| 13 |
create_time |
datetime |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
创建时间 |
| 14 |
update_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
更新时间 |
| 编号 |
名称 |
数据类型 |
长度 |
小数位 |
允许空值 |
主键 |
默认值 |
说明 |
| 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： |
| 编号 |
名称 |
数据类型 |
长度 |
小数位 |
允许空值 |
主键 |
默认值 |
说明 |
| 1 |
material_type_id |
int |
10 |
0 |
N |
Y |
物资类型ID |
|
| 2 |
material_type |
varchar |
64 |
0 |
Y |
N |
物资类型 |
|
| 3 |
recommend |
int |
10 |
0 |
N |
N |
0 |
智能推荐 |
| 4 |
create_time |
datetime |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
创建时间 |
| 5 |
update_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
更新时间 |
| 编号 |
名称 |
数据类型 |
长度 |
小数位 |
允许空值 |
主键 |
默认值 |
说明 |
| 1 |
material_warehouse_id |
int |
10 |
0 |
N |
Y |
物资仓库ID |
|
| 2 |
item_no |
varchar |
64 |
0 |
Y |
N |
物资序号 |
|
| 3 |
item_name |
varchar |
64 |
0 |
Y |
N |
物资名称 |
|
| 4 |
material_type |
varchar |
64 |
0 |
Y |
N |
物资类型 |
|
| 5 |
material_specifications |
varchar |
64 |
0 |
Y |
N |
物资规格 |
|
| 6 |
material_unit |
varchar |
64 |
0 |
Y |
N |
物资单位 |
|
| 7 |
inventory_quantity |
int |
10 |
0 |
Y |
N |
0 |
库存数量 |
| 8 |
material_details |
longtext |
2147483647 |
0 |
Y |
N |
物资详情 |
|
| 9 |
recommend |
int |
10 |
0 |
N |
N |
0 |
智能推荐 |
| 10 |
create_time |
datetime |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
创建时间 |
| 11 |
update_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
更新时间 |
| 编号 |
名称 |
数据类型 |
长度 |
小数位 |
允许空值 |
主键 |
默认值 |
说明 |
| 1 |
material_warehousing_id |
int |
10 |
0 |
N |
Y |
物资入库ID |
|
| 2 |
warehousing_no |
varchar |
64 |
0 |
Y |
N |
入库号 |
|
| 3 |
item_no |
varchar |
64 |
0 |
Y |
N |
物资序号 |
|
| 4 |
item_name |
varchar |
64 |
0 |
Y |
N |
物资名称 |
|
| 5 |
material_type |
varchar |
64 |
0 |
Y |
N |
物资类型 |
|
| 6 |
material_specifications |
varchar |
64 |
0 |
Y |
N |
物资规格 |
|
| 7 |
material_unit |
varchar |
64 |
0 |
Y |
N |
物资单位 |
|
| 8 |
receipt_quantity |
int |
10 |
0 |
Y |
N |
0 |
入库数量 |
| 9 |
warehousing_date |
date |
10 |
0 |
Y |
N |
入库日期 |
|
| 10 |
recommend |
int |
10 |
0 |
N |
N |
0 |
智能推荐 |
| 11 |
create_time |
datetime |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
创建时间 |
| 12 |
update_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
更新时间 |
| 编号 |
名称 |
数据类型 |
长度 |
小数位 |
允许空值 |
主键 |
默认值 |
说明 |
| 1 |
ordinary_users_id |
int |
10 |
0 |
N |
Y |
普通用户ID |
|
| 2 |
user_name |
varchar |
64 |
0 |
Y |
N |
用户姓名 |
|
| 3 |
gender |
varchar |
64 |
0 |
Y |
N |
性别 |
|
| 4 |
examine_state |
varchar |
16 |
0 |
N |
N |
已通过 |
审核状态 |
| 5 |
recommend |
int |
10 |
0 |
N |
N |
0 |
智能推荐 |
| 6 |
user_id |
int |
10 |
0 |
N |
N |
0 |
用户ID |
| 7 |
create_time |
datetime |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
创建时间 |
| 8 |
update_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
更新时间 |
| 编号 |
名称 |
数据类型 |
长度 |
小数位 |
允许空值 |
主键 |
默认值 |
说明 |
| 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 |
文件类型 |
| 编号 |
名称 |
数据类型 |
长度 |
小数位 |
允许空值 |
主键 |
默认值 |
说明 |
| 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 |
创建时间： |
| 编号 |
名称 |
数据类型 |
长度 |
小数位 |
允许空值 |
主键 |
默认值 |
说明 |
| 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 |
更新时间： |
| 编号 |
名称 |
数据类型 |
长度 |
小数位 |
允许空值 |
主键 |
默认值 |
说明 |
| 1 |
user_sign_in_id |
int |
10 |
0 |
N |
Y |
用户签收ID |
|
| 2 |
application_no |
varchar |
64 |
0 |
N |
N |
申领号 |
|
| 3 |
item_no |
varchar |
64 |
0 |
Y |
N |
物资序号 |
|
| 4 |
item_name |
varchar |
64 |
0 |
Y |
N |
物资名称 |
|
| 5 |
material_type |
varchar |
64 |
0 |
Y |
N |
物资类型 |
|
| 6 |
material_specifications |
varchar |
64 |
0 |
Y |
N |
物资规格 |
|
| 7 |
material_unit |
varchar |
64 |
0 |
Y |
N |
物资单位 |
|
| 8 |
ordinary_users |
int |
10 |
0 |
Y |
N |
0 |
普通用户 |
| 9 |
user_name |
varchar |
64 |
0 |
Y |
N |
用户姓名 |
|
| 10 |
application_quantity |
int |
10 |
0 |
Y |
N |
0 |
申领数量 |
| 11 |
signing_date |
date |
10 |
0 |
Y |
N |
签收日期 |
|
| 12 |
remarks |
text |
65535 |
0 |
Y |
N |
备注 |
|
| 13 |
examine_state |
varchar |
16 |
0 |
N |
N |
未审核 |
审核状态 |
| 14 |
examine_reply |
varchar |
16 |
0 |
Y |
N |
审核回复 |
|
| 15 |
recommend |
int |
10 |
0 |
N |
N |
0 |
智能推荐 |
| 16 |
create_time |
datetime |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
创建时间 |
| 17 |
update_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
更新时间 |
1．登录模块，用户管理员可以通过登录进入该系统，如果输入正确，则可以进入该系统，显示的结果如下。
用户登录界面如下图所示。
图5-1登录模块界面
2．用户注册，某个人员进入该系统，则注册该用户的信息，如果注册成功，就可以进入该系统，显示的结果如下。
注册用户界面如下图所示。
图5-2注册用户界面
3．创建用户流程，首先获取用户的基本信息，然后将姓名转换为拼音做为用户名，默认密码是admin向数据库添加一条记录。
创建用户流程图如下图所示。
图5-3创建用户流程图
5.2用户管理功能模块实现
1．用户注册，审核用户注册信息，主要页面是yuangongxinxi_add.html文件，通过调用add()方法，将用户参数传入，实现用户信息的添加。
用户添加页面如下图所示。
图5-4用户添加页面
2．用户修改，管理员可以修改已存在的用户信息，除主键的ID不能修改外，其他属性基本都能修，主要页面是yuangongxinxi_update.html，通过调用update()方法，将用户参数传入，实现用户信息的修改。
3．用户查询，用户添加之后可以进行用户查询，输入用户编号可以查询出该用户的所有信息。包括用户编号、用户名称和电话。
4．用户删除，用对不需要的用户，或者输入错误的用户信息，管理员可以对其进删除，通过调用delete()方法，将用户参数传入，实现用户信息的删除。
5．用户添加流程，开始输入用户信息，在程序中验证输入的信息是否规范，如果规范就输入成功，如果不规范将重新进行输入。
用户添加流程图如下图所示。
图5-6用户添加流程图
1．物资添加，管理员添加物资信息，主要页面是wuzi_add.html文件，通过调用commDao类的add()方法，将物资参数传入，实现物资信息的添加。
物资添加页面如下图所示。
图5-7物资添加页面
2．物资修改，管理员可以修改已存在的物资信息，除主键的ID不能修改外，其他属性基本都能修改，主要页面是wuzi_update.html，通过调用commDao类的update()方法，将物资参数传入，实现物资信息的修改。
3．物资查询，物资添加之后可以进行物资查询，输入物资编号可以查询出该物资的所有信息。包括物资编号、物资名称、物资价格。
物资查询界面如下图所示。
图5-8物资查询页面
4．物资删除，对不需要的物资，或者输入错误的物资信息，管理员可以对其进删除，通过调用commDao类的delete()方法，将物资参数传入，实现物资信息的删除。
1．物资入库，如果管理员想进行物资入库，物资入库之前须要对物资进行登记，登记完之后进行物资入库，物资入库之后，生成入库记录，物资的当前库存量=入库前的数量加上入库数量，在库存在会显示入库的物资,，入库配送信息则将已入库的物资数量去除，则从库存数量减去配送信息数量得到库存总数量。
物资入库页面如下图所示。
图5-9物资入库页面
物资入库流程图如下图所示。
图5-10物资入库流程图
2．物资出库，和物资入库相反的是物资出库，物资的出库和出库上架都是对物资进行出库，物资出库之后，生成出库记录，物资的当前库存量=出库前的数量-出库数量，如果当前库存量小于出库量，则出库失败，物资出库配送信息则去除出库出去的物资，物资的库存量加上配送信息量得到物资现在的库存总量。
物资出库页面如下图所示。
图5-11物资出库页面
3．库存查询，用户点击该功能后，系统自动列出所有物资的信息和当前库存量，所有物资的总量进行计算。
物资查询界面如下图所示。
图5-12库存查询页面
4．用户签收信息页面可查看申请号、物资库号、申领数量、用户姓名、申领数量、物资名称、物资规格等信息进行增删改查等操作。
图5-13用户签收页面
6.1测试目的
测试的目的不仅要如何去组织测试，通过分析错误的产生原因以及结果，以便改进。在系统测试中，第一个目的就是检验系统在完成过程中的逻辑问题和系统可能存在的问题。然后通过测试修正原本的错误，提高系统的质量。第二个目的就是检测系统的安全性、可靠性也就是说系统的内容是不是安全的，会不会出现遗失等情况，系统是否能很好的正常的运行。
从爱心捐赠物资维护系统的实际情况来考虑，系统测试的根本就是：各项功能是否能够正常运行，不同的用户可以通过系统都做出哪些操作。能否对系统的数据进行调用，对表的增删改查操作，并且系统数据和数据库的数据是否一致。
6.2测试方法
一个业务模块应该由许多功能单元共同实现，黑盒测试针对业务功能是否能按计划完成，并且不考虑系统内部的结构和效率问题，白盒测试的要求就是要尽可能的测试到所有的组成结构，即要尽量包含所有的功能模块、覆盖全部路径。这种测试要求测试人员必须完全了解系统的业务逻辑及处理过程。但是完成上面的要求是一件很难的事，并且若程序中含有循环之后，路径的数量会越来越大，执行每一条路径都将会变得极不现实。
6.3测试过程
6.3.1系统测试计划
通过这个测试体现了此系统的功能比较完善，系统运行比较稳定，足以证明此系统具有安全性和完整性。测试计划进度表在测试之前用来计划测试目的于测试的范围，并且计划出测试的方法以及测试的时间。软件的质量是我们的追求，所以测试的过程是十分重要的，测试计划因此也成为了测试工作的基础。
系统测试计划如下表所示。
表6-1系统测试计划表
| 测试任务 |
工作描述 |
计划开始日期 |
计划结束日期 |
| 测试策划阶段 |
制定测试的计划、时间和预测效果 |
||
| 测试设计阶段 |
选定测试用例，回顾测试覆盖 |
||
| 测试实现阶段 |
开发测试用例/脚本 |
||
| 测试执行阶段 |
测试用例/脚本执行 |
||
| 测试总结阶段 |
生成测试和缺陷填写报告 |
6.3.2系统测试用例
1．用户登录模块测试用例，用户登录系统时须要输入用户名和密码，用户名和密码输入正确则登录成功，否则将会给会相应提示。对用户登录输入用户名和密码设计详细测试用例。
用户登录测试用例如下表所示。
表6-2用户登录测试用例表
| 设计人 |
测试人 |
功能编号 |
1 |
|||||||||
| 功能组 |
登录界面 |
功能点 |
用户登录 |
测试日期 |
||||||||
| 测试环境及前提 |
||||||||||||
| 测试条件 |
已添加用户A用户：1，密码: B用户：2,密码: |
|||||||||||
| 测试项目及内容 |
||||||||||||
| 测试步骤 |
输入项 |
预期输出项 |
实际输出 |
|||||||||
| 1 |
空值/空值 |
提示“用户名或密码不能为空！” |
提示“用户名或密码不能为空！” |
|||||||||
| 2 |
空值/123 |
|||||||||||
| 3 |
123/空值 |
|||||||||||
| 4 |
1/1 |
成功登录到主程序，“系统设置”菜单中拥有所有权限 |
成功登录到主程序，“系统设置”菜单中拥有所有权限 |
|||||||||
| 111/1 |
提示“用户名或密码错误，请重新输入” |
提示“用户名或密码错误，请重新输入” |
||||||||||
| 5 |
2/2 |
成功登录到主程序，在“系统设置”菜单中只能修改自己的密码 |
成功登录到主程序，在“系统设置”菜单中只能修改自己的密码 |
|||||||||
| 测试结论 |
用户登录功能可以正常使用 |
总体结论 |
基本通过 |
|||||||||
| 测试结论 |
功能可正常使用 |
总体结论 |
基本通过 |
|||||||||
2．用户管理测试用例，添加用户时须要输入用户的详细信息，当用户信息输入正确时则输入成功，当用户信息输入不正确时则给出相应提示。
添加用户测试用例表如下表所示。
表6-3用户管理测试用例表
| 设计人 |
测试人 |
功能编号 |
2 |
||||
| 功能组 |
系统设置 |
功能点 |
添加用户 |
测试日期 |
|||
| 测试环境及前提 |
|||||||
| 测试条件 |
系统中存在欲创建人的基本信息 |
||||||
| 测试项目及内容 |
|||||||
| 测试步骤 |
输入项 |
预期输出项 |
实际输出 |
||||
| 1 |
选择一条记录点击创建用户按钮 |
提示“用户创建成功！” |
提示“用户创建成功！” |
||||
| 2 |
使用管理员权限登录为刚刚创建的用户授权 |
提示“授权成功！” |
提示“授权成功！” |
||||
| 3 |
实用刚刚创建的用户登录系统 |
提示“登录成功！” |
提示“登录成功！” |
||||
| 测试结论 |
添加用户功能可以正常使用 |
总体结论 |
基本通过 |
||||
3．物资管理测试用例，对物资管理功能模块进行增删改查的测试。
物资管理测试用例如下表所示。
表6-4添加物资测试用例
| 设计人 |
测试人 |
功能编号 |
3 |
|||||
| 功能组 |
物资管理界面 |
功能点 |
添加物资 |
测试日期 |
||||
| 测试环境及前提 |
||||||||
| 测试条件 |
进入物资管理模块 |
|||||||
| 测试项目及内容 |
||||||||
| 测试步骤 |
输入项 |
预期输出项 |
实际输出 |
|||||
| 1 |
添加物资时，没有输入任何物资信息 |
提示“物资添加失败！” |
提示“物资添加失败！” |
|||||
| 2 |
添加物资时，输入带*号的文本框，并且符合格式要求 |
提示“物资添加成功！” |
提示“物资添加成功！” |
|||||
| 3 |
添加物资时，输入所有文本框，并且格式符合要求 |
提示“物资添加成功！” |
提示“物资添加成功！” |
|||||
| 4 |
添加物资时，只输入没有带*号的文本框 |
提示“物资添加失败！” |
提示“物资添加失败！” |
|||||
4．物资入库管理测试用例，物资入库测试物资入库情况，可以选择一个物资进行入库，可以选则多个物资进行入库。
物资入库用例表如下表所示。
表6-5物资入库管理测试用例表
| 设计人 |
测试人 |
功能编号 |
4 |
|||||
| 功能组 |
入库 |
功能点 |
物资入库 |
测试日期 |
||||
| 测试环境及前提 |
||||||||
| 测试条件 |
已录入物资信息 |
|||||||
| 测试项目及内容 |
||||||||
| 测试步骤 |
输入项 |
预期输出项 |
实际输出 |
|||||
| 1 |
选择一个物资，点击入库按钮，输入该物资入库数量 |
入库成功 |
入库成功 |
|||||
| 2 |
选择一个物资，点击入库按钮，没有输入该物资入库数量 |
请输入入库数量 |
请输入入库数量 |
|||||
| 测试结论 |
物资入库功能可以正常使用 |
总体结论 |
基本通过 |
|||||
测试结果包括界面及功能测试和代码测试两部分，本系统对每个功能点做了详细的测试，测试结果正常。
测试结果表如下表所示。
表6-6系统功能测试结果表
| 序号 |
测试模块 |
功能点 |
质量保证标准 |
问题属性 |
测试结果 |
| F1 |
系统用户管理模块 |
修改密码 |
正确性 |
故障 |
正常 |
| 权限设置 |
正确性 |
故障 |
正常 |
||
| 角色管理 |
正确性 |
缺陷 |
正常 |
||
| 用户信息添加 |
正确性 |
故障 |
正常 |
||
| 用户信息修改 |
正确性 |
故障 |
正常 |
||
| 用户信息查询 |
正确性 |
故障 |
正常 |
||
| 用户信息删除 |
正确性 |
故障 |
正常 |
||
| 退出系统 |
正确性 |
故障 |
正常 |
||
| F2 |
功能管理模块 |
物资信息添加 |
正确性 |
故障 |
正常 |
| 物资信息修改 |
正确性 |
故障 |
正常 |
||
| 物资信息删除 |
正确性 |
故障 |
正常 |
||
| 入库信息添加 |
正确性 |
故障 |
正常 |
||
| 入库信息修改 |
正确性 |
故障 |
正常 |
||
| 入库信息删除 |
正确性 |
故障 |
正常 |
||
| 出库信息添加 |
正确性 |
故障 |
正常 |
||
| 出库信息修改 |
正确性 |
故障 |
正常 |
||
| 出库信息删除 |
正确性 |
故障 |
正常 |
||
| 签收信息添加 |
正确性 |
故障 |
正常 |
||
| 签收信息修改 |
正确性 |
故障 |
正常 |
||
| 签收信息删除 |
正确性 |
故障 |
正常 |
本系统是通过计算机技术，结合物资管理的需求，研制出的一套用于各个的爱心捐赠物资维护系统。该系统能够为的物资管理提供方便，能够帮助对其进行信息化管理，能够为对各方面的管理提高工作效率。本系统还能够将各个资料录入，让管理层在网上查询所需要的资料，这样一来，就能够省去了专门负责库存管理人的工作量，也为库存管理工作提供了便利。
在对本系统进行了详细的分析以及一系列的可行性研究之后，根据该系统的设计构想，对本软件进行了开发设计。在确定了本系统具有较高的可行性以后，通过对系统的数据库的分析和总体的功能模块的设计，本系统前台采用的是java开发技术，以MySQL作为后台数据库连接开发。在对系统进行详细的需求分析后，针对不同的需求设立不同的板块，发挥各部分不同的作用。根据该系统的功能结构图展示出了系统内各功能模块之间的业务逻辑结构。并且通过所设计的E-R图，表示出系统各个部分的功能，涉及到系统中各部分的联系，可以让读者能够清晰的了解到本系统的运行流程，并能够进一步的了解到系统各功能模块的相关信息。
[1]李秀红,徐介新,吕兰兰,王勍.基于SSM的高校实验室管理系统的设计与实现[J].软件工程,2017,20(06):24-26.
[2]袁斌.基于SSM的图书商城系统设计t初探[J].经营管理者,2017,(18):268-269.
[3]陈倩.基于SSM的OA办公平台[J].经贸实践,2017,(12):223.
[4]施万里.从ESP到SSM:专门用途日语教师专业发展研究[J].旅游纵览(下半月),2017,(08):247+249.
[5]李俊.基于jsp的数据库开发技术研究[J].才智,2017,(20):265.
[6]周江,李月.一种基于SSM技术的网页表格组件的设计与实现[J].现代计算机(专业版),2017,(21):48-51.
[7]韩银锋.SSM实现网站访问次数计数累计[J].数字技术与应用,2017,(06):205+208.
[8]袁永彦.基于SSM技术的体育用品管理系统设计与实现[J].电子设计工程,2017,25(14):172-174+178.
[9]周文华,胡玉欣,周嘉雯,张之江.SSM+Servlet+javaBean开发的登录系统[J].工业控制计算机,2017,30(08):132-133+147.
[10]张继东.MySQL数据库基于SSM的访问技术[J].电子技术与软件工程,2017,(15):169.
[11]黄小根.基于SSM+MVC模式的个人博客系统设计[J].电脑编程技巧与维护,2017,(16):24-25+32.
[12]陈娟.基于SSM的校园二手物品交易系统的设计与实现[J].计算机产品与流通,2018(11):140-141.
[13]刘欣华.基于jsp技术的网络考试系统的研究与设计[J].现代职业教育,2017,(05):80.
[14]AbbasMrAnsar,EliyanaProfAnis,EkowatiDrDian,SaudMrMuhammad,RazaMrAli,WardaniMsRatna.Datasetoncopingstrategiesinthedigitalage:Theroleofpsychologicalwell-beingandsocialcapitalamonguniversitystudentsinjavaTimor,Surabaya,Indonesia.[J].Datainbrief,2020,30.
[15]PatríciaAmorim,PedroSousa,ErnestoJardim,ManuelaAzevedo,GuiM.Menezes.Length-frequencydataapproachestoevaluatesnapperandgrouperfisheriesinthejavaSea,Indonesia[J].FisheriesResearch,2020,229.
[16]Mr.AnsarAbbas,Prof.AnisEliyana,Dr.DianEkowati,Mr.MuhammadSaud,Mr.AliRaza,Ms.RatnaWardani.Datasetoncopingstrategiesinthedigitalage:Theroleofpsychologicalwell-beingandsocialcapitalamonguniversitystudentsinjavaTimor,Surabaya,Indonesia[J].DatainBrief,2020,30.
[17]PengxiangZhou,ShaohongXia.Effectsoftheheterogeneoussubductingplateonseismicity:Constraintsfromb-valuesintheAndaman–Sumatra–javasubductionzone[J].PhysicsoftheEarthandPlanetaryInteriors,2020.
[18]FranciscoAleixo,SeánA.O’Callaghan,LuísDuclaSoares,PauloNunes,RuiPrieto.AragoJ:Afree,open‐sourcesoftwaretoaidsinglecameraphotogrammetrystudies[J].MethodsinEcologyandEvolution,2020,11(5).
[19]BelénRíos-Sánchez,DavidCosta-daSilva,NataliaMartín-Yuste,CarmenSánchez-?vila.Deeplearningforfacerecognitiononmobiledevices[J].IETBiometrics,2020,9(3).
[20] MoeljadiMoeljadi, TriningsihSriSupriyati, SherlindaOctaYuniarsa.PersonalMotivationalFactorstoAligningInnovationCulture:EvidenceonTrenggalek,Eastjava,Indonesia[J].SHSWebofConferences,2020,76.
After more than three months of hands-on practice, the diligent guidance of teachers and the enthusiastic help of classmates and friends, the basic functions of my graduation project love donation material maintenance system have been basically completed.
In this design, continuous discussion and learning made me familiar with and gave me a preliminary understanding of SSM related technologies. What I am doing is a B/S structure of a love donation material maintenance system, which gives me a preliminary understanding of what is needed to build a website and the operating environment. During this design, I read a lot of books, and in a limited time Over time, I have enriched my knowledge of donation material maintenance system technology and accumulated some experience. At first, I had a preliminary understanding of Java. Through this design, I further understood its working principle, learned how to configure the server environment and connect to the database source. During the design process, I also learned to use Pycharm to design a simple page, which enhanced my hands-on skills. ability, stimulated interest in this area.
However, due to various issues such as time, foundation, and lack of practice, there are still many problems that need to be solved, and many aspects of the design are not fully considered or not considered.
I am very grateful to my teachers, my classmates, and my friends, and I hope that I can continue to support my various interests in my future study life, and continue to learn and progress so that I can achieve independent completion. I sincerely apologize for the many shortcomings in the design.
Please follow and like + privately message the blogger to receive the project source code for free