Lade die kostenlose Kindle-App herunter und lese deine Kindle-Bücher sofort auf deinem Smartphone, Tablet oder Computer – kein Kindle-Gerät erforderlich.
Mit Kindle für Web kannst du sofort in deinem Browser lesen.
Scanne den folgenden Code mit deiner Mobiltelefonkamera und lade die Kindle-App herunter.
Bild nicht verfügbar
Farbe:
-
-
-
- Herunterladen, um dieses Videos wiederzugeben Flash Player
Den Autoren folgen
OK
BRINGING DESIGN TO SOFTWARE Taschenbuch – 1. Februar 1996
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.
- Seitenzahl der Print-Ausgabe352 Seiten
- SpracheEnglisch
- HerausgeberAddison Wesley
- Erscheinungstermin1. Februar 1996
- Abmessungen16.51 x 1.91 x 23.5 cm
- ISBN-100201854910
- ISBN-13978-0201854916
Produktbeschreibungen
Amazon.de
Buchrückseite
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.
0201854910B04062001
Über den Autor und weitere Mitwirkende
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.
0201854910AB04062001
Produktinformation
- Herausgeber : Addison Wesley (1. Februar 1996)
- Sprache : Englisch
- Taschenbuch : 352 Seiten
- ISBN-10 : 0201854910
- ISBN-13 : 978-0201854916
- Abmessungen : 16.51 x 1.91 x 23.5 cm
- Amazon Bestseller-Rang: Nr. 2.176.582 in Bücher (Siehe Top 100 in Bücher)
- Nr. 6.118 in Softwareentwicklung (Bücher)
- Nr. 63.355 in Ingenieurwissenschaft & Technik (Bücher)
- Nr. 1.186.708 in Fremdsprachige Bücher
- Kundenrezensionen:
Über die Autoren

Entdecke weitere Bücher des Autors, sehe ähnliche Autoren, lese Buchempfehlungen und vieles mehr.

Entdecke weitere Bücher des Autors, sehe ähnliche Autoren, lese Buchempfehlungen und vieles mehr.
Kundenrezensionen
- 5 Sterne4 Sterne3 Sterne2 Sterne1 Stern5 Sterne32%57%0%12%0%32%
- 5 Sterne4 Sterne3 Sterne2 Sterne1 Stern4 Sterne32%57%0%12%0%57%
- 5 Sterne4 Sterne3 Sterne2 Sterne1 Stern3 Sterne32%57%0%12%0%0%
- 5 Sterne4 Sterne3 Sterne2 Sterne1 Stern2 Sterne32%57%0%12%0%12%
- 5 Sterne4 Sterne3 Sterne2 Sterne1 Stern1 Stern32%57%0%12%0%0%
Kundenbewertungen, einschließlich Produkt-Sternebewertungen, helfen Kunden, mehr über das Produkt zu erfahren und zu entscheiden, ob es das richtige Produkt für sie ist.
Um die Gesamtbewertung der Sterne und die prozentuale Aufschlüsselung nach Sternen zu berechnen, verwenden wir keinen einfachen Durchschnitt. Stattdessen berücksichtigt unser System beispielsweise, wie aktuell eine Bewertung ist und ob der Prüfer den Artikel bei Amazon gekauft hat. Es wurden auch Bewertungen analysiert, um die Vertrauenswürdigkeit zu überprüfen.
Erfahren Sie mehr darüber, wie Kundenbewertungen bei Amazon funktionieren.Spitzenrezensionen aus Deutschland
Derzeit tritt ein Problem beim Filtern der Rezensionen auf. Bitte versuche es später erneut.
- Bewertet in Deutschland am 20. Februar 2000Winograd brings together a mix of software designers, computer scientists, graphic artists, architects, scientists, and consultants, and their conceptions and methodologies for software design. Each describes their design situations from his or her position of expertise. Each of the "designers" has a similar message, ease of use and interaction must be relevant to the user, not only to the hierarchical structure of the software. Another point in the book is, if software is designed in such a way as to have the user append knowledge, as opposed to throw all daily logic of how things work in their world out the window, the learning curve for new software would be minimal.
The designer's involvement needs to be invoked from the beginning of the software project, and should not be considered as just a "final coat of spray-on aesthetics". Thought and design energy need to be given towards the capabilities of identifying the skill level and needs of the user, so that the user can accomplish his or her tasks while enduring the least amount of frustration. Hopefully the user will also learn something through his or her experience with the software, which would then bring them up to a new level of mastery. The use of design teams, with members encapsulating differing points of view, is emphasized as a successful methodology for the development of such software applications.
- Bewertet in Deutschland am 15. Februar 2000This book is a collection of chapters focusing on design and design topics. The chapter authors are from a variety of disciplines including software and product design, technology, architecture, graphic arts, and philosophy. This diversity adds to the richness in which the book addresses "design," expands the notion of the "designer" community of practice, and illustrates the importance of multifunctionality in design by taking lessons of practice from a variety of disciplines. After each chapter a "profile" of a product or situation is provided as a real-life example of the key points of the chapter.
The following themes appeared throughout the book:
· There needs to be a move from product-centered design to user-centered (or maybe use-centered) design. Talking, observing, interacting and listening with the users are key activities in making this happen.
· The move to a user-centered design can be aided by recognizing and professionalizing the role of a designer in the software development process. (in this book people are variously referred to as software designers, interaction designers, artist-designers, software architects, etc.)
· There is a need for tools and materials developed for software designers to create a language of design, and to develop prototypes and models. These things are needed for use in the design process to allow for a "conversation with the materials," --to create opportunities for exploration of the design, which may lead to unexpected characteristics and surprises. These, in turn, allow for reflection and lead to the development of better questions about our design and design process. These tools and methods also allow for communicating ideas, changes and goals to others involved in the design process.
· Design is a team-sport. Successful designers will be familiar with the roles, language and concerns of everyone involved in the design process so as best to include them, and their contributions, into the overall design effort. It's also true that the design process resides within an organization, whose values, culture, management and business concerns have an impact on the success of design efforts. A skillful designer will be aware of (and perhaps challenge) the impact of the organization on the design process to allow the design effort to be as successful as possible.
This is a good thought-starter for anyone interested in broadening their definition of designer and incorporating additional perspectives into their design practices.
- Bewertet in Deutschland am 15. Februar 2000"Bringing Design to Software" is not a software design "how-to" book; it is an edited exploration of the nature of software design through dialog. It investigates the concepts of software, design and prototyping as basal considerations for an understanding of the tenets of software design as a practice. The dialog involves looking at design from a number of areas including software design, other design fields, research, instruction and design management. Winograd, et al., have compiled the perspectives of practitioners from the fields mentioned above, many of them responsible for some aspect of some of the most popular applications currently available, and profiled explanatory and illuminating projects and programs to accompany those perspectives. They have woven this collection of experiences into a coherent focus on the factors and issues characteristic of design activities and the inherent "...situated nature of design - a sensitivity to the human context in all its richness and variety," proffering that design is both enabled and constrained by interaction with people.
The book promotes the idea that the most important people in software design are the users. Mitchell Kapor (interface designer for Lotus 1-2-3), the author of chapter 1, says that "...design...(is) where you stand with a foot in two worlds - the world of technology and the world of people and human purposes - and you try to bring the two together." "Bringing Design to Software" attempts to provide a way of looking at the interaction between the users and their world from a software design perspective and should be read by anyone seeking to enhance their ability to design software or to better understand software design considerations.
- Bewertet in Deutschland am 21. August 1997One or two of the essays are interesting; the others are either fuzzy attempts at deep thinking ("We need new paradigms! Bartender! New paradigms all 'round!") or spend too much time touting whatever it is the authors have that they want advertised. Inconsistent (in both level and quality), but with some buried nuggets