Contents
1 Introduction 1
1.1 Research Background 1
1.2 Purpose and Significance 1
1.3 Development Tools and Technology 1
2 Requirements Analysis 3
2.1 Functional Requirements Analysis 3
2.1.1 Website Foreground Functions 3
2.1.2 Website Background Functions 3
2.2 Performance Analysis 3
2.3 System User Cases Figure 4
3 System Design 5
3.1 System Overall Design 5
3.2 Database Analysis and Design 5
3.2.1 Database Conceptual Design 6
3.2.2 Database Physical Structure 7
4 System Main Function Realization 11
4.1 System Registration Page Realization 11
4.2 System Login Page Realization 12
4.3 Realization of the front desk function of the system 14
4.3.1 First-level classification module 14 4.3.2
Commodity module 16
4.3.3 Shopping module 22
4.3.4 Order module 24
4.3.5 Message module 26
4.4 System background function realization 27
4.4.1 User module 27
4.4.2 Primary classification module 28
4.4.3 Secondary classification module 32
4.4.4 Commodity classification module 36
4.4.5 Message management module 38
5 System testing and maintenance 40
5.1 System test environment 40
5.1.1 Hardware environment 40
5.1.2 Software environment 40
5.2 System test content 40
5.3 System maintenance 41
6 Summary 42
7 References 43 8
Acknowledgments 44
2 Requirements analysis
2.1 Functional requirements analysis
2.1.1 Website front desk function
1 .Homepage: Provide a website homepage, displaying the trademark of the company, the login and registration of the website users, the first-level classification of all commodities, the display of popular commodities and the latest commodities, etc.
2. User registration: complete the use of the registration function for users who have not yet registered, involve data validity verification in the registration process, and use ajax to complete the asynchronous verification of whether the user name has been registered.
3. User login: The login operation provided for registered and activated users.
4. User exit: For logged-in users, exit the system.
5. Product display on the home page: display the latest and popular products.
6. Product display on the category page: Display all products under the category according to the first-level classification and the second-level classification.
7. Product detail display: When you click on a product, you can display the specific detailed information of the product.
8. Shopping cart: used to store the user's shopping content, and the user can modify his shopping cart according to his own situation.
9. Orders: For users who have logged in, they can pay for the contents of the shopping cart to generate orders, and can pay or view their own orders.
10. Message sharing: The website has opened a separate message sharing area for logged-in users to freely post comments, share experience information, and communicate and interact.
2.1.2 Background functions of the website
1. Administrator login: The administrator logs in according to the account and password.
2. First-level and second-level category management of commodities: managers can manage the first-level and second-level categories displayed on the front desk, including adding, deleting, and modifying operations.
3. Commodity management: The administrator can manage the commodities displayed on the front desk, including adding, modifying, deleting, and querying functions, and can also upload commodity pictures.
4. User management: The administrator can view all information of all users who have registered in the website.
2.2 Performance analysis
Response time:
ignoring network, hardware and plug-in factors, based on local tests, the response time of the foreground is 0.8 seconds, and the response time of background operations is 0.9 seconds.
3 System design
3.1 Overall design of the system
The development of the system adopts the B/S mode, and the construction of the whole system is based on the ssm (Spring+SpringMvc+MyBatis) integration framework.
In-depth study of the JavaEE architecture, each framework selected in the technology selection of the project is analyzed and studied separately. SpringMvc is a web-side framework. Mybatis is a lightweight persistence layer framework that provides the mapping between persistent classes and databases in an object-oriented manner. It is an excellent ORM framework. Spring is also a lightweight framework, and its IOC and AOP ideas are worth learning for architects. Through the integration of the three frameworks, a scalable, portable, and maintainable software system can be easily constructed.
The SSM framework is currently the most popular and mature set of open source frameworks in the J2EE field. It is based on the MVC design pattern and gives full play to the advantages of MVC. SSM is a set of lightweight framework. Compared with EJB, SSM inherits its advantages and has obvious improvement in development and execution efficiency. For developers, it is easier to learn and master than EJB . At present, the SSM framework is also being continuously optimized and maintained, and its operation is becoming more and more stable.
According to the above function analysis, the system function module structure diagram is obtained as shown in Figure 3-1:
Figure 3-1 Structure diagram of system function modules
package com.shop.Utils;
import java.util.List;
public class PageBean<T> {
private int page;//第几页
private int totlePage;//一共多少页
private int limitPage;//每页多少个
private List<T> list;//目标集合
public int getPage() {
return page;
}
public void setPage(int page) {
this.page = page;
}
public int getTotlePage() {
return totlePage;
}
public void setTotlePage(int totlePage) {
this.totlePage = totlePage;
}
public int getLimitPage() {
return limitPage;
}
public void setLimitPage(int limitPage) {
this.limitPage = limitPage;
}
public List<T> getList() {
return list;
}
public void setList(List<T> list) {
this.list = list;
}
public String toString() {
return "PageBean [page=" + page + ", totlePage=" + totlePage
+ ", limitPage=" + limitPage + ", list=" + list + "]";
}
}
