Bringing Design to Software - Tapa blanda

Acerca del autor

Terry Winograd is professor of computer science at Stanford University where he has developed an innovative program in software design. Winograd completed much of his work on this book at Interval Research Corporation, where he is a regular consultant. He is a member of the advisory board of the Association for Software Design, the editorial board of Human-Computer Interaction, and the national board of Computer Professionals for Social Responsibility.

De la contraportada

In this landmark book, Terry Winograd shows how to improve the practice of software design by applying lessons from other areas of design to the creation of software. The goal is to create software that works -- really works -- because it is both appropriate and effective for the people who use it.

The book contains essays contributed by prominent software and design professionals, interviews with experts, and profiles of successful projects and products. These elements are woven together to illuminate what design is, to identify the common core of practices in every design field, and to show how software builders can apply these practices to produce software that is more satisfying for users. The initial chapters view software from the user's perspective, featuring the insights of experienced software designers and developers, including Mitchell Kapor, David Liddle, John Rheinfrank, Peter Denning, and John Seely Brown. Subsequent chapters turn to the designer and the design process, with contributions from designers and design experts, including David Kelley, Donald Schön, and Donald Norman. Profiles discussing Mosaic, Quicken, Macintosh Human Interface Guidelines, Microsoft Bob, and other notable applications and projects highlight key points in the chapters.

This book is for a broad community of people who conceive, develop, market, evaluate, and use software. It is foremost for software designers-- particularly the reflective designer who is driven by practical concerns yet is able to step back for a moment and reflect on what works, what doesn't work, and why. At the same time, it reveals new directions and new possibilities for programmers who build software and for product managers who bring software to market.