| Use Case | Login |
|---|---|
| Id | 1 |
| Brief Description | Users can log in |
| Primary Actors | User |
| Secondary Actors | None |
| Preconditions | 1. User must have the app installed |
| Main Flow | 1. User selects app icon on the screen. 2. Android client displays login screen. 3. User enters details. 4. User selects log in option. 5. Android client displays the home page |
| PostCondition | 1. User successfully logged in. |
| Alternative Flows | WrongLogin |
| Use Case | Alternative Flow: Login:WrongLogin |
|---|---|
| Id | 1.1 |
| Brief Description | Android client informs user of wrong login details |
| Primary Actors | User |
| Secondary Actors | None |
| Preconditions | 1. User has selected log in option |
| Main Flow | 1. The alternative flow starts after step 4 of the main flow. 2. Android client displays a wrong login details message. 3. Android client returns to login screen. |
| PostCondition | None |
| Alternative Flows | None |
| Use Case | Register |
|---|---|
| Id | 2 |
| Brief Description | User can register on the Android client |
| Primary Actors | User |
| Secondary Actors | None |
| Preconditions | 1. User must have the app installed |
| Main Flow | 1. User selects app icon on the screen 2. Android client displays login screen 3. User chooses register option 4. Android client displays register page 5. User fills out missing information 6. User selects sign up option 7. Android client displays a successfully registered message 8. Android client returns to login screen |
| PostCondition | 1. User successfully registered |
| Alternative Flows | IncorrectDetails |
| Use Case | Alternative Flow: Register:IncorrectDetails |
|---|---|
| Id | 2.1 |
| Brief Description | Android client informs user of incorrect details |
| Primary Actors | User |
| Secondary Actors | None |
| Preconditions | 1. User has selected sign up option |
| Main Flow | 1. The alternative flow starts after step 6 of the main flow 2. Android client displays an incorrect details message 3. Android client returns to register page |
| PostCondition | None |
| Alternative Flows | None |
| View Data | Create New Patient |
|---|---|
| Id | 3 |
| Brief Description | User can view their vital data |
| Primary Actors | User |
| Secondary Actors | System |
| Preconditions | 1. User must be loggin in |
| Main Flow | 1. Android client displays the home page 2. User selects one from the list 3. Android client displays a new page that contains information |
| PostCondition | 1. The information page is displayed |
| Alternative Flows | None |
| Use Case | Send Data |
|---|---|
| Id | 4 |
| Brief Description | User can update their vital information |
| Primary Actors | User |
| Secondary Actors | None |
| Preconditions | 1. User must be logged in |
| Main Flow | 1. User selects Input option 2. Android client displays a list of vitals 3. User chooses the required one 4. Android client displays the input form 5. User fill in missing data 6. User chooses save option 7. Android client displays a successful message 8. Android client returns to home page |
| PostCondition | 1. Vital information is updated |
| Alternative Flows | IncorrectData |
| Use Case | Alternative Flow: SendData:IncorrectData |
|---|---|
| Id | 4.1 |
| Brief Description | Android client informs user of incorrect data entered |
| Primary Actors | User |
| Secondary Actors | None |
| Preconditions | 1. User has submitted data using input form |
| Main Flow | 1. The alternative flow starts after step 6 of the main flow 2. The Android client displays an incorrect data message 3. The Android client returns to input form page |
| PostCondition | None |
| Alternative Flows | None |
| Use Case | Data Synchronisation |
|---|---|
| Id | 5 |
| Brief Description | User can synchronise their data from other apps with Android client |
| Primary Actors | User |
| Secondary Actors | None |
| Preconditions | 1. User must be logged in 2. User must have supported apps installed/th> |
| Main Flow | 1. User selects synchronise option 2. Android client displays a list of apps 3. User chooses one option 4. Android client displays a successful message 5. Android client returns to home page |
| PostCondition | 1. Android client synchronises with other apps |
| Alternative Flows | None |
| Use Case | Data Sharing |
|---|---|
| Id | 6 |
| Brief Description | User can share data with health providers |
| Primary Actors | User |
| Secondary Actors | None |
| Preconditions | 1. User must be logged in |
| Main Flow | 1. User selects share option 2. Android client displays a list of health providers 3. User ticks the desired health provider(s) 4. User selects save option 5. Android client displays a successful message 6. Android client returns to the home page |
| PostCondition | 1. Android client shares user’s vital data with health providers |
| Alternative Flows | None |
| Use Case | Edit Profile |
|---|---|
| Id | 7 |
| Brief Description | User edit personal profile |
| Primary Actors | User |
| Secondary Actors | None |
| Preconditions | 1. User must be logged in |
| Main Flow | 1. User selects edit profile option 2. Android client displays user’s profile page 3. User fills in what needs to be changed 4. User selects save option 5. Android client displays a successful message 6. Android client returns to home page |
| PostCondition | 1. User successfully edited person profile |
| Alternative Flows | None |
| Use Case | Delete Account |
|---|---|
| Id | 8 |
| Brief Description | User can delete account |
| Primary Actors | User |
| Secondary Actors | None |
| Preconditions | 1. User must be logged in |
| Main Flow | 1. User selects delete account option 2. Android client displays a confirmation pop up 3. User selects confirm option 4. Android client displays log in screen |
| PostCondition | 1. User’s account has been deleted from the database |
| Alternative Flows | None |
| Use Case | Data Visualisation |
|---|---|
| Id | 9 |
| Brief Description | User can display data under different forms |
| Primary Actors | User |
| Secondary Actors | None |
| Preconditions | 1. User must be logged in |
| Main Flow | 1. User selects delete data visualisaton option 2. Android client displays a list of available options 3. User chooses one option 4. Android client displays a successful message 5. Android client returns to home page |
| PostCondition | 1. User has applied data visualisation preference |
| Alternative Flows | None |