|
||||||||||||||||||||
|
||||||||||||||||||||
|
||||||||||||||||||||
Usability Engineering
und über 1 Million weitere Bücher verfügbar für Amazon Kindle .
Erfahren Sie mehr
| |||||||||||||||
|
|
Produktinformation
Möchten Sie die Produktinformationen aktualisieren oder Feedback zu den Produktabbildungen geben?
Ist der Verkauf dieses Produkts für Sie nicht akzeptabel? |
Mehr über die Autoren
Entdecken Sie Bücher, lesen Sie über Autoren und mehr
Produktbeschreibungen
Pressestimmen
"This book is ideally suited for a problem-based curriculum in which students simultaneously learn good development processes while completing a term project. The book gives excellent guidance, and the case study approach is an excellent organizer and motivator. At last, the proper problem-based textbook." - Don Norman, Nielsen Norman Group "One of the nice things about this book is that it identifies where tradeoffs exist in developing user interfaces. Too many books provide guidelines as if they were absolute; unfortunately, this is not the case. Tradeoffs must be constantly made, and understanding how one usability objective can impact another is critical to good design." - Jon Meads, Usability Architects
Kurzbeschreibung
You don't need to be convinced. You know that usability is key to the success of any interactive system-from commercial software to B2B Web sites to handheld devices. But you need skills to make usability part of your product development equation. How will you assess your users' needs and preferences? How will you design effective solutions that are grounded in users' current practices? How will you evaluate and refine these designs to ensure a quality product? Usability Engineering: Scenario-Based Development of Human-Computer Interaction is a radical departure from traditional books that emphasize theory and address experts. This book focuses on the realities of product development, showing how user interaction scenarios can make usability practices an integral part of interactive system development. As you'll learn, usability engineering is not the application of inflexible rules; it's a process of analysis, prototyping, and problem solving in which you evaluate tradeoffs, make reasoned decisions, and maximize the overall value of your product.
Welche anderen Artikel kaufen Kunden, nachdem sie diesen Artikel angesehen haben?
In diesem Buch
(Mehr dazu)
Einleitungssatz
During the 1990s scenario-based software development techniques became increasingly prominent in software engineering and human-computer interaction. Lesen Sie die erste Seite
Buchdeckel | Copyright | Inhaltsverzeichnis | Auszug | Stichwortverzeichnis
During the 1990s scenario-based software development techniques became increasingly prominent in software engineering and human-computer interaction. Lesen Sie die erste Seite
Mehr entdecken
Wortanzeiger
Ausgewählte Seiten ansehenWortanzeiger
Buchdeckel | Copyright | Inhaltsverzeichnis | Auszug | Stichwortverzeichnis
Tags(Was ist das?)Bei einem Tag handelt es sich um ein Schlagwort, das zum Produkt passt.
Tags erleichtern allen Kunden die Suche und die Sortierung ihrer Lieblingsprodukte. |
Kundenrezensionen
Es gibt noch keine Kundenrezensionen auf Amazon.de
5 Sterne
4 Sterne
3 Sterne
2 Sterne
1 Sterne
Die hilfreichsten Kundenrezensionen auf Amazon.com (beta)
Amazon.com:
4 Rezensionen
11 von 14 Kunden fanden die folgende Rezension hilfreich
Very well organized
21. Dezember 2001
Format:Gebundene Ausgabe
This book is a good reference in many points of the usability process - evaluation, design, and testing. The authors organize chapters in a very structured way that the content is very digestible. At 448 pages, the book isn't meant to be read in a single session, but again, it's a great reference.
My favorite part about this book is the fact that it actually has a section on user documentation - something that is lacking in many books on the subject of usability, and the achilles heel of many projects.
2 von 2 Kunden fanden die folgende Rezension hilfreich
Great and applicable for other domains
2. Juni 2007
Format:Gebundene Ausgabe
A very good book mainly focused on Scenario-Based analysis which you can actually use in every other subject and aspects of your life (even if you are choosing between trips). I bought this book as a text book for an HCI subject in VT and it was interesting to follow.
Myopic, innaccurate
18. Mai 2012
Format:Gebundene Ausgabe
This book delivers little specific usability advice, but as another review said, touts its authors' pet theory they call "scenario based design." Often, it simply misinforms. Take this quote from the pages available on Look Inside:
---
"Software engineering is founded on the ideas of structured programming (Mills 1971): Programmers first define the major structures of a software system - the database, the event handler, and the network server..."
---
The term "software engineering," according to Wikipedia, appeared in the 1950s, well before Goto Considered Harmful popularized "structured programming." The authors, however, handily ignore this and imply that Mills invented structured programming with databases, event handlers and servers, leading to a new dawn of computer engineering. Nevermind that ARPANET was at that time a toddler and what they call "structured programming" only barely resembles the accepted definition.
While these particular errors do not relate directly to the relative merits of the usability advice this book offers, they do illustrate a careless quality in the research. Furthermore, they indicate the authors' apparent unfamiliarity with software development history and practical software construction.
---
"Software engineering is founded on the ideas of structured programming (Mills 1971): Programmers first define the major structures of a software system - the database, the event handler, and the network server..."
---
The term "software engineering," according to Wikipedia, appeared in the 1950s, well before Goto Considered Harmful popularized "structured programming." The authors, however, handily ignore this and imply that Mills invented structured programming with databases, event handlers and servers, leading to a new dawn of computer engineering. Nevermind that ARPANET was at that time a toddler and what they call "structured programming" only barely resembles the accepted definition.
While these particular errors do not relate directly to the relative merits of the usability advice this book offers, they do illustrate a careless quality in the research. Furthermore, they indicate the authors' apparent unfamiliarity with software development history and practical software construction.
Waren diese Rezensionen hilfreich?
Wir wollen von Ihnen hören.
Kunden diskutieren
|
Das Forum zu diesem Produkt
Fragen stellen, Meinungen austauschen, Einblicke gewinnen Aktive Diskussionen in ähnlichen Foren
Kundendiskussionen durchsuchen
|
Ähnliche Foren
|
||||||||||||||||||||||||||||||||||
Lieblingslisten
|
|
Ähnliche Artikel finden
Anhand des Sachgebietes nach ähnlichen Produkten suchen:
Ihr Kommentar
Möchten Sie die Produktinformationen aktualisieren oder Feedback zu den Produktabbildungen geben?
|
