<< 1 >>
Rating:  Summary: This book will improve the quality of your products ! Review: As a Software Developer and Consultant, I found this book to be a clear and practical guide that will be a valuable asset to all system development professionals.I strongly recommend it to all systems professionals, and believe it is a MUST HAVE for systems analysts ! The book presents a step-by-step methodology that contrasts how things are "normally" done with how they should be done to achieve optimum results and satisfied customers. In addition to analyzing why and how traditional approaches fail, the text provides a comprehensive checklist that can be followed to avoid common mistakes and improve the quality of the most significant aspect of develop: gathering and documenting requirements ! Presented in a easy-to-read format sprinkled with wry humor, you are likely to find it a more enjoyable read than most technical texts.
Rating:  Summary: Testing Requirements is Part of Discovering Requirements Review: If you ever wanted to know if your requirements were accurate and complete, this book will help. As Robin says on p. 13, "...we're going to intermix discovery methods with techniques for testing the adequacy of requirements." Using his problem pyramid - which includes a way to measure the problem and the solution - Robin discusses several techniques to elicit and define requirements.
Robin defines 64 techniques to test requirements - throughout a project. For example, test method #17, "identify assumptions" is common sense that too few people remember. Test method #53 is "Defining acceptance criteria," a technique useful for any project if you want to know you've built what the customer wanted.
Between the problem pyramid emphasis on measurement and the various tests, the book can help you meet its promise of preventing too much requirements change throughout a project.
Rating:  Summary: Defining requirements for software gurus and the rest of us Review: This book is eminently readable for all practitioners who have to deal with the challenge of identifying and adequately defining requirements. While the focus of this book is predominantly software, the techniques utilized are equally applicable to other industries. Whether you're dealing with design, process, business or regulatory requirements, having a controlled methodology for assembling, describing, classifying, revising and prioritizing is an oft undervalued organizational asset. Goldsmith makes a significant contribution to the dialog of requirements definition.
<< 1 >>
|