-
Notifications
You must be signed in to change notification settings - Fork 3
Requirements Model
Laurier Gauvin edited this page Oct 12, 2024
·
3 revisions
- The application shall allow the owner to manage the administration of the store.
1.1. The application shall allow the owner to manage employee accounts.
1.1.1. The application shall allow the owner to create an account for a store employee by specifying their email, username, and password.
1.1.2. The application shall allow the owner to remove the existing account of a store employee.
1.2. The application shall allow the owner to manage the game categories.
1.2.1. The application shall allow the owner to add game categories by specifying the category name.
1.2.2. The application shall allow the owner to remove game categories.
1.2.3. The application shall allow the owner to update the names of game categories.
1.3. The application shall allow the owner to view the order history of all customers.
1.4. The application shall allow the owner to review and reply to customer reviews.
1.5. The application shall allow the owner to modify the store policy.
1.6. The application shall allow the owner to create, modify, and delete store promotions.
1.7. The application shall allow the owner to approve or deny requests.
1.7.1. The application shall allow the owner to approve or deny game additions requests.
1.7.2. The application shall allow the owner to approve or deny game removal requests.
1.7.3. The application shall allow the owner to approve or deny app user ban requests. - The application shall allow store staff to manage the game catalog.
2.1. The application shall allow store staff to update the number of copies of a game.
2.2. The application shall allow store staff to request the addition of a game to the game catalog by specifying its title, category, price, description, and public opinion.
2.3. The application shall allow store staff to request the removal of a game from the game catalog.
2.4. When a game is removed from the game catalog, all copies of the game shall be removed from customers’ carts which contain copies of the game. - The application shall allow customers to create an account by providing a unique email, username, password, delivery address, and phone number.
- The application shall allow registered app users to authenticate themselves to the application.
4.1. The login process shall allow app users to authenticate themselves using either their username or email, along with their password.
4.2. The login process shall allow app users who have successfully self-authenticated to access their account. - The application shall allow app users to view the catalog of games available for purchase.
5.1. For each game category, the application shall allow the app user to view a list of games associated with the category.
5.2. The application shall allow the app user to search for games by inputting a game title into the search bar.
5.3. The application shall display the top available promotion alongside each game. - The application shall allow customers to purchase game copies.
6.1. The application shall allow the customer to add games to their cart.
6.2. The application shall allow the customer to remove games from their cart.
6.3. The application shall allow the customer to checkout with the game copies in their cart.
6.3.1. The application shall allow the customer to input their payment information during the checkout process.
6.3.1.1. During the checkout process, the application shall ask the customer whether they wish to save their payment information to their account.
6.3.2. The application shall allow the customer to confirm their purchase to complete the checkout process.
6.3.2.1. The application shall create a tracking number for a purchase.
6.3.3. The application shall allow the customer to exit the checkout process while preserving cart information.
6.3.4. For each game purchased by the customer, the application shall decrease the inventory amount of the game by the number of copies of that game the customer purchased.
6.4. The application shall allow customers to return their entire order so long as the return is within 7 days of purchase, and the reason for the return is indicated. - The application shall allow customers to view a list of their previous orders.
- The application shall allow customers to add and remove games from their wishlist.
- The application shall allow customers to post reviews solely for games they have purchased.
9.1. The application shall allow the customer to post only one review for each game they have purchased. - The application shall allow staff to view the email address, physical address, username, and wish list of registered customers.
10.1. The employees shall have access to customers’ username, email, address, order history, and wishlist.
10.2. The owner shall have access to all the customers’ information except for passwords.
- The application shall have an intuitive user interface that can be navigated by a new app user with minimal training.
1.1. The application shall allow a new app user to register for a customer account in less than 10 minutes, for 95% of new app users.
1.2. The checkout process shall be able to be completed by the customer in less than 10 minutes, for 95% of customers.
1.3. The application shall allow an app user to find and view a desired game in less than 5 minutes, for 95% of app users. - The application's filtering algorithm shall allow the user to filter through the game catalog within less than 10 seconds 95% of the time.
- The game shop system shall run on the browsers including Google Chrome, Edge, IE, and Firefox.
- The application shall encrypt sensitive customer data, including passwords and payment information, during its storage.
- The application shall provide a troubleshooting process.
5.1. The application shall display server errors to the app user.
5.2. The application shall display error messages when incomplete or incorrect information is provided during the checkout process.
Home
How to run the Application
- Domain Model
- Requirements Model
- Use Case Specifications
- Use Case Diagrams
- Deliverable 1 Testing Documentation
- Deliverable 1 Record of Operations
- Extra Notes