AG Liquid Feedback/Use Cases

Use Cases

Actors

1. Visitor Someone using the system without beeing logged in.
2. User Someone who is registered with the sytem and logged in
3. Initiator A user becomes initiator of an initiative if he created it
4. Supporter A user becomes supporter of an initiative if he supports it
5. Administrator A user who has special rights to administer the system

Catalog

1. Initiative A proposal created by a initiator which is to be decided upon by users. An initiative belongs to one area.
2. Delegation A user can delegate his vote to another user regarding an area
3. Area A hierarchical grouping of interests.

User Administration

User Self Register

Name UC1

Description A new User is created and all necessary data is collected and inserted into the relevant tables.

Actors Visitor Administrator

Status WorkInProgress

Includes none

Trigger Visitor clicks on "register"

Preconditions

1. Theres no user with the requested Name already registered
2. User self registration is enabled

Invariants none

Postconditions

Normal Flow

1. Visitor clicks on Self Register Link
2. System provides user registration form
3. Visitor fills in the required data, clicks submit
4. System does validation and if validation erros occur, the user registration form is presented again with the fields causing the validation error marked in red and accompanied with a validation error message pointing out the problem.
5. If validation passes, user is presented the welcome page and automatically logged in.

Alternative flow none

Hints none

Use Case History

1. Ov3rdriv3 13:43, 29. Jul. 2012 (CEST) Initial definition

Login Problems

Name UC2

Description
A Visitor is having login problems. If he does not already have an account, he gets information on how to get one, or, if he recieved an token that has expired, he can enter his email-adress to request a new token. If he already has an account, he can request another token to change his username or password. For every of these actions except the registration, there's a note left in the database.

Actors Visitors

Status WorkInProgress

Includes none

Trigger Visitor clicks on "I have login problems"

Preconditions none

Invariants none

Postconditions

Normal Flow

1. Visitor clicks on "I have login problems"-Link
2. System asks: "Do you have an active account?"
   • Visitor clicks on "No"-Link

   • System writes: "You need an account to log in."
     + <registration information>
     
     Did you recieved a token? Try clicking on the Link in the email you recieved from us or enter the token here and click on the submit button:"
     + Textbox + Submit-Button
     
     and the system goes on: "If this doesn't help, you can request a new token (works only if you already recieved a token from us). Please enter your email-adress and press the submit button."
     + Textbox + Submit-Button
     
     and the system still goes on: "If nothing of this works, try to reach our administrator:"
     + Contact-Form.

   • Visitor clicks on "Yes"-Link

   • System writes: "We could send you an email to the adress that's saved in your account, so you can change your login-data. Just enter your email-adress an press the submit button:"
     + textbox + submit-button
     
     and the system goes on: "If you already recieved a token, enter it here:"
     + textbox + submit-button
     
     and the system still goes on: "If this doesn't help, try to reach our administrator:"
     + Contact-Form.

3. Visitor fills in the required data, clicks submit
4. System does validation with the entered token or the cantact-form and if validation erros occur, the form is presented again with the fields causing the validation error marked in red and accompanied with one of the following validation error messages pointing out the problem:

   1. "Please fill in the missing fields, to proceed."
   2. "The token you have enterd has expired. Please request a new one."
   3. "The token you have enterd is not valid. You have x more trials."
   4. "You have enterd more than x times a wrong token. Please try to contact our administrator."

5. If the visitor has entered a token and the validation is correct, he becomes a user (new session) and becomes redirected to the relevant page.
6. if the visitor has entered a message for the administrator and the validation is correct, an email is sent.
7. If the visitor has entered an email-adress, the system writes: "Thank you. If your email-adress matches with one of the accounts, you will recieve an email with a new token from us."
8. A note about the visitor-action is left in the relevant database-table.

Alternative flow none

Hints none

Use Case History

1. Michael Palm 18:30, 29. Jul. 2012 (CEST) Initial definition / Not finished
2. Michael Palm 16:01, 30. Jul. 2012 (CEST) Finished