Question

URGENT..

Using Johnson and Henderson’s (2002) framework, describe the conceptual models that underlie the design of:

Metaphors and analogies:

Concepts:

Relationships:

Mappings:

• An electronic personal calendar found on a personal computer.

• A shared calendar found on the web.

Answer 1

1.Metaphors and analogies:

It is used to enable the user to understand how the product performs and how to use it.

2.Concepts:

Concepts provide the detail overview of topics to the user that they need to understand.Concepts can perform many operations on relative attributes like create and manipulate .

3.Relationship:

The relationship between concepts is the important thing to define the relative importance of the objects and actions, and to determine whether an object contains another object, or it is part of it.

4.Mappings:

The mapping between the metaphors, concepts and the user experience helps to design and invoke the product.

An electronic personal calendar found on a personal computer

1.Major metaphors and analogies:

From the metaphore perspective the most prominent one found on a personal calendar on a personal computer  is "events", and the major metaphor and analogy includes managing a diary. Other important analogies include a using yearly planner, monthly calendars, daily planner, notifications, invitations,text-editing applications, which feature file save, delete and create functions, etc..

2.Concept:

  Concept includes the performance of the calendar and what you can do with it; i.e..you can perform many operations on calendar such as creating, deleting and modifying,rejecting events, linking events to calendars,deletion of them, inviting and being invited, corresponding with updates and announcements, attaching documents, etc..

3.Relationship:

The calendar contains calendars i.e a year calendar contains different months calendars,which is referred to the group of events, Events can be turned to other events either by links or later events in the calendar. Events contain start and end, dates and times, locations, personal status, meeting name, etc.. and these events have priority preferences for example, sending an event invitation is more important than being able to respond or receive response to an invitation,and also rather than  adding an attachment or linking the event to a calendar or inviting paricipants to the event the most important thing is to schedule and save an event.

4.Mapping:

The organised chronological structure of the calendar interface, consists of years, weeks and days. Events are created and added to this structure, which can either correspond to being personal, work/business-related, holiday and more.When a user creates an event the system requires that they create a name, and define start and end dates/time. When a user creates a calendar the system requires that they create a name only. User can add existing events or create new ones. To invite individuals to an event an “invitation” corresponds to an email message can be used . These Invitations contain the information regarding the meeting and links that enable recipients and the recipient can accept or reject the meeting request.

A shared calendar found on the web:

1.Major metaphors and analogies:

From the metaphore perspective the most prominent one found on a shared calendar is "events", and the major metaphor and analogy includes managing a diary. Other important analogies include a using yearly planner, monthly calendars, daily planner, notifications ,text-editing applications, which feature file save, delete and create functions, etc..Another important one where sharing is involved includes invitations.

2.Concept:

Concepts in a shared calendar would involve owners and participants, which includes setting owners and participants, changing owners and participants, deleting participants, blocking participants, adding participants, events, single instance and recurring events, private and shared events, mine others’ events, creating events, sharing events, saving events, modifying events, deleting events, receiving events, sending events, accepting events, rejecting events, linking events to calendars, attaching documents to events, adding alerts to events, etc..

3.Relationship:

Relationship between concepts place a greater importance to saving events than inviting attendees, and sending an event invitation would be more important than the attendance of those invited.The calendar contains a group of events,as calendar contains calendars,these events are directly linked to the calendar as well as calendars.Events can be linked to the other events via the calendars and these events can be private or it can be shared and each event has owner who has to allow the permissions to perform modifications on shared events.

4.Mapping:

   The organised chronological structure of the calendar interface, consists of years, weeks and days. Events are created and added to this structure, which can either correspond to being personal, work/business-related, holiday and more.When a user creates an event the system requires that they create a name, and define start and end dates/time. When a user creates a calendar the system requires that they create a name only. User can add existing events or create new ones. To invite individuals to an event an “invitation” corresponds to an email message can be used , and to modify that event or calendar an “owner” corresponds to the person has right privileges. “Participants” correspond to owners are related to an event or calendar but are not able to make modifications to that entity. When a user creates a calendar or event s/he is automatically assigned as the owner. Owners can modify ownership status and rights privileges assigned to participants of an event or group. These Invitations contain the information regarding the meeting and links that enable recipients and the recipient can accept or reject the meeting request.