The Process of interaction design <Chapter 9>
There are many different fields of design, There are many things to consider about who is involved. Chapter 9 is talking about big four different subjects who is involved, practical issue, lifecycle model, and who is user. There are many different of design field, to be process their design to be a product. There are few steps like discuss other people beside designer and ask them about how it thinks, find revision of design, and improvement. If user think there are too much waste of time in store, user might find store that not complicate. Goal of user-centered means not technology, the meaning is should develop a product for user. Who are the users? Before we learn interaction design pulled together into a process, it is important to know who the users are. Users is buying product from system, test system, and choose better product between many companies. The meaning of ‘needs’ is very complicate question these days, people can’t imagine how much technology can developed.
I think interaction design is involved in everyone these days. Customer compete many different companies to buy a product. Standard design is not for best seller these days. When I go shopping, there are cheap and simple design, and expensive and fancy design items. Many people brought clothes or any other products depend on design. I read a PC magazine about Sony computer design. Sony computer processor is not higher than other companies, too much over priced. However, customer think design is better than others, so Sony computer became to best seller. I think design require to consider about who is user and what user ‘needs’. When standard of product is developed, design can not be same all the time. Deeper, there are a lot of ideas of design but after pre-test, there will be only few design can survive that competition.
Identifying needs and establishing requirements <Chapter 10>
In chapter 10, what, how and why achieve activities, requirements, data gathering, data analysis, interpretation, and presentation, task description, task analysis. What designer trying to achieve in the requirement is understand user and produce a set of stable requirement. Gathering data, then analyze and interpret, then extract requirements. A requirement is what it should do or how it should perform. There are two different requirements, functional and non-functional. Functional requirement is what system should do it, and non-functional requirement is what restriction on the system, and its development. Data gathering in the requirements is to collect sufficient, relevant, and appropriate data so stable these data can be produced. Gathering data from interview and focus groups, interview is good to gathering data like issues. It is important to developer meet user and listen their feeling involved. Focus groups are good to gathering data too, gaining a consensus view and highlighting areas and disagreement can easily talk in focus group. There are few more examples of data gathering, questionnaires, direct observation, indirect observation, studying documentation, and researching similar product. Data gathering is essential special to designer for making better product they produce. After gathering data, they have to analysis, interpretation, and presentation about data. Task description and task analysis are to present user and pre-test before make product.
Requirement is what system has to be. User wants to have better systems to require. Times goes by, user want to more requirement programs in computer and other product. Like 10 years ago, when I wanted to buy computer and digital camera. I only use computer for typing and not much playing others and digital camera for take a picture. However, these days, options of digital camera is totally different like take a picture, record voice, make a movie, watch, and upload pictures in web-site. Computer is faster and faster and does on-line games, watch movie, TV, word process, and etc. So requirement of system is developed a lot. There are is underwater PCs example in 10.1. This example is interesting to know because there was a different prototype computer used voice recognition, but bubble sound is too loud. It couldn’t quiet work. When we go to undersea, we only have one hand to use so they make smaller and all the buttons are easy to click in one hand. Also, camera to sending message and GPS system tells where diver at. The surface of computer is kind of interesting and looks good this computer. Surface is big difference between traditional computer and wet PC. I have few questions about wet PC, when I see the picture of wet PC there is no monitor, then how can we see like computer? And In text, there is GPS system in wet PC but how can we find in undersea?
May 20, 2008 at 9:59 am
Great example with Sony product perception vs. function. That would be a good place to provide a link to the article you read or similar resources supporting your statement. Don’t be shy about adding relevant links. The other example pulled from your own life was also helpful and interesting.
The writing is a bit difficult to read.