Download PDF Bringing Design to Software, by Terry Winograd
Bringing Design To Software, By Terry Winograd. Allow's check out! We will frequently discover this sentence everywhere. When still being a children, mommy used to buy us to constantly check out, so did the teacher. Some books Bringing Design To Software, By Terry Winograd are totally reviewed in a week and also we need the responsibility to sustain reading Bringing Design To Software, By Terry Winograd What around now? Do you still love reading? Is reading just for you who have obligation? Definitely not! We below supply you a brand-new book entitled Bringing Design To Software, By Terry Winograd to check out.
Bringing Design to Software, by Terry Winograd
Download PDF Bringing Design to Software, by Terry Winograd
Bringing Design To Software, By Terry Winograd. In what instance do you like reviewing so much? What regarding the kind of the e-book Bringing Design To Software, By Terry Winograd The have to read? Well, everyone has their own reason must read some books Bringing Design To Software, By Terry Winograd Mainly, it will certainly connect to their need to get expertise from the e-book Bringing Design To Software, By Terry Winograd and also want to read merely to obtain amusement. Novels, tale e-book, as well as various other amusing books end up being so preferred this day. Besides, the clinical publications will certainly likewise be the most effective reason to choose, specifically for the students, educators, medical professionals, business owner, as well as various other occupations that love reading.
For everyone, if you want to start joining with others to review a book, this Bringing Design To Software, By Terry Winograd is much suggested. As well as you need to obtain guide Bringing Design To Software, By Terry Winograd below, in the link download that we offer. Why should be below? If you desire various other type of publications, you will always find them and Bringing Design To Software, By Terry Winograd Economics, national politics, social, scientific researches, religions, Fictions, and also a lot more books are provided. These offered books remain in the soft files.
Why should soft documents? As this Bringing Design To Software, By Terry Winograd, many people likewise will have to acquire the book faster. However, sometimes it's so far method to get guide Bringing Design To Software, By Terry Winograd, even in various other country or city. So, to reduce you in locating guides Bringing Design To Software, By Terry Winograd that will support you, we assist you by offering the lists. It's not only the listing. We will offer the recommended book Bringing Design To Software, By Terry Winograd link that can be downloaded directly. So, it will not need more times and even days to position it as well as various other books.
Collect guide Bringing Design To Software, By Terry Winograd begin with currently. However the extra method is by collecting the soft documents of guide Bringing Design To Software, By Terry Winograd Taking the soft data can be saved or saved in computer or in your laptop computer. So, it can be greater than a book Bringing Design To Software, By Terry Winograd that you have. The most convenient means to expose is that you can also save the soft file of Bringing Design To Software, By Terry Winograd in your ideal as well as available gizmo. This problem will certainly mean you too often review Bringing Design To Software, By Terry Winograd in the extra times more than chatting or gossiping. It will not make you have bad habit, yet it will certainly lead you to have much better practice to check out book Bringing Design To Software, By Terry Winograd.
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 users 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, a
- Sales Rank: #1204946 in Books
- Published on: 1996-04-12
- Original language: English
- Number of items: 1
- Dimensions: 9.20" h x .90" w x 6.20" l, 1.15 pounds
- Binding: Paperback
- 352 pages
Amazon.com Review
Design of software has often taken place in isolation from the many lessons learned in the design of objects or non-computer processes. Continuing in the tradition of Donald Norman's highly influential Design of Everyday Things, this collection of essays provides essential inspiration for reflective software designers driven by practical concerns of what works, what doesn't--and why. Contains contributions by such insightful software engineers as David Liddle, Donald Norman, John Bennett, and Michael Schrage.
From the Inside Flap
Portions of this preface appear in Interactions magazine, Volume III, Number 2, March, 1996. Used with permission.
Software is an ambiguous word. People who talk about software may be thinking about the structure of program components, about the functionality of an application, about the look and feel of an interface, or about the overall user experience of a hardware - software environment. Each of these perspectives brings along its own context of understanding about what matters, what can be designed, and what tools and methods are appropriate.
Design is also an ambiguous word. Among its many meanings, there runs a common thread, linking the intent and activities of a designer to the results that are produced when a designed object is experienced in practice. Although there is a huge diversity among the design disciplines, we can find common concerns and principles that are applicable to the design of any object, whether it is a poster, a household appliance, or a housing development.
In Bringing Design to Software, our goal is to improve the practice of software design, through thinking about design from a broader perspective, and exploring how lessons from all areas of design can be applied to software. We use the word exploring here consciously; what you will read is an open-ended foray into ideas, rather than a how-to handbook of rules and methods. Software design is still a young field, and we are far from having a clear articulation of the relevant principles. Software design is a user-oriented field, and as such will always have the human openness of disciplines such as architecture and graphic design, rather than the hard-edged formulaic certainty of engineering design.
This book brings a collection of diverse perspectives to bear on the common topic of software design. The authors include software designers, designers in other fields, researchers, teachers, software industry executives, and industry analysts. Each chapter, in its own way, addresses two key sets of questions.
What is design, and what happens in designing? How can we apply an understanding of design to the practice of software design, to produce software that is better for users?
In communicating their different perspectives, our authors have designed their texts to address readers who have a variety of professional backgrounds and of reasons for interest in software. Our natural audience is the growing group of people who consider themselves software designers--people who work day by day to produce new software, interfaces, and user experiences. Ultimately, their work is where, to use a popular phrase, the rubber meets the road. Effective software design requires effective software designers, and we address their concerns in both the discussions and the software-design examples given in brief profiles throughout the book.
The individual designer, however, does not represent the whole story of software design. Software designers work in (and with) organizations that include people who manage software development, market software, develop hardware, write documentation, and perform all the other activities needed to get software to users. A deeper understanding of the design process and of the goals of software design can be valuable to everyone engaged in the software enterprise. Many of our chapters and examples have as much to say to the people who manage design organizations as to the people who work within those organizations.
Looking further outside of the immediate design environment, we have included perspectives that address students and researchers in human-computer interaction. Although this book is not primarily a scholarly analysis, we have included a large number of references, and each author has suggested further readings that ground the discussion in the professional literature. In this book, we raise many more questions than we answer, and the pointers to other writing may help readers to seek and develop their own answers.
Expanding our circle still further, we hope that the book will be of interest to professionals in other design disciplines, such as architecture, graphic design, product design, and urban design. In "bringing design to software," we have included chapters by designers from all these fields, exploring how insights from their own disciplines can be brought to bear on software design. Colleagues from these disciplines may find it valuable both to see the connections to software, and to reflect on the nature of their own work.
Finally, a pervasive theme of this book is that one group of people is most important in software design--the users. Although our primary focus is how to do software design well, the book has much to say about the selection, introduction, and use of software. If every buyer and user of software applications has a well-developed understanding of software design, the industry will be forced to respond with better-designed software. We want to reach out to this larger audience of people who care about what software can do for them, and to help make the software that is available to them become more appropriate, more usable, and more enjoyable.
Our goal is to make visible what is common and timeless to design, while looking at the world at hand--the cases and examples that make up the tradition of software design in its short history. We have written to communicate with the reflective designer--someone who is driven by practical concerns, and who is also able to take a moment to step back and reflect on what works, what doesn't work, and why. Origins
This book developed from a workshop on software design in the summer of 1992, organized by the Project on People, Computers, and Design at Stanford University, with support from the National Science Foundation, Interval Research Corporation, and the Association for Software Design. A group of 30 software designers, graphic designers, industrial designers, researchers, and teachers got together for a lively 3-day discussion on what software design is and might be, and on what we could see emerging in each of our disciplines that would help us to define and promote new visions of software design. At the end of that workshop, several of the participants agreed to work together on a book that would merge their individual perspectives into a composite picture of software design. Since then, we have gone through an extensive process of prototyping, debugging, and user testing many versions of this book. The result is an integrated collection of essays and interviews, addressing issues and concerns that are central to the functionality, usability, and value of software. Acknowledgments
In any project of this length and scope, many people contribute their knowledge and skills. We have been assisted by colleagues whose understanding and whose work on this volume are truly remarkable. First, and most obviously, the chapter authors have been diligent in reworking their contributions, patient in following the book through its changes of direction, and insightful in their writing and comments. The experience of producing this book has been a challenging dialog, in which they have eagerly and actively engaged.
Numerous people were instrumental in creating the original workshop, including the organizing committee--Bradley Hartfield, Mitchell Kapor, David Kelley, Donald Norman, Donald Sch�n, Andrew Singer, and Terry Winograd--and the conference director, Cynthia Lewis, with assistance from Barry Polley. The other conference participants (in addition to the contributors of chapters to the book) were Jeanne Bamberger (MIT), Nathaniel Borenstein (Bellcore, currently First Virtual), Larry Bucciarelli (MIT), Robert Carr (Autodesk), Parvati Dev (Stanford Medical School), Laird Foshay (Tabula Interactive), Nick Flor (UC San Diego), Chris Graham (Microsoft), John Hestenes (National Science Foundation), Susan Kare (design consultant), Jason Lewis (vivid), David Liddle (Interval Research), Kyle Mashima (Objective Software), Raul Medina-Mora (Action Technologies), Gary Perlman (Ohio State University), David Rine (George Mason University), Kurt Schmucker (Apple Computer), Lee Sproull (Boston University), Suzanne Stefanac (Mac World), Susan Stucky (Institute for Research on Learning), Bill Verplank (Interval Research), Patrick Whitney (Institute of Design, Illinois Institute of Technology), Sean White (Interval Research), and Karen Wieckert (Stanford University).
The workshop and much of the subsequent work on the book were supported generously by the Interval Research Corporation. Interval's president, David Liddle, deserves a special note of thanks for his consistent and persistent efforts on behalf of this work and for his support of the development of software design in many other ways. Financial support also came from the National Science Foundation, Directorate for Computer and Information Science and Engineering, grant #CDA-9018898.
Valuable editorial assistance and reviews have been provided by Robert Brunner, Allan Bush, Laird Foshay, Jonathan Grudin, Peter Hildebrand, Barbara Knapp, Donald Lindsay, Mary Miller, Barry Polley, Richard Rubinstein, Suzanne Stefanac, Howard Tamler, Bill Verplank, and Sean White. Peter Gordon of Addison-Wesley and Lyn Dupr� have been active participants in the development of the book, providing the kind of editorial input that authors hope for and rarely get from a publisher.
Finally, switching from the editorial "we" to an individual "I," I can convey only a small part of the tremendous gratitude and admiration I have for my coeditors, John Bennett, Laura De Young, and Brad Hartfield. Each of them has given the kind of dedication and effort that might be expected of a solo editor. They have labored over chapters, read and commented on drafts, worked through dozens of meetings and discussions, and contributed to the manuscript in every possible way. It is a cliche to say "without them it would not have been possible," but, in this case, the assertion is decidedly true. This book is a group production, through and through.
And now the group expands to include you, the reader, whose active participation we invite. We hope that this book will inspire you to add your own perspective--to speak up in the ongoing dialog about what software is, what it can do, and how we can design it more effectively to suit human needs and concerns.
Terry Winograd (winograd@cs.stanford)
John Bennett (bennett@pcd.stanford)
Laura De Young (laura@windrose)
Bradley Hartfield (hartfield.chi@xerox)
0201854910P04062001
From the Back Cover
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
Most helpful customer reviews
12 of 13 people found the following review helpful.
Bringing Design to Software
By Robin Lindbeck
This 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.
7 of 8 people found the following review helpful.
Take the user into account
By Jennifer Ryan
Winograd 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.
3 of 3 people found the following review helpful.
Design is not only for the designers.
By Henry L Smith
"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.
See all 9 customer reviews...
Bringing Design to Software, by Terry Winograd PDF
Bringing Design to Software, by Terry Winograd EPub
Bringing Design to Software, by Terry Winograd Doc
Bringing Design to Software, by Terry Winograd iBooks
Bringing Design to Software, by Terry Winograd rtf
Bringing Design to Software, by Terry Winograd Mobipocket
Bringing Design to Software, by Terry Winograd Kindle
Bringing Design to Software, by Terry Winograd PDF
Bringing Design to Software, by Terry Winograd PDF
Bringing Design to Software, by Terry Winograd PDF
Bringing Design to Software, by Terry Winograd PDF
