Dashboard > The DataPortability Project > ... > Templates and Tools > Use Case Template
  The DataPortability Project Log In | Sign Up   View a printable version of the current page.  
  Use Case Template
Added by Christian Scholz , last edited by Christian Scholz on Apr 21, 2008
Labels: 
(None)

   

General Information  

Name/Goal e.g.: The user wants to create a new account (should be the same as the page name)
Release 1 (increase on final edits/copy before)
Status
Draft
Author(s) Put your name(s) here.
Trigger The user clickt the Register button
Primary Actor
User
Success Guarantee
The user has registered a new account
Minimal Guarantee
The database state is in a valid state
Preconditions
The user needs to have an OpenID
Context of Use
website
Parent Use Cases
link the parent use case here if available
Sub Use Cases
list of sub usecases which are referenced  

Main Success Senario

(list the steps which are the ones to reach the goal without any failures)

  1. The system presents a registration form (see form definition below)
  2. The user fills in the details and submits the form 
  3. The system validates the data and creates a new user
  4. The system send a confirmation email to the user's email address
  5. The user clicks the link inside the email
  6. The system activates the new user

Extensons

 (list the failure cases with extended steps here)

3a. The passwords do not match
3a1. The system displays an appropriate message to the user and asks him to try again
3a2. back to 1. with already submitted values displayed in the form.

3b. The username is already taken
3b1. The system displays a message
3b2. back to 1. with already submitted values displayed in the form.

5a. The user does not click the link
5a1. The system disabled the user account after 30 days.

5a1a. The user tries to login with the 30 days.
5a1a1. The system displays a message that he needs to active his account and offers the possibility to resend the confirmation link.
5a1a2. The user looks up the URL and clicks the confirmation link. Back to 6.

5a1a1a. The user does not have the email anymore
5a1a1a1. The user asks the system to send the link again
5a1a1a2. back to 4

(please delete this part, it's just an example of nested extensions and failures within failures).

Data Descriptions

(list here the data presented in e.g. the form in 1.)

User Registration Form

Field Type
Username String
Password
String
Password Confirmation
String
EMail Address
EMail

Open Issues

  • Issue 1
  • Issue 2

Comments

 Please add comments here. Do not edit the above use case without talking to the author(s).

Powered by Atlassian Confluence 2.7.1, the Enterprise Wiki. Bug/feature request - Atlassian news - Contact administrators