IFD:Course Interaction Design: Difference between revisions

IFD:Course Interaction Design (view source)

Revision as of 16:53, 16 January 2011

244 bytes removed , 16 January 2011

no edit summary

JanD

Bureaucrats, emailconfirmed

1,221

edits

@@ Line 28: / Line 28: @@
 ===how to use this course and how it is structured===
 This course aims for covering the whole design process. This means you will learn
-* To find out what you need to consider in your design in the section "Explore your idea"
+* To find out what you need to consider in your design. This is done by gathering informations about user goals, existing problems and already existing solutions - all covered in "Explore your idea"
-* To realize your (preliminary) designs. Techniques for doing this without coding is covered in the  secction "techniques for designing". The Sections "Basics of Psychology" and "Principles and best Practices" will provide you the informations to make your applications easy to use.
+* To realize your (preliminary) designs. Techniques for doing this without coding is covered in the  section "techniques for designing". The Sections "Basics of Psychology" and "Principles and best Practices" will provide you the informations to make your applications easy to use.
-* To test your design and to realize interactive prototypes of it. this is covered in "Get to know if your ideas work!"
+* To test your design and to realize interactive prototypes of it. Some things that seem to be great turn out to be unsuitable for your users. You will get all sorts of interesting insights that will help you in improving your ideas. This is covered in "Get to know if your ideas work!"
+[[File:IterativeDesign.png|300px|iterative design process]]
+What is special about the interaction design process is that you don't do exploration-design-testing only once but you go through this circle several times, improving your design further and further by working on it from different perspectives and checking with reality. It helps as well to be more creative at the end: by dealing with your users, you will see your designs from a new perspective and so develop new ideas.
+When you design minor features, you don't need to do all steps each time you try to solve a problem. It is very common to design, test and refine the design based on the test's results to test again.
-[[File:IterativeDesign.png|300px|iterative design process]]
 <!--
 * You can apply this to your problems. small and big ones.
 *established
--->
-The iterative design process helps you to structure your design process. It is an easy to use cycle model, which steps you can follow. The Process of doing so is explained in this guide.
-The steps are:
+The iterative design process helps you to structure your design process. It is an easy to use cycle model, which steps you can follow.
-# '''Research:''' in which you gather informations about user goals, existing problems and already existing solutions.
-#'''Formulating you aims:''' Helps you to know what you actually want to achieve with your design (and what not!). This can be seen as belonging to research but it is crucial to make the research useful, so it's got its own bullet-point!
-#'''Design:''' Is creating solutions for what you want to achieve. You start with a broad design of that is fairly abstract and make your ideas more concrete over time. For minor things new research would be too elaborate - than you repeat the smaller cycle of designing and testing in succession.
-#'''Testing:''' After you designed you need to test if your ideas work as you expected. This is can be a hard thing to do because some things that seem to be great turn out to be unsuitable for your users. You will get all sorts of interesting insights that will help you in improving your ideas.
-The model is called iterative because you will go through the all or a part of the steps several time. Doing all steps one after the other one time is known as an "iteration". Each time you do so, you improve your product and former abstract things will become more concrete.
+The model is called iterative because you will go through the all or a part of the steps several time. Doing all steps one after the other one time is known as an "iteration". Each time you do so, you improve your product and your ideas will evolve from being abstract to more and more concrete products.
 The model can be applied for designing the general product as well as for designing a small feature. You don't need to do all steps each time you try to solve a problem. It is very common to design, test and refine the design based on the test's results to test again. But you should at least consider the possibility to research.
-So what is all that good for? Following the steps helps you to understand your users by doing research. So you don't design for non-existing needs or interfaces nobody can use. It helps as well to be more creative at the end: by dealing with your users, you will see your designs from a new perspective and so develop new ideas.
+So what is all that good for? Following the steps helps you to understand your users by doing research. So you don't design for non-existing needs or interfaces nobody can use.
+-->
 '''A small Example:'''
 Imagine you design a new mobile phone. You can use the process that is suggested here to design the general product: You will research how people will use the phone, you will determine which features you need for meeting the users needs. Than you will design how all features work together in the phone and how it will look like. At the end you test it.