Chapter 9 focuses around the process of interaction design. The book introduces interactive design as the idea of creatively and practically making products to support the way people communicate and interact in their everyday and working lives. What we talked about in class and also what is stressed in the book is that when starting a design process it is important to get a list of requirements about who your user is so that you can better understand who your user is so that the needs and desires of your target audience are met, this topic is talked more about in chapter 10 but it is also important to understand when reading chapter 9. Chapter 9 also points out the importance of planning your project as clearly as possible so that you have a clear understanding of your resources(time, money, human resources, etc). The book does a good job of pointing out the importance of incorporating the user into the design process which is important to the design team when trying to figure out whether or not they are on the right path to creating a truly user centered design. The book gives a some design process models that have been used over the years for teams that are trying to figure out a god approach to creating a user centered design. We talked in depth about a few of the models in class but I just wanted to point out that my favorite model was the “usability engineering lifecycle” model because from a usability standpoint this is a really great model. Each step of the design process is really well thought out and I like it a lot, however, the learnability for this model is tough because it’s a tough model to understand, there is a lot going on and it would take a little bit of time to really understand the model and its true advantages and disadvantages.
Chapter 10 looks at the importance of identifying need and establishing requirements about your design project and your user. Who is your user, what are their attributes, why do they need this new technology, how does it help them, what are some constraints to consider when designing a prototype, besically you want to list out all of your what’s, why’s, when’s, where’s, and how’s for your project, doing this will better help you understand your user and ultimately will make your user-centered design a kick ass design that people will really like and hopefully will make you rich as a result of people liking it. The book talks about the different kinds of ways that you can gather data about your user, it’s important to keep in mind the cost and the time that it will take to get this information and analyze it, basically so that you don’t go over your budget and ruin your whole project. We talked about stakeholders and why they are important to keep in mind when creating a user centered design. Basically everyone who will be affected by the design project should be kept in mind when planning and creating the project. The book talks about getting information about primary, secondary, and tertiary parties involved in the after market purchase of the design. It’s a good idea to keep in mind the people who will be using the design, or who are either directly indirectly affected by the use of the design. This is an important concept in the book and we talked about it a little bit in class on Wednesday and I think that it’s valid and should be taken seriously. That’s basically what I got out of the two chapters, there is a little bit more but I gotta leave my house to go to class. Thanks for reading. Peace.