In my first article I touched upon the sketch-based method of user interface development. But what is a sketch (or as it is sometimes called a template) and what is it for? I think it would be logical to dwell at length on this issue.
All the participants of the development process inevitably deal with sketches: the customer, developers, the architect, designers, analysts, testers and even sales managers. The only person who will never see sketches is the end user of the product. Nevertheless it is the end user, whom the whole process of sketch creation should cater for. It is just as evident as the fact that a newspaper editor caters for the newspaper readers when composing an issue.
The main requirement for a sketch is accuracy and carefulness in sketch implementation. Sketch creation usually takes much more time than for example design creation for a sketch. However time expenditure is something that cannot be avoided at this stage. So if you have made up your mind to develop UI through sketches, be ready to spend some time.
Usually a well-elaborated sketch meets the following requirements:
Real-time law observance
Everybody knows that twice two makes four. So to save time or for any other reasons you shouldn’t state in the sketch that twice two makes six. Why so? Because explaining it to the customer will take you twice as much time as you save.
Precision in real data representation
If you possess the real data, you should enter this and no other data in the sketch. If you don’t have the real data you can substitute them only with data that are close to real (or at least you believe them to be close to real).
Precision in functionality description
If a sketch refers to a complicated field, all the operations on this screen should be further explained in a text application. The most common questions like “What can I do here?” usually require just a short and simple explanation.
Indication of a sketch position in the workflow
If the program under development is a complex one, then it is necessary to clearly define where the sketch is placed from the workflow point of view.
Carefulness
Carelessly performed work doesn't befit a professional. In case of a sketch it is especially important to have the work done neatly, as all development team members are involved in using the sketches.
If you observe these basic requirements you will make up a good sketch. But if it will be excellent depends on your understanding of human psychology and logic.
All the participants of the development process inevitably deal with sketches: the customer, developers, the architect, designers, analysts, testers and even sales managers. The only person who will never see sketches is the end user of the product. Nevertheless it is the end user, whom the whole process of sketch creation should cater for. It is just as evident as the fact that a newspaper editor caters for the newspaper readers when composing an issue.
The main requirement for a sketch is accuracy and carefulness in sketch implementation. Sketch creation usually takes much more time than for example design creation for a sketch. However time expenditure is something that cannot be avoided at this stage. So if you have made up your mind to develop UI through sketches, be ready to spend some time.
Usually a well-elaborated sketch meets the following requirements:
Real-time law observance
Everybody knows that twice two makes four. So to save time or for any other reasons you shouldn’t state in the sketch that twice two makes six. Why so? Because explaining it to the customer will take you twice as much time as you save.
Precision in real data representation
If you possess the real data, you should enter this and no other data in the sketch. If you don’t have the real data you can substitute them only with data that are close to real (or at least you believe them to be close to real).
Precision in functionality description
If a sketch refers to a complicated field, all the operations on this screen should be further explained in a text application. The most common questions like “What can I do here?” usually require just a short and simple explanation.
Indication of a sketch position in the workflow
If the program under development is a complex one, then it is necessary to clearly define where the sketch is placed from the workflow point of view.
Carefulness
Carelessly performed work doesn't befit a professional. In case of a sketch it is especially important to have the work done neatly, as all development team members are involved in using the sketches.
If you observe these basic requirements you will make up a good sketch. But if it will be excellent depends on your understanding of human psychology and logic.
 | Posted by Ekaterina Molchanova, QA Analyst |
| Bookmark or share: |          |
