-
Notifications
You must be signed in to change notification settings - Fork 5
Habits
Nazim Bhuiyan edited this page Oct 13, 2017
·
7 revisions
UC 01.01.01 | |
---|---|
Use Case Name | AddHabit |
Participating actors | User |
Goal | Add new habit to profile |
Trigger | User selects add habit button |
Precondition | User is logged in |
Postcondition | New habit is added |
Basic Flow | 1. User selects add habit button |
2. User enters habit type, title, reason, what days of the week it should occur, and date to start | |
3. App adds habit to profile | |
Exceptions | As a participant, I want a habit title to be no more than 20 characters and habit reason to be no more than 30 characters. |
Related artifacts | US 01.01.01, US 01.02.01, US 01.06.01 |
UC 01.02.01 | |
---|---|
Use Case Name | ViewHabit |
Participating actors | User |
Goal | View habit and its corresponding details: Name, message, start date, repeating days, status indicator |
Trigger | User selects the habit from the list of habits |
Precondition | User is logged in |
Postcondition | Habit details are displayed |
Basic Flow | 1. User selects habit whose information they want displayed |
2. App displays habit information | |
Exceptions | |
Related artifacts | US 01.03.01, US 01.07.01, US 01.08.01 |
UC 01.03.01 | |
---|---|
Use Case Name | EditHabit |
Participating actors | User |
Goal | Edit habit and its corresponding details |
Trigger | User selects the habit from the list of habits |
Precondition | User is logged in |
Postcondition | Habit information is updated |
Basic Flow | 1. User selects habit whose information they want displayed |
2. User edits habit details | |
3. User presses done | |
4. App updates habit information | |
Exceptions | habit title to be no more than 20 characters and habit reason to be no more than 30 characters |
Related artifacts | US 01.04.01, US 01.06.01 |
UC 01.04.01 | |
---|---|
Use Case Name | DeleteHabit |
Participating actors | User |
Goal | Delete an existing habit |
Trigger | User selects the habit from the list of habits |
Precondition | User is logged in |
Postcondition | Habit is deleted |
Basic Flow | 1. User selects habit from list of habits |
2. User presses delete | |
3. App deletes habit | |
Exceptions | |
Related artifacts | US 01.05.01 |
UC 01.05.01 | |
---|---|
Use Case Name | ViewTodaysHabits |
Participating actors | User |
Goal | View the habits to do today |
Trigger | User selects the today option for the list of habits |
Precondition | User is logged in |
Postcondition | List of habits set for the current day appears |
Basic Flow | 1. User selects today |
2. App displays the list of habits to be done today | |
Exceptions | |
Related artifacts | US 01.07.01 |
UC 01.06.01 | |
---|---|
Use Case Name | ViewHabitProgressByType |
Participating actors | User |
Goal | View the habit progress status by habit type |
Trigger | User selects view habit progress |
Precondition | User is logged in |
Postcondition | List of habits progress by type appears |
Basic Flow | 1. User selects habit progress |
2. App displays the list of habit progress by type | |
Exceptions | |
Related artifacts | US 01.07.01 |
Copyright (c) 2017 CMPUT301F17T11
Please abide by the Code of Student Behavior and the Computing Science Department Course Policies of the University of Alberta.
This Project is licensed under the MIT License. Click here to view the full license terms.
- Meetings
- Project Part 2
- Project Part 3
- Project Part 4
- Project Part 5