Authors: Margaret Bruce, Rachel Cooper, Rachel Cooper
ISBN-13: 9780471987208, ISBN-10: 0471987204
Format: Hardcover
Publisher: Wiley, John & Sons, Incorporated
Date Published: February 2001
Edition: (Non-applicable)
Dr. Margaret Bruce is Professor of Design Management and Marketing and Head of Department of Textiles, UMIST. She has written several books and papers on design and innovation and carried out international research programmes in these fields. She has developed courses and run executive programmes in Product Development Management and Design and edits the International Journal of Product Development, Innovation and Management.
Dr. Rachel Cooper is Professor of Design Management and Associate Head of Research in the School of Art and Design at the University of Salford. She is Chair of the European Design Academy and edits the international journal, The Design Journal. She has published several books and papers in design management, new product development and conducted major research programes in this field.
Defining a process of requirements capture as the "front end" or "pre-development" of the product development process is imperative. The front end is a critical phase because once the concept has been defined, then about 80% of subsequent costs will have been committed.
Without the requirements capture process, false assumptions regarding customer, technical and other requirements may be made. Such false assumptions lead to errors in the product specification which may only be uncovered later in the process. It does not take much to imagine the impact this has on time and money.
With the current focus on achieving quick response, managers worry that more effort expended on requirements capture at the front end will increase the time of product development. However, companies with intensive front end activities spend 40% less time on product development than those that ignore this stage. In addition, companies with an effective requirements capture process gain more profits and revenue from new products than those that do not have an adequate requirements capture process.
The writing is on the wall.
Requirements capture is the process by which the needs, preferences, and requirements of individuals and groups significant to product development are researched and identified. In this text, Bruce (design management and marketing, UMIST) and Cooper (design management, U. of Salford) describe how to implement requirements capture within any organization. They contend that by devoting more attention to this pre-development phase, companies can save time during product development and avoid costly false assumptions. Annotation c. Book News, Inc., Portland, OR (booknews.com)
Acknowledgements | ix | |
Introduction | xi | |
Section 1 | Requirements Capture | 1 |
1 | New Product Development | 3 |
2 | Requirements: Ideas, Research and Strategy | 27 |
3 | Requirements: Market Research Tools and Techniques | 49 |
Section 2 | Capturing and Managing Requirements Capture in Practice | 79 |
4 | Introduction to the Case Studies | 81 |
5 | Colossus Case Study | 83 |
6 | Vantage Case Study | 105 |
7 | Bandage Case Study | 133 |
8 | Construct Case Study | 157 |
Section 3 | Guidelines to Requirements Capture | 171 |
9 | Requirements Capture Process | 173 |
10 | Integrating Requirements Capture with Product Development | 191 |
References | 201 | |
Index | 209 |