HCI

 

eVents

Project Assignment 1: Task Analysis
Project Assignment 2: Prototype Version 1
Project Assignment 3: Analytical evaluation
Project Assignment 4: Prototype Version 2
Contact us
 
1.-Metaphore Discussion 2. PICTIVE Report
3. Prototype Report 4. Prototype User's Manual

1.Metaphor Discussion

 

  • Invitations

o   Metaphor Description:

§  An individual will plan out a party or event and mail out invitations to other people for a party or event.

o   Matches:

§  Both the project design and the metaphor involve creating an event and sharing it with guests.

§  They usually involve an RSVP system for determining the number of guests attending the event.

o   Mismatches:

§  The metaphor does not necessarily keep a history of past events.

§  The metaphor is usually done using “snail mail,” whereas our project design uses cell phone communication.

 

  • Agenda on the go

o   Metaphor Description:

§  Using the concept of a pocket paper agenda, an individual would record their daily/monthly events to keep track of their schedule.  In addition, some agenda possess a contacts list so that the user has quick access to the phone numbers of their friends/colleagues.

o   Matches:

§  Both the project design and the metaphor have an “event-storing” feature that enables the user to view a history of these events.

§  Phones and agendas have space to store contact information.

o   Mismatches:

§  Our project design will have the capability to share an event with other individuals; while the events on the agenda have to be copied into another person's agenda to share it.

§  The agenda is physical and on paper, as opposed to the electronic project design.

 

  • Whiteboard calendar

o   Metaphor Description:

§  A whiteboard calendar allows multiple users to view an event/data that a user has written on a specific date of a calendar, allowing other users to add/modify information for the event, or to potentially delete the event.  The changes are propagated to all users.

o   Matches:

§  Both the project design and the metaphor have a primary goal of storing events and represent them in a way that is intuitive to users, in a calendar view.

§  The whiteboard calendar implies that the information in this calendar is sharable with other individuals, which is coincident with the project design.

o   Mismatches:

§  The whiteboard calendar idea implies that other individuals, that are not the event creator, can edit/delete details from the event and expect the changes to be propagated to the other event participants.

 

                We felt that these metaphors possessed the most critical matches to our project design while possessing mismatches that helped to differentiate the project design from the actual metaphor, since the metaphors must have imperfect mappings to the project design (Carroll, Mack, & Kellogg, p 69).  The combination of the metaphors we chose at this stage covered all of the primary goals of our project, which are: storing events on some device, sharing with other users, and the creator has some notion of how many people are attending the event.

                From these metaphors, we decided to choose a composite metaphor of the Invitations and the Agenda on the go, since the combination covers the aforementioned primary goals, also not allowing the users to modify the event, like the whiteboard calendar does.  Since our primary goals are storing the event on some device and sharing it, we felt that the composite metaphor was necessary, because the Invitations do not store the event and the Agenda on the go cannot share the event directly.  Finally, we felt that the composite metaphor was necessary since the composite covers the domain more completely by utilizing complementary metaphors (Carroll, Mack, & Kellogg, p 75).



2.PICTIVE Report

We selected four different potential users that were not related with our project and are not CS majors; they helped us to develop an interface design for the e-vents application with the PICTIVE method.  We explained them the intended task of the application, which it consists in sharing individual events with one or more contacts at the same time through a smart-phone application. We selected these four potential users because all of them have experience with the use of smart-phones, and they face some difficulties in trying to organizing people for an event.

Participant #1:  She is a sophomore college student with a part-time job.  She acknowledges her needs to organize get-togethers with friends, study groups and relatives.  Also, she currently shares her work and school schedules via a real bulletin board at home.


Participant #2:  He is a senior college student with a part-time job.  His needs are very similar to those of participant #1. 


Participant #3:  She is an accountant on her 30’s, mother of three young kids.  She expressed her frustration for organizing the birthday parties for their kids and trying to find a date where all her family has a free schedule.


Participant #4:  He is an engineer on his 50’s, Father of two college graduates.  He explained the difficulty that he faces when trying to organize a family trip or a family reunion, since both of his children work full-time and attend graduate-school.


These four users represented and created a visual layout of how they imagined the interface of the different screens of our application.  Two users agree that all they needed was to enhance the calendar on the smart-phone with a “share” option.  Using the current calendar on the phone, they will go to a selected event then press “options” and from this option select “share” which should take them to a screen of contacts with check boxes to be able to select recipients and after this press “send” to complete process.  Also they stated that if they were to buy a new application with a “sharing” capability built-in that will force them to re-enter every single event carried on their current phone-calendars they most likely will not buy it.


The PICTIVE results showed that the other two users preferred to have a calendar as a way to orient themselves with future dates and days. Also that they liked to have a screen where the entire event’s information can be filled; this screen includes:  title, location, starting and ending time and notes; just like they usually enter a new event on their phone’s calendar.  As an additional feature to facilitate a better selection for the sharing process, the users preferred to have a button for sharing that particular event, which it would take to a list with their contacts’ information for a better and easy selection.  A third screen was intended for a view of all the pending invitations where they could decide either to accept the event or reject it.


One feature of our application that attracted them is the convenience in being able to share single events instead of having to share their entire calendar, giving them a sense of privacy. As a conclusion of these PICTIVE sessions, we have two choices: one was to follow one of our user’s recommendations to the letter and only augment the existing iPhone calendar; or two, which is what we decided to do, make an application that imports and exports an event from/to current calendar.  Making a stand-alone application that may or may not require its own calendar for displaying events.

These PICTIVE sessions give us a few other ideas that have already appeared during the Contextual Interview.  Users requested to have an RSVP with a comment field, and also to include a notification indicator for the user to identify pending events on queue.



IF Unable to see YouTube video, click HERE
SEE ANOTHER PICTIVE VIDEO "HERE"
 

3.Prototype Report

Our prototype is a windows form executable file.  It has interactive features like buttons, check boxes, dialogues, calendar; the prototype has been sized similar to the iPhones screen resolution. 

                The first screen is the “Today's events” that follows closely with one of the designs that came out of our PICTIVEs.  This seemed a reasonable and logical first screen for our app as it displays the current day's events and allows the viewing of pending event notifications and adding of new events.  The choice of a flag to indicate pending events and a plus symbol to indicate to add an event were chosen based on user input and the PICTIVE results.

                 The Flag of our prototype takes the user to the pending events screen, showing the invitation events pending to be accept/reject.  Buttons on the screen allow a user to add the event to calendar, delete the notice, and RSVP.  This screen deviates most from the PICTIVE.  Most of the deviations are for clarity purposes and layout of the text items on the page due to the uncertainty of how it will fit with longer titles, and to add the additional functionality of the RSVP system.

                The plus symbol on the front page accesses the add event page.  This follows closely most of our PICTIVEs for the “add event” screen.  We felt that it was a fairly straightforward design for an input form.  The “Share” button  takes you to the contacts screen to select the contacts you wish  to send the event to.  The choice of scrolling through and using check boxes were suggestions brought up by users in the PICTIVE and in our Contextual interview as being a “familiar” means of selecting who to send to.  The cancel button on both of these screens takes the user back to the front page.

Download our prototype: OpenOffice version | Power-Point version

4.Prototype User's Manual

Getting started

1.      Open the application and the first screen you will see is your eVents for today.

2. In the same screen at the top sides, you can find the option to add a new event (+ symbol), or the option to look in your Pending Notices (flag symbol).

 




Pending Notices

1.  At this screen you can see the first pending event. You have the option to Add to Calendar in case you want accept this request.




2. After you choose the option Add to calendar, a pop up window will appear, with the confirmation of this action. After accepting you will see a message notifying this.




3.  If you don’t want to accept the invitation, then you have the option  Delete Notice. A confirmation pop up will appear, if deleted a message notifying this will appear.




4.  On the bottom part of the Pending Notices screen, we can find the RSVP option (if is requested by the creator). You have the question Will you attend? And then you choose one of four options:  Yes, Yes with friends, maybe, or No.

5.  Just select what is better for you, and then click the option Add to calendar.

If you don’t want to add events or delete notices at this moment from your pending list window, then you have the option to go back to main/home screen, just select the Home button.


Create a new event

If you choose to create and share your eVent with others, here's how:

1.      When you select/press the Add eVent option at the main screen (+ symbol), the following screen will appear:




2.      Type the Title of your eVent, Location, Date, Start time and End time and a brief Comments of the event.

3.      Click on Share event, to display your contacts list.

4.      The contacts list will appear; check the box of the contacts you want to invite tho the event.





5.      Click the Share icon and the invitation will be send.

6.      Now your event is saved in your calendar, and you will receive a pop up window with the confirmation that this event has been sent.





Add events from others

If you receive an event request, here are your options:

  1. A pop up window with the event invitation will be stored at your Pending Events screen.

2.      At this moment you just have to apply the steps for the Pending Events screen.