[Kevin Yoshimoto]

Project 02: [Android Snow Gear Project]

CST 338 [Fall 2021 Section 2]

[Snow Gear Community Market]

[I am developing an application that allows users to sell, lend, and borrow snow gear through creating
accounts and uploading items to a database.]
[Snow gear to be rented out, sold, or lended out.]
[The admin can see all the other users of the application and can remove objects.]

Please mark each use case as 'pass' Or 'fail'. The use case passes if it does what it intended to do. It
fails if it does not. See the example below for more information.

Table of contents
Use Case 01: Predefined Users 3
pass 3

Use Case 02: Persistence 4

pass/fail 4

Use Case 03: Add a user 5

pass/fail 5

Use Case 04: Delete a user 6

pass/fail 6

Use Case 05: add an gear 7

pass/fail 7

Use Case 06: Add user from admin page 7

pass/fail 8

Use Case 07: Delete an item 9

pass/fail 9

Use Case 08: Checking out an object 10

pass/fail 10

Use Case 09: Checking all checked out objects 11

pass/fail 11

Use Case 10: Viewing other users 12

 pass/fail 12

Use Case 11: Checking in a rental object 13

pass/fail 13

Use Case 12: Searching for gear 14

pass/fail 14

Use Case 13: Login as an existing user 15

pass/fail 15

Use Case 14: Logout of account 16

pass/fail 16

Use Case 15: Changing User to Admin 17

pass/fail 17

Use Case 16: Changing Admin to User 18

pass/fail 18
Use Case 01: Predefined Users

pass

1. Force quit the application1

2. Login as testuser1
3. Display the username 'testuser1'
4. Logout
5. Login as admin2
6. Display the username 'admin2'
7. Display something specific to the admin user.
a. Something like an admin button or a link to edit items.

This use case passes if all of these conditions are met. It fails otherwise.

1
How to force quit an application in Android:
https://www.digitaltrends.com/mobile/how-to-force-close-apps-android/
Use Case 02: Persistence

pass/fail

1. Add an item to the database

2. Force quit the application2
3. Show the item added in step 1 is still in the database
4. Change an item in the database
5. Force quit the application
6. Show the item modifications from step 4 have been saved

2
How to force quit an application in Android:
https://www.digitaltrends.com/mobile/how-to-force-close-apps-android/
Use Case 03: Add a user

pass/fail

1. User clicks on the ‘Create a new user’ button.

2. Application displays the create an account screen.
3. User types in desired username.
4. User types in desired password.
5. User clicks the create button.
6. Application displays the home page with a congratulations message.
7. Use case ends.
Use Case 04: Delete a user

pass/fail

1. User clicks on the settings button.

2. Application displays the settings screen.
3. User clicks the ‘Delete account’ button.
4. Application displays an assurance message and 2 buttons to continue or end the application.
5. User clicks continue button.
6. Application deletes user account and displays deletion message.
7. Use case ends.

Alternate: [End the application]

5. User clicks end application button.
6. Application displays the home screen.
7. Use case ends.
Use Case 05: add an gear

pass/fail

1. User clicks on the ‘add gear’ button.

2. Application displays an edit text for the name, price, and stock of the gear.
3. User enters in the desired values for the attributes of the item to be added.
4. User clicks the submit button.
5. Application displays a message congratulating the user for successfully creating an item.
6. Use case ends.
Use Case 06: Add user from admin page

pass/fail

1. User logs in.

2. Application goes to landing page.
3. User clicks on the Admin button
4. Application goes to the admin page.
5. User clicks on the View Existing Users button.
6. Application takes user to the View Existing Users Page.
7. User clicks on the “plus” button.
8. User enters in the username and password for the new user.
9. User clicks on save icon.
10. Application sends message confirming the user was created.
11. Use case ends.
Use Case 07: Delete an item

pass/fail

1. User clicks on the “Remove Gear button”.

2. Application displays the item’s menu screen.
3. User enters the name of the gear they want to remove.
4. User clicks on the “Remove Button”.
5. Application displays the home page and displays a message confirming the object was deleted.
6. End use case.
Use Case 08: Checking out an object

pass/fail

1. User clicks on the search button.

2. Application takes user to search window.
3. User enters in desired object name.
4. User hits the save button.
5. Application tells user the object has been checked out.
6. End use case.
Alternate: [No objects found]

4. Application displays a message stating that no objects with the desired name were found.
5. End use case.
Use Case 09 Checking all checked out objects

pass/fail

4. User clicks on the “search for checked out gear” button.

5. Application takes user to the list of gear that reflect a true value of the isCheckedOut parameter
in SnowGear object.
6. End use case.
Use Case 10 Viewing other users

pass/fail

1. Admin clicks on the view other users button.

2. Application displays a list of all the other accounts that use the application.
3. End use case.
Use Case 11 Checking in a rental object

pass/fail

1. User clicks on the check-in button from the home page.

2. Application displays a screen asking the user to specify which object they would like to check-in.
3. User chooses the desired object to check-in.
4. Application displays a confirmation message telling the user that the object has been
checked-in.
5. End use case.
Use Case 12 Searching for gear

pass/fail

5. User logs in.

6. Application takes user to the landing page.
7. User clicks on search Gear to checkout button.
8. Application takes user to page showing all Gear available to checkout.
Use Case 13 Login as an existing user

pass/fail

1. User clicks on the returning user button.

2. Application displays the login page requiring both a username and password.
3. User enters in desired username and password.
4. Application displays the home page of the application.
5. End use case.
Alternate: [Wrong Password]
4. Application displays an error message letting the user know the password was wrong for the
desired username.
5. End use case.
Alternate: [Wrong Username]
4. Application displays an error message letting the user know the username does not exist in the
database.
5. End use case.
Use Case 14 Logout of account

pass/fail

6. User clicks on the sign out button from the home page.
7. Application displays a message asking the user if they are sure they want to log out.
8. User clicks on the sign out button.
9. Application displays the login page with the user signed out.
10. End use case.
Alternate: [Do not want to sign out]
11. User clicks on the cancel button.
12. Application displays the home page.
13. End use case.
Use Case 15 Changing User to Admin

pass/fail

1. Admin logs in.

2. Admin selects the admin button.
3. Application shows the admin page.
4. Admin selects the change user button.
5. Application shows the change user page.
6. Admin inputs user’s username.
7. Admin selects the change to admin.
8. Application changes user to admin and shows the admin page.
9. End use case.
Alternative: [Wrong username]
8. Application displays no users with that username message.
9. End use case.
Alternative: [Username is for admin]
8. Application displays that the username belongs to an admin account.
9. End use case.
Use Case 16 Changing Admin to User

pass/fail

1. Admin logs in.

2. Admin selects the admin button.
3. Application shows the admin page.
4. Admin selects the change user button.
5. Application shows the change user page.
6. Admin inputs user’s username.
7. Admin selects the change to regular user button.
8. Application changes Admin to user and shows the admin page.
9. End use case.
Alternative: [Wrong username]
8. Application displays no users with that username message.
9. End use case.
Alternative: [Username is for admin]
8. Application displays that the username belongs to an admin account.
9. End use case.