Professional Documents
Culture Documents
p2 Android Application Use Case Document
p2 Android Application Use Case Document
p2 Android Application Use Case Document
Table of contents
Initial Layout 2
Use Case Model 3
Create Account - (New) User 3
View Existing Users - Admin 4
Entity Relationship Diagram (ERD) 5
Use Case 01: Predefined Users 6
Use Case 02: Sign Up 7
Use Case 03: Add a user 8
Use Case 04: Delete a user 9
Use Case 05: Place an Order 10
Use Case 06: View Order History 11
Use Case 07: Cancel Order 12
Use Case 08: User Authentication 13
Use Case 09 Alternate Flow 1: Add a User that Already Exists 14
Use Case 10 Alternate Flow 2: Delete a User that DNE 15
Use Case 11 Alternate Flow 3: Login with Invalid Credentials 16
Use Case 12 Alternate Flow 4: Sign Up with invalid credentials 17
Initial Layout
Use Case Model
{Enter Username}
2. User enters a username into the username textbox
3. Application validates that username does not already exist
a. If it does, when the user presses the sign up button, display an error and request user to
either login or enter a different username
b. If it does not, proceed
{Enter Password}
4. User enters a password in the initial password textbox
5. User enters a password in the confirmation textbox
6. Application validates that initial password and password confirmation match
a. If they do not, when the user presses the sign up button, display an error message
telling the user that the passwords do not match
b. If they do, proceed
{Press Sign Up}
7. User presses Sign Up button
a. Machine validates all provided fields and stores the information in the database
View Existing Users - Admin
{Sign In}
1. Use case begins when admin begins entering username and password
2. Press sign in button
a. If admin entered login information that does not exist, application will display error
message
b. If admin entered login information of a standard user, application will log them in as said
standard user
c. If admin entered valid admin login information, proceed as admin
{Enter Admin Menu}
3. Admin presses the Admin button
{View Existing Users}
4. Admin presses view existing items button
5. Application displays existing users
Entity Relationship Diagram (ERD)
Use Case 01: Predefined Users
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: Sign Up
2
How to force quit an application in Android:
https://www.digitaltrends.com/mobile/how-to-force-close-apps-android/
Use Case 04: Delete a user
1. Login as admin
2. Press admin button
3. Press add user button
4. Add a username that already exists to the database
5. Validate that a message saying “User already exists” appears.
6. Force quit the application3
7. Reopen application
8. Login as admin
9. Press admin button
10. Press View existing users
11. Validate that the user we attempted to create only exists in one instance
3
How to force quit an application in Android:
https://www.digitaltrends.com/mobile/how-to-force-close-apps-android/
Use Case 10 Alternate Flow 2: Delete a User that DNE
1. Login as admin
2. Press admin button
3. Press view existing users
4. Choose a username that does not exist in the existing users
5. Return to admin menu
6. Press delete user button
7. Delete the username that does not exist in the database
8. Validate that a message saying “User does not exist” appears.
9. Force quit the application4
10. Reopen application
11. Login as admin
12. Press admin button
13. Press View existing users
14. Validate that the user we attempted to delete still does not exist and no other errors occurred
15. Attempt to create a new user with the previous credentials
16. Login as that user and validate that it was successful
4
How to force quit an application in Android:
https://www.digitaltrends.com/mobile/how-to-force-close-apps-android/
Use Case 11 Alternate Flow 3: Login with Invalid Credentials