Table of contents
1.1 Purpose and significance of the topic
1. 4 Paper structure and chapter arrangement
2 System analysis of pharmacy management system
3 Overall design of pharmacy management system
3.1 System architecture design
3.2 System function module design
3.2.1 Overall functional module design
3.2.3 Comment management module design
3.2.4 Mall management module design
3.2.5 Order management module design
3.3.1 Database conceptual structure design
3.3.2 Database logical structure design
4 Detailed design and implementation of pharmacy management system
4.1.2 User registration interface
4.1.5 Shipping address interface
4.1.8 Drug information interface
4. 2 Administrator function module
4. 2.1Announcement management interface
4. 2.2 Resource management interface
4. 2.3 Mall management interface
4. 2.4 System user management interface
In the information society, there is a need for targeted ways to obtain information, but the expansion of the ways is basically the direction that people strive for. Due to deviations in the perspective, people can often obtain different types of information, which is also the most difficult to overcome with technology. subject. For issues such as pharmacy management systems, conduct research and analysis on the pharmacy management system, and then develop and design a pharmacy management system to solve the problems.
The main functional modules of the pharmacy management system include carousel chart (carousel chart management) announcement management (announcement) resource management (drug information, information classification) mall management (drug information, classification list, order list) system users (administrators, ordinary users , seller) module management (member information, order evaluation), adopts an object-oriented development model for software development and hardware setup, which can well meet the needs of actual use and improves the corresponding software setup and program coding. In the work, MySQL is used as the main storage unit of background data, and the ssm framework and Java language are used to code and develop the business system, realizing all the functions of this system. This report first analyzes the background, role, and significance of the research, laying the foundation for the rationality of the research work. Analyzing various needs and technical issues of the pharmacy management system, proving the necessity and technical feasibility of the system, and then giving a basic introduction to the technical software and design ideas that need to be used to design the system, and finally implementing the pharmacy management system and Deployment runs using it.
Keywords : Java technology; MYSQL; pharmacy management system
Abstract
In the information society, there is a need for targeted information acquisition channels, but the expansion of channels is basically the direction of people's efforts. Due to the deviation in perspective, people often can obtain different types of information, which is also the most difficult topic for technology to overcome. Research and analyze the pharmacy management system and other issues, and then develop and design a pharmacy management system to solve the problems.
The main functional modules of the pharmacy management system include rotation chart (rotation chart management) announcement management (announcement) resource management (drug information, information classification) mall management (drug information, classification list, order list) system user (administrator, ordinary user, seller) module management (member information, order evaluation), adopting an object-oriented development model for software development and hardware installation, It can well meet the actual usage needs, improve the corresponding software installation and program coding work, adopt MySQL as the main storage unit for backend data, use the SSM framework, Java language, code and develop the business system, and achieve all the functions of this system. This report first analyzes the background, role, and significance of the research, laying the foundation for the rationality of the research work. Analyze the various requirements and technical issues of the pharmacy management system, prove the necessity and technical feasibility of the system, and then provide a basic introduction to the technical software and design ideas required for designing the system. Finally, implement the pharmacy management system and deploy it for operation.
Keywords:Java technology; MYSQL； Pharmacy Management System
1 Introduction
1.1 Purpose and significance of the topic
The rapid development of modern science and technology has made the operation and management of pharmacies more and more complex. Not only is the amount of information that workers need to process in their daily work gradually increasing, but the interrelationships between various data and the requirements for processing and sorting are more complex. Therefore, pharmacy drug information processing must be faster and more accurate, otherwise it cannot meet the needs of modern management. However, in the manual operation mode, as the workload continues to increase, pharmacy managers are busy with tedious routine work all day long. They have neither time nor ability to process drug information well, and it is difficult to process drug information in a timely manner. Conduct analysis and implement supervision. At the same time, we must improve market competitiveness and provide good customer service. In the case of manual management, it is difficult for pharmaceutical sales staff to make correct supply commitments to customers. In order for pharmacies to respond to customer needs in a timely manner, they must have accurate and relevant information. Only in this way can they obtain the best benefits in the competition. A better management system can provide relevant information queries, reflect the operating status of pharmacy drugs in real time and accurately, and enable managers to make better predictions and decisions. The pharmacy management information system is designed to adapt to this situation, using modern management tools to make pharmacy management more efficient and faster, and transforming from manual management to computer management. It not only reduces the consumption of human and financial resources, but also improves the efficiency and accuracy of management, allowing managers to complete their work more conveniently, quickly and effectively.
The pharmacy management system includes drug information, order evaluation, member information, etc. It is an important part of pharmacy information management. Pharmacy management is a trivial, complex and very meticulous job. Manually carrying out the daily purchase, sale and inventory of the pharmacy can easily lead to the phenomenon of "empty orders", and bad debts and wrong debts often occur. It is the repetitiveness, regularity, and timeliness of pharmacy management that make computer informatization of pharmacy management possible. Computers carry out the daily management of pharmacies, which can not only ensure the correct accounting of the purchase, sale and inventory of medicines, but also strictly standardize the enterprise's receivables and payables management, and use advanced management models to promote the rapid development of pharmacies and realize store management. Systematization, standardization and automation.
1.2 Research background
Today's era is like an information age. In today's rapidly developing world, traditional manual accounting and other management methods can no longer meet the current development needs. The groupization and chainization of pharmaceutical business models are the current development trends of the entire domestic pharmaceutical industry. The traditional marketing model is about to gradually withdraw. Society becomes history. This pharmacy management system is developed and designed to meet the current pharmacy management needs.
This system is mainly based on running on Windows platform, comprehensively developed using SSM, and using MySQL database to complete the implementation of each functional module of the pharmacy management system. This system realizes a series of functions such as order evaluation and member information, reducing the tedious work processes of the past, and combining the advantages of past pharmacy management to improve the management and operation efficiency of the entire pharmacy, making it information-based, standardized and efficient.
1.3 Research methods
First, through engine search or relevant literature, we learned about the background of the system development and the significance of designing the system, and collected user demand information. Secondly, in terms of development tools, it was finally decided to use the ssm platform to design and develop this system, with MySQL as the tool for designing the database. That is, the user interface is implemented using Java language and connected with the database to achieve complete communication functions. After that, the general functional modules of the system are designed. Mainly from the perspective of convenience for users and administrators, the analysis is carried out to clarify the functions that the system should have. The final step is to test the system, discover existing problems and find solutions through use case testing. Utilize the existing development platform, combine the knowledge you have learned, and complete the design with the guidance of the teacher to ensure the usability and practicality of the system.
1.4 Paper structure and chapter arrangement
The paper will be organized hierarchically. In addition to the abstract, acknowledgments, and literature references, the main text will also analyze the website requirements, describe the general design and implemented functions, and finally list some debugging records. The main structure of the paper is as follows:
Chapter 1: Introduction. The first chapter mainly introduces the background of the project research, the current situation of system development and the research content and main work of this article.
Chapter 2: System requirements analysis. Chapter 2 mainly conducts demand analysis from the aspects of users and functions of the system.
Chapter 3: System Design. Chapter 3 mainly carries out functional design of the system framework, system function modules and database.
Chapter 4: System implementation. Chapter 4 mainly introduces the system framework construction and the implementation of the system interface.
Chapter 5: System Testing. Chapter 5 mainly tests some interfaces of the system and tests the main functions.
2 System analysis of pharmacy management system
System analysis is a prerequisite for developing a project. Through system analysis, the basic needs of the main users of the system can be well understood, and this is also the reason for the development of the project. Then, a feasibility analysis is performed on the system development, which usually includes technical feasibility, economic feasibility, etc. The feasibility analysis is also an analysis from the overall perspective of the project. Then the specific requirements of the project are analyzed. The analysis method is generally implemented through the user's use case diagram. The following is a detailed introduction.
2.1 Feasibility analysis
( 1) Operational feasibility:
The design of this project refers to several cases of website development under this mode, analyzes their operation interfaces, and combines many cases to highlight people-oriented simplified operations, so people with basic computer knowledge can operate this project.
Therefore, there is no problem with operational feasibility.
(2) Technical feasibility:
Technical feasibility refers to the feasibility of building a framework, as well as the system's adaptability to technological upgrading when better technologies emerge, and the development time and cost ratio.
Existing Java technology can cater to the construction of all e-commerce systems. When developing this pharmacy management system, I used Java+MYSQL to run the overall program.
In summary, there is no problem with the technical feasibility.
(3) Legal feasibility:
From a developer's perspective, Java and MYSQL are open source and free online, and there will be no legal disputes regarding intellectual property rights.
From a user perspective, as long as contraband is no longer sold on the system, treaties and agreements are made with the system, and illegal payments are eliminated.
In summary, there is no problem with the legal feasibility.
2.2.1 Data flow
The main purpose of the pharmacy management system is to realize the online purchase of medicines. Figure 2-1 is the data flow diagram of the system.
Figure 2-1 Expanded view of drug purchase operations
3.3.2 Business process
After analyzing the data flow of the system, let’s look at the business process of the system. Figure 2-2 is the business flow chart:
Figure 2-2 Business flow chart
According to the roles of the pharmacy management system, I divided it into three parts: the ordinary user management module, the seller management module and the administrator management module.
Ordinary user management module:
(1) User registration and login: Users register as members and log in to the pharmacy management system; users add, delete, modify and check personal information, such as personal information and password changes.
(2) Users view drugs: Users browse drug information, and after discovering the drugs they like, they can add + purchase + comment + collect.
(3) Drug information: Users browse information and view drug information released by managers.
(4) Announcements: Users read announcements and view bank announcement information released by managers.
(5) Shopping cart: Users can purchase additional drugs they like. In the shopping cart, they can view all purchased drugs. It supports changing the quantity of drugs, deleting drugs, and selecting and purchasing.
(6) My order: After submitting the order, the user can manage the submitted order.
(7) Delivery address: When you click the "My Address" button in "My", your delivery address information will be displayed, and the addition, deletion, modification, and check of the delivery address will be supported.
(8) My Collection: When you click the "My Collection" button in "My", various information collected by you will be displayed. Search and query for collection information are supported. If you no longer want to collect a certain information , just click Delete.
(9) Order evaluation: Click "Order evaluation" to view the evaluation of your order.
Administrator management module:
(1) Login: The administrator can enter the username + password to log in in the background. The administrator's username and password are set directly in the database.
(2) Carousel image: Administrators can click the "Carousel image" menu to add, delete, modify, and check the carousel image displayed on the home page.
(3) Announcement management: The administrator can click the "Announcement Management" menu to view all announcement information in the system. The administrator can modify existing announcements, add new announcements, or delete announcements.
(4) System User: When the administrator clicks on the "System User" menu, the three submenus of administrator, seller and ordinary user will be displayed. The administrator can add, delete, modify and check the information of these three roles;
(5) Resource management: The administrator can add, delete, modify and check the drug information and information classification displayed in the pharmacy management system in the background.
(6) Mall management: Comprehensive management of all drugs, drug categories and order information submitted by users in the pharmacy management system.
(7) Module management: Under the "Module Management" menu, we will see member information and order evaluations, and the administrator can add, delete, modify and check them.
The non-functional requirements of the pharmacy management system include the safety, reliability, performance, scalability, etc. of the pharmacy management system. The details can be expressed in the following 3-1 table:
Table 3-1 Pharmacy management system non-functional requirements table
| safety |
Mainly refers to the installation of the pharmacy management system database, the use of the database and the setting of passwords must comply with regulations. |
| reliability |
Reliability means that the pharmacy management system can operate according to the user's instructions. After testing, the reliability is over 90%. |
| performance |
Performance is a necessary condition for the pharmacy management system to occupy the market, so it is best to have good performance. |
| Scalability |
For example, the database reserves multiple attributes, such as the use of interfaces, to ensure the non-functional requirements of the system. |
| Ease of use |
Users only need to follow the page display content of the pharmacy management system and operate. |
| maintainability |
The maintainability of pharmacy management system development is very important. After testing, there is no problem with maintainability. |
2.4 System use case analysis
Through the analysis of 2.3 functions, the use case diagram of this pharmacy management system is obtained:
An example of a user role is shown in Figure 2-3.
Figure 2-3 Pharmacy management system user role use case diagram
An example of the seller role is shown in Figure 2-4.
Figure 2-4 Pharmacy management system seller role use case diagram
The administrator on the web backend management maintains all data information in the entire pharmacy management system. Figure 2-5 shows an example of the administrator role.
Figure 2-5 Pharmacy management system administrator role use case diagram
This chapter mainly determines the functions to be realized by the entire pharmacy management system through feasibility analysis, process analysis, functional requirements analysis, and system use case analysis of the pharmacy management system. It also provides standards for code implementation and testing of pharmacy management systems.
3 Overall design of pharmacy management system
The main contents discussed in this chapter include the functional module design and database system design of the pharmacy management system.
3.1 System architecture design
This pharmacy management system is architecturally divided into three layers: presentation layer (UI), business logic layer (BLL) and data layer (DL).
Figure 3-1 System architecture design diagram of pharmacy management system
Presentation layer (UI): Also known as the UI layer, it mainly completes the UI interaction function of the pharmacy management system. A good UI can improve the user experience and enhance the user's comfort when using the pharmacy management system. The UI interface design must also adapt to different versions of pharmacy management systems and different size resolutions to achieve good compatibility. The UI interaction function requirements are reasonable, and users must obtain consistent interaction results when performing interactive operations. This requires the presentation layer to be well connected with the business logic layer.
Business Logic Layer (BLL): Mainly completes the data processing function of this pharmacy management system. The data transmitted by the user from the presentation layer is processed by the business logic layer and delivered to the data layer. The data read by the system from the data layer is processed by the business logic layer and delivered to the presentation layer.
Data layer (DL): Since the data of this pharmacy management system is placed in the mysql database on the server side, the parts that belong to the service layer can be directly integrated into the business logic layer, so there is only a database in the data layer, which mainly completes the functions of this pharmacy. Management system's data storage and management functions.
3.2 System function module design
3.2.1 Overall functional module design
In the previous chapter, the functional requirements and non-functional requirements of the system were mainly analyzed, and the use cases in this pharmacy management system were analyzed based on the requirements. Then the next step is to start designing the architecture, main functions and database of this pharmacy management system. The pharmacy management system is derived based on the demand analysis in the previous chapter, and its overall design module diagram is shown in Figure 3-2.
Figure 3-2 Function module diagram of pharmacy management system
3.2.2 User module design
The backend manager can add, delete, modify and check the users registered in the frontend. The user module structure diagram is as follows:
Figure 3-3 Member user module structure diagram
3.2.3 Comment management module design
The pharmacy management system is an open platform for communication. System users and managers can comment on the information on the platform to increase interaction between users. But at the same time, in order to better standardize the content of comments and give administrators the function of deleting inappropriate comments, a comment management module needs to be specially designed. The specific structure diagram is as follows:
Figure 3-4 Structure diagram of comment module
3.2.4 Mall management module design
The pharmacy management system needs to store a lot of drug information. Its module functional structure. The specific structure diagram is as follows:
Figure 3-5 Mall module structure diagram
3.2.5 Order management module design
One of the most important functions of the pharmacy management system is purchasing. Its module function structure is as follows:
Figure 3-5 Order module structure diagram
Database design generally includes three major processes: demand analysis, conceptual model design, and database table creation. The demand analysis has been explained in the previous chapter, and the conceptual model design has two parts: conceptual model and logical structure design.
3.3.1 Database conceptual structure design
The following is the total ER entity relationship diagram of the main database tables in the entire pharmacy management system.
Figure 3-6 Overall ER relationship diagram of pharmacy management system
According to the total ER diagram of the database of the pharmacy management system, it can be concluded that the pharmacy management system requires many ER diagrams. Here are some main database ER model diagrams.
Figure 3-7 Ordinary user ER relationship diagram
Figure 3-8 Order evaluation ER relationship diagram
Figure 3-9 Member information ER relationship diagram
Figure 3-10 Order information ER relationship diagram
Figure 3-11 Address information ER relationship diagram
3.3.2 Database logical structure design
From the total ER relationship diagram in the Chinese pharmacy management system in the previous section, it can be concluded that a total of many data tables need to be created. Here I mainly list several major database table structure designs.
Table address (shipping address:)
| serial number |
name |
type of data |
length |
Decimal places |
Allow null values |
primary key |
default value |
illustrate |
| 1 |
address_id |
int |
10 |
0 |
N |
Y |
Shipping address: |
|
| 2 |
name |
varchar |
32 |
0 |
Y |
N |
Name: |
|
| 3 |
phone |
varchar |
13 |
0 |
Y |
N |
cell phone: |
|
| 4 |
postcode |
varchar |
8 |
0 |
Y |
N |
post code: |
|
| 5 |
address |
varchar |
255 |
0 |
N |
N |
address: |
|
| 6 |
user_id |
mediumint |
8 |
0 |
N |
N |
User ID: [0,8388607] User obtains other user-related data |
|
| 7 |
create_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
Creation time: |
| 8 |
update_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
Update time: |
| 9 |
default |
bit |
1 |
0 |
N |
N |
0 |
Default judgment |
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 cart (shopping cart)
| serial number |
name |
type of data |
length |
Decimal places |
Allow null values |
primary key |
default value |
illustrate |
| 1 |
cart_id |
int |
10 |
0 |
N |
Y |
Shopping cart ID: |
|
| 2 |
title |
varchar |
64 |
0 |
Y |
N |
title: |
|
| 3 |
img |
varchar |
255 |
0 |
N |
N |
0 |
picture: |
| 4 |
user_id |
int |
10 |
0 |
N |
N |
0 |
User ID: |
| 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 |
state |
int |
10 |
0 |
N |
N |
0 |
Status: In use, expired |
| 8 |
price |
double |
9 |
2 |
N |
N |
0.00 |
unit price: |
| 9 |
price_ago |
double |
9 |
2 |
N |
N |
0.00 |
Original price: |
| 10 |
price_count |
double |
11 |
2 |
N |
N |
0.00 |
Total price: |
| 11 |
num |
int |
10 |
0 |
N |
N |
1 |
quantity: |
| 12 |
goods_id |
mediumint |
8 |
0 |
N |
N |
Drug id: [0,8388607] |
|
| 13 |
type |
varchar |
64 |
0 |
N |
N |
uncategorized |
Drug classification: |
| 14 |
description |
varchar |
255 |
0 |
Y |
N |
Description: [0,255] is used for product specification description |
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 |
Collection ID: |
|
| 2 |
user_id |
int |
10 |
0 |
N |
N |
0 |
Collector ID: |
| 3 |
source_table |
varchar |
255 |
0 |
Y |
N |
Source table: |
|
| 4 |
source_field |
varchar |
255 |
0 |
Y |
N |
Source field: |
|
| 5 |
source_id |
int |
10 |
0 |
N |
N |
0 |
Source ID: |
| 6 |
title |
varchar |
255 |
0 |
Y |
N |
title: |
|
| 7 |
img |
varchar |
255 |
0 |
Y |
N |
Cover: |
|
| 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 comment (comment)
| serial number |
name |
type of data |
length |
Decimal places |
Allow null values |
primary key |
default value |
illustrate |
| 1 |
comment_id |
int |
10 |
0 |
N |
Y |
Comment ID: |
|
| 2 |
user_id |
int |
10 |
0 |
N |
N |
0 |
Commenter ID: |
| 3 |
reply_to_id |
int |
10 |
0 |
N |
N |
0 |
Reply comment ID: empty is 0 |
| 4 |
content |
longtext |
2147483647 |
0 |
Y |
N |
content: |
|
| 5 |
nickname |
varchar |
255 |
0 |
Y |
N |
Nick name: |
|
| 6 |
avatar |
varchar |
255 |
0 |
Y |
N |
Avatar address: [0,255] |
|
| 7 |
create_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
Creation time: |
| 8 |
update_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
Update time: |
| 9 |
source_table |
varchar |
255 |
0 |
Y |
N |
Source table: |
|
| 10 |
source_field |
varchar |
255 |
0 |
Y |
N |
Source field: |
|
| 11 |
source_id |
int |
10 |
0 |
N |
N |
0 |
Source ID: |
Table drug_information (drug information)
| serial number |
name |
type of data |
length |
Decimal places |
Allow null values |
primary key |
default value |
illustrate |
| 1 |
drug_information_id |
int |
10 |
0 |
N |
Y |
Drug information ID |
|
| 2 |
salesperson |
int |
10 |
0 |
Y |
N |
0 |
Seller |
| 3 |
drug_name |
varchar |
64 |
0 |
Y |
N |
Drug Name |
|
| 4 |
specifications |
varchar |
64 |
0 |
Y |
N |
Specification |
|
| 5 |
recommend |
int |
10 |
0 |
N |
N |
0 |
Intelligent Recommendation |
| 6 |
cart_title |
varchar |
125 |
0 |
Y |
N |
Title: [0,125] used in tags of product html |
|
| 7 |
cart_img |
text |
65535 |
0 |
Y |
N |
Cover image: used to display on the product list page |
|
| 8 |
cart_description |
varchar |
255 |
0 |
Y |
N |
Description: [0,255] is used for product specification description |
|
| 9 |
cart_price_ago |
double |
8 |
2 |
N |
N |
0.00 |
Original price: [1] |
| 10 |
cart_price |
double |
8 |
2 |
N |
N |
0.00 |
Selling price: [1] |
| 11 |
cart_inventory |
int |
10 |
0 |
N |
N |
0 |
Drug Inventory |
| 12 |
cart_type |
varchar |
64 |
0 |
N |
N |
uncategorized |
Drug classification: |
| 13 |
cart_content |
longtext |
2147483647 |
0 |
Y |
N |
Text: the main content of the product |
|
| 14 |
cart_img_1 |
text |
65535 |
0 |
Y |
N |
Main picture 1: |
|
| 15 |
cart_img_2 |
text |
65535 |
0 |
Y |
N |
Main picture 2: |
|
| 16 |
cart_img_3 |
text |
65535 |
0 |
Y |
N |
Main picture 3: |
|
| 17 |
cart_img_4 |
text |
65535 |
0 |
Y |
N |
Main picture 4: |
|
| 18 |
cart_img_5 |
text |
65535 |
0 |
Y |
N |
Main picture 5: |
|
| 19 |
create_time |
datetime |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
creation time |
| 20 |
update_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
Update time |
Table goods_type (goods type)
| serial number |
name |
type of data |
length |
Decimal places |
Allow null values |
primary key |
default value |
illustrate |
| 1 |
type_id |
int |
10 |
0 |
N |
Y |
Product category ID: |
|
| 2 |
father_id |
smallint |
5 |
0 |
N |
N |
0 |
Parent category ID: [0,32767] |
| 3 |
name |
varchar |
255 |
0 |
Y |
N |
product name: |
|
| 4 |
desc |
varchar |
255 |
0 |
Y |
N |
describe: |
|
| 5 |
icon |
varchar |
255 |
0 |
Y |
N |
icon: |
|
| 6 |
source_table |
varchar |
255 |
0 |
Y |
N |
Source table: |
|
| 7 |
source_field |
varchar |
255 |
0 |
Y |
N |
Source field: |
|
| 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 hits (user clicks)
| serial number |
name |
type of data |
length |
Decimal places |
Allow null values |
primary key |
default value |
illustrate |
| 1 |
hits_id |
int |
10 |
0 |
N |
Y |
Like ID: |
|
| 2 |
user_id |
int |
10 |
0 |
N |
N |
0 |
Liked by: |
| 3 |
create_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
Creation time: |
| 4 |
update_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
Update time: |
| 5 |
source_table |
varchar |
255 |
0 |
Y |
N |
Source table: |
|
| 6 |
source_field |
varchar |
255 |
0 |
Y |
N |
Source field: |
|
| 7 |
source_id |
int |
10 |
0 |
N |
N |
0 |
Source ID: |
Table member_information (member information)
| serial number |
name |
type of data |
length |
Decimal places |
Allow null values |
primary key |
default value |
illustrate |
| 1 |
member_information_id |
int |
10 |
0 |
N |
Y |
Member information ID |
|
| 2 |
user |
int |
10 |
0 |
Y |
N |
0 |
user |
| 3 |
member_name |
varchar |
64 |
0 |
Y |
N |
Member's name |
|
| 4 |
contact_number |
varchar |
64 |
0 |
Y |
N |
contact number |
|
| 5 |
start_time |
date |
10 |
0 |
Y |
N |
Starting time |
|
| 6 |
end_time |
date |
10 |
0 |
Y |
N |
End Time |
|
| 7 |
remarks |
text |
65535 |
0 |
Y |
N |
Remark |
|
| 8 |
recommend |
int |
10 |
0 |
N |
N |
0 |
Intelligent Recommendation |
| 9 |
create_time |
datetime |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
creation time |
| 10 |
update_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
Update time |
Notice (announcement)
| serial number |
name |
type of data |
length |
Decimal places |
Allow null values |
primary key |
default value |
illustrate |
| 1 |
notice_id |
mediumint |
8 |
0 |
N |
Y |
Announcement id: |
|
| 2 |
title |
varchar |
125 |
0 |
N |
N |
title: |
|
| 3 |
content |
longtext |
2147483647 |
0 |
Y |
N |
text: |
|
| 4 |
create_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
Creation time: |
| 5 |
update_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
Update time: |
Table order (order)
| serial number |
name |
type of data |
length |
Decimal places |
Allow null values |
primary key |
default value |
illustrate |
| 1 |
order_id |
int |
10 |
0 |
N |
Y |
Order ID: |
|
| 2 |
order_number |
varchar |
64 |
0 |
Y |
N |
order number: |
|
| 3 |
goods_id |
mediumint |
8 |
0 |
N |
N |
Product id: [0,8388607] |
|
| 4 |
title |
varchar |
32 |
0 |
Y |
N |
Product title: |
|
| 5 |
img |
varchar |
255 |
0 |
Y |
N |
product picture: |
|
| 6 |
price |
double |
10 |
2 |
N |
N |
0.00 |
price: |
| 7 |
price_ago |
double |
10 |
2 |
N |
N |
0.00 |
Original price: |
| 8 |
num |
int |
10 |
0 |
N |
N |
1 |
quantity: |
| 9 |
price_count |
double |
8 |
2 |
N |
N |
0.00 |
Total price: |
| 10 |
norms |
varchar |
255 |
0 |
Y |
N |
Specification: |
|
| 11 |
type |
varchar |
64 |
0 |
N |
N |
uncategorized |
Categories: |
| 12 |
contact_name |
varchar |
32 |
0 |
Y |
N |
Contact name: |
|
| 13 |
contact_email |
varchar |
125 |
0 |
Y |
N |
Contact email: |
|
| 14 |
contact_phone |
varchar |
11 |
0 |
Y |
N |
Contact mobile phone: |
|
| 15 |
contact_address |
varchar |
255 |
0 |
Y |
N |
Recipient address: |
|
| 16 |
postal_code |
varchar |
9 |
0 |
Y |
N |
postal code: |
|
| 17 |
user_id |
int |
10 |
0 |
N |
N |
0 |
Buyer ID: |
| 18 |
merchant_id |
mediumint |
8 |
0 |
N |
N |
0 |
Merchant ID: |
| 19 |
create_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
Creation time: |
| 20 |
update_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
Update time: |
| 21 |
description |
varchar |
255 |
0 |
Y |
N |
Description: [0,255] is used for product specification description |
|
| 22 |
state |
varchar |
16 |
0 |
N |
N |
Pending payment |
Order status: awaiting payment, awaiting shipment, awaiting signature, signed, awaiting refund, refunded, rejected, completed |
Table order_evaluation (order evaluation)
| serial number |
name |
type of data |
length |
Decimal places |
Allow null values |
primary key |
default value |
illustrate |
| 1 |
order_evaluation_id |
int |
10 |
0 |
N |
Y |
Order evaluation ID |
|
| 2 |
order_number |
varchar |
64 |
0 |
Y |
N |
order number |
|
| 3 |
drug_name |
varchar |
64 |
0 |
Y |
N |
Drug Name |
|
| 4 |
purchase_quantity |
varchar |
64 |
0 |
Y |
N |
Purchase quantity |
|
| 5 |
salesperson |
int |
10 |
0 |
Y |
N |
0 |
Seller |
| 6 |
user |
int |
10 |
0 |
Y |
N |
0 |
user |
| 7 |
user_name |
varchar |
64 |
0 |
Y |
N |
username |
|
| 8 |
evaluation_score |
varchar |
64 |
0 |
Y |
N |
Rating score |
|
| 9 |
evaluation_content |
text |
65535 |
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 |
更新时间 |
表ordinary_users (普通用户)
| 编号 |
名称 |
数据类型 |
长度 |
小数位 |
允许空值 |
主键 |
默认值 |
说明 |
| 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 |
更新时间 |
表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已取消 |
表seller (卖家)
| 编号 |
名称 |
数据类型 |
长度 |
小数位 |
允许空值 |
主键 |
默认值 |
说明 |
| 1 |
seller_id |
int |
10 |
0 |
N |
Y |
卖家ID |
|
| 2 |
sales_no |
varchar |
64 |
0 |
N |
N |
销售工号 |
|
| 3 |
sales_name |
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 |
更新时间 |
表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 |
文件类型 |
整个药房管理系统的需求分析主要对系统总体架构以及功能模块的设计，通过建立E-R模型和数据库逻辑系统设计完成了数据库系统设计。
4 药房管理系统详细设计与实现
药房管理系统的详细设计与实现主要是根据前面的药房管理系统的需求分析和药房管理系统的总体设计来设计页面并实现业务逻辑。主要从药房管理系统界面实现、业务逻辑实现这两部分进行介绍。
4.1用户功能模块
4.1.1 前台首页界面
当进入药房管理系统的时候，首先映入眼帘的是系统的导航栏，下面是轮播图以及系统内容，其主界面展示如下图4-1所示。
图4-1 前台首页界面图
4.1.2 用户注册界面
不是药房管理系统中正式用户的是可以在线进行注册的，如果你没有本药房管理系统的账号的话，添加“注册”，当填写上自己的账号+密码+确认密码+昵称+邮箱+手机号等后再点击“注册”按钮后将会先验证输入的有没有空数据，再次验证密码和确认密码是否是一样的，最后验证输入的账户名和数据库表中已经注册的账户名是否重复，只有都验证没问题后即可会员注册成功。其用用户注册展示如下图4-2所示。
图4-2 前台用户注册图
注册关键代码如下所示。
/**
* 注册
* @return
*/
@PostMapping("register")
public Map<String, Object> signUp(HttpServletRequest request) throws IOException {
// 查询用户
Map<String, String> query = new HashMap<>();
Map<String,Object> map = service.readBody(request.getReader());
query.put("username",String.valueOf(map.get("username")));
List list = service.selectBaseList(service.select(query, new HashMap<>()));
if (list.size()>0){
return error(30000, "用户已存在");
}
map.put("password",service.encryption(String.valueOf(map.get("password"))));
service.insert(map);
return success(1);
}
public Map<String,Object> readBody(BufferedReader reader){
BufferedReader br = null;
StringBuilder sb = new StringBuilder("");
try{
br = reader;
String str;
while ((str = br.readLine()) != null){
sb.append(str);
}
br.close();
String json = sb.toString();
return JSONObject.parseObject(json, Map.class);
}catch (IOException e){
e.printStackTrace();
}finally{
if (null != br){
try{
br.close();
}catch (IOException e){
e.printStackTrace();
}
}
}
return null;
}
public void insert(Map<String,Object> body){
E entity = JSON.parseObject(JSON.toJSONString(body),eClass);
baseMapper.insert(entity);
log.info("[{}] - 插入操作：{}",entity);
}
4.1.3 用户登录界面
药房管理系统中的前台上注册后的用户是可以通过自己的账户名和密码进行登录的，当会员输入完整的自己的账户名和密码信息并点击“登录”按钮后，将会首先验证输入的有没有空数据，再次验证输入的账户名+密码和数据库中当前保存的用户信息是否一致，只有在一致后将会登录成功并自动跳转到药房管理系统的首页中；否则将会提示相应错误信息，用户登录界面如下图4-3所示。
图4-3用户登录界面图
登录代码如下：
/**
* 登录
* @param data
* @param httpServletRequest
* @return
*/
@PostMapping("login")
public Map<String, Object> login(@RequestBody Map<String, String> data, HttpServletRequest httpServletRequest) {
log.info("[执行登录接口]");
String username = data.get("username");
String email = data.get("email");
String phone = data.get("phone");
String password = data.get("password");
List resultList = null;
QueryWrapper wrapper = new QueryWrapper<User>();
Map<String, String> map = new HashMap<>();
if(username != null && "".equals(username) == false){
map.put("username", username);
resultList = service.selectBaseList(service.select(map, new HashMap<>()));
}
else if(email != null && "".equals(email) == false){
map.put("email", email);
resultList = service.selectBaseList(service.select(map, new HashMap<>()));
}
else if(phone != null && "".equals(phone) == false){
map.put("phone", phone);
resultList = service.selectBaseList(service.select(map, new HashMap<>()));
}else{
return error(30000, "账号或密码不能为空");
}
if (resultList == null || password == null) {
return error(30000, "账号或密码不能为空");
}
//判断是否有这个用户
if (resultList.size()<=0){
return error(30000,"用户不存在");
}
User byUsername = (User) resultList.get(0);
Map<String, String> groupMap = new HashMap<>();
groupMap.put("name",byUsername.getUserGroup());
List groupList = userGroupService.selectBaseList(userGroupService.select(groupMap, new HashMap<>()));
if (groupList.size()<1){
return error(30000,"用户组不存在");
}
UserGroup userGroup = (UserGroup) groupList.get(0);
//查询用户审核状态
if (!StringUtils.isEmpty(userGroup.getSourceTable())){
String res = service.selectExamineState(userGroup.getSourceTable(),byUsername.getUserId());
if (res==null){
return error(30000,"用户不存在");
}
if (!res.equals("已通过")){
return error(30000,"该用户审核未通过");
}
}
//查询用户状态
if (byUsername.getState()!=1){
return error(30000,"用户非可用状态，不能登录");
}
String md5password = service.encryption(password);
if (byUsername.getPassword().equals(md5password)) {
// 存储Token到数据库
AccessToken accessToken = new AccessToken();
accessToken.setToken(UUID.randomUUID().toString().replaceAll("-", ""));
accessToken.setUser_id(byUsername.getUserId());
tokenService.save(accessToken);
// 返回用户信息
JSONObject user = JSONObject.parseObject(JSONObject.toJSONString(byUsername));
user.put("token", accessToken.getToken());
JSONObject ret = new JSONObject();
ret.put("obj",user);
return success(ret);
} else {
return error(30000, "账号或密码不正确");
}
}
public String select(Map<String,String> query,Map<String,String> config){
StringBuffer sql = new StringBuffer("select ");
sql.append(config.get(FindConfig.FIELD) == null || "".equals(config.get(FindConfig.FIELD)) ? "*" : config.get(FindConfig.FIELD)).append(" ");
sql.append("from ").append("`").append(table).append("`").append(toWhereSql(query, "0".equals(config.get(FindConfig.LIKE))));
if (config.get(FindConfig.GROUP_BY) != null && !"".equals(config.get(FindConfig.GROUP_BY))){
sql.append("group by ").append(config.get(FindConfig.GROUP_BY)).append(" ");
}
if (config.get(FindConfig.ORDER_BY) != null && !"".equals(config.get(FindConfig.ORDER_BY))){
sql.append("order by ").append(config.get(FindConfig.ORDER_BY)).append(" ");
}
if (config.get(FindConfig.PAGE) != null && !"".equals(config.get(FindConfig.PAGE))){
int page = config.get(FindConfig.PAGE) != null && !"".equals(config.get(FindConfig.PAGE)) ? Integer.parseInt(config.get(FindConfig.PAGE)) : 1;
int limit = config.get(FindConfig.SIZE) != null && !"".equals(config.get(FindConfig.SIZE)) ? Integer.parseInt(config.get(FindConfig.SIZE)) : 10;
sql.append(" limit ").append( (page-1)*limit ).append(" , ").append(limit);
}
log.info("[{}] - 查询操作，sql: {}",table,sql);
return sql.toString();
}
public List selectBaseList(String select) {
List<Map<String,Object>> mapList = baseMapper.selectBaseList(select);
List<E> list = new ArrayList<>();
for (Map<String,Object> map:mapList) {
list.add(JSON.parseObject(JSON.toJSONString(map),eClass));
}
return list;
}
4.1.4我的账户界面
当用户点击右上角“我的”这个按钮，会出现子菜单，点击“我的账户”可以对个人的资料、登录系统的密码以及自己收藏的信息进行设置管理，我的账户界面如下图4-4所示。
图4-4我的账户界面图
4.1.5 收货地址界面
当用户点击“收货地址”右后，就回去显示出目前现有的地址，也可以添加新的地址，界面如下图4-5所示。
图4-5收货地址界面图
4.1.6 药品详情界面
当访客点击了任意药品后将会进入该款药品的详情界面，可以了解到该药品的图片信息、药品信息、价钱信息等，同时可以对该药品进行加购+立即购买+收藏+点赞+评论，药品详情展示页面如图4-6所示。
图4-6 药品详情界面图
4.1.7 我的订单界面
当用户点击“我的订单”链接后就进入自己购买的订单的界面展示，界面如下图4-7所示。
图4-7 我的订单界面图
4.1.8药品资讯界面
访客点击药房管理系统中导航栏上的“药品资讯”后将会进入到该“药品资讯”列表的界面，然后选择想要看的药品资讯，点击进入到详细界面，同时可以进行点赞、收藏、评论操作，药品资讯界面如下图4-8 所示。
图4-8 药品资讯界面图
4.2管理员功能模块
4.2.1公告管理界面
管理员点击“公告管理”菜单可以查看到系统中的所有公告信息，对已经存在的公告，管理员可以修改，也可以添加新的公告或者删除公告。界面如下图4-9所示。
图4-10公告管理界面图
公告管理逻辑代码如下所示。
@RequestMapping("/get_obj")
public Map<String, Object> obj(HttpServletRequest request) {
List resultList = service.selectBaseList(service.select(service.readQuery(request), service.readConfig(request)));
if (resultList.size() > 0) {
JSONObject jsonObject = new JSONObject();
jsonObject.put("obj",resultList.get(0));
return success(jsonObject);
} else {
return success(null);
}
}
4.2.2 资源管理界面
管理员点击“资源管理”菜单能够对其下子菜单药品资讯和资讯的分类进行增删改查。界面如下图4-10所示。
图4-10资源管理界面图
资源管理关键代码如下所示。
@RequestMapping("/get_list")
public Map<String, Object> getList(HttpServletRequest request) {
Map<String, Object> map = service.selectToPage(service.readQuery(request), service.readConfig(request));
return success(map);
}
4.2.3 商城管理界面
点击“商城”按钮可以查看到所有卖家发布的药品的信息。界面如下图4-11所示。
图4-11商城管理界面图
商城管理关键代码如下所示。
@RequestMapping(value = "/del")
@Transactional
public Map<String, Object> del(HttpServletRequest request) {
service.delete(service.readQuery(request), service.readConfig(request));
return success(1);
}
4.2.4 系统用户管理界面
管理员点击“系统用户”菜单可以对系统中存在的用户进行管理，包含了管理员用户、卖家和普通用户。界面如下图4-12所示。
图4-12系统用户管理界面图
4.2.5 模块管理界面
药房管理系统中的管理人员在“模块管理”这一菜单下是可以对药房管理系统内的会员信息、订单评价进行管控的，其管理界面如下图4-13所示。
图4-13模块管理界面图
5系统测试
系统开发到了最后一个阶段那就是系统测试，系统测试对软件的开发其实是非常有必要的。因为没什么系统一经开发出来就可能会尽善尽美，再厉害的系统开发工程师也会在系统开发的时候出现纰漏，系统测试能够较好的改正一些bug，为后期系统的维护性提供很好的支持。通过系统测试，开发人员也可以建立自己对系统的信心，为后期的系统版本的跟新提供支持。
系统测试包括：用户登录功能测试、药品展示功能测试、药品添加、药品搜索、密码修改功能测试，如表5-1、5-2、5-3、5-4、5-5所示：
表5-1 用户登录功能测试表
| 用例名称 |
用户登录系统 |
| 目的 |
测试用户通过正确的用户名和密码可否登录功能 |
| 前提 |
未登录的情况下 |
| 测试流程 |
1) 进入登录页面 2) 输入正确的用户名和密码 |
| 预期结果 |
用户名和密码正确的时候，跳转到登录成功界面，反之则显示错误信息，提示重新输入 |
| 实际结果 |
实际结果与预期结果一致 |
药品查看功能测试：
表5-2 药品查看功能测试表
| 用例名称 |
药品查看 |
| 目的 |
测试药品查看功能 |
| 前提 |
用户登录 |
| 测试流程 |
点击药品列表 |
| 预期结果 |
可以查看到所有药品信息 |
| 实际结果 |
实际结果与预期结果一致 |
管理员添加药品界面测试：
表5-3 管理员添加药品界面测试表
| 用例名称 |
药品发布测试用例 |
| 目的 |
测试药品发布功能 |
| 前提 |
用户正常登录情况下 |
| 测试流程 |
1）卖家点击药品信息管理就，然后点击添加后并填写信息。 2）点击进行提交。 |
| 预期结果 |
提交以后，页面首页会显示新的药品信息 |
| 实际结果 |
实际结果与预期结果一致 |
药品搜索功能测试：
表5-4药品搜索功能测试表
| 用例名称 |
药品搜索测试 |
| 目的 |
测试药品搜索功能 |
| 前提 |
无 |
| 测试流程 |
1）在搜索框填入搜索关键字。 2）点击搜索按钮。 |
| 预期结果 |
页面显示包含有搜索关键字的药品 |
| 实际结果 |
实际结果与预期结果一致 |
密码修改功能测试：
表5-5 密码修改功能测试表
| 用例名称 |
密码修改测试用例 |
| 目的 |
测试管理员密码修改功能 |
| 前提 |
管理员用户正常登录情况下 |
| 测试流程 |
1）管理员密码修改并完成填写。 2）点击进行提交。 |
| 预期结果 |
使用新的密码可以登录 |
| 实际结果 |
实际结果与预期结果一致 |
通过编写药房管理系统的测试用例，已经检测完毕用户登录模块、药品查看模块、药品添加模块、药品搜索模块、密码修改功能测试，通过这5大模块为药房管理系统的后期推广运营提供了强力的技术支撑。
至此，药房管理系统已经结束，在开发前做了许多的准备，在本系统的设计和开发过程中阅览和学习了许多文献资料，从中我也收获了很多宝贵的方法和设计思路，对系统的开发也起到了很重要的作用，系统的开发技术选用的都是自己比较熟悉的，比如Web、Java技术、MYSQL，这些技术都是在以前的学习中学到了，其中许多的设计思路和方法都是在以前不断地学习中摸索出来的经验，其实对于我们来说工作量还是比较大的，但是正是由于之前的积累与准备，才能顺利的完成这个项目，由此看来，积累经验跟做好准备是十分重要的事情。
当然在该系统的设计与实现的过程中也离不开老师以及同学们的帮助，正是因为他们的指导与帮助，我才能够成功的在预期内完成了这个系统。同时在这个过程当中我也收获了很多东西，此系统也有需要改进的地方，但是由于专业知识的浅薄，并不能做到十分完美，希望以后有机会可以让其真正的投入到使用之中。
[1]付恩狄,姚明亮,梁宇柔,彭伟军.基于JAVA技术的设备绝缘状态自动化监控方法[J].电气自动化,2023,45(02):36-38+41.
[2]伍德鹏,李佩学.基于SSM框架的高职院校教学办公用品管理信息系统设计研究[J].轻工科技,2023,39(01):99-101.
[3]李晋华,葛毅,李世川.嵌入Java Web服务的桌面应用开发技术研究[J].电脑编程技巧与维护,2022(11):51-53.DOI:10.16184/j.cnki.comprg.2022.11.003.
[4]沈志元,张文健.基于Java技术的医院管理系统的设计与实现[J].电脑知识与技术,2022,18(32):38-40+54.DOI:10.14004/j.cnki.ckt.2022.1994.
[5]李文友,赵静,江肇洋. 中医中央药房管理系统[P]. 江苏省：CN115331795A,2022-11-11.
[6]曹泽翰.基于SSM框架的流体力学课程虚拟仿真实验平台设计[J].信息与电脑(理论版),2022,34(20):34-36.
[7]王棋.基于SSM框架的网上摄影系统设计与实现[J].电子质量,2022(10):89-93.
[8]李思睿,郑大翔,李志芳.医院药房管理系统前端工程化设计与实现[J].软件工程,2022,25(09):18-21+4.DOI:10.19644/j.cnki.issn2096-1472.2022.009.005.
[9]王哲.基于闭环管理改造模式下的门诊药房管理系统对提高患者取药高峰时间段发药质量与缩短等候时间的影响[J].抗感染药学,2021,18(05):752-755.DOI:10.13493/j.issn.1672-7878.2021.05-035.
[10]. 360Quadrants; Best Pharmacy Management Systems In 2020 - Latest Quadrant Ranking Released By 360quadrants[J]. Computer Weekly News,2020.
[11]王颖瑞. 药房信息管理系统的设计与实现[D].北京邮电大学,2020.DOI:10.26969/d.cnki.gbydu.2020.001363.
[12]谢晓,叶德.自动化药房管理系统在医院药房中的应用价值[J].齐齐哈尔医学院学报,2020,41(12):1511-1513.
[13]苏茂泉,李志贤.智慧云药房管理系统的设计与实现[J].电子技术与软件工程,2019(17):1-2.
[14]马骥,葛君,薄旭芬,沈雁.自动化药房管理系统在医院药房中的应用[J].中医药管理杂志,2019,27(05):114-115.DOI:10.16690/j.cnki.1007-9203.2019.05.060.
[15]. Pharmacy Management System Market 2018 Global Share, Trend, Segmentation and Forecast to 2023[J]. M2 Presswire,2018.
致 谢
逝者如斯夫，不舍昼夜。转眼间，大学生会员活便已经接近尾声，人面对着离别与结束，总是充满着不舍与茫然，我亦如此，仍记得那年秋天，我迫不及待的提前一天到了学校，面对学校巍峨的大门，我心里充满了期待：这里，就是我新生活的起点吗？那天，阳光明媚，学校的欢迎仪式很热烈，我面对着一个个对着我微笑的同学，仿佛一缕缕阳光透过胸口照进了我心里，同时，在那天我认识可爱的室友，我们携手共同度过了这难忘的两年。如今，我望着这篇论文的致谢，不禁又要问自己：现在，我们就要说再见了吗？
感慨莫名，不知所言。遥想当初刚来学校的时候，心里总是想着工科学校会过于板正，会缺乏一些柔情，当时心里甚至有一点点排斥，但是随着我对学校的慢慢认识与了解，我才认识到了她的美丽，她的柔情，并且慢慢的喜欢上了这个校园，但是时间太快了，快到我还没有好好体会她的美丽便要离开了，但是她带给我的回忆，永远不会离开我，也许真正离开那天我的眼里会满含泪水，我不是因为难过，我只是想将她的样子映在我的泪水里，刻在我的心里。最后，感谢我的老师们，是你们教授了我们知识与做人的道理；感谢我的室友们，是你们陪伴了我如此之久；感谢每位关心与支持我的人。
少年，追风赶月莫停留，平荒尽处是春山。
请关注点赞+私信博主，免费领取项目源码