<unnamed>| View: | Hide Browser | Browser on the left | Browser on the right | Dictionary |
| Report: | General Info | Relations | Tagged Values |
| Use Case Description | |
| Actors | Player, Administraitor |
|---|---|
| Sumary | Open existing user account. |
| Preconditions | Socket connection must be established between the Player and Mud Server. |
| Flow of Events |
1. Player responds with username when Mud Server requests login name. 2. Mud Server verifies username exists. [alternate course A: invalid username] 3. Mud Server requests password. 4. Player responds with password. 5. Mud Server validates password. [alternate course B: invalid password] 6. Mud Server locates Player thread. 7. End use case. Alternate Course A: 1. Mud Server notifies Player of invalid username. 2. End use case. Return to use case: Log In step 1. Alternate Course B: 1. Mud Server notifies Player of invalid password. 2. Return to primary flow step 3. |
| Error Conditions | Invalid log in information. |
| Concurrent Activities | |
| Postconditions | Player thread is identified. |
| Quality Requirements | The activity succeeds or fails without corrupting system. |
| Comments | |
| General Info | |
| Name | Open Existing Account |
| Abstract | false |
| Leaf | false |
| Root | false |
| Owner | Account Mangement |
| Relations | |||
| Name | Type | Begins | Ends |
| <unnamed> | extend | Open Existing Account | Log In |
| Tagged Values | ||
| Tag Definition/Tag Name | Value | Documentation |
| Tag Definition: UseCase Number : UCNumber[1] | 1 | |