设计原本【英文版】.pdf

Preface
I write to prod designers and design project managers into think-
ing hard about the process of designing things, especially complex
systems. The viewpoint is that of an engineer, focused on utility
and effectiveness but also on efficiency and
Who Should Read This Book?
In The Mythical Man-Month I aimed at “professional programmers,
professional managers, and especially professional managers of
programmers.” I argued the necessity, difficulty, and methods of
achieving conceptual integrity when software is built by teams.
This book widens the scope considerably and adds lessons
from 35 more years. Design experiences convince me that there
are constants across design processes in a diverse range of design
domains. Hence the target readers are:
1. Designers of many kinds.  Systematic design excluding intu-
ition yields pedestrian follow-ons and knock-offs; intuitive design
without system yields flawed fancies. How to weld intuition and
systematic approach? How to grow as a designer? How to func-
tion in a design team?
Whereas I aim for relevance to many domains, I expect an
audience weighted toward computer software and hardware
designers—to whom I am best positioned to speak concretely.
Thus some of my examples in these areas will involve technical
detail. Others should feel comfortable skipping them.
2. Design project managers.  To avoid disaster, the project man-
ager must blend both theory and lessons from hands-on experi-
ence as he designs his design process, rather than just replicating