Report on Development Process

Development Process

Low-fidelity Prototype Screens:







Process at Arriving at High Fidelity Prototype

One change that was implemented in the high fidelity prototype is the removal of the documentation of medications taken by the patient. It was originally thought that it would be beneficial to keep track of which medications the patient is prescribed, and whether or not the patient is actually taking them as advised. However, the CapMed PHR software already includes the functionality of keeping track of medications.
Another design change that was implemented was the simplification of the interface. In general, the look and feel of the low fidelity prototype is much more cluttered than the high fidelity prototype. An example of this can be seen in the removal of very long lists of choices such as the lists of choices for the question "What food/drink did you consume today?" While it is not bad to have lists, having lists that are extremely long can overwhelm the patient, and therefore make the journal less effective because the patient then might not enjoy using it as much. Having a very busy interface can also make the patient feel like they are in less control over the journal, which does not follow the guideline of supporting internal locus of control. Patients should feel like DailyLog is a tool that is aiding them in recovery, and not a burdensome program that they must answer to daily.
Further more, having a more dynamic format that allows the physician to specify what questions and which response style customizes the journal to fit the needs of each individual patient. When creating the low fidelity prototype, the feature of giving the physician the ability to add his own questions was realized, but the high fidelity prototype just seems less restrictive and confining.
The layout of the high fidelity prototype is also more contusive to flow. The low fidelity prototype had a quadrant-like layout, creating a circular flow. However, the high fidelity prototype creates a vertical flow that facilitates progressing through the journal.
There is a progress bar on the low-fidelity prototype indicating to patients how much of the journal they have completed. While having a progress bar might be beneficial for an application like an installation wizard, it was decided that a progress bar was not as applicable for a journal.

Web Accessibility