| View: | Hide Browser | Browser on the left | Browser on the right | Dictionary |
| Report: | General Info | Extension Points | Relations | Tagged Values |
| Use Case Description | |
| Actors | Player, Administraitor |
|---|---|
| Sumary | Delete user's own account. |
| Preconditions | User account exists. User is logged into the Mud Server. |
| Flow of Events |
1. Mud Server prompts Player to confirm deletion. 2. Player responds with confirmation. [alternate course A: Player cancels delete] 3. Mud Server removes socket connection from Player thread. 4. Mud Server deletes user account. [extension point: use case Perform Abandonment Protocol] 6. Player thread is destroyed. 5. End use case. Alternate Course A: 1. Mud Server notifies Player that delete was canceled. 2. End use case. |
| Error Conditions | |
| Concurrent Activities | |
| Postconditions | Player account is deleted. |
| Quality Requirements | The activity succeeds or fails without corrupting system. |
| Comments | |
| General Info | |
| Name | Delete Account |
| Abstract | false |
| Leaf | false |
| Root | false |
| Owner | Account Mangement |
| Extension Points |
| cleanup |
| Relations | |||
| Name | Type | Begins | Ends |
| association | Player | Delete Account | |
| extend | Perform Abandonment Protocol | Delete Account | |
| Tagged Values | ||
| Tag Definition/Tag Name | Value | Documentation |
| Tag Definition: UseCase Number : UCNumber[1] | 8 | |
| General Info | |
| Name | cleanup |
| Owner | Delete Account |