Creative Product Design: A Practical Guide to Requirements Capture Management
| Author | : | |
| Rating | : | 4.69 (991 Votes) |
| Asin | : | 0471987204 |
| Format Type | : | paperback |
| Number of Pages | : | 236 Pages |
| Publish Date | : | 2017-04-19 |
| Language | : | English |
DESCRIPTION:
"Not what I expected" according to A Customer. While offering many ways available for requirements capture, the author leaves each chapter with no recommeded approach to pursue. The reader is left to decide how to proceed. I would prefer a more biased view on successful methods.
She has published several books and papers in design management, new product development and conducted major research programes in this field. 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 Ma
What is the problem? Typically, out of nine month's product development cycle, only two weeks are devoted to the generation of ideas and creative design - the "front end". This is the missing link - insufficient idea generation and creativity management, or the pre-development phase, can lead to the failure of the product. So, what can you do to avoid product failure? Requirements Capture is the "front end". Achieving commercial success through innovation is highly desirable, but difficult to achieve in practice. 50% of product development costs are likely to result in a failed product and in some sectors, such as FMCGs, this figure is more like 75%. Requirements cature defines: * Customer, user and market requirements * Design requirements * Technical requirements The requirements capture model constitutes three phases: * Information gathering * Information transformation * Requirements generation In this book, Margaret Bruce and Rachel Cooper present and explain requirements capture in a step-by-step, practical guide that will enable you to plan and implement the process successfully within your organisation. It is the processs by which the needs, preferences and requirements of individuals and groups significant to product development are researched and identified. Wheth
From the Inside Flap Defining a process of requirements capture as the "front end" or "pre-development" of the product development process is imperative. 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. 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. Such false assumptions lead to errors in the product specification which may only be uncovered later in the process. Without the requirements capture process, false assumptions regarding customer, technical and other requirements may be made. The front end is a critical phase because once the concept has been defined, then abou