Rating: 
Summary: Fails to explain the GAP between Biz Objectives & Outcomes
Review: Software requirements begin with business objectives, definition, requirements, and expectations. Business community always looks at the bigger picture, on the other hand, systems or business analyst merely focus on specific information, result is the actual requirements get lost between the translations and the software projects fail or are delayed and exceed their budget. This book eloquently spells out six skills crucial for defining comprehensive software requirements, like analyzing the problem, understanding user needs, defining the system, managing scope, refining system definition and system validation. If you have difficulties in defining and maintaining the system requirements, this book could significantly improve the focus. However, this book fails to explain the gap between business objectives and outcome. However, linking this book to preliminary step of software development would overcome initial snag, ensuring the system design and implementation likely to be successful. By Vivek Dixit, Stanford.edu
Rating:
Summary: Possibly the best book on requirements management
Review: The authors for his book have incredible software engineering experience in life critical systems to include medical devices, and real time embedded systems. They successfully built a software company based primarily on their formal implementation of requirements management, which were refined over many years and grew to incorporate modern aspects of software engineering as the subtitle "A Unified Approach" suggests. I don't believe you can find better authors who can write from their experiences of tried and true, proven techniques on requirements management. This book does not read like a dry textbook. Rather its illustrations and style keep the reader interested and informed of best practices through out the book. This hard cover book should be a source of constant reference, if you need to understand the best requirements elicitation techniques such as: JAD sessions, requirements management workshops, storyboarding techniques, prototyping, etc... The recent copyright (2000) and the fact that this book is part of Addison Wesley's Object Technology Series is just icing on the cake.
Rating: 
Summary: The Definitive Book on Software Requirements
Review: This book is an excellent reference on exactly what is needed in the software requirements process. Not only does it clearly define, step by step procedures on eliciting and managing requirements, it also provides examples, templates, discussion on scope creep, verification, and other relevant areas. The authors have made this somewhat "fuzzy" process incredibly easy to follow by breaking the book down into short, easy to read chapters. They also weave throughout the book their (sometimes amusing) past experiences. Indeed, the appendices apply their approach to other methods including RUP, CMM, ISO, etc. Great book - highly effective!
Rating:
Summary: Outstanding
Review: This book is must-reading for project managers. The writing is crisp, and the chapters short -- each topic is nailed tight. I can see myself re-reading parts of this book in years to come as a refresher on core concepts. There is a case-study woven into the text to illustrate various techniques. About the only improvement I could recommend to the book would be that the case-study be more fully developed (with detailed requirements, diagrams, models, etc), perhaps in an appendix.
Rating:
Summary: Basics
Review: This is a good book to read and have in the bookself. It gets you started and even if you have knowledge of requirements management, you should see it what's inside. However I do software that is very complex (telecommunications) and for this kind of environment this book just isn't enough. I would have hoped for more compact text with fewer pictures and more concrete real world examples. This book resembles too much children's books. Well anyway, as I said this book is anyway a must read, but you have to read more. I found many good ideas and could broaden my understanding by reading "Customer Centered Products" by Ivy F. Hooks and Kristin A. Farry.
Rating:
Summary: Basics
Review: This is a good book to read and have in the bookself. It gets you started and even if you have knowledge of requirements management, you should see it what's inside. However I do software that is very complex (telecommunications) and for this kind of environment this book just isn't enough. I would have hoped for more compact text with fewer pictures and more concrete real world examples. This book resembles too much children's books. Well anyway, as I said this book is anyway a must read, but you have to read more. I found many good ideas and could broaden my understanding by reading "Customer Centered Products" by Ivy F. Hooks and Kristin A. Farry.
Rating:
Summary: Requirements 101
Review: This is a well structured and in-depth look at requirements management - however, I felt that the authors could have easily compressed the salient points into about half the space. I am sure any interested readers will find many little jems in this book - but remember, first and foremost, it is a CLASSROOM TEXT BOOK. So get your skimming skills ready or else be prepared for a good dose of academia.
Rating:
Summary: Excellent, informative guide to requirements gathering
Review: This is an excellent book for building a strong foundation in requirements gathering. The authors have clearly been doing requirements gathering for years and are kind of enough to share volumes of their hard fought wisdom with the rest of us. I found parts of the book, especially the beginning, a little slow to get to the point. However you can just skim any parts that might be a little drawn out and there is more than enough outstanding content to make it very worthwhile. This book provides wonderful insight, persuasive arguments, multiple views and ideas for how requirements are best gathered, a clear style of explaining concepts, and a pleasant and entertaining writing style. Requirements gathering is such a large topic that the book could not possibly teach EVERYTHING you might ever need to know about requirements gathering, but it gives an outstanding basis from which you can continue to build in whichever directions are most appropriate for you. A very expereienced requirements gatherer might find the book somewhat introductory but would certainly still gain wonderful insights from parts of the book. I think both beginners and experts will benefit from this book.
Rating:
Summary: Excellent, informative guide to requirements gathering
Review: This is an excellent book for building a strong foundation in requirements gathering. The authors have clearly been doing requirements gathering for years and are kind of enough to share volumes of their hard fought wisdom with the rest of us. I found parts of the book, especially the beginning, a little slow to get to the point. However you can just skim any parts that might be a little drawn out and there is more than enough outstanding content to make it very worthwhile. This book provides wonderful insight, persuasive arguments, multiple views and ideas for how requirements are best gathered, a clear style of explaining concepts, and a pleasant and entertaining writing style. Requirements gathering is such a large topic that the book could not possibly teach EVERYTHING you might ever need to know about requirements gathering, but it gives an outstanding basis from which you can continue to build in whichever directions are most appropriate for you. A very expereienced requirements gatherer might find the book somewhat introductory but would certainly still gain wonderful insights from parts of the book. I think both beginners and experts will benefit from this book.
Rating:
Summary: A must for anyone in software development
Review: This is the most inspiring book I have read for years! I recommend it to *anyone* involved in software development or even those who are about to make an investment in software for own use. Stakeholders at all levels, even the guardians of the company's money bag, the users, developers, project managers etc. should all read - and then practice what the authors preach. This comprehensive book should make it easy to adopt the suggested processes.
|
