Benutzer-Werkzeuge
se:usability
Unterschiede
Hier werden die Unterschiede zwischen zwei Versionen angezeigt.
| Beide Seiten der vorigen Revision Vorhergehende Überarbeitung Nächste Überarbeitung | Vorhergehende Überarbeitung Nächste Überarbeitung Beide Seiten der Revision | ||
|
se:usability [2008-01-14 15:33] stefan |
se:usability [2008-02-23 18:07] stefan |
||
|---|---|---|---|
| Zeile 1: | Zeile 1: | ||
| + | ===== Klausur ===== | ||
| + | * **Usability** bezeichnet das Ausmaß zu dem ein Programm von festgelegten Benutzern verwendet werden kann, um festgelegte Ziele effektiv, effizient und zufriedenstellend in einem gegebenen Kontext zu erreichen. | ||
| + | * Kontext: Benutzer, Ausgabe, Ausstattung | ||
| + | * Maße: Effektivität, Effizienz, Zufriedenheit | ||
| + | * **Ergonomie** ist sowohl eine wissenschaftliche Disziplin, die sich mit dem Verständnis von Interaktionen zwischen Menschen und Systemen beschäftigt, als auch der Beruf, der die Theorie, Prinzipien, Daten und Methoden anwendet, um die Leistung eines Systems und das Wohlbefinden des Menschen, der damit arbeitet, zu optimieren. | ||
| + | * Usability konzentriert sich auf: | ||
| + | * Benutzung | ||
| + | * Aufgabe | ||
| + | * Leistung | ||
| + | * Aufgabenunterstützung | ||
| + | * Was wurde bei Usability falsch gemacht? | ||
| + | * Design | ||
| + | * Prozess | ||
| + | * Benutzer | ||
| + | * Kurz gesagt: Usability wurde als unwichtig abgetan, Produkt konzentriert sich nicht auf Aufgaben der Benutzer | ||
| + | * Usage-centered Product Design | ||
| + | * Spezifikation aus Kundensicht | ||
| + | * Die vier Usability-Aspekte stehen im Vordergrund | ||
| + | * Modellgetrieben | ||
| + | * Technologie wird komplett außen vor gelassen | ||
| + | * Offen für Innovationen | ||
| + | * Definierte Methoden sind lehr- und erlernbar | ||
| + | * Abgrenzung User-centered Design | ||
| + | * Ablauf | ||
| + | * Benutzer identifizieren (gegen Systemakteure abgrenzen) | ||
| + | * Benutzerrollen modellieren | ||
| + | * Aufgaben identifizieren | ||
| + | * Gruppierung der Aufgaben (Priorisierung) | ||
| + | * Darstellung und Interaktionen ableiten | ||
| + | |||
| ===== Exercises ===== | ===== Exercises ===== | ||
| Zeile 85: | Zeile 115: | ||
| The user wants to reach his goal quickly and without being distracted. If he needs to open a help screen and search for information regarding his current problem that costs time and the user needs to switch from help to the actual work and back. If you provide inline help (e.g. balloon tips) the user gets help without the need to explicitly search for it and is not disturbed in his work. Also, built-in help can be much more to the point than a generally written help text. | The user wants to reach his goal quickly and without being distracted. If he needs to open a help screen and search for information regarding his current problem that costs time and the user needs to switch from help to the actual work and back. If you provide inline help (e.g. balloon tips) the user gets help without the need to explicitly search for it and is not disturbed in his work. Also, built-in help can be much more to the point than a generally written help text. | ||
| + | |||
| ==== Exercise 4.1 ==== | ==== Exercise 4.1 ==== | ||
| Zeile 90: | Zeile 121: | ||
| I think most websites habe bad usability because they are not given the attention they need by the companies. Many companies still think of a website as kind of a business card and not as their representation on the internet. Also the fact that many websites are programmed by high school students who do not have the required skills to design a good website may be a reason. For many companies, a website is something you need but you do not want to pay much money for, so usability is neglected. | I think most websites habe bad usability because they are not given the attention they need by the companies. Many companies still think of a website as kind of a business card and not as their representation on the internet. Also the fact that many websites are programmed by high school students who do not have the required skills to design a good website may be a reason. For many companies, a website is something you need but you do not want to pay much money for, so usability is neglected. | ||
| + | |||
| + | |||
| + | ==== Exercise 5.1 ==== | ||
| + | **Find some wrong designs in products you are using! Make suggestions for improvement.** | ||
| + | |||
| + | ToDo | ||
| + | |||
| + | ==== Exercise 5.1 ==== | ||
| + | **Why should you think about trends?** | ||
| + | |||
| + | If a new trend emerges and your product is the only one that has not implemented it, that would be a big problem. Programs like Microsoft Windows and Office set trends that will most likely be accepted by the mass of customers. So if you do not react to trends or even worse do not know that there are certain trends, that could lead to dissatisfied customers. | ||
| + | |||
| + | |||
| + | ==== Exercise 5.2 ==== | ||
| + | **Find out the key features of Microsoft Office 2007 and the problems they want to solve compared to former solutions.** | ||
| + | |||
| + | * Replaced menus with "Ribbon", Office button ("pearl) -> groups commands by tasks | ||
| + | * Contextual tabs -> commands appear in the right context (e.g. table formatting if you click on a table) | ||
| + | * Live previews of the available commands provide the user with a better understanding of the commands' outcome | ||
| + | * [[http://office.microsoft.com/en-us/help/HA101679411033.aspx#2|The Microsoft Office Fluent user interface overview - Key Features]] | ||
| + | |||
| + | ==== Exercise 6.1 ==== | ||
| + | **Why does a usability engineer need so many skills?** | ||
| + | |||
| + | Usability is a core feature of a software product. For this reason, a usability engineer needs to have knowledge in the field of software development and of course design itself. But he also has to convince management and other departments that usability is crucial and may not be neglected. For this reason, he needs good communication skills. He also needs to be able to feel with the customer and see the software from different perspectives to reach a certain level of usability. And nonetheless, he also needs the basis knowledge about design, ergonomics etc. to finally implement the usability. | ||
se/usability.txt · Zuletzt geändert: 2014-04-05 11:42 (Externe Bearbeitung)
Seiten-Werkzeuge
Falls nicht anders bezeichnet, ist der Inhalt dieses Wikis unter der folgenden Lizenz veröffentlicht: CC Attribution-Noncommercial-Share Alike 4.0 International
