» » Mastering the Requirements Process: Getting Requirements Right (3rd Edition)

eBook Mastering the Requirements Process: Getting Requirements Right (3rd Edition) epub

by Suzanne Robertson

eBook Mastering the Requirements Process: Getting Requirements Right (3rd Edition) epub
  • ISBN: 0321815742
  • Author: Suzanne Robertson
  • Genre: Techno
  • Subcategory: Programming
  • Language: English
  • Publisher: Addison-Wesley Professional; 3 edition (August 16, 2012)
  • Pages: 576 pages
  • ePUB size: 1139 kb
  • FB2 size 1341 kb
  • Formats doc azw mobi lrf


In fairness, the book should be called "Mastering the APPLICATION SOFTWARE Requirements Process," because that's really what it is about

In fairness, the book should be called "Mastering the APPLICATION SOFTWARE Requirements Process," because that's really what it is about In summary, this is a great introduction to use cases, scenarios, application software requirements, and fit criteria development, with many practical and useful examples. While I highly recommend the book for those with a need to understand these subjects, you will probably need more than just this book to master the requirements process. 6 people found this helpful.

Mastering the requirements process : getting requirements right, Suzanne Robertson, James Robertson. 3rd ed. p. cm. Includes bibliographical references and index. ISBN 978-0-321-81574-3 (hardcover : alk. paper) 1. Project management.

Mastering the Requirements Process book.

Getting the requirements right is crucial if we are to build systems that best meet our needs. We know, beyond doubt, that the right requirements produce an end result that is as innovative and beneficial as it can be, and that system development is both effective and efficient. If the purpose is to create one of the best books on requirements yet written, the authors have succeeded. Software can solve almost any problem. The trick is knowing what the problem is. With about half of all software errors originating in the requirements activity, it is clear that a better understanding of the problem is needed.

This is a brand new book at a great price. Author Suzanne Robertson. Publication Year 2012. Publisher Addison-Wesley Professional. Chapter 2: The Requirements Process 13. in which we present a process for discovering requirements and discuss how you might use it. ISBN-10: 0-321-81574-2. ISBN-13: 978-0-321-81574-3. The Requirements Process in Context 14. A Case Study 15. Project Blastoff 15.

Robertson Suzanne (EN). Many organizations appear willing to spend huge amounts on fixing and altering poorly specified software, but seem unwilling to invest a much smaller amount to get the requirements right in the first place.

In this total update of the bestselling guide, the authors show how to discover precisely what the customer wants and needs while doing the minimum requirements work according to the project's level of agility

Getting requirements right.

Are you sure you want to remove Mastering the requirements process from your list? Mastering the requirements process. Getting requirements right. by Suzanne Robertson. Published 2012 by Addison-Wesley in Upper Saddle River, NJ.

“If the purpose is to create one of the best books on requirements yet written, the authors have succeeded.”

—Capers Jones

Software can solve almost any problem. The trick is knowing what the problem is. With about half of all software errors originating in the requirements activity, it is clear that a better understanding of the problem is needed.

Getting the requirements right is crucial if we are to build systems that best meet our needs. We know, beyond doubt, that the right requirements produce an end result that is as innovative and beneficial as it can be, and that system development is both effective and efficient.

Mastering the Requirements Process: Getting Requirements Right, Third Edition, sets out an industry-proven process for gathering and verifying requirements, regardless of whether you work in a traditional or agile development environment. In this sweeping update of the bestselling guide, the authors show how to discover precisely what the customer wants and needs, in the most efficient manner possible.

Features include

The Volere requirements process for discovering requirements, for use with both traditional and iterative environments A specification template that can be used as the basis for your own requirements specifications Formality guides that help you funnel your efforts into only the requirements work needed for your particular development environment and project How to make requirements testable using fit criteria Checklists to help identify stakeholders, users, non-functional requirements, and more Methods for reusing requirements and requirements patterns

New features include

Strategy guides for different environments, including outsourcing Strategies for gathering and implementing requirements for iterative releases “Thinking above the line” to find the real problem How to move from requirements to finding the right solution The Brown Cow model for clearer viewpoints of the system Using story cards as requirements Using the Volere Knowledge Model to help record and communicate requirements Fundamental truths about requirements and system development
Comments: (7)
Tiainar
I found this book very helpful and it was easy to read, unlike some other requirements books I have reviewed. It is a good introductory book covering the following general phases:

1. Conception
2. Scoping
3. Work Investigation
4. Product Determination
5. Requirements Definition
6. and, to some degree, Construction

I very much appreciated that the authors provided insights which are application to small, medium, and large project (what they call "rabbits," "horses," and "elephants," and that three different requirements development strategies were examined:

1. External
2. Iterative
3. Sequential

I also found the "How Now, Brown Cow" model very practical (despite the name). This is a simple and effective model for differentiating the current state from the future state by following a simple four-step process, using use cases and scenarios. It helps the analyst differentiate the essence of the current state (business use cases) from the technology-dependent part of the current state, and then enables the analyst to enhance the essence and finally develop the product use cases which are then used to create requirements.

In fairness, the book should be called "Mastering the APPLICATION SOFTWARE Requirements Process," because that's really what it is about. Some of the ideas and principles are certainly applicable to hardware or embedded software development, but this book focuses heavily on the utilization of use cases and scenarios, which, as the terms imply, are based on behavior analysis typical of software applications with a lot of user interaction. In other words, if you are trying to write requirements for an air-to-air missile, this may not be the best book for you.

I also wish the authors would have written more about multi-level requirements hierarchies, e.g. system, subsystem, component, and how to compose requirements with a multi-level structure. On a related note, the relationship between requirements and design descriptions could also have used more treatment. For example, if the customer (e.g. marketing) developing the requirements has a detailed understanding of the desired user interface sequence and screen graphics, how would (if at all) one write requirements to that effect so that an external developer can understand what is desired, particularly if the graphics are complicated and critical, as in a medical application?

In summary, this is a great introduction to use cases, scenarios, application software requirements, and fit criteria development, with many practical and useful examples. While I highly recommend the book for those with a need to understand these subjects, you will probably need more than just this book to master the requirements process.
Mr.Champions
Are you in a hurry to implement a requirements-gathering process? Are you not keen on reading 500+ pages?

If you were going to read just *parts* of the Mastering the Requirements Process book, I recommend these parts, in this order:

- Chapter 1: 1-12
- Glossary: 511-516
- All end-of-chapter Summaries: 65, 85, 145, 222, 242-243, 277-278, 301, 321-322, 335, 351, 369, 391-392
- Volere template outline: 393-394
- Key elements IMO: 67, 82-84, 223-243, 240-241, 250-261, 329-333, 425-429, 449-457
- Time-permitting, all of Appendix A: 393-471
Fenius
I was thrust into the position of business analyst, with the only saving grace being given a few months to ease into it. I read several books on requirements, but while they all offered great advice on actually constructing the requirement (I am thinking Karl Wiegers) , what they missed was how you you go about discovering the software requirements in a real live situation. This book does exactly that. It provides you with a theoretical approach (the business use case to product use case to functional requirement) that can drive a methodological approach that will steer you toward discovering the actual requirements. This is the greatest value, but the details of the snow card also provide a few clever little tricks to make sure the requirement you write is sound. If you find yourself in a pinch, don't look elsewhere or be cheap, simply start here.
Nicanagy
I was initially a bit put off by the graphics in this book, which make clip art look classy. However, the writing is really, really good, and the treatment of the subject area is nothing short of amazing. Unlike other books on requirements that take the approach of a reference book and consequently read like a phone directory, Mastering the Requirements Process follows a case study from end to end, saving the reference materials for the appendixes, where they belong. Did I mention how good the writing is? The reason that most technical books are impossible to read is the poor quality of the prose and of the organization of the material. This is a happy exception to that tendency. I really like this book.
BlessСhild
Everyone has their own style when it comes to writing requirements. And I have always subscribed to the fact that there is no right or wrong way for writing them. After reading this book I have changed my mind. This is thr correct way for writing functional requirements. The author breaks things down into simple terms and best of all not only explains how the requirements should he written but also why they should be written in that manner. The Appendix has great examples that give you a practical application for everything that you learned in the book.
Kabei
The book is really general and generic. everything is common knowledge. the whole book is about being the middle man between developers and understanding what the customer wants in their product being built. Everything is repeated over and over. its very short, the font seems to be bigger on it than other textbooks I have, probably to make it seem like its more information in the book with more pages. I did not enjoy it.
Kezan
The book is fairly well written and, for the most part, easy to navigate and understand. However, there are multiple times where diagrams are presented as images, and these diagrams are the only model for important concepts. You cannot zoom into these images on the Kindle versions, and they are by default impossible to read. Do not buy the kindle version of this book if you actually want to learn something from it.
Excellent textbook on requirements process. More so that you can apply to anything not only tech acquisition. It devotes a good number of chapters on how to get a good sense of what the requirements are, how to find them, before thinking of a solution.
eBooks Related to Mastering the Requirements Process: Getting Requirements Right (3rd Edition)
Contacts | Privacy Policy | DMCA
All rights reserved.
lycee-pablo-picasso.fr © 2016-2020