-
Notifications
You must be signed in to change notification settings - Fork 1
Requirements Model
FR1 The gallery system shall allow the user to create an account to enable him to login to the application.
FR2 The gallery system shall allow the registered user to login into the application with his email and password in less than 10 seconds.
FR3 The gallery system shall inform the user that his login attempt is unsuccessful upon the use of invalid credentials.
FR4 The gallery system shall allow the logged-in artist to post his artwork into the virtual store so that customers can view and potentially buy the artwork.
FR5 The gallery system shall allow the logged in artist to remove his unpurchased artwork from the system.
FR6 The gallery system shall allow the logged in customer to place an order for an artwork from the virtual store.
FR7 The gallery system shall allow the logged in customer to view the list of his previous purchases.
FR8 The gallery system shall allow the logged in customer to rate an artist on a scale of 1 to 5 stars after receiving the order.
FR9 The gallery system shall allow the logged in customer to add/change his delivery address.
FR10 The gallery system shall allow the user to reset their password upon request.
FR11 The gallery system shall notify the customer that his order is ready for pickup/shipment.
FR12. The gallery system shall inform an artist that a copy of his artwork has been purchased so he can deliver the artwork to the store/customer.
FR13 The gallery system shall allow the logged in admin to manage the list of existing users in the application.
NFR1 Installation of a mobile version of the application shall not alter any data saved in the database.
NFR2 The system shall keep all customers' data private and not accessible by other users except artists delivering to that customer.
Title: Create account
Actor(s): User
Intention: The intention of the User is to create an account in the Artsee application.
Precondition: User has opened the application.
Main Scenario:
1: User clicks on "create account" button in the application.
2: The application prompts the User to fill out an account registration form.
3: The User fills out the required information including first name, last name, phone number, email and password and optionally address.
4. The User submits the registration form.
5. The application verifies that the information entered by the User is complete and valid.
6. The application successfully creates the account for the User.
Alternatives/Exceptions:
4a: An account with the same email already exists.
4a.1: Application prompts user to re-enter a different email; Use case continues at step 3.
4b: User enters incomplete and/or invalid information.
4b.1: Application prompts user to re-enter incomplete/invalid fields in the form. Use case continues at step 3.
Post-condition: Account created successfully.
Title: Login to the Application
Actor(s): User
Intention: The intention of the User is to login into the Artsee application using the user's credentials.
Precondition: User has opened the application and has an account.
Main Scenario:
1: User clicks on "login" button in the application.
2: The application prompts the User to fill in the user's email address and password.
3: The User fills in the email address and password.
4. The User submits the login form.
5. The application verifies that the information entered by the user is correct.
6. The application successfully logins the user into the artsee application.
Alternatives/Exceptions:
5a: An account with the inputed email address does not exist.
5a.1: Application notifies the user that the email address is not linked to an account.
5b: User enters an incorrect password.
5b.1: Application notifies the user that the password is incorrect.
Post-condition: User successfully enters the Artsee application.
Title: Post Artwork
Actor(s): Artist
Intention: The intention of the Artist is to post an artwork in the Artsee application.
Precondition: User has opened the application and is logged in as an Artist.
Main Scenario:
- Artist clicks on “post artwork” button in the application.
- Application prompts Artist to fill out an artwork posting form
- The Artist fills out the information about the artwork including: name, a brief description, asking price, date it was made, and the quantity of stock.
- The Artist submits the registration form
- The application verifies that the information entered is valid.
- The application posts the artwork for customers to see.
Alternatives/Exceptions
4a: An artwork with the same name exists.
4a1: The application gives a warning "There is another artwork with the same name. Are you sure you want to proceed?".
4a2 i: The Artist clicks on “rename” button in the application ; Use case continues at step 3.
4a2 ii: The Artist clicks on “continue” button in the application; Use case continues at step 4.
4b: The description field was left empty.
4b1: The application gives a warning "There is no artwork description. Are you sure you want to proceed?".
4b2 i: The Artist clicks on “edit description” button in the application; Use case continues at step 3.
4b2 ii: The Artist can leave the description blank. Use case continues at step 4.
4c: The asking price is less than 1.00$
4c1: The application prompts the Artist to enter a price greater than 1.00$; Use case continues at step 3
4d: The date of fabrication is invalid
4d1: The application prompts the Artist to enter a valid date; use case continues at step 3.
4e: The quantity in stock is set to 0.
4e1: The application prompts the Artist to input a number greater than 0 for the stock quantity; Use case continues at step 3.
Post-condition: Artwork posted successfully.
Title: Remove Artwork
Actor(s): Artist
Intention: The intention of the Artist is to remove a posted artwork in the Artsee application.
Precondition: User has opened the application and is logged in as an Artist, and User has an existing artwork posting.
Main Scenario:
- The Artist clicks on “remove artwork” button on an artwork post in the application.
- The application prompts the artist to select the number of artworks to be removed.
- The Artist enters the number of artworks or selects “All”.
- The application verifies that the information entered is valid.
- The application prompts the user with a message “Are you sure you want to remove these artworks from the Artsee gallery”.
- The application removes the artwork for customers to see.
Alternatives/Exceptions
4a: The Artist entered a value of 0 for number of artworks.
4a1: The application prompts the Artist to enter a valid number of artworks to remove; Use case continues at step 3.
4b: The Artist entered a value greater than the number of artworks that could be removed; Use case continues at step 3.
5a: The Artist clicks “continue” button in the application; Use case continues at step 6.
5b: The artist clicks “cancel” button in the application; Use case continues at step 3.
Post-condition: The artwork was removed successfully.
Title: Place an Order
Actor(s): Customer
Intention: The intention of the customer is to place an order on an artwork from the Artsee store.
Precondition: User is currently on the artwork detailed view page.
Main Scenario:
1: The Customer clicks on “add to cart” button from the artwork detailed view page.
2: The Customer clicks proceed to checkout button on the top right of the application page.
3: The Customer selects the payment method for paying upon delivery and the delivery method.
4: The Customer clicks confirm order.
5. The application verifies that the information entered by the user is correct.
6. The application successfully places the order.
Alternatives/Exceptions:
5a: The Customer selected shipping as the preferred delivery method, but never linked an address to his account.
5a.1: The application prompts the user to fill in the user’s address.
5a.2 The User enters his address.; Use case continues at Step 4.
Post-condition: User receives a notification verifying that the order has been placed.
Group 15 Ragheed Qasmieh, Daniel Schwartz, Matt Langshur, Enan Ashaduzzaman, Matteo Barbieri