Use cases

3. Use cases

Use Case 1

name: Adding an exercise to existing program

primary actor(s): user

preconditions: you own the exercise or trainer has sent it to you (you can see the exercise on your list of exercises); you have the existing program

expected result: New exercise added to the program; exercise count is increased by one.

main success scenario:

1. User sees the list of programs he has.
2. User selects a program by tapping on it.
3. User sees a list of exercises that are associated with selected program (are included in selected program)
4. User selects the „exercise“ tab.
5. User sees a list that contains all the exercises that the user has.
6. User clicks the „add“ button behind the name of the exercise.
7. Exercise is added to the program; exercise count is increased by one.

alternative scenarios:

first:

6a) User clicks on the name of the exercise

7a) User sees the screen of the exercise.

8a) User swipes back to the list of exercises. (continues from point 5 in main scenario)

Use Case 2

name: Creating a new program

primary actor(s): user

preconditions: none

expected result: new program is created

main success scenario:

1. User sees the screen of programs view (if he hasn’t got any, the list is empty)
2. User clicks the „add“ button.
3. User sees the list of clients.
4. User selects a client.
5. User sees the screen for creating a program.
6. User names the program.
7. User selects template to use for creating.
8. User presses „forward“ button.
9. Program appears in the list of user programs.
10. User sees a list that contains all the exercises that are in the template.
11. User selects the „exercise“ tab.
12. User sees a list that contains all the exercises that the user has.
13. User clicks the „add“ button behind the name of the exercise.
14. Exercise is added to the program; exercise count is increased by one.

alternative scenarios:

first:

4a) User clicks „add“ button.

5a) User fills in client details.

6a) User selects „add“.

7a) Client is added to the list. (continues from point 4 in main scenario)

second:

4b) User clicks „add“ button.

5b) User fills in client details.

6b) User selects „cancel“.

7b) Client is not added to the list. (continues from point 4 in main scenario)

third:

4c) User clicks „add“ button.

5c) User leaves one client field unfilled.

6c) The „add“ button is not selectable.

7c) User has the opportunity to fill all fields and select „add“ (in which case the client is added to the list) or press „cancel“. (continues from point 4 in main scenario)

fourth:

6d) User does not give the program a name.

7d) User selects template to use for creating.

8d) The „forward“ button is not selectable.

fifth:

7e) User presses „forward“ button.

8e) Program appears in the list of user programs.

9e) User sees an empty list. (continues from point 11 in main scenario)