Assignment Approach
From our User Needs & Task Analysis we found that the needs of our two representative users, students and workers, were very similar. Workers may have slightly less use for some of the features, but their needs were similar. With this in mind, we decided to make prototypes that would meet both users' needs while at the same time make it easy for workers to skip the extra features they would not use. We would not eliminate these features altogether because we believe students would value them.
Our group decided to make two different prototypes in Microsoft Power point in order to discover how best to meet this goal. Part of the team worked on one and the other part of the team worked on the other. Each prototype was to emphasize different navigation and options. Upon their completion, the group would conduct cognitive walkthroughs of each prototype and discuss which aspects of each prototype to use, eliminate, or revise.
The first prototype's goal was to make many options available at once. This prototype was designed for "power users" who would want to make use of most, if not all, of the features of our system. We felt this design best reflected the needs of students. The second prototype was made for "minimalist users". These users would find a system with less options visible at one time, with the most needed ones prioritized, more akin to their needs. The other options would be available, but would be "tucked away" on other screens. This prototype was believed to best reflect the needs of our worker users.
Prototypes
Below are the Prototype files. Both prototypes were created in Power point Power point 2002 or higher is recommended but it may work correctly in other versions.
Prototype #1 |
Prototype # 2 |
||
|---|---|---|---|
The annotations are attached to each slide in the Power point presentations and can be viewed by using the "Notes" view option in Power point The separate notes files are included so that they can be viewed separate (or during) each presentation.
Cognitive Walkthroughs
Below is each prototype's respective cognitive walkthrough.
Prototype #1 Cognitive Walkthrough
Overall
When you enter the prototype, there are directions that tell the reader to click on the screen to enter the work area. From this point, it is assumed that the user may be able to click on anything he/she desires (which does happen!). Also, there is gestalt at play ? the clock remains a constant feature (otherwise it would not be considered to be an alarm clock), there is an option that allows the user to go to the previous page whenever they need to, the arrows all have the same design, and items that require a user to transfer files are layed-out in column formation. A menu appears on the screen with six categories: Alarms, Calendar, To Do List, Music, Photos, and Customize. The user has the ability to click on either the icon or the word to enter each domain. Also, the device highlights the current component that the user is working on, letting him/her know what is happening as it happens. It is hard to do something wrong and completely mess up the system. Even at a low-fidelity prototype, the system is very forgiving and may allow the user to go back a step or reset all work to null altogether.
Alarm
A user can either set up a new alarm or view/modify current alarms on this mechanism. When a user selecs New Alarm, he/she is prompted to enter the time to have the alarm go off. The next screen offers several options. Headers display the order to do the step, which should be apparent to the user, since everything is numbered (first, select the day, then select how often the alarm should sound for the event). The user sees the After this is complete, the user comes face-to-face with the last step ? choosing the sound for the alarm. Also, the user is able to review all aspects of the event before confirming. Since everything is touch screen and has labels of what to enter, the user should have minimal trouble figuring out what tasks to perform.
When a user needs to edit an event, he/she can see all events on the screen. There are two buttons that allow the viewer to change or delete. If the event gets changed, the specifications of the summary appear. In a future version, this feature could ask the user if he/she wants to change the context of the message, rather than just the date, time, and song. When you delete, a calendar with dates bolded displays, to show what could be deleted. The user can click the bolded date and specifications of that event appear. The user cannot delete anything, but rather change the description and other information. The user can tell what to do easily, but it may or may not happen.
Calendar
Very straight forward. A typical monthly calendar with arrows (to advance the month) is presented to the user, just as anyone would expect. It is placed on the left side. Here, dates with current activities are bolded. The user has the ability to add/edit events from here. If the user is inclinded to click on a bolded date, the specifications of an event/multiple events will appear to the right of the calendar, close enough for those to see the relationship, but far enough to prevent the screen from being cluttered. However, when a person selects Add Alarm, he/she is sent to the To Do List. This may confuse the user, but may be worked out in a future version.
To Do List
Simple layout that shows items in a list that the user enters, plus an option to add or delete more entries. If a user wants to Add an new event, a blank box will appear on the left with several options. This box is for the user to enter information using the stylus. It is not apparent to a very novice user to do this. He/she may think something has gone horribly wrong with the screen. Perhaps a header above this writing area may prevent any confusion. Other than that, there are clearly labeled boxes underneath, asking the user what action to take with the user data newly inputted.
Music
The user is presented with two options: Play Music, or Upload Music. When the user selects the Play Music option, he/she is faced with four options: radio, CD, MP3, Playlist. Since these options are in columns without boundaries, it may be confusing to the viewer at first; the eyes are accustomed to look left-to-right throughout the entire length of the interface and now it is suddenly switched to looking up-and-down, while reading left-to-right. Other than that, the system clearly lists general functions, such as Browse, and Play. If the user gets past the sudden structure shock, he/she may find this part rather enjoyable because each part mimics components typically found on a radio, or a cd player. Therefore, he/she can recognize this easily and perform the tasks quickly. Once a song is selected, the system displays the title, artist, track number in the playlist, and a row of typical playing/stop keys.
Uploading music looks very similar to Play Music, to keep with gestalt of the Music category. The user can create a playlist with MP3s already in the system; the arrow in the middle of Upload MP3 and Make Playlist denotes that a file transfer process may happen. The user has the same choices as in the previous option for Music. The user, hopefully would not get lost and/or confused by this portion.
Photos
Photos has the typical two-category front page. The user may View Photos or Upload Photos. Under View Photos, the user can look at all the photos that are currently in the system. There is even an option to perform a slideshow event. This feature, however, works with only one photo. Also, when the user clicks on another photo, the device automatically goes to Upload Photos. If the user wants to upload photos, he/she are taken to a screen where they can browse their system and look for more photos. This feature mimics the Upload MP3 feature and Playlist feature shown in other areas of the systemfs software. This portion, following the left-to-right column construct, seems very clear. It could possibly be the pyscholoy of universal transfer button at play.
Customize Features
The user will be able to perform the correct tasks. The current settings are all underlined, much like the customizable feature menu found in most video games. This format makes it easy for the user to figure out what available actions are there and what they need. As with any lo-fi prototype, however, there are bugs that need to be worked out.
Prototype #2 Cognitive Walkthrough
Common Tasks
1. Set up an alarm
2. Set up an event in the calendar
Infrequent but Important Tasks
3. Customize Gui interface with photo.
Questions for Steps of Task
1. Will the correct action be sufficiently evident to the users?
2. Will the user notice that the correct action is available?
3. Will the user interpret the response from the action correctly?
Task 1: Set up an alarm
Step 1: Select the correct sub-section in order to set an alarm.
Will the correct action be sufficiently evident to the users?
Answer: Yes, the "Alarms" subsection is visible to the user.
Will the user notice that the correct action is available?
Answer: Yes, the buttons seem press-able and are familiar to the user.
Will the user interpret the response from the action correctly?
Answer: The change of page and new title "Alarms" gives the user feedback.
Step 2: Choose to set up a new alarm.
Will the correct action be sufficiently evident to the users?
Answer: Yes, the option to add/change alarms is visible.
Will the user notice that the correct action is available?
Answer: Yes, the option is in the middle of the page. It could be more visible or more apparent. The option is definitely visible.
Will the user interpret the response from the action correctly?
Answer: The new "Add New" title informs the user that they have reached the correct destination.
Step 3: Set the alarm
Will the correct action be sufficiently evident to the users?
Answer: Yes, the visible options are familiar to the user. One can set the time as it has a likeness to setting other time devices.
Will the user notice that the correct action is available?
Answer: Yes, the accept button is familiar. If there is a mistake they can clear the selected options
Will the user interpret the response from the action correctly?
Answer: There is not feedback presented after setting the alarm.
Task 2: Set up an event in the calendar
Step 1: Choose to edit the calendar.
Will the correct action be sufficiently evident to the users?
Answer: Not evident that setting a new event requires the user to enter the calendar page.
Will the user notice that the correct action is available?
Answer: Perhaps not, unless they are can intuitively figure out that they are required to enter the calendar sub-section.
Will the user interpret the response from the action correctly?
Answer: Yes, once they enter the calendar section it is evident that they made the right choice.
Step 2: Choose to add a new event.
Will the correct action be sufficiently evident to the users?
Answer: Yes, the button is familiar to the user and easily identifiable.
Will the user notice that the correct action is available?
Answer: Yes, the use of labels allows the user to know that the action they want to make is available.
Will the user interpret the response from the action correctly?
Answer: No, given that the feedback for selecting to add a new event is missing.
Task 3: Customize Gui interface with photo.
Step 1: Choose the options menu.
Will the correct action be sufficiently evident to the users?
Answer: Yes, the options button is easily found through navigating the bar. The left and right hand navigational bars are familiar and their feedback is apparent. Therefore choosing the options menu is evident.
Will the user notice that the correct action is available?
Answer: If the user wants to edit their options, they know where to go.
Will the user interpret the response from the action correctly?
Answer: Yes, many options pop up giving the user a good experience with the interface. It is familiar looking, giving the user control over the device.
Step 2: Choose to make the background a photo.
Will the correct action be sufficiently evident to the users?
Answer: Yes, the option to make the background a photo is in the background area.
Will the user notice that the correct action is available?
Answer: Yes, the background section houses the button to make a photo the background.
Will the user interpret the response from the action correctly?
Answer: No feedback is presented at this time.
Presentation
The group's midterm powerpoint presentation is here.
Navigation
Information
Chronos Alarm Clock Project was created by Group 6 in Professor Jacek Gwizdka's Fall 2006 HCI Class.
Group 6 Members:
Peter Holt
Maria Musillo
Jeremy Pharo
Anisah Syed
This page was last updated on Wednesday, November 1, 2006