Online Mall Shopping System (1)

☝☝☝ Make sure you look at the catalogue first. ☝☝☝

The following separate statement section please see ☞ Online shopping mall (2)

1. Part of the functional requirements of the product
1. Self-management of users

Use case name	User Registration
Use Case number	SRS-01
Introduction to use Cases	Register a new user
Priority level	High
Predecessor condition	No
Post condition	Displays the registration success prompt and jumps to the login page.
Operation Process	Steps	Triggered by	Describe
1	User	Enter personal information.
2	System	Check that personal information is legal.
3	System	Input the personal information into the database.
Alternative process
Exception process
Constraint conditions	Register the user name to be valid and detect whether the user name is empty or already exists.
Input and Constraints	Username (name): string, length 0-10, direct input, required. Password (password): string, length 0-30, direct input, required. Confirm Password (passwordcheck): string, length 0-30, direct input, required. Province (province): integral type, required. City: Integral type, required. Email: string, length 0-30, direct input. Cell phone Number (telephone): string, length 11, direct input. Verification Code (VALIDATECODE): string, length 0-5, user input. must be filled in.

Use case name	User Login
Use Case number	SRS-02
Introduction to use Cases	User Login
Priority level	High
Predecessor condition	User already registered
Post condition	Go to the User Administration home page.
Operation Process	Steps	Triggered by	Describe
1	User	Enter the login information and check to see if the user is remembered.
2	System	Detection is empty.
3	System	If checked, write cookies, access the database, check the login information is correct. If correct, rewrite session, enter Personal Management homepage, otherwise, please login again, to use case SRS-05.
Alternative process
Exception process
Constraint conditions	Detects if the user name entered is valid and detects whether the user name is empty.
Input and Constraints	Username (name): string, length 0-10, direct input, required. Password (password): string, length 0-30, direct input, required. Remember User (Isremember): boolean, optional input.

Use case name	User basic Information modification
Use Case number	SRS-07
Introduction to use Cases	Users to modify their own details.
Priority level	High
Predecessor condition	User is logged in
Post condition	Enter User Details Display page
Operation Process	Steps	Triggered by	Describe
1	User	Open your own Details Display page and go to the Modify page.
2	System	The category displays the user's basic information and is required to be displayed as a text box.
3	User	Modify your basic information (name, nickname, name visibility, gender, age, birthday, province, city, Avatar, personality signature). Modify your contact (contact telephone, QQ, MSN). Revise your hobbies (like books, music, movies, hobbies, games).
4	User	Click the OK button.
5	System	Submits the user-modified information to the database and returns the result of the modification.
Alternative process
Exception process
Constraint conditions	No.
Input and Constraints	Sex (Sex): Boolean, select Input. Age: Integral type, select input. Account balance (Money): Money type, defaults to 0. Birthday (Birthday): Date type, select Input. Province (Provinceid): Foreign key (province table), Length 0-255, list box select input. Town (Cityid): Foreign key (city table), Length 0-255, list box select input. Avatar (photo): string, length 0-500, record file saved in site folder location, user upload. Personality signature (DSP): string, length 0-200, direct input. Email: string, length 0-30, direct input. Cell phone Number (telephone): string, length 11, direct input. QQ Number (QQ): string, length 0-15, only required number, direct input. MSN (MSN): string, length 0-50, mailbox format, direct input. Hobby Book (Lovebook): string, length 0-200, direct input. Hobby Music (Lovemusic): string, length 0-200, direct input. Hobby Movie (Lovemovie): string, length 0-200, direct input. Hobby Sport (Lovesport): string, length 0-200, direct input. Hobby Game (LoveGame): string, length 0-200, direct input.

1.2 Search for merchandise

Use case name	Search for Merchandise
Use Case number	SRS-08
Introduction to use Cases	The user enters the keyword to search for all the corresponding items.
Priority level	High
Predecessor condition
Post condition
Operation Process	Steps	Triggered by	Describe
1	User	Enter the search page, enter the search for the keyword keyword, you can select a keyword search criteria (such as commodity categories, brands, prices, etc.) to search for goods.
2	System	According to the user search the key word query database, if found to meet the requirements of the goods are displayed, otherwise show no corresponding commodity information exists.
Alternative process
Exception process
Constraint conditions	The input search item keyword is not empty.
Input and Constraints	Keywords (searchkey): string, length 0-20, direct input, required.

Use case name	View Product
Use Case number	SRS-09
Introduction to use Cases	Users to view the details of the corresponding product.
Priority level	High
Predecessor condition
Post condition
Operation Process	Steps	Triggered by	Describe
1	User	Click on the product that you have searched for information that you want to view.
2	System	According to the user click on the commodity query database, if found to meet the requirements of the goods will be the details of the product display, otherwise show no corresponding commodity information exists.
Alternative process
Exception process
Constraint conditions
Input and Constraints

1.3 Purchase of goods

Use case name	Place the Order
Use Case number	SRS-12
Introduction to use Cases	The user will want to purchase the merchandise order well and generate the new order.
Priority level	High
Predecessor condition	User is logged in
Post condition
Operation Process	Steps	Triggered by	Describe
1	User	Complete the detailed information of the order.
2	System	The information of this order is deposited into the database, a new order is generated, and no payment is made for the order: unpaid, the order is issued to the seller but the seller does not ship the goods.
Alternative process
Exception process
Constraint conditions	Commodity information is not empty, commodity inventory sufficient order requirements, the user account balance is sufficient, an order number for only one order to use, regardless of whether the order is completed or not the order number can only be used once.
Input and Constraints	Buyer Username: The information from the buyer's information table, into the order form. Seller Username: The information from the seller's information sheet is placed in the order form. Product Information: The goods from the list of the various types of information. Purchase quantity: Integral type, direct input, required. Shipping Address: String, length 0-100, required. Buyer's cell phone number: string, length 11, required.

Use case name	Payment fee
Use Case number	SRS-13
Introduction to use Cases	The user pays the cost to the mall (as the middleman) and displays the payment in the order, the seller can ship the goods.
Priority level	High
Predecessor condition	The user has logged in and placed an order.
Post condition
Operation Process	Steps	Triggered by	Describe
1	User	Select to pay for this order.
2	System	Display the order as paid, reminding seller to issue.
Alternative process
Exception process
Constraint conditions	Buyer pays the balance enough in the treasure.
Input and Constraints
Note	Change the payment status in the order to paid.

1.4 User Order Management

Use case name	User modifies order status
Use Case number	SRS-16
Introduction to use Cases	When the user receives the goods, the order status is completed and the administrator can transfer the money.
Priority level	High
Predecessor condition	A user has placed an order with the seller, and the order status is shipping status.
Post condition	Show order status modified to: XX, and then jump to the order information page.
Operation Process	Steps	Triggered by	Describe
1	User	The user opens the order after receiving the arrival.
2	System	Pull out order information from the database.
3	User	The user changes the order status to complete.
4	System	The database records the modified order status (completed).
Alternative process
Exception process
Constraint conditions
Input and Constraints	Product information (from the Foreign key commodity table corresponding to the order to fetch the information). Seller username (information from the Order table). User information (from the database to the shipping address, mobile phone number, etc.). Modify order Status: complete.

1.5 sellers Order Management

Use case name	Seller modifies order Status
Use Case number	SRS-17
Introduction to use Cases	The seller modifies the order status.
Priority level	High
Predecessor condition	A user has placed an order with the seller, the seller can modify the order status.
Post condition	Show order status modified to: XX, and then jump to the order information page.
Operation Process	Steps	Triggered by	Describe
1	Seller	Check the user's orders for themselves.
2	System	Pull out order information from the database.
3	Seller	Revise the order status according to the inventory of the goods.
4	System	The database records the modified order status (revocation, payment, delivery, delay).
Alternative process
Exception process
Constraint conditions
Input and Constraints	Product information (from the Foreign key commodity table corresponding to the order to fetch the information). Seller username (information from the Order table). User information (from the database to the shipping address, mobile phone number, etc.). Modify Order Status: Select Input, divided into 4 states (revocation, payment, delivery, delay).

Use case name	Seller Changes Order Information
Use Case number	SRS-18
Introduction to use Cases	The seller changes the order information.
Priority level	High
Predecessor condition	The order item is sold to the user for modification.
Post condition	Jump to the Order information page.
Operation Process	Steps	Triggered by	Describe
1	Seller	Check the user's orders for themselves.
2	System	Pull out order information from the database.
3	Seller	Modify the order information that you want to modify.
4	System	To check the database records, to determine whether the revised order is reasonable (inventory of goods is sufficient, and the type of goods can not be modified, the number can only be reduced can not increase, to increase only the seller and the buyer once again to carry out an order transaction), modified to save.
Alternative process
Exception process
Constraint conditions
Input and Constraints	Product information (from the Foreign key commodity table corresponding to the order to fetch the information). Seller username (information from the Order table). User information (from the database to the shipping address, mobile phone number, etc.).

1.6 Commodity Management

Use case name	Product Shelves
Use Case number	SRS-19
Introduction to use Cases	The seller publishes information about the goods to be sold.
Priority level	High
Predecessor condition	The user is a registered member.
Post condition	Jump to the information page for this item.
Operation Process	Steps	Triggered by	Describe
1	Seller	Publish the product information.
2	System	Enter the database and add the product information.
Alternative process
Exception process
Constraint conditions
Input and Constraints	Buyer User name: Product Information:

Use case name	Modify Product Information
Use Case number	SRS-20
Introduction to use Cases	Revise the merchandise information released by the seller.
Priority level	High
Predecessor condition	The user has logged in, and has modified its own published products.
Post condition	Jump to the information page for this item.
Operation Process	Steps	Triggered by	Describe
1	Seller	Modify the product information.
2	System	Enter the database and modify the product information.
Alternative process
Exception process
Constraint conditions
Input and Constraints	Buyer User name: Product Information:

1.7 would management

,

Use case name	Admin return money to buyer
use Case number	SRS-21
Use case brief	User paid to intermediary administrator but lost order transaction due to return or loss of goods Failure, the user can apply for a refund request, the administrator will transfer funds to return the user.
Precedence	High
Preconditions	The user has logged in, and the order payment item is paid, the order status is revoked, the return is returned or the goods have not arrived, and the money is returned to the buyer.