Interaktion i projekten (Lars Kjelldahl)

Ni ska göra ett användargränssnitt till er prototyp.
Det finns två situationer då detta gränssnitt ska användas:
  för de användare det är tänkt
  i samband med slutpresentationen i D2 i maj

Några kriterier att tänka på:
  - det bör vara begripligt-enkelt-självförklarande
  - det bör fånga upp vanliga fel
  - det bör kunna anpassas så att det fungerar även i D2 med t.ex.
    tillräckligt stor text
  - kanske innehålla någon bra "demo-möjlighet" med tanke på slutpresentationen.
  - prova gränssnittet på ett tidigt stadium på någon utanför gruppen - här
    är det inte säkert att ni bara ska lyssna på uppdragsgivaren
    (om han/hon inte själv är en typisk användare)

***************************************************************
User interface reviews ­ 10 questions
Nils-Erik Gustafsson, Ericsson Utvecklings AB, +46-8-727 4066; Nils-Erik.Gustafsson@ericsson.com
To review user interfaces is difficult! The following 10 questions may
hopefully prove useful, but remember that positive responses only are
required ­ not sufficient...
1. Are terms and symbols used consistently?
2. Is the required information readily available? The required functions?
3. Where am I? What is the name of the application, the object (if any), and the operation?
What is happening?
4. What can I do? Which operations are possible to perform?
5. Is all the required information where I need it?
6. Can I go back one step in the interaction and undo a previous operation?
7. Can I interrupt and quit the application without losing information?
8. Is the information sensibly grouped? (Menus, windows, etc.)
9. Are graphical elements such as colour and lines used in a subtle and consistent manner?
10. Are response times reasonable (from the user¹s point of view)? Do I get the right type of
feedback?
As you can see, many of these questions are difficult to answer with a straight ³yes² or ³no².
What do I, e.g., mean with ³required² functions? The system developer has one opinion, the
intended users most likely different ones before and after having used the system for some
time, and it is not certain that any of these are correct...
A sensible strategy is often (always?) to start by developing a rudimentary version with a
minimum of fundamental functions, make this available to real users and then follow up on
frequency of use and actual need. When designing a Swiss Army knife, it makes sense to start
with the big blade and not with the toothpick. System design is best done in a similar manner.
References
Microsoft: Microsoft Windows User Experience, ISBN 0-7356-0566-1
Amiga User Interface Style Guide, ISBN 0-201-57757-7
Apple: Macintosh Human Interface Guidelines, ISBN 0-201-62216-5
Apple: HyperCard Stack Design Guidelines, ISBN 0-201-51784-1
IBM: Object-Oriented Interface Design ­ IBM Common User Access Guidelines, SC34-4399-00
Java: Java Look and Feel Design Guidelines, ISBN 0-201-61585-1
OSF/Motif Style Guide, ISBN 0-13-643123-2
Sun: OPEN LOOK Graphical User Interface Application Style Guidelines, ISBN 0-201-52364-7