Requirements Model

1. Functional Requirements

ID	Requirements
FR1	The art gallery system shall allow users to create their own by registration 95% of the time.
FR2	The art gallery system shall allow artists to upload their art pieces for sale 95% of the time.
FR3	The art gallery system shall allow customers to browse and purchase art pieces.
FR4	The art gallery system shall be able to promote artwork available on users’ premises.
FR5	The art gallery system shall allow artists to deliver their art to their customers by mail.
FR6	The art gallery system shall allow customers to pick up their purchased art pieces at the store.
FR7	The art gallery system shall charge commission for the sold artwork.
FR8	The art gallery system shall allow users to login their own account using the email and password registered.
FR9	The art gallery system shall allow users to check the status (available, unavailable, purchased, pending, delivering) for all art pieces.
FR10	The art gallery system shall allow customers to cancel a purchase before payment.

2. Non-functional Requirements

ID	Requirements
NFR1	The art gallery system shall support at least 10 payments at the same time.
NFR2	The art gallery system shall load user’s profile within 5 seconds after request.
NFR3	The art gallery system shall be able to be familiarized by user within 15 minutes of reading the instruction.
NFR4	The art gallery system shall have less than 30min downtime per month.

3. Use case Diagram

4. Detailed Specification for 5 most important use cases

Log in account -- Amelia

• Use case: The art gallery system shall allow users to login their own account using the email and password registered.
• Scenario: As a user, I want to be able to log into my account using the email address and password registered to interact with the relevant functions of the system.
• Actor: User
• Intention: The intention of the user is to log into his/her homepage to access the functions for the art gallery system.
• Pre-condition: The user is on the login page and clicked the “login” button.
• Step:
  
  1. User writes his/her email as an input
  2. User writes the correct password associated with the email account
  3. User clicks “Login” button.
  4. Art gallery system checks the database to cross reference with an existing email and password
  5. Art gallery system returns the result for this request.
• Basic Path:
  
  1. User writes his/her email as an input
  2. User writes the correct password associated with the email account
  3. User clicks “Login” button.
  4. Art gallery system checks the database to cross reference with an existing email and password
  5. The email and passwords match an existing user stored in database; the system returns success.
  6. The system opens the homepage for this user, which includes user profile, promoted art pieces and purchase history.
• Alternate/Exception path:
  
  • The user input wrong password for the first time, then clicked login button
    1. The system displays “wrong password” with the buttons “try again” and “forgot password”
    2. If the user clicked “try again”, the system will stay on the login page to allow user to enter email and password again.
    3. If the user clicked “forgot password”, the system will display the page for recovering password.
  • The user input wrong password for the second time, then clicked login button
    1. The system displays “wrong password” with the buttons “try again” and “forgot password”
    2. If the user clicked “try again”, the system will stay on the login page to allow user to enter email and password again.
    3. If the user clicked “forgot password”, the system will display the page for recovering password.
  • The user input wrong password from the third time, then clicked login button
    1. The system displays “wrong password” with display the page for recovering password.
  • The user input email that does not exist, then clicked login button
    1. The system displays “user does not exist” with the button “try again” and “create a new user”
    2. If the user clicked “try again”, the system will stay on login page to allow user to enter email and password again
    3. If the user clicked “create a new user”, the system will display the registration page for new user.
  • the user did not enter email/password
    1. The system displays a warning asking the user to fill in the blank.
• Postcondition (success): The system displays the homepage for this user
• Postcondition (failure):
  1. The system stays on this page waiting for the user to try again
  2. The system displays a warning asking the user to fill in the blank
  3. The system redirects the user to the recovering password page.
  4. The system redirects the user to the create new user page. **In-store pick-up ** -- Linpei Duan(Angelina)
     
• Use case: The art gallery system shall allow customers to pick up their purchased art pieces at the store.
• Scenario: As a customer, I want to be able to pick up my purchased air pieces at the store.
• Actor: Customer
• Intention: The customer intends to pick purchased art pieces up at the store.
• Pre-condition: The customer purchased the art piece and choose the “In-store pick up” delivery method.
• Step:
  
  1. The customer types his/her name, phone number, street address, city, province, country, and postal code on the delivery page.
  2. The system provides nearby store addresses to the customer. The customer chooses the store.
  3. The system provides a pick-up reference number and the address of the store to the customer.
  4. Once the art piece is purchased, the customer could see his/her in-store pick-up status changes to pending.
  5. Once the art piece is delivered to the store, the customer’s in-store pick-up status changes to available for pick up.
  6. The customer goes to the store and provides his/her phone pick-up reference number, phone number, and name.
  7. The customer shall be able to pick up his/her purchased art piece and his/her in-store pick-up status changes to picked up.
• Basic Path:
  
  1. The customer types his/her name, phone number, street address, city, province, country, and postal code on the delivery page.
  2. The system provides nearby store addresses to the customer. The customer chooses the store.
  3. The system provides a pick-up reference number and the address of the store to the customer.
  4. The customer provides name, phone number, and pick-up reference number when enters the store.
  5. His/her information matches the one on the system, the customer successfully picked up.
• Alternate/Exception path:
  
  • The customer wants to change his/her information after getting the reference number.
    1. The system has a "go back" button. The customer should change his/her information.
  • The customer wants to cancel his/her purchase item.
    1. Use the "go back" button and goes to the payment page to cancel the payment.
  • Customer wants to change a store to pick up
    1. Before the status of in-store pick-up changes to available for pick-up, the customer could click the "change store" button and the system will provide available nearby stores.
    2. After the status changes, the "change store" button will disappear. The customer needs to call the store and pays an extra fee for the delivery.
  • No nearby store at all
    1. The customer might choose another delivery method or choose a further store.
  • The customer provides wrong information during pick-up
    1. The customer has one chance to check his/her information and reference number.
• Postcondition (success): The customer successfully picks up his/her purchased art piece.
• Postcondition (failure):
  1. The system asks the customer to choose another delivery method or choose a further store.
  2. The system asks the customer to choose another store.
  3. The system asks the customer to provide his/her name, phone number, and reference number again.
  4. The system shows that the pick up failed. The customer has a chance to go back and check his/her information and goes to the store to pick up again.