HI501 · Unit 5

HI501 Unit 5 usability walkthrough example

Health Informatics Purdue University Global Free custom sample in 24 to 48h

A bedtime glucose of 247 on a composite medical ward should lead straight to a correctional insulin dose, yet the scale that converts one into the other sits on a tab the nurse cannot see while charting. At that screen, this HI501 Unit 5 usability walkthrough stops, counts steps and rates each problem against Nielsen's heuristics.

What this page holds

The dose window that hides the insulin scale is the failing screen this HI501 Unit 5 walkthrough names, rates at severity [3] and sketches again. Searches like "hi 501 unit 5 assignment example", "hi501 unit 5 sample" and "hi501 unit 5 example" land here.

What a finished HI501 Unit 5 usability walkthrough looks like

Method comes first and is kept honest: a cognitive walkthrough of one task in a training environment by the composite writer, then two nurses observed completing the same task on a live unit, identifiers excluded. The task is bounded tightly, from glucose result to documented dose. A step table follows with each click, screen and field, the four walkthrough questions answered yes or no at every step, and the seconds taken. Thirteen steps span five screens. At step nine, the dose window asks for units of insulin while the scale sits under order details on another tab, so the nurse either remembers the scale row or leaves and returns. Both observed nurses left and returned. Findings are listed with the heuristic each violates and Nielsen's zero-to-four severity rating.

How a HI501 Unit 5 example is structured

An introduction names the task and why it was chosen: frequent, time-sensitive and easy to get wrong by one scale row. Method follows, with the limits stated in the same paragraph, one writer and two observed nurses being evidence enough for a walkthrough and nowhere near enough for a rate. The step table is the core. Findings come next, one short entry each: what happened, the step, the heuristic, severity and a sentence of consequence. The dose window finding leads, recognition rather than recall at severity [3]; a units field that accepts decimals without warning follows under error prevention; the last glucose shown only as a flag color is a visibility problem. A redesign sketch puts the latest glucose and the matching scale row inside the dose window. The conclusion stays on the observed task.

One task, tightly bounded

Glucose result to documented correctional dose at bedtime, chosen because it is frequent, time-pressed and wrong by a single row when it goes wrong.

Walkthrough plus two observations

A training-environment walkthrough by the writer and two nurses watched on a live unit, with the limits of that evidence stated beside it.

Thirteen steps, five screens

Every click and field in order, the four walkthrough questions answered at each step, and seconds recorded where observation allowed.

Findings with severity

Scale hidden from the dose window, decimals accepted silently, and glucose shown only as a color, each tied to a named heuristic and rated.

A dose window that shows the scale

One redesign sketch placing the latest glucose and its matching row where the dose is entered, with every other step left alone.

Where marks go in HI501 Unit 5

Opinion presented as evaluation is where most walkthroughs fall short: calling a screen cluttered or unintuitive tells a reader nothing a designer could act on. Criteria in this course mostly expect the failing step named, and a paper that reviews the whole product in general terms has usually missed it. Heuristics cited without a step attached lose ground in a similar way, as do severity ratings with no scale identified. Some papers inflate thin evidence, reporting two observations as a finding about all nurses; honesty about sample size tends to be rewarded rather than penalized. A redesign that rebuilds every screen invites the question of cost. The narrower sketch, fixing the observed failure and leaving working steps alone, reads as judgment.

Get a HI501 Unit 5 example written to your instructions

Usability tasks differ widely: some sections name the system and the task, others let the writer choose. Either way, include what Unit 5 hands out, the rubric and any screenshots or descriptions supplied. Expect a step table, rated findings and one redesign sketch within 24-48h, and no fee for a first custom sample.

HI501 Unit 5 questions, answered

Can I do a usability walkthrough without access to a real system?

Yes, with the method adjusted. Many vendors publish demonstration videos, and some courses supply screenshots or a training login. A walkthrough built from those can still count steps and name a failing screen. Say plainly what the source was, since graders read evidence claims closely, and avoid screenshots of any live record from a workplace.

Which heuristics should the walkthrough use?

Nielsen's ten are the most widely cited and suit most tasks. Zhang and colleagues adapted a set for medical devices that some sections prefer for clinical equipment. Whichever set appears, the example's approach holds: each finding names one heuristic, one step and one severity, so a reader can check the match rather than accept a general verdict.

What is the difference between a cognitive walkthrough and heuristic evaluation?

A cognitive walkthrough follows one task step by step and asks whether a new user would know what to do at each point. Heuristic evaluation reviews an interface against a list of principles without necessarily following a task. The example combines them: the walkthrough finds where the task fails, and the heuristics explain why, which suits a paper built around one screen.