Designing from Both Sides of the Screen: How Designers and Engineers Can Collabo
Ellen Isaacs, Alan Walendowski
- 出版商: New Riders
- 出版日期: 2001-12-10
- 售價: $1,840
- 貴賓價: 9.5 折 $1,748
- 語言: 英文
- 頁數: 352
- 裝訂: Paperback
- ISBN: 0672321513
- ISBN-13: 9780672321511
已絕版
買這商品的人也買了...
-
$912User and Task Analysis for Interface Design
-
$1,810$1,720 -
$860$679 -
$700The Art & Science of Web Design
-
$2,380$2,261 -
$950$855 -
$600$510 -
$299Usability: The Site Speaks for Itself
-
$860$731 -
$450$383 -
$1,440C++ Templates: The Complete Guide (Hardcover)
-
$650$514 -
$590$466 -
$1,045Human Factors in Consumer Products
-
$2,810$2,670 -
$750$675 -
$560$504 -
$2,340$2,223 -
$720$569 -
$450$351 -
$420$328 -
$850$723 -
$2,275$2,161 -
$525Digital Storytelling : A Creator's Guide to Interactive Entertainment (Paperback)
-
$490Starting Electronics Construction: Techniques, Equipment and Projects
相關主題
商品描述
Written from the perspectives of both a user interface designer and a software engineer, this book demonstrates rather than just describes how to build technology that cooperates with people. It begins with a set of interaction design principles that apply to a broad range of technology, illustrating with examples from the Web, desktop software, cell phones, PDAs, cameras, voice menus, interactive TV, and more. It goes on to show how these principles are applied in practice during the development process -- when the ideal design can conflict with other engineering goals.
The authors demonstrate how their team built a full-featured instant messenger application for the wireless Palm and PC. Through this realistic example, they describe the many subtle tradeoffs that arise between design and engineering goals. Through simulated conversations, they show how they came to understand each other's goals and constraints and found solutions that addressed both of their needs -- and ultimately the needs of users who just want their technology to work.
Table of Contents
Introduction.
THE GOAL.
1. On Being a Butler.
2. Don't Impose: Respect Physical Effort.
3.
Don't Impose: Respect Mental Effort.
4. Be Helpful.
THE PROCESS.
5. Setting Up: Understanding Users' Needs.
6.
Structuring the User Interface.
7. Laying Out the User Interface.
8.
Architecting with the UI in Mind
9. Initial Development.
10. Iterative
Development: Observing Use.
11. Conclusion.
APPENDIXES.
Appendix A. Guidelines.
Appendix B. Recommended Readings.
Index.