Use Case #1:
Use Case #2
Use Case #3
Use Case #4
Use Case #5
|
Log into the Chatroom
| Goal: |
The goal of the system is to allow the user to log on into the chatroom |
| Scope: |
Global |
| Level: |
User |
| Precondition: |
User has access to the web site |
| Success Condition: |
User is able to log on into the chatroom |
| Failure Condition: |
User is unable to log on into the chatroom |
| Trigger: |
User has questions/problems that need to be addressed by the head of the board |
| Actors: |
User |
| Type: |
Primary |
| Purpose: |
To allow the user to log on into the chatroom |
| Description: |
User, after accessing the website, will come to the login page. To log on, user will choose a room, type in a name and click on the Send link or just simply press Enter. System will validate to see if user name has been taken. If yes, system will display an error message stating that the user name is no longer available. If no, then user is taken into the chatroom. |
| Cross Reference: |
Requirement 1 |
Typical Course of Event
| Actor Action |
System Response |
1. User types the website's address and presses Enter. |
|
2. User chooses a chatroom, types a user name, then clicks on the Send button or presses Enter. |
|
|
3. The system checks to see if user name chosen is taken. |
|
3a. If yes, the system displays an error message stating that user name is taken, and user is taken back to step 2. |
|
3b. If no, the system takes user into the chatroom. |
Go to Sequence Diagram #1
|