Catch up and being brave enough to publish things once again! Again, we went through this chapter back in October, so I'll recap what I've noted:
First, the chapter went into great detail about Assumptions and Claims made in a design process. The meanings in this context are as follows:
Assumption: taking something for granted.
Claim: Stating a truth that is still open to question.
I also noted that the importance emphasised in this chapter revolved around each perspective in the design process e.g. a software engineer being concerned with the coding and breakdown of a system and a project manager being concerned with budget, team workers and time restraints. They are considered in their implications in relation to one another. The likely disagreements and time consumption from these team meetings and consultations are better addressed earlier rather than later, in order to avoid the flaws and extra costs of the final product occurring.
The chapter also described the smartphone, which came into being in 2002 with Orange's SPV (Sounds Pictures Video) being the first on the market.
Assumptions: phone companies assumed that many customers wanted to make video calls, download songs and movies while on the move. This may have been correct in some ways and incorrect in others, as for a start video calls are common, but more so on a laptop and webcam interface; not on a handheld device. I personally wouldn't want to do all of these things on a mobile whilst on the move.
The chapter also highlighted the framework of core questions often used to aid design teams in the process of explicating an idea, there were:
1. Are there problems with an existing product? If so, why?
2. Why do you think there are problems?
3. How do you think design ideas might overcome this?
4. How do you think your proposed design ideas support, change or correct ways of doing things?
Flickr was drawn on for being the first blog-based photo sharing site.
Assumption: just as people like to blog, so too would people want to share photos with the rest of the world and get comments for them.
Claim: Almost certainly the best online photo management and sharing application in the world.
It also talked about conceptualizing the design space by a good understanding of the problem space and understanding the system through developing a conceptual model (defined as a high-level description of how a system is organised), ranging with classic examples such as the Spreadsheet by VisiCalc and 8010 Star system by Xerox.
8010 Star System (Xerox, 1981)
It was also highlighted that the Interface Metaphor was an essential component of the conceptual model. An Interface Metaphor is a way to map out familiar and unfamiliar knowledge, enabling users to understand and learn about the new domain. However, there is opposition to this method which uses the Trash Can icon a prime example of its arguments.
To summarise, this chapter explains in detail the importance of understanding and conceptualising a design space before attempting to build something.
Chapter 2 Assignments:
a.) Compare the organisation of each in the following:
- A personal pocket-sized calendar diary (one week to a page)
- A wall calendar (one month to a page, usually with pictures)
- A wall planner (displaying a whole year)
- The central organisational structure for all of them entails days, months and years; the consistency that relates all three types. Their differences are in their highlighting of different elements based on their own individual purpose.
- Wall calendars and planners are mutually designed as posters and intended to be used in a place of its own, contrasting with dairies that are shaped as portable books. Wall calendars and planners are designed to be hung up for reference as well as for pinpointing key events at a glance (usually in an office environment or home study, but probably extended to kitchens and such). Diaries, however, are designed to help you with constant organisation, especially when on foot (this is pretty much a way of life for me, which has helped greatly).
- Diaries normally include additional images such as world/country maps, address books, note pads, information on international holidays and sometimes smaller yearly planners resembling those hung on a wall. These tend to reflect the diary as the portable life-organiser.
- Wall calendars and diaries allow for more annotation to dates, unlike the yearly planner. But even wall calendars tend to be limited in space as well. Diaries are ideal for devoting a full day of planning such as appointments, activities, travel plans etc.
- Diaries and wall calendars tend to have many themes, quotes and aesthetic designs, thus adding to the variety of experience and perhaps serving as a reflection to the owner's personality. I remember getting my mother a themed calendar about pigeons one Christmas (she hates pigeons).
- An electronic personal calendar
- A shared calendar
Looking at my own computer and referring back to my working time in the NHS (where I shared and managed multiple diaries on Outlook) the descriptions I give according to this framework are as follows:
An electronic personal calendar
The major metaphor and analogy of an electronic calendar and shared one is that of managing a diary; such is the the typical admin setting. Other analogies I believe include the use of yearly planners and notifications/alerts. Events strike me as a metaphor in this case, and so do invitations.
Concepts behind this include that of the calendar and what you can do with it; such as creating, deleting and modifying. Events, being the metaphorical social elements of this conceptual model entail the creation, deletion of them, inviting and being invited, corresponding with updates and announcements, attaching documents, etc.
Relationship between concepts clearly has to do with calendars containing a group of events to be referred to. Events can lead onto other events either by links or later events in the calendar. All that said, these things will be weighed up against each other in numerous ways depending on the organisation and preference of the user.
Mappings in the calendar's sense entail the organised chronological structure of the interface, consisting 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.
A shared calendar
The major metaphor and analogy is that of managing a planner. Another important one where sharing is involved includes invitations.
Concepts in a shared calendar would involve owners and participants; such as adding participants, blocking them; deleting them; setting various permissions for them as well as taking permissions away; changing owners and participants etc.
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.
Mappings, again, this largely has to do with events. The priority of such an element can also be applied with "low-importance" or indeed "high importance." These events will automatically add to another person's calendar should they accept an invitation from a created event, which can specify time, location and further details.
That's it for Chapter 2.
No comments:
Post a Comment