Bureaucrats, emailconfirmed
1,221
edits
→...in words
| Line 246: | Line 246: | ||
Even if this is not seen commonly as "design" you can turn your ideas into words to communicate them or to check if you are clear about what you want to do. This is a technique that is very useful in earlier stages after the first big research on your users and their goals. Guided by what you find out you can write down what you want to provide to meet these goals. | Even if this is not seen commonly as "design" you can turn your ideas into words to communicate them or to check if you are clear about what you want to do. This is a technique that is very useful in earlier stages after the first big research on your users and their goals. Guided by what you find out you can write down what you want to provide to meet these goals. | ||
A structured approach of this is defining "Requirements". This is defining the things your product needs to do at the end – in early phases the very essential ones. | A structured approach of this is defining "Requirements". This is defining the things your product needs to do at the end – in early phases the very essential ones. | ||
You can do this by writing them down as Sentences contnaining data, an action done with it and possibly the context. Data is a "thing" that represents some kind of information. That can be a phone number, an image, a file, a bookmark etc. | |||
An example would be: Look up [action] a phonebook entry [thing] while talking [context]. Or: play [action] music [thing] | |||
You can as well structure this more and make lists with the requirements. | |||
* Actions - what does the system need to be able to do? (e.g. sync files with PC, text WYSIWYG entry, inform the user about current appointments) | |||
* Data - with which kind of data ("things") does the system need to deal? (e.g. play MP3 music, handle max. 10,000 user profiles etc.) | |||
* Context – Where is the system used and for which purposes? (e.g. in public and outside, so it must be durable) | |||
* User - Which kind of user shall deal with the system? (e.g. the product is aimed to design students) | |||
There my be other kinds of requiremets that you need to consider when developing your product. This could be size of the product, speed, final price, that it needs to feel "cool" for teens to have it etc. | |||
==Sketches== | ==Sketches== | ||
[[File:UI-Sketch-Flickr-Kyle_McDonald.jpg|thumb|50px|left]] | [[File:UI-Sketch-Flickr-Kyle_McDonald.jpg|thumb|50px|left]] | ||