Updated: 11/12/16
Use Cases
| Use Case ID | Project | Use Case Name |
|---|---|---|
| UC1 | Design Guide | Find Component |
| UC2 | Design Guide | Find Design Element |
| UC3 | MDT Dashboard | Dashboard Login |
| UC4 | MDT Dashboard | Patient Search |
| UC5 | MDT Dashboard | Patient Information |
| UC6 | Dashboard | Patient Information Visualisation |
| UC7 | Dashboard | Patient Information Visualisation Dynamic |
| UC8 | Dashboard | Patient Information Visualisation Interactive |
| UC9 | Form Renderer | Form Loading |
| UC10 | Form Renderer | Form Filling |
| UC11 | Form Renderer | Form Submission |
Click on any use case to expand.
Expanded View
| USE CASE | Find Component |
| ID | UC1 |
| BRIEF DESCRIPTION | A user consults the design guide for component guidelines |
| PRIMARY ACTORS | User |
| SECONDARY ACTORS | None |
| PRECONDITIONS | None |
| MAIN FLOW | 1. The use case is initiated when the user access the design guide website
2. The user navigates to the appropriate section 3. The user finds the component he/she is looking for 4. The user reads the guidelines to create the component |
| POSTCONDITIONS | None |
| ALTERNATIVE FLOWS | None |
| USE CASE | Find Design Element |
| ID | UC2 |
| BRIEF DESCRIPTION | A user consults the design guide for a design element |
| PRIMARY ACTORS | User |
| SECONDARY ACTORS | None |
| PRECONDITIONS | None |
| MAIN FLOW | 1. The use case is initiated when the user access the design guide website
2. The user navigates to the appropriate section 3. The user finds the design guidelines he/she is looking for 4. The user follows these guidelines while creating the appropriate pages |
| POSTCONDITIONS | None |
| ALTERNATIVE FLOWS | None |
| USE CASE | Dashboard Login |
| ID | UC3 |
| BRIEF DESCRIPTION | A user logs into the MDT dashboard |
| PRIMARY ACTORS | User |
| SECONDARY ACTORS | None |
| PRECONDITIONS | None |
| MAIN FLOW | 1. The use case is initiated when the user access the MDT Dashboard
2. The user enters the appropriate login information 3. The user chooses to log in as a MDT staff or a clinician |
| POSTCONDITIONS | None |
| ALTERNATIVE FLOWS | None |
| USE CASE | Patient Search |
| ID | UC4 |
| BRIEF DESCRIPTION | A user searches for a patient on the MDT dashboard |
| PRIMARY ACTORS | User |
| SECONDARY ACTORS | None |
| PRECONDITIONS | Dashboard Login |
| MAIN FLOW | 1. The use case is initiated when the user access the MDT Dashboard Patient search
2. The user enters the patient's name in the patient search bar 3. The user selects the correct patient from the dropdown |
| POSTCONDITIONS | None |
| ALTERNATIVE FLOWS | None |
| USE CASE | Patient Information |
| ID | UC5 |
| BRIEF DESCRIPTION | A user identifies the patient and attemps to grasp the current health status of the patient through past records |
| PRIMARY ACTORS | User |
| SECONDARY ACTORS | None |
| PRECONDITIONS | Dashboard Login, Patient Search |
| MAIN FLOW | 1. The use case is initiated when the user has selected a patient through "patient search"
2. The user is able to access different pieces of information about the user displayed on the user's profile page |
| POSTCONDITIONS | None |
| ALTERNATIVE FLOWS | None |
| USE CASE | Patient Information Visualisation |
| ID | UC6 |
| BRIEF DESCRIPTION | A user wishes to see some patient data in graph form or other forms of visualisation |
| PRIMARY ACTORS | User |
| SECONDARY ACTORS | None |
| PRECONDITIONS | Dashboard Login, Patient Search |
| MAIN FLOW | 1. The use case is initiated when the user selects the option to display a certain type of data in a certain form
2. The web app visualises the data and the visualisation is presented to the user 3. The user gains more patient information more accurately and quickly |
| POSTCONDITIONS | None |
| ALTERNATIVE FLOWS | None |
| USE CASE | Patient Information Visualisation Dynamic |
| ID | UC7 |
| BRIEF DESCRIPTION | A user wishes to see some patient data in dynamic visualisation |
| PRIMARY ACTORS | User |
| SECONDARY ACTORS | None |
| PRECONDITIONS | Dashboard Login, Patient Search |
| MAIN FLOW | 1. The use case is initiated when the user selects the option to display a certain type of data in dynamic form
2. The web app visualises the data and the visualisation is presented dynamically to the user 3. (Dynamic visualisation maybe more appropriate for some types of data than others) 4. The user gains more patient information more accurately and quickly |
| POSTCONDITIONS | None |
| ALTERNATIVE FLOWS | None |
| USE CASE | Patient Information Visualisation Interactive |
| ID | UC8 |
| BRIEF DESCRIPTION | A user wishes to see some patient data in interactive visualisation |
| PRIMARY ACTORS | User |
| SECONDARY ACTORS | None |
| PRECONDITIONS | Dashboard Login, Patient Search |
| MAIN FLOW | 1. The use case is initiated when the user selects the option to display a certain type of data in interactive form
2. The web app visualises the data and the visualisation is presented to the user with interactive options 3. (interactive visualisation maybe more appropriate for some types of data than others) 4. The user gains more patient information while given the ability to modify parameters |
| POSTCONDITIONS | None |
| ALTERNATIVE FLOWS | None |
| USE CASE | Form Loading |
| ID | UC9 |
| BRIEF DESCRIPTION | A user requests a form |
| PRIMARY ACTORS | User |
| SECONDARY ACTORS | None |
| PRECONDITIONS | Dashboard Login, Patient Search |
| MAIN FLOW | 1. The use case is initiated when the user selects a form to fill in for submission
2. The form renderer collects the necessary components from the backend and generates the form 3. The form is displayed for the user to fill in |
| POSTCONDITIONS | None |
| ALTERNATIVE FLOWS | None |
| USE CASE | Form Filling |
| ID | UC10 |
| BRIEF DESCRIPTION | A user fills in a form |
| PRIMARY ACTORS | User |
| SECONDARY ACTORS | None |
| PRECONDITIONS | Dashboard Login, Patient Search, Form Loading |
| MAIN FLOW | 1. The use case is initiated after the user has the requested form on screen
2. The user inputs the necessary information with automated input format detector |
| POSTCONDITIONS | None |
| ALTERNATIVE FLOWS | None |
| USE CASE | Form Submission |
| ID | UC11 |
| BRIEF DESCRIPTION | A user submits a form |
| PRIMARY ACTORS | User |
| SECONDARY ACTORS | None |
| PRECONDITIONS | Dashboard Login, Patient Search, Form Loading, Form Filling |
| MAIN FLOW | 1. The use case is initiated after the user has filled in a form
2. The user clicks the submit button to submit the form |
| POSTCONDITIONS | None |
| ALTERNATIVE FLOWS | None |
Tags
background research testing dashboard plans for term 2 our project architecture research