Combined Report Summary

	A	B	C	D	E	F	G	H	I	J	K
1	Key Function	Sub task	ID number	Grouping	Problem	Severity	Problem Justification	Recommendation	Heurastics Principle	Owner	Comments

2	Enter Data	Entering Triggers	1	Visual - Icon	Delete button text is not aligned to the center	1	The red plus signs are misleading because users might associate plus sign as "add" function instead of red cross symbol. Symbol is not repesenting the triggers, so users might associate the icon with "plus" symbol. This might lead to confusion to users.	- Change the red plus signs to green checked icons once selected, instead of displaying blue check sign on the right. - Using iconography that matches the trigger would aid users better.	Visibility of system status	Sup
3		Entering Triggers	2	Visual - Icon	Icons for Triggers is used inconsistently between the landing page and the trigger listing page.	1	Icon differences may confuse the user about where they are and what they can do in the screen, causing the user to slow down and be frustrated.	Use consistent icons everywhere Triggers are shown, use the new suggested icon for Triggers provided in style guide.	Consistency and Standards, Match Real World	Ann
4		Main Page	3	Visual - Communication	User can not see full list of selected Symptoms, Triggers, and Medication from main page, before clicking Save Record.	2	User cannot review the list for accuracy without clicking through to the selection lists.	Show full list of data.	Error Prevention	Ann
5		Save Entered Data	4	Visual - Communciation/feedback	Save Record Button is not visually salient enough to alert user that need to press button to submit information entered within "Enter Data" area.	2	Micro interactions for each entry screen (ex Peak Flow) allow user to enter/select value, but no feedback that data accepted into entry. When use back button to return to Enter Data area, some feedback that values entered as summary appears. But not obvious data still not submitted - must click save record. Save Record button is small and does not appear to be part of submitting current record and appears in same visual state whether user has entered information for record or not.	Consider making Save Record button near bottom of screen, spanning width of screen, using Main button style from style guide. Button should be in inactive state until the user enters all required information, use Main inactive button style from style guide.	Visibility of system status	MJ
6		Save Entered Data	5	Visual - Communciation	User does not have cues on whether they are entering data or not. User has to hit back button to go to a main dashboard to see if the data has been entered. On iphone it has "enter data" button.	3	Users are afraid of back button because they fear losing data.	Consider including a "Cancel" button to back-out of screen at top left of screen, using secondary button style from style guide, Include "Enter Data" button to save entered information at tope right of screen, using primary button style from the style guide.	Error Prevention, Consistency and Standards, Match Real World	MJ
7		Save Entered Data	6	Visual - Communication	Inconsistent visual aid - "Active" pages are highlighted blue but also bread crumbs like "save button" is also highlighted blue	1	This might be misleading users to think that the highlighted blue buttons are already saved, although will not be saved until users hit the button	Highlight active pages with blue color and make button colors to green color. Change the button location to bottom of the page	Visibility of system status, Consistency and Standards	Sup
8		Save Entered Data	7	Functional	User may have accidently clicked on Save Record, there is no way for user to stop saving action.	2	By accidentally hitting the Save Record button, the user's task is stopped and they need to restart entering the data, causing frustration. They would also need to find how to delete the accidental record entry.	Provide a dialog box as stated in the style to ask user "Continue saving record?" with a Cancel button and a OK button.	Error Prevention, Help with Errors	Ann	Maybe use this as jusftification
9		Save Entered Data	8	Functional, Communication	When user clicks save record with no fields filled out, error message includes 'fev1'. Seems like a generic message unrelated to fields user sees on screen.	2	User may become confused to see items in the error message that aren't on the screen, they may feel they won't be able to fill in the data correctly.	In the error message, match the missing required fields with the fields the user sees on the screen.	Error Prevention, Help with Errors, Consistency and Standards	Ann	"You must fill in data"
10		Enter Custom Symptoms	9	Functional	Users do not have freedom to add symptoms.	2	While users are able to add custom triggers and medications, they are not able to add custom symptoms. This inconsistency might lead to a lack of user satisfaction. User may not continue using application as it doesn't fit their needs.	Add custom symptom functionality, similar to the triggers page.	User control and freedom, Consistency and Standards, Flexibility and Efficiency of Use	Sup
11		Enter Symptoms	10	Functional	The logic of the symptoms is not consistent - On the symptoms section, when user clicks on “no cough, wheeze, chest tightness, or shortness of breath during the day or night” the checked symptoms (cough, wheeze, chest tightness, shortness of breath) are automatically unchecked, preventing users to record conflicting data. However, it does not prevent the error for when user checks both “can do usual activities” and “cannot do usual activities.,” allowing users submit conflicting data..	3	Users will lose trust of the app.	When users check "can do usual activities" all the items relating to usual activities on "worse" or "critical" symptoms should be unchecked.	Error prevention		Include Picture
12		Enter Symptoms	11	Visual - Icon	Iconography does not communicate anything - all the symptoms (well, worse, critical) use the same icons.	1	The icons do not communicate or guide users, they may not understand their place in the page and need to scroll page know where they are. This can lead to confusion.	Phase 1 - change the colors of icon (green - well), (worse - yellow), (critical - red), Phase 2 - create actual icon system for symptoms	Recognition rather than recall	Sup
13		Enter Symptoms	12	Communication	Under Symptoms, critical has option with wording "Yellow Zone". On the same screen, what is Yellow Zone is called worse.	2	User may not understand the term causing them to slow down and be confused.	Add color coding for for Well (Green), Worse (Yellow), Critical(Red) in the headers for each section on the screen (for Well, Worse, Critical) to help reinforce the Zone and associated colors. Consider reducing the taxonomy and using one set of terms.	Help with Errors, Match Real World, Recognition rather than recall	Ann
14		Enter Custom Medication	13	Functional	Enter Data/Medication area does not have option to update app's list of medications, only an option to manually add custom medication.	3	Forcing user to manually enter medication increases liklihood of a data entry error and a misundrstanding of prescription by a third party that references app for patient. Additionally, user may choose to abandon app and adopt another application that provides regular medication updates that comport with ever changing pharmacutical market.	Suggest to remove Edit Action plan button from screen. User should only edit action plan from the action plan area of the application. On action plan screen: Provide option to update app medication list/mechanism to check for updates that is salient to user. - List is not complete and also popular medications are not listed - Your regimen might change	Error prevention, Recognition rather than recall	MJ	Important
15		Enter Medication/Simple Plan vs. Asthma Action Plan	14	Functional	Option to enter medication under "Simple Plan" or "Asthma Action Plan" complicates user's medication entry, revision, and action plan reference	4	Once enter medication under either Simple Plan or Asthma Action plan, this high level menu option goes away and user has no ability to choose to revise medication by selecting the other option. This may frustrate the user as s/he may want to revise how initially entered medication. This may also disorient user as the medication screen changes so much that user may assume they were in a different section of the app when the initially entered medication. User may abandon app if cannot recover. Additionally, Action Plan use is implemented differently depending on whether user entered medication via Simple Plan or Asthma Action Plan options. This is confusing to user and increases likelihood that user will incorrectly use action plan functionality, not use action plan functionality at all, or abandon app altogether.	This needs to be added to new feature list to complete User interaction design: Suggestion eliminate Simple Plan medication entry option. Medication entry should have one clear pathway for entry that directly comports with Action Plan functionality.	Consistency and standards, Help with Errors, Error prevention, Flexibility and Efficiency of Use	MJ	Create interation to onboard new users and educate them about stages of action plan - Do not edit data inside enter data, do that at action plan - Rescue > Controller associated Green>Yellow - Edit Action plan > error prevention - Recommendation
16	Diary Chart	Enter Symptoms to Edit the Data	15	Visual	Cancel button location is not consistent.	2	Inconsistent placement of cancel button, users might make mistakes.	Consider replacing cancel with back button. Place save button in the bottom with main button style from style guide.	Consistency and Standards	Sup
17		Delete Button	16	Visual	Delete button text is not aligned to the center	1	Minor aesthetic problem decreasing credibility of the app.	Align the tex to center		Sup
18		Add User	17	Functional	Add User screen does not have cancel button.	1	User may decide to not add a person after all, the back button is not obvious as a cancel. User can become frustrated trying to exit screen.	Add a cancel button on the top right of the screen in the blue bar.	Consistency and Standards, Control and Freedom	Ann	On android "add person" whole user system - first, it does not prevent error when u do not put in name, no edit button on the pre selected list,
19		Add User	18	Functional	User cannot delete a person from list.	2	User will be frustrated to have people listed that should no longer be on list. They may accidently report to people who should no longer receive it.	Suggest a new screen for person information, with an option to delete person.	Control and Freedom, Error Prevention, Flexibility and Efficiency of Use		Note: iPhone does not include Name as a field for the add people screen. Nor does it include DR/RN, School, Other.
20		Add User	19	Feedback	Can add a user more than once (same email more than once), it creates duplicate records.	2	User can accidentally add a user more than once without being alerted of duplication, which can cause confusion over which record is correct, and be overwhelmed by having a list longer than necessary.	Suggest preventing user from adding email more than once and alerting with a dialog box message "Email is already in use with another record."	Error Prevention	Ann
21		Add User	20	Functional	Person email or name may change, and it cannot be edited.	3	User may need to edit a person's (email or name) information. User will be frustrated with a list that includes inaccurate information. User is slowed down needing to think about which people in list have accurate information	Suggest a new screen for person information, allowing user to edit input boxes for name and email.	Error Prevention, Flexibility and Efficiency of Use	Ann
22		Add User	21	Feedback	Not requiring name makes it hard to identify user on send screen.	3	User will be frustrated being able to identify who the report is being sent to. User may not know who is listed and list a person duplicate times.	Require the name field when adding or editing a person.	Error Prevention	Ann
23		Viewing Reports	22	Visual - Icon	Icons for Triggers is used inconsistently between the landing page and the trigger listing page.	1	Icon differences may confuse the user about where they are and what they can do in the screen, causing the user to slow down and be frustrated.	Use consistent icons everywhere Triggers are shown, use the new suggested icon for Triggers provided in style guide.	Consistency and Standards, Match Real World	Ann
24		Viewing Reports	23	Communication	Abbreviation PFM is used for Peak Flow, along with the wording Peak Flow. Value is displayed twice.	1	Duplicated content may confuse the user, as they wonder how the content could be different, this can slow them as they use the application and complete their task.	Remove PFM from the display.	Consistency and Standards, Aesthetics and Minimal Design	Ann
25		Status Messages	24	Feedback	Status messaging usage is inconsistent. Sometimes the user is alerted of an action that will happen, something they are alerted after it has happened. Delete record alerts and shows the uploading to cloud screen. Send Report does not alert, but gives user message it was sent.	2	Inconsistent user of feedback through dialogs may cause the user frustration and need to redo tasks as it is not clear what will or has happened. User may stop using application due to lack of feedback and messaging.	Create a consistent experience with dialog boxes, providing users with the ability to stop or continue with actions, such as sending a report.	Consistency and Standards, Error Prevention	Ann
26		Rotate Screen	25	Reminder	User needs to recall that rotating screen will show records chart over time.	2	User may not realize there are other features to look at, and not see and utilize all the information they have access to.	Either present the same information regardless of orientation or make sure there is always a hint that if the orientation changes, new information will be shown.	Recall v Recognition	Ann
27		Rotate Screen	26	Reminder	User is unaware that if they turn phone horizontally, different/new information is presented to them on certain screens.	2	User may not realize there are other features to look at, and not see and utilize all the information they have access to.	Either present the same information regardless of orientation or make sure there is always a hint that if the orientation changes, new information will be shown.	Visibility of system status	Carli
28		Main Page	27	Visual	Text shows under arrows.	1	User needs to strain to see text under the arrow, they may be frustrated due to not seeing the information they are about to send.	Clean up layout so text wraps before it goes under arrow, leaving 10pixels of space between text and arrow.	Aesthetics and Minimal Design	Ann
29		Main Page	28	Visual	Records within a date run together and is cluttered. Items appear to run together.	1	User may have a hard time seing when one record stops and the next starts, causing the user to slow down when reviewing they records before sending.	Add a 3 pixel tall border between records within a date.	Aesthetics and Minimal Design	Ann
30	Reminders	Edit reminders	29	Visual	To turn or change the reminder, user must slide the circle/knob. However, the element does not look like a slider. Therefore, the user does not understand what action they should take.	2	See comment to the right.	Change UI element to look more like a slider, or develop it so that user can just tap, which is more in-line with what the UI element appears to do.	Match between system and the real world	Carli	- get rid of "first" wording or change the order list - either allow user to enter as prescribed or completely customized
31	Action Plan	Add customer Resque Meds pop up	29	Functional	No exit, cancel paths with the pop up	4	Users cannot cancel, exit out of the custom meds pop up. Users are forced to input false data in order to exit. Once the false data is entered, users cannot delete the medications from the list. This is critical mistake of the app, users will feel frustrated with the interaction.	- Create cancel button on the pop up, allowing users to exit. - Create edit button on top and allow users to delete entered data	User control and freedom	Sup
32		Check mark medication	30	Visual	Checkmark area is small.	2	The small area can slow the user down from missed touches. Difference of touch area size from similar screens may slow down and confuse users.	Make the whole background of the item background touchable.	Consistency & Standards	Ann	Android problem
33		Check mark medication	31	Logic	Check marks need to be checked in order down the page is unclear. Grey versus white background lacks information for significance.	3	Unclear instructions will slow down users with missed touches on touching items out of order, leading to inefficiency and frustration.	Add progress lines from the first to last medicine listed as on the yellow action plan screen. Provide contextual help screen to provide ifnroamtion about the button background colors. Screen should slide out on top of the current screen, Help icon should be at the top right of the screen.	Provide Help, Control & Freedom	Ann	Logic is not clear - it is allowing you to select things in a sequencial order. However, it is unclear.
34		Check mark medication	32	Visual	Check marks are different from similar screens throughout the application.	1	Users may slow down or wonder about the difference between check mark icons.	Use similar checkmarks throughout the application. Use the check marks provided in this screenshot wherever check marks are used on the whole app.	Consistency & Standards	Ann
35		Start action plan	33	Visual	In the yellow action plan, the word 'Start' needs to be precisely touched to start the action plan.	2	The small area can slow the user down from missed touches. Difference of touch area size from similar screens may slow down and confuse users.	Make the whole background of the Start action plan touchable. - make affordance	Control, Consistency & Standards	Ann
36		Stop action plan	34	Visual, Feedback	Stopping Yellow action provides no alert to confirm action.	4	Action plans can take up to 1.5 hours, user may accidentally touch Stop, which may require user to start a new action plan part way through treatment and miss timed medication, frustrating user and causing potential health issues. User may decide the application does not fit their asthma treatment needs.	Provide a dialog for user to confirm stopping of action plan.	Error Prevention	Ann	no pause
37		Progress through action plan	35	Visual	When timed progress reaches How are you steps. If status is Green or Yellow based on answers to questions, the screen goes back to the progress screen without a prompt to help the user know what to do next. Red asked user if they wanted to disabled Yellow plan progress, which then ends test. Label "disable" in Red dialog for disable doesn't match action on Yellow zone screen "stop."	4	User may not know what next steps are based on answers, they may not realize what they need to do to start the next step, they slow down as they work out what to do next. User may be confused between the difference in "disable" and "stop."	Provide a dialog to help the user understand what they can do next, like the Red Zone dialog in the screenshot. For Red - "You are in the Red Zone. Do you want to stop the yellow action plan and call emergency?" Yes - Take user to Red zone screen, where the user can call emergency. No - take user to Yellow zone screen, where the next step starts (oh, this is bad). For Green - "You are in the Green Zone. Do you want to continue with yellow zone?" Yes - Take user to Yellow zone, where the next step starts. No - Take user to Green zone. For Yellow - "You are in the Yellow Zone. Do you want to continue with yellow zone?" Yes - Take user to Yellow zone, where the next step starts. No - Take user to Green zone. (need something better)	Help with Errors, consistency & Standards	Ann
38		Start action plan	36	Edit button should not be here	Edit button disappears when yellow action plan is started and users goes to another section of app during action plan progress. After the action plan is completed, the Edit button returned if user goes to another section, then back to action plan.	4	User becomes frustrated and their next task slowed down when a control disappears and they need to click around to see if it comes back. User should not be able to edit a Yellow Action plan when it's in progress, being able to so will cause errors in treatment plan and user might incur possible health issues.	Make sure the Edit button is visible again after the yellow action plan is completed or terminated before completion. Edit button should not be available during the progress of a yellow action plan.	Control and Freedom, Error Prevention	Ann
39		Add Symptom	37	Visual - Icon/Communication	Within Action Plan > Symptoms, icons next to each symptom are all the same. These are not meaningful icons.	1	?????	Remove icons or replace with meaningful icons.	Match between system and the real world	Carli	It would be difficult to find icons to match each symptom, the number of different icons could be hard for the user to understand and be overwhelming.
40	Settings	Reference Help	38	onboarding and place	Label/term definition and help materials are hidden from user within "Settings" section rather than directly available to user during critical app tasks	2	Terms and labels within app, particularly within Enter Data Area screens, may be unfamilar to new asthma patient, caretaker. Terms are domain specific (ex. Peak Flow, Triggers, l/min, Action Plan) by necessity. Users may already be overwhelemed by new terms with a chronic condition and not have patience or tolerance to seek out help materials hidden wihtin other functional areas of the app. RIsk that user will abandon using app OR misunderstand terms and incorrectly use app in a way that risks physical harm.	Consider creating stand-alone "Help" Section with icon/button with bottom menu rather than placing help and definition materials within "Settings. Further consider using Tool Tip definition pop-ups for terms within Enter Data control areas, particuarly within critical areas such as medication entry and action plan set-up.	Match between system and real world/Error prevention/Help and Documentation	MJ
41	Entire App		39	visual	In the upper right-hand corner of the app – depending on the screen, the button is either “cancel” or “save”. Different buttons are shown the same place from screen to screen.	3	The user expects buttons shown in the same place of the screen everywhere they find it. The user can become confused not knowing what action will take place when they change. Their task ompletion will be slowed down. This can also cause errors to be made.	The upper right-hand corner button should be consistent throughout, it should be the main action - save. Cancel should be on the upper Left corner.	Consistency and standards , Error prevention	Carli
42			40	visual	When changing settings or adjusting symptoms, triggers, medications etc., sometimes the user is given the option to save their changes. Other times, they are given the option to go back or cancel.	3	Inconcisistent placement of same elements from screen to screen can confuse the user as to what actions to take, and slow the user down as they need to review what each button does. Errors may be performed if a clearly labeled button the user is expecting is not available. Inconsistent use of buttons can be confusing.	When user needs to save entered data, a save button should be on the screen, at top right corner. On the top left corner should be a cancel button, which takes the user to the previous screen.	Consistency and standards	Carli
43		Save Report/Enter data, Send report/Diary Chart	41	Skip dialog	"Skip for now" functionality is unknown to user	3	The app only explains the save to cloud functionality in the Settings FAQ, user may not realize information would be uploaded to the cloud, user may be confused about where the information is being saved and if it's secure - they may have concerned about HIPPA. User may want to opt-out of feature, and may stop using app do to data sharing.	Allow user to opt out of saving to cloud - google database of anonymous user data.Also seen on enter data.	Control and Freedom, System Status	Ann	Android Specific
44		Save Report/Enter data, Send report/Diary Chart	42	Skip dialog	"Skip for now" dialog disappears before user can interact with it.	3	User will be frustrated that they can not stop the upload action.	In the dialog box from previous issue, allow the user to close dialog with OK button.	Control and Freedom, System Status	Ann	Android Specific
45		Save Report/Enter data, Send report/Diary Chart	43	Skip dialog	User can not interaction with "Skip for Now"	3	When the dialog stay open long enough, the user will try to touch "Skip for Now" and be frustrated the action continues with uploading.	In the dialog box from previous issue, include a Skip Upload button.	Control and Freedom, System Status	Ann	Android Specific
46		Save Report/Enter data, Send report/Diary Chart	44	Skip dialog	Skip for Now dialog is inconsistent display with other dialogs.	3	Difference in dialog design from rest of application can confuse user.	Create dialog (as stated in previous screens) including OK and Skip Upload buttons. After user selection, display message that report was sent and/or uploaded to cloud.	Consistency
47
48	Severity Rating Index	Heuristics
49	0 - Dont agree that this is a usability problem	1- Visibility of system status
50	1 - cosmetic problem	2 - Match between system and real world
51	2 - Minor usability problem	3- User control and freedom
52	3 - major usability problem; important to fix	4 - Consistency and standards
53	4 - usability catastrophe; imperative to fix	5 - Error prevention
54		6 - Recognition rather than recall
55		7 - Flexibility and efficiency of use
56		8 - Aesthetic and minimalist design
57		9 - Help with errors
58		10 - Provide help (if needed)
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100