(with source code) Design and implementation of springboot campus second-hand trading platform

Summary

With the popularization and development of the Internet, it has become more and more common to sell and buy things online. Out of consideration for campus development, various second-hand websites have been implemented in many campuses, which improves the utilization of campus resources. efficiency. However, the manpower and financial resources needed to build most websites are generally high, and the deployment of high-powered hardware is also a hurdle, which makes most of the second-hand websites not take shape, and the post-maintenance costs of the platform have also dragged down many users. How to solve this problem? We need to find a better technology and method to reduce the response time of the website and improve the high concurrency performance of the system, improve the user experience, reduce hardware requirements, and be able to use cheaper hardware for deployment, thereby reducing the cost of the website The cost of construction. The development project of this second-hand trading platform on campus uses java technology + MYSQL database to explain various needs analysis of the topic, and then discusses the overall design and detailed design of the website, and gives the construction method of the overall structure of the website . So as to meet the needs of most second-hand websites.

Keywords : java technology; MYSQL; campus second-hand trading platform 

Abstract

With the popularization and development of the Internet, selling and buying things online has become more and more routine. For the consideration of campus development, various second-hand websites have been implemented on many campuses, which improves the utilization of campus resources. effectiveness. However, the manpower and financial resources required to build most of the websites are generally high, and the deployment of high-energy hardware is also a hurdle, so that most of the second-hand websites have not been formed, and the later maintenance costs of the platform have also dragged down many users. How to solve this problem? We need to find a better technology and method to reduce the response time of the website, improve the high concurrency performance of the system, improve the user experience, reduce hardware requirements, and be able to use cheaper hardware for deployment. cost of construction. The development project of this campus second-hand information website uses java technology + MYSQL database to explain the various needs analysis and description of the topic, and then discusses the overall design and detailed design of the website, and gives the construction method of the overall structure of the website . So as to meet the needs of most of the second-hand websites.

Keywords: java technology; MYSQL; campus second-hand information website

Table of contents

Summary

1 Introduction

1.1 Research Background

1.2 Research status at home and abroad

1.3 Paper Structure and Chapter Arrangement

1.4 Development Tools and Technologies

1.4.1 Springboot framework introduction

1.4.2 Mysql database

1.4.3 B/S structure

2 Systematic analysis of campus second-hand trading platform

2.1 Feasibility analysis

2.2 System flow analysis

2.2.1 Data flow

3.3.2 Business process

2.3 System function analysis

2.3.1 Functional Analysis

2.3.2 Non-functional analysis

2.4 System use case analysis

2.5 Summary of this chapter

3 Overall design of campus second-hand trading platform

3.1 System architecture design

3.2 System function module design

3.2.1 Overall functional module design

3.2.2 User module design

3.2.3 Comment management module design

3.2.4 Commodity Management Module Design

3.2.5 Order Management Module Design

3.3 Database design

3.3.1 Database conceptual structure design

3.3.2 Database logical structure design

4 Detailed design and implementation of campus second-hand trading platform

4.1 User Function Module

4.1.1 Front page interface

4.1.2 Buyer registration interface

4.1.3 Buyer login interface

4.1.4 Commodity information interface

4.1.5 Shipping address interface

4.1.6 Product Details Interface

4.1.7 My order interface

4.2 Seller function modules

4.2.1 Mall management interface

4.2.2 Order list interface

4.3 Administrator function module

4.3.1 User Management Interface

4.3.2 Message management interface

4.3.3 Commodity information management interface

4.3.4 Announcement information list interface

5 system test

5.1 Purpose of system testing

5.2 System Test Cases

5.3 System test results

in conclusion

references

thanks

1 Introduction

1.1 Research Background

At present, most industries are gradually bringing e-commerce informatization into their own enterprises, mainly Internet platforms dominated by e-commerce services. For example, if you are currently focusing on second-hand transactions on campus, you must closely focus on second-hand campus transactions. Through the empowerment of the Internet platform, it can provide intelligent services to the second-hand market, and improve the utilization efficiency of campus resources while providing users with substantial convenience. Therefore, the campus second-hand trading platform is more in line with the needs of current campus users, and can better adapt to the current competitive pressure of the second-hand industry [1]. The campus second-hand trading platform uses the "Internet +" C2C service as a model. While providing users with online independent selection of second-hand goods, it can help sellers realize the utilization rate of second-hand, and can also make efforts for the intelligent development of the second-hand industry.

1.2 Research status at home and abroad

Due to the daily development of computer technology in the past few years, in modern life, all kinds of information processing operations we need are done by using computers. Maintained [2]. Therefore, it is necessary to realize the electronic management of second-hand transactions on campus, and improve the management efficiency and sales efficiency of second-hand transactions on campus.

Because the traditional second-hand transaction methods at home and abroad are based on manual work, and human energy and work accuracy are limited, the traditional second-hand transaction data management methods will inevitably have shortcomings such as low efficiency and low accuracy, and are accompanied by It leads to a large waste of human resources [3]. In the work of management, the computer machines involved are better than humans, and can meet the requirements of speed, accuracy, and low resource consumption. Based on these remarkable advantages, if we can design a complete campus second-hand trading platform that meets the needs of specific campus users, the service quality of second-hand trading will be greatly improved. With such a campus second-hand trading platform, buyers only need to log in to the system to see all the second-hand goods and make purchases, and sellers only need to log in to the system to sell second-hand goods. Management personnel only need a small number of professionals Perform daily data review, management and regular maintenance on the database [4]. During the whole process, the user only needs to provide a small amount of necessary information, and most of the data processing work is completed by the database and related programs, saving a lot of time. If there is an error in some part of the information in the database, the user can reduce the time and effort spent in the troubleshooting process by batch modification and other methods. Therefore, it is very necessary to develop a competent campus second-hand trading platform for the campus.

1.3 Thesis structure and chapter arrangement

The thesis will be arranged in layers, except for the abstract acknowledgments and references, the main text will also analyze the requirements of the website, explain the general design and implemented functions, and finally list some commissioning records. The main structure of the thesis is as follows:

Chapter 1: Introduction. The first chapter mainly introduces the background of the subject research, the status quo of system development and the research content and main work of this paper.

Chapter Two: System Requirements Analysis. The second chapter mainly conducts demand analysis from the aspects of system users and functions.

Chapter Three: System Design. The third chapter mainly carries on the function design to the system frame, the system function module, the database.

Chapter Four: System Realization. The fourth chapter mainly introduces the construction of the system framework and the realization of the system interface.

Chapter Five: System Testing. Chapter 5 mainly tests some interfaces of the system and tests the main functions

Chapter Six: Summary.

1.4 Development tools and technologies

The front-end part of the system is developed based on the MVVM model, using the B/S model, and the back-end part is developed based on the Java springboot framework.

Front-end part: The front-end framework adopts the popular progressive JavaScript framework Vue.js. Use Vue-Router and Vuex to achieve dynamic routing and global state management, Ajax to achieve front-end and back-end communication, Element UI component library to make the page quickly prototype, and the front-end of the project realizes responsiveness through grid layout, which can be adapted to PC, tablet, mobile, etc. Perfect layout display for different screen sizes.

Back-end part: use springboot as the development framework, and integrate MyBatis, Redis and other related technologies at the same time.

Software development environment and development tools:

Operating system: Windows 10, Windows 7, Windows 8

Development language: Java

Use the framework: springboot

Front-end technology: JavaScript, VUE.js (2.X), css3

Development tools: IDEA (2020 version)/MyEclipse (10)/Eclipse, Visual Studio Code

Database: MySQL 5.7.26 (version number)

Database management tools: phpstudy/Navicat

JDK version: Java sdk8

Maven:apache-maven 3.8.3-bin

Tomcat:apache-tomcat-7.0.88

1. 4 . 1 S springboot framework introduction 

The Spring framework is an open source application framework on the Java platform that provides a container with inversion of control features. Although the Spring framework itself has no restrictions on the programming model, its frequent use in Java applications made it so popular that it was later used as a supplement or even a substitute for the EJB (EnterpriseJavaBeans) model. The Spring framework provides a series of solutions for development, such as using the core features of inversion of control, and implementing inversion of control through dependency injection to realize the containerization of the management object life cycle, using aspect-oriented programming for declarative transaction management, and integrating A variety of persistence technologies manage data access, provide a large number of excellent web frameworks to facilitate development, and so on. The Spring framework has the feature of inversion of control (IOC). IOC is designed to facilitate project maintenance and testing. It provides a method for unified configuration and management of Java objects through the Java reflection mechanism. The Spring framework uses the container to manage the life cycle of objects. The container can configure objects by scanning XML files or specific Java annotations on classes. Developers can obtain objects through dependency lookup or dependency injection. Aspect Oriented Programming(AOP) framework, the Spring AOP framework is based on the proxy mode, and can be configured at runtime; the AOP framework is mainly modularized for the cross concerns between modules. The AOP framework of the Spring framework only provides basic AOP features. Although it cannot be compared with the AspectJ framework, it can also meet the basic needs through integration with AspectJ. Functions such as transaction management and remote access under the Spring framework can be realized by using Spring AOP technology. Spring's transaction management framework brings an abstraction mechanism to the Java platform that enables local and global transactions, as well as nested transactions, to work with savepoints and in almost any environment on the Java platform. Spring integrates multiple transaction templates. The system can configure transactions through transaction templates, XML or Java annotations, and the transaction framework integrates functions such as messaging and caching. Spring's data access framework addresses common difficulties developers encounter when using databases in their applications. It not only provides support for all popular data access frameworks such as Java: JDBC, iBATS/MyBATIs, Hibernate, Java Data Objects (JDO), ApacheOJB and Apache Cayne, but also can be used with Spring's transaction management to provide data access Flexible abstraction. The Spring framework initially did not intend to build its own Web MVC framework . During the development process, its developers believed that the separation between the presentation layer and the request processing layer of the existing Struts Web framework and between the request processing layer and the model was not enough, so they created Spring MVC.

1.4.2 Mysql database

Mysql Database, usually abbreviated as Mysql, is a relational database management system. Mysql database system is one of the most popular relational database management systems at present. Its system has good portability, powerful functions and is very convenient to use. Mysql supports many systems and hardware, including HP-UX, Linux, MicrosoftWindows, SunSolaris, AppleMac, etc.

Features of Mysql system:

(1) The architecture of Mysql's multi-thread server enables it to support multi-user and high-performance transaction processing of big data with only a few resources;

(2) Mysql supports a large amount of multimedia data, such as sound, animation, binary graphics and multidimensional data structures, etc.;

(3) Mysql provides a security and confidentiality management system with good security, consistency and integrity;

(4) Possess new distributed database capabilities and distributed processing capabilities;

(5) Provide some high-level language interface software, which can help rapid development of client-based applications, with good portability, connectivity and compatibility.

The logical structure of Mysql database includes table space (tablespace), segment (segment), range (extend), data block (datablock), and schema object (schemaobject). Each database can be logically divided into one or more table spaces, and each table space is composed of one or more data files. Mysql database is divided into system table space and non-system table space, each Mysql database contains a system table space called SYSTEM.

1. 4 . 3  B/S structure 

The B/S (browser/server) structure is the current mainstream network structure model. It can concentrate the core functions of the system on the server, and can help system developers simplify operations and facilitate maintenance and use. Users only need to install 360 browser, Google browser, QQ browser and other popular browsers on the client side, and install databases such as sqlserver and mysql database in the computer. The installed browser interacts with the server-side database for information and data. Many things that special software can do can also be realized by using the B/S structure mode, which can combine technologies such as Web browser technology, ActiveX technology and various scripting languages. Help program developers save a lot of development costs. At present, the B/S structure has become the mainstream structure of program development. Its best feature is that it has no location restrictions and does not need to install special software. Laptops or computers can access the system with Internet access. The system uses B/S for development, which will save trouble in the later system maintenance. It does not need to operate on the server for all problems. Simple client-side processing can solve some problems. The developed program will also enhance the interaction with users. The browser can be refreshed in real time to update the local data information of the program.

 

2 Systematic analysis of campus second-hand trading platform

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. Further, feasibility analysis is carried out on system development, usually including technical feasibility, economic feasibility, etc. Feasibility analysis is also an analysis from the overall perspective of the project. Then it is to analyze the specific needs of the project, and the means of analysis are generally realized through the user's use case diagram. The following is a detailed introduction.

2.1 Feasibility analysis

(1) Economic feasibility:

Economic feasibility here only represents the operation and maintenance cost of the website, and the development cost is not considered here.

At present, the number of campus second-hand trading platforms under this model is increasing day by day, and the number of online shopping has become popular and popular. The number of users is on the rise. When the number of users is large, the operation and maintenance costs can be filled by advertising fees, including development costs.

So there is no question of economic viability.

(2) Operation feasibility:

The design of this project refers to several development cases of websites under this mode, analyzes their operation interface, combines many cases together, and highlights the people-oriented and simplified operation, so people with basic computer knowledge can operate this project.

Therefore, there is no problem with operability.

(3) Technical feasibility:

Technical feasibility refers to the feasibility of building a framework, and the acceptability of system technology upgrades when better technologies emerge, and the ratio of development time to cost.

The existing java technology can cater to the construction of all e-commerce systems. When developing this campus second-hand trading platform, I used springboot+MYSQL to run the overall program.

In summary, there is no problem with the technical feasibility.

(4) Legal feasibility:

From the perspective of developers, springboot and MYSQL are open source and free online, and there will be no legal disputes in terms of intellectual property rights.

From the perspective of user use, as long as no contraband is sold on the system, a treaty agreement is made on the system, and illegal payments are eliminated.

In summary, there is no question of legal feasibility.

2.2 System flow analysis

2.2.1 Data flow

The main purpose of the campus second-hand trading platform is to realize the online purchase of second-hand goods. Figure 2-1 is the data flow diagram of the system.

 

Figure 2-1 Expansion diagram of product purchase operation

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

2.3 System function analysis

2.3.1 Functional Analysis

According to the role of the campus second-hand trading platform, I divided it into three parts: user management module, seller management module and administrator management module.

User management module:

(1) User registration and login: the user registers as a member and logs in to the campus second-hand trading platform; the user adds, deletes, modifies and checks personal information, such as personal information and password changes.

(2) Users view products: Users browse product information, and after finding products they like, they can purchase + comment + bookmark.

(3) Campus information: Users browse information and view campus information released by administrators.

(4) Message board: Users can view, publish and comment on the submissions submitted by users under the menu of message board.

(5) Commodity purchase: The user can purchase additional commodities that he likes. In the shopping cart, when the user confirms that the submission is completed, it will be submitted to the backend system of the server and an order will be generated.

(6) My order: After the user submits the order, he can manage the submitted order.

Seller Management Module:

(1) My message: The seller replies and deletes the message submitted by the user.

(2) Mall management: administrators can add, delete, modify and check existing commodities in the campus second-hand trading platform.

(3) Order list: View the purchased my product orders and manage the submitted orders.

Administrator management module:

(1) User management: The administrator can control the user information registered on the front desk, and can also control the administrator information.

(2) Campus information management: The administrator can add, delete, modify and check the campus information displayed on the campus second-hand trading platform in the background.

(3) Message management: administrators can add, delete, modify and check the messages submitted by users in the campus second-hand trading platform and the classification of messages.

(4) Classification management: The administrator controls the classification of commodities in the campus second-hand trading platform.

(5) Mall management: The administrator controls the commodity orders submitted by the seller.

(6) System management: The administrator can publish the carousel picture displayed on the homepage of the campus second-hand trading platform and some announcements in the system to the system, so that users can view system information in a timely manner and make reasonable arrangements.

2.3.2 Non-functional analysis

The non-functional requirements of the campus second-hand trading platform, such as the security, reliability, performance, and scalability of the campus second-hand trading platform. Specifically, it can be expressed in the following table 3-1:

Table 3-1 Non-functional Requirements Table of Campus Second-hand Trading Platform

safety

It mainly refers to the installation of the campus second-hand trading platform database, the use of the database and the setting of passwords must comply with the regulations.

reliability

Reliability means that the campus second-hand trading platform can install the user's instructions to operate. After testing, the reliability is more than 90%.

performance

Performance is a necessary condition for campus second-hand trading platforms 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 campus second-hand trading platform to operate.

maintainability

The maintainability of the development of the campus second-hand trading platform is very important. After testing, there is no problem with the maintainability

2.4 System use case analysis

Through the analysis of 2.3 functions, the use case diagram of the second-hand trading platform on this campus is obtained:

Figure 2-3 shows an example of a user role.

 

Figure 2-3 User role use case diagram of campus second-hand trading platform

The administrator on the web background management maintains all the data information in the second-hand trading platform of the entire campus. Figure 2-5 shows an example of an administrator role.

 

figure 2-4Use case diagram of the administrator role of the campus second-hand trading platform

An example of a seller role is shown in Figure 2-5.

 

Figure 2-5 Use case diagram of the role of sellers on campus second-hand trading platform

2.5 Summary of this chapter

This chapter mainly determines the functions to be realized by the entire campus second-hand trading platform through the feasibility analysis, process analysis, functional demand analysis, and system use case analysis of the campus second-hand trading platform. At the same time, it also provides standards for the code implementation and testing of the campus second-hand trading platform.

3 The overall design of the campus second-hand trading platform

This chapter mainly discusses the functional module design and database system design of the campus second-hand trading platform.

3.1 System architecture design

The campus second-hand trading platform is divided into three layers in terms of architecture: presentation layer (UI), business logic layer (BLL) and data layer (DL).

                                        

 

Figure 3-1 System architecture design diagram of campus second-hand trading platform

 

Presentation layer (UI): Also known as the UI layer, it mainly completes the UI interaction function of the second-hand trading platform on campus. A good UI can improve the user experience of users and enhance the comfort of users when using the second-hand trading platform on campus. The UI interface design should also be adapted to different versions of campus second-hand trading platforms and resolutions of different sizes to achieve good compatibility. The requirements for UI interaction functions are reasonable, and users must obtain consistent interaction results when performing interactive operations, which requires a good connection between the presentation layer and the business logic layer.

Business logic layer (BLL): It mainly completes the data processing function of the campus second-hand trading platform. The data transmitted by the user from the presentation layer is processed and delivered to the data layer through the business logic layer, and the data read by the system from the data layer is processed and delivered to the presentation layer through the business logic layer.

Data layer (DL): Since the data of the campus second-hand trading platform is placed in the mysql database on the server side, the part that belongs 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 Data storage and management functions of the campus second-hand trading platform.

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 the campus second-hand trading platform were analyzed according to the requirements. Then the next step is to start designing the structure, main functions and database of the campus second-hand trading platform. The campus second-hand trading platform is based on the analysis of the requirements in the previous chapters, and its overall design module diagram is shown in Figure 3-2.

 

Figure 3-2 Functional module diagram of the campus second-hand trading platform

3.2.2 User module design

The background manager can add, delete, modify and check the users registered in the front desk. The structure diagram of the user module is as follows:

 

Figure 3-3 User module structure diagram

3.2.3 Comment management module design

The campus second-hand trading platform is an open platform of communication nature. Member users can communicate on the platform to increase the interaction between users. But at the same time, in order to better regulate 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 Comment module structure diagram

3.2.4 Commodity management module design

The campus second-hand trading platform needs to store a lot of commodity information, and its module function structure, the specific structure diagram is as follows:

 

Figure 3-5 Mall module structure diagram

3.2.5 Design of order management module

One of the most important functions of the campus second-hand trading platform is to purchase. Its module function structure, the specific structure diagram is as follows:

 

Figure 3-5 Order module structure diagram

3.3 Database design

Database design generally includes three major processes: requirements analysis, conceptual model design, and database table establishment. Requirements analysis has been explained in the previous chapters, and conceptual model design has two parts: conceptual model and logical structure design.

3.3.1 Conceptual structure design of database

The following is the ER entity relationship diagram of the main database tables in the second-hand trading platform on campus.

Figure 3-6 The overall ER relationship diagram of the campus second-hand trading platform

 

According to the database ER relationship diagram of the campus second-hand trading platform, it can be concluded that the campus second-hand trading platform needs many ER diagrams. Here are some main database ER model diagrams.

 

Figure 3-7 Buyer Information ER Relationship Diagram

 

Figure 3-8 Order information ER relationship diagram

3.3.2 Database logical structure design

From the total ER relationship diagram in the campus second-hand trading platform in the previous section, it can be concluded that a lot of data tables need to be created. Here I mainly list several major database table structure designs.

address

Field Name

type

length

not null

primary key

field description

address_id

int

11

no

primary key

Shipping address

name

varchar

32

yes

Name

phone

varchar

13

yes

cell phone

postcode

varchar

8

yes

post code

address

varchar

255

no

address

user_id

mediumint

8

no

User ID

create_time

timestamp

0

no

creation time

update_time

timestamp

0

no

update time

default

tinyint

1

no

default judgment

buyers

Field Name

type

length

not null

primary key

field description

buyers_id

int

11

no

primary key

Buyer ID

buyer_number

varchar

64

no

buyer number

buyer_gender

varchar

64

yes

buyer gender

buyer_age

varchar

64

yes

buyer's age

buyer_school

varchar

64

yes

Buyer School

buyer_address

varchar

64

yes

Buyer's address

buyer_birthday

date

0

yes

buyer's birthday

brief_introduction

varchar

64

yes

Buyer Profile

examine_state

varchar

16

no

Approval Status

recommend

int

11

no

Intelligent Recommendation

user_id

int

11

no

User ID

create_time

datetime

0

no

creation time

update_time

timestamp

0

no

update time

cart

Field Name

type

length

not null

primary key

field description

cart_id

int

11

no

primary key

shopping cart ID

title

varchar

64

yes

title

img

varchar

255

no

picture

user_id

int

10

no

User ID

create_time

timestamp

0

no

creation time

update_time

timestamp

0

no

update time

state

int

1

no

Status in use, expired

price

double

8

no

unit price

price_ago

double

8

no

original price

price_count

double

10

no

total price

num

int

8

no

quantity

goods_id

mediumint

8

no

commodity id

type

varchar

64

no

Categories

description

varchar

255

yes

describe

comment

Field Name

type

length

not null

primary key

field description

comment_id

int

11

no

primary key

Comment ID

user_id

int

11

no

Reviewer ID

reply_to_id

int

11

no

Reply to comment ID

content

longtext

0

yes

content

nickname

varchar

255

yes

Nick name

avatar

varchar

255

yes

Avatar address

create_time

timestamp

0

no

creation time

update_time

timestamp

0

no

update time

source_table

varchar

255

yes

source table

source_field

varchar

255

yes

source field

source_id

int

10

no

source ID

order

Field Name

type

length

not null

primary key

field description

order_id

int

11

no

primary key

order ID

order_number

varchar

64

yes

order number

goods_id

mediumint

8

no

commodity id

title

varchar

32

yes

product title

img

varchar

255

yes

product picture

price

double

10

no

price

price_ago

double

10

no

original price

num

int

8

no

quantity

price_count

double

8

no

total price

norms

varchar

255

yes

Specification

type

varchar

64

no

Categories

contact_name

varchar

32

yes

Contact name

contact_email

varchar

125

yes

Contact email

contact_phone

varchar

11

yes

contact phone

contact_address

varchar

255

yes

Recipient address

postal_code

varchar

9

yes

zip code

user_id

int

10

no

Buyer ID

merchant_id

mediumint

8

no

Merchant ID

create_time

timestamp

0

no

creation time

update_time

timestamp

0

no

update time

description

varchar

255

yes

describe

state

varchar

16

no

Order Status Pending Payment

second_hand_mall

Field Name

type

length

not null

primary key

field description

second_hand_mall_id

int

11

主键

二手商城ID

seller

int

11

卖家

remarks

varchar

64

备注

hits

int

11

点击数

recommend

int

11

智能推荐

cart_title

varchar

125

标题

cart_img

text

0

封面图

cart_description

varchar

255

描述

cart_price_ago

double

8

原价

cart_price

double

8

卖价

cart_inventory

int

11

商品库存

cart_type

varchar

64

商品分类

cart_content

longtext

0

正文产品的主体内容

cart_img_1

text

0

主图1

cart_img_2

text

0

主图2

cart_img_3

text

0

主图3

cart_img_4

text

0

主图4

cart_img_5

text

0

主图5

create_time

datetime

0

创建时间

update_time

timestamp

0

更新时间

seller

字段名称

类型

长度

不是null

主键

字段说明

seller_id

int

11

主键

卖家ID

seller_number

varchar

64

卖家编号

seller_gender

varchar

64

卖家性别

age

varchar

64

卖家年龄

seller_school

varchar

64

卖家学校

address

varchar

64

卖家地址

seller_birthday

date

0

卖家生日

brief_introduction

varchar

64

卖家简介

examine_state

varchar

16

审核状态

recommend

int

11

智能推荐

user_id

int

11

用户ID

create_time

datetime

0

创建时间

update_time

timestamp

0

更新时间

sign_in_score

字段名称

类型

长度

不是null

主键

字段说明

sign_in_score_id

int

11

主键

签收评分ID

order_number

varchar

64

订单编号

purchase_goods

varchar

64

购买商品

commodity_price

varchar

64

商品价格

sign_in_status

varchar

64

签收状态

star_rating

varchar

64

星级评分

purchase_user

int

11

购买用户

business

int

11

商家

remarks

longtext

0

备注

recommend

int

11

智能推荐

create_time

datetime

0

创建时间

update_time

timestamp

0

更新时间

4 校园二手交易平台详细设计与实现

校园二手交易平台的详细设计与实现主要是根据前面的校园二手交易平台的需求分析和校园二手交易平台的总体设计来设计页面并实现业务逻辑。主要从校园二手交易平台界面实现、业务逻辑实现这两部分进行介绍。

4.1用户功能模块

4.1.1 前台首页界面

当进入校园二手交易平台的时候,首先映入眼帘的是系统的导航栏,下面是轮播图以及系统内容,其主界面展示如下图4-1所示。

 

图4-1 前台首页界面图             

4.1.2 买家注册界面

不是校园二手交易平台中正式会员的是可以在线进行注册的,如果你没有本校园二手交易平台的账号的话,添加“注册”,当填写上自己的账号+密码+确认密码+昵称+邮箱+手机号等后再点击“注册”按钮后将会先验证输入的有没有空数据,再次验证密码和确认密码是否是一样的,最后验证输入的账户名和数据库表中已经注册的账户名是否重复,只有都验证没问题后即可会员注册成功。其用会员注册界面展示如下图4-2所示。

 

图4-2 前台会员注册界面图       

4.1.3 买家登录界面

校园二手交易平台中的前台上注册后的会员是可以通过自己的账户名和密码进行登录的,当会员输入完整的自己的账户名和密码信息并点击“登录”按钮后,将会首先验证输入的有没有空数据,再次验证输入的账户名+密码和数据库中当前保存的用户信息是否一致,只有在一致后将会登录成功并自动跳转到校园二手交易平台的首页中;否则将会提示相应错误信息,用户登录界面如下图4-3所示。

 

图4-3买家登录界面图         

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.2 卖家功能模块

4.2.1商城管理界面

卖家进入后台后点击“商城管理”,能够看到自己发布的二手信息,对二手商品进行管控。界面如下图4-8所示。

 

图4-8 商城管理界面图    

4.2.2订单列表界面

卖家进入后台后点击“订单列表”,能够看到用户购买自己商品的时候提交的订单。界面如下图4-9所示。

 

图4-9 订单列表界面图    

4.3管理员功能模块

4.3.1 用户管理界面

校园二手交易平台中的管理人员是可以对前台注册的用户进行管理的,也可以对管理员进行管控。界面如下图4-10所示。

 

图4-10用户管理界面图

4.3.2留言管理界面

校园二手交易平台中的管理人员是可以对前台用户发布的留言进行管控的,界面如下图4-11所示。

 

图4-11留言界面图      

4.3.3 商品信息管理界面

校园二手交易平台中的管理人员是可以对校园二手交易平台内发布的商品进行维护和管理的,支持增删改查操作。界面如下图4-12所示。

 

图4-12商品信息管理界面图         

4.3.4 公告信息列表界面

校园二手交易平台中的管理人员是可以对校园二手交易平台内的公告信息进行维护和管理的。公告信息列表界面如下图4-13所示。

 

图4-13公告信息列表界面图        

5系统测试

5.1系统测试的目的

系统开发到了最后一个阶段那就是系统测试,系统测试对软件的开发其实是非常有必要的。因为没什么系统一经开发出来就可能会尽善尽美,再厉害的系统开发工程师也会在系统开发的时候出现纰漏,系统测试能够较好的改正一些bug,为后期系统的维护性提供很好的支持。通过系统测试,开发人员也可以建立自己对系统的信心,为后期的系统版本的跟新提供支持。

5.2 系统测试用例

系统测试包括:用户登录功能测试、商品展示功能测试、商品添加、商品搜索、密码修改功能测试,如表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.3 系统测试结果

通过编写校园二手交易平台的测试用例,已经检测完毕用户登录模块、商品查看模块、商品添加模块、商品搜索模块、密码修改功能测试,通过这5大模块为校园二手交易平台的后期推广运营提供了强力的技术支撑。

结论

至此,校园二手交易平台已经结束,在开发前做了许多的准备,在本系统的设计和开发过程中阅览和学习了许多文献资料,从中我也收获了很多宝贵的方法和设计思路,对系统的开发也起到了很重要的作用,系统的开发技术选用的都是自己比较熟悉的,比如Web、java技术、MYSQL,这些技术都是在以前的学习中学到了,其中许多的设计思路和方法都是在以前不断地学习中摸索出来的经验,其实对于我们来说工作量还是比较大的,但是正是由于之前的积累与准备,才能顺利的完成这个项目,由此看来,积累经验跟做好准备是十分重要的事情。

当然在该系统的设计与实现的过程中也离不开老师以及同学们的帮助,正是因为他们的指导与帮助,我才能够成功的在预期内完成了这个系统。同时在这个过程当中我也收获了很多东西,此系统也有需要改进的地方,但是由于专业知识的浅薄,并不能做到十分完美,希望以后有机会可以让其真正的投入到使用之中。

参考文献

[1]狄喜凤.基于学生信息管理系统的软件测试策略研究[J].电子技术与软件工程,2021(02):82-83.

[2]张嘉豪,赵亮,翁铭隆,张华俊,李文欣.基于springboot+SpringBoot技术实现服务器监控的研究[J].科学技术创新,2020(33):101-102.

[3]郭俊杰. 基于springboot的线下商圈服务管理系统设计与实现[D].桂林理工大学,2020.

[4]康军林.辽宁省河长制信息管理系统建设的实践与思考[J].水资源开发与管理,2020(06):80-84.

[5]沈世平,林平,赵亚南,谢振平,刘渊.无锡河长制综合信息平台建设与思考[J].江苏水利,2020(06):25-31.

[6]唐湘茜,张俊,王源楠,邓晶.河长制信息管理系统[J].水利水电快报,2020,41(04):6-7.

[7]周彪. 基于springboot框架的Java后端代码生成器的设计与实现[D].大连理工大学,2020.

[8]贾少燕, 基于互联网+的智慧河长制信息管理系统研发. 河南省,河南省水利勘测设计研究有限公司,2020-04-02.

[9]邹秀清,罗得寸,林平,沈世平,谢振平,王玉珏,丁勇.基于区块链的河长制水质信息存证系统[J].应用科学学报,2020,38(01):65-80.

[10]Yuxiang Hou. The design and implementation of the framework for Spring+SpringMVC+MyBatis in the development of Web application[A]. Institute of Management Science and Industrial Engineering.Proceedings of 2019 4th International Industrial Informatics and Computer Engineering Conference(IIICEC 2019)[C].Institute of Management Science and Industrial Engineering:计算机科学与电子技术国际学会(Computer Science and Electronic Technology International Society),2019:6.

[11]马强.河长制背景下的智慧信息管理平台建设探究[J].地下水,2019,41(05):155-156.

[12]张爽.铁岭市河长制信息管理平台的研发与应用[J].吉林水利,2019(07):60-62.

[13]夏添,刘发永,姜跃昆,马色伍,陈雨.成都市河长制管理信息系统的设计与实践[J].四川水利,2019,40(03):113-118.

[14]江金娜. 高校成人教育学生信息管理系统的分析与设计[D].广东工业大学,2019.

[15]王禹杰. “互联网 智慧河长”信息管理系统设计与实现[D].合肥工业大学,2019.

[16]阚琳.整体性治理视角下河长制创新研究——以江苏省为例[J].中国农村水利水电,2019(02):39-43.

[17]陈志忠.数据挖掘聚类算法在学生信息管理系统中的应用[J].电脑知识与技术,2017,13(24):21-22.

[18]王微漪. 基于Web的高职院校学生信息管理系统的设计与实现[D].北京工业大学,2017.

[19]徐波. 数字化校园建设中学生信息管理系统的设计与实现[D].湖北工业大学,2016.

[20]赵嫚.学生宿舍信息管理系统的设计与应用[J].科技展望,2016,26(27):5+66.

致  谢

逝者如斯夫,不舍昼夜。转眼间,大学生会员活便已经接近尾声,人面对着离别与结束,总是充满着不舍与茫然,我亦如此,仍记得那年秋天,我迫不及待的提前一天到了学校,面对学校巍峨的大门,我心里充满了期待:这里,就是我新生活的起点吗?那天,阳光明媚,学校的欢迎仪式很热烈,我面对着一个个对着我微笑的同学,仿佛一缕缕阳光透过胸口照进了我心里,同时,在那天我认识可爱的室友,我们携手共同度过了这难忘的两年。如今,我望着这篇论文的致谢,不禁又要问自己:现在,我们就要说再见了吗?

Feeling inexplicable, do not know what to say. When I first came to school, I always thought that the engineering school would be too rigid and lack some tenderness. At that time, I even felt a little repulsive, but as I gradually got to know and understand the school, I realized that Her beauty, her tenderness, and she gradually fell in love with this campus, but the time is too fast, and I will leave before I fully appreciate her beauty, but the memories she brings to me will never be Leave me, maybe my eyes will be full of tears on the day I really leave, I am not because I am sad, I just want to reflect her appearance in my tears and engrave it in my heart. Finally, I would like to thank my teachers for teaching us knowledge and principles of life; thank my roommates for accompanying me for so long; and thank everyone who cared and supported me.

Young man, don't stay after chasing the wind and the moon, the plains are full of spring mountains.

Please pay attention to like + private message blogger, get the source code of the project for free

Guess you like

Origin blog.csdn.net/Q_3461074420/article/details/131640201