Course design report - supermarket cash register system javaweb (with source code)

Table of contents

1. System requirements analysis

1.1Problem description

1.2 Functional requirements

2. Outline design

2.1 Overall system design

2.2. Functions of each module

2.2.1 Interface of content module

2.2.2 Interface of order module

2.2.3 Interface of payment module

2.2.4 File download interface

3. Detailed design

3.1 Front-end module design

3.1.1 The product display interface is designed as follows

3.1.2 The customer order interface design is as follows

3.1.3 Member verification design is as follows

3.1.4 The export sales status is designed as follows

3.2 Backend module design

3.2.1 The project structure is shown in the figure:

3.2.2 Four modules are designed:

3.2.3 Content module design ideas

3.2.4 Design idea of ​​order module

3.2.5 Design idea of ​​pay payment module

3.2.6 Design ideas for file downloading

3.2.7 java class diagram

3.3 Database design (underscore is the primary key)

3.3.1 Two-dimensional table

3.3.2 is 图

4. Run the test

4.1 Content page function test

4.1.1 Query product list test

4.1.1 Test new products

4.1.2 Modify functional tests

4.1.3 Delete functional test

4.1.3 Add order function test

4.2 Order page function test

4.2.1 Display order list and payment amount information function test

4.2.2 Payment function test

4.2.3 Member verification function test

4.3 Member verification function (written in 4.2.3) is omitted

4.4 Export sales function test

5. Experience

6. Appendix

6.1 Source code

7. Scoring Form

1. System requirements analysis

1.1 Problem description

Supermarket cashier system

The cashier enters the customer's membership card number (if there is a card) and the purchased item number. Retrieving the relevant price information from the database, returning this information to the cashier, and at the same time, the total sales volume at the cashier, the remaining amount of the relevant types of goods, and the consumption situation of the cardholder customer are submitted to the database for storage for query.

In addition, the customer's consumption status and personal information will not be recorded for purchases without a card. If a customer without a card purchases more than 200 yuan at a time, a membership card can be issued, and he can enjoy a 10% discount for future purchases in the mall.

1.2 Functional requirements

(1) Management of member information

(2) Management of product information (inventory). Support importing product information

(3) Customer shopping

(4) Management of customer orders

(5) Supermarket sales summary, support export sales.

2. Outline design

2.1 Overall system design

The detailed functional requirements are as follows:

  • If you have a card, you can get 10% off. If you don’t have a card, record whether a consumption is over 200 yuan. If you have a full card, you will be issued a membership card (join the membership information form), and you can enjoy 10% off for future purchases

  • Support for adding new products, querying all products, querying the current product,

  • Support order query, payment, and order information insertion into customer order form

  • After the member purchases the product, the purchase information is inserted into the consumption status table of the customer holding the card

  • Update the product inventory table and the supermarket sales table after the customer purchases the product

  • Support exporting supermarket sales table

So I divided the project into 4 modules

The first is the content module, which is responsible for querying products and the like;

Guess you like

Origin blog.csdn.net/m0_71106830/article/details/131354871