In this book [beta-version], the author has collected over one-hundred descriptions of design and development processes, from architecture, industrial design, mechanical engineering, quality management, and software development. They range from short mnemonic devices, such as the 4Ds (deﬁne, design, develop, deploy), to elaborate schemes, such as Archer’s 9-phase, 229-step “systematic method for designers.” Some are synonyms for the same process; others represent differing approaches to design.
His purpose is to initiate discussion surrounding the following questions:
- How do we design? Why do we do it that way?
- How do we describe what we do? Why do we talk about it that way?
- How do we do better?
- How do we minimize risk while also maximizing creativity?
- When must we use a heavy-weight process? And when will a light-weight process sufﬁce?
- What is the place of interaction design within the larger software development process?
- What is the place of the software development process within the larger business formation processes?
- What does it mean to conceive of business formation as a design process?
If you have some ideas on the book, or if he’s missing any design theories, let him know.