Use Case 107: Online Gaming Support

This document presents a detailed case study, 'Use Case #107: Users are Unable to Play Online,' focusing on the process of a user seeking help for gaming issues through an online support system. It outlines the user's journey from accessing the help chat link to resolving their problem with tech support. The case study includes preconditions, a main success scenario, and various extensions covering scenarios like regular users, password requirements, password recovery, and connection issues. It also references an initial design of the user interface and a use case diagram, providing a comprehensive view of the user interaction with the support system.

Use Case #107: Users are Unable to Play Online
1.1 Author:
Khalid Alsubaie
1.2 Last Update:
9/14/16
1.3 Status:
Under Review
1.4 Description
The User wants to get help for any issues/errors that occurs while gaming.
The Customer provides an easy and convenient way to help/assist its users through the application
The developer follows-up, adds, improves, edits, debugs, and updates the customer’s application to make sure
the customer’s application is running perfectly.
1.5 Level
Sea Level
1.6 Trigger
The User clicks the Help Chat link.
1.7 Primary Actor
The Primary Actor is the User asking for help from Tech Support to get their issues while gaming resolved.
1.8 Preconditions
The User [Primary Actor] must have an active Internet connection, logged onto the [fungame.com/help] site
open in the browser and a unique game username ID.
1.9 Main Success Scenario
1. The User connects to the website.
2. System asks the User to sign up.
3. The User is taken to “Create Account” page.
4. The User fills in their account information.
5. The User fills in their password.
6. System checks for valid information.
7. System authorizes User’s valid information.
8. The User confirms their sign up.
9. The User is taken to the sign in page.
10. The User enters their username and password.
11. The User clicks “Sing in Button.”
12. The User chooses issues/problem subject from the list.
13. The User submits the help request.
14. Systems connects the User to the Tech Support Rep.

15. The User starts chatting with Tech Support Rep.
16. The User logs out.
1.10 Extensions
2a: User is a regular User:
1. System asks the User to enter their existing username and password.
2. The User is taken to the “Sign in” page.
3. The User enters their existing username and password.
5a: Password requirements:
1. The User must enter 8 characters including one or more uppercase letter and number.
2. The User must not enter DOB or SSN as a password.
10a. User enters invalid password
1. System displays message.
2. The User is taken to “Password Recovery” page.
3. The User must enter their security question and security answer.
4. System checks User’s valid security question and security answer.
5. System asks the User to enter their email.
6. System authorizes User valid information.
7. System sends new password to the User’s email.
8. System logs out the User from the website.
9. The User is asked to reenter their new Temp. Password.
10. System verifies the User correct password.
11. System asks User to enter a new password.
15a. The User disconnects/loses their internet connection between the chat:
1. System asks the User to renter their username and password.
2. The User renter their username and password.
3. System logs the customer to the main page.

Use Case Diagram

Initial Design of User Interface