MIS 441Scheduling System Interface DesignTucson Medical CenterMilestone 4: Low-Fidelity Chauffeured TestingCreative Design ParadigmsPriscilla AguileraDavid Jen-Ping HsuLynn NguyenMonna SebringGui SilvaChris StaleyScheduling System Interface DesignTucson Medical CenterMilestone 4: Low-Fidelity Chauffeured TestingMilestone4:Low-Fidelity Chauffeured Testing ......................................................................................................2Introduction................................................................................................................................................................3PartZipants.............................................................................................................................................................10Apparatus...............................................................................................................................................................10Scenarios................................................................................................................................................................11Procedure...............................................................................................................................................................13Test Measures........................................................................................................................................................14Discussion..................................................................................................................................................................20Appendices ................................................................................................................................................................22A: Peer Evaluations................................................................................................................................................23B: Greeter ScriptC: Facilitator Script.....................................................................................................................24C: Facilitator Script.. ..............................................................................................................................................25D: Signed Consent Foms......................................................................................................................................26E: Pre-Test Questionnaire.. ................................................................................................................................... 27F: Post-Test Questionnaire .....................................................................................................................................28G: Chauffeured Prototype..................................................................................................................................... 29H: Raw Data Observer Notes ...............................................................................................................................30I: Video Taper of Chauffeured Testing Sessions...................................................................................................3 12introductionTucson Medical Center Emergency Services currently uses a pencil and paper schedulingsystem. Creative Design Paradigms is developing a user interface for a computerized schedulingsystem for the department. The purpose of this document is to describe the chauffeured low-fidelity prototype testing of the system that was conducted with three employees who would usesuch a system. The goal of this testing is to discover design problems and overlooked user needsand desires. The use of a low-fidelity prototype is intended to encourage test participants to offerhonest feedback. The paper “computer” lets the users know that the system is still malleable.They can see that their suggestions are taken seriously when they see you make an on-the-flychange to the system./JPrototypeWe decided that our prototype should be constructed with the familiar format of a webbrowser. For our first scenario, entering a schedule, the user is greeted by a log-in screen thathas the TMC logo across the top, along with a heading identifying it as the login to thescheduling system. A message greets the user, asking them to enter their username andpassword. The username and password are the identical to those used to log onto the otherhospital systems. For our prototype, we had a generic username and password. After enteringthis data, users click the “Login” button, and are taken to the second screen which displays agreeting and their personal information: name, job title, primary working shift, and primaryworking area. A message informs the user that if any of their information is incorrect they canchange it by clicking on a button that will take them to a change profile screen. This feature isdisabled in our prototype, as it is outside the scope of our scenario.After viewing this message, the user should click on the “Record Schedule” button on themenu bar. This action takes them to a screen, which looks like a calendar with the title“Schedule Request form for period beginning on February 24th, 2002.” Schedules are posted ona four-week, rather than monthly, basis. The calendar metaphor is appropriate for a schedulingsystem. At this point, a dialog box pops up with basic instructions on how to enter an employeeschedule (Appendix G, Instructions). Users are instructed to click on a day to start the process offilling in their schedule. The instructions include a picture of what will appear in the calendar asthey enter their schedule preferences. WVFPAR” box because of its fivebuttons. The user is referred to a legend at the bottom of the screen that corresponds to the fivey-3buttons: W (work), E (hospital education), A (available), P (Paid Time Off or PTO), & RA(requested day off). There are also two drop-down menus, one containing shift times, and theother work areas.d’ b’The user can choose to click an “OK” box, so that the instructions don’t appear again, orthey can simply click the close button. If they do not click the “OK” box, the instructions dialogbox will appear on their next login to the scheduler. This instructional menu was added after ourfirst chauffeured test when it became evident that some simple instructions were needed.The user should now click on