What do you think?
Rate this book
Addison-Wesley Object Technology Series
Managing Software Requirements: A Use Case Approach
"Many projects fail because developers fail to build the right thing. Developers of any kind of application should read this book." Grady Booch
"A comprehensive solution to the requirements challenges faced by every development team. Full of insight and ideas all developers can learn from." Ivar Jacobson
Despite the wealth of development knowledge, experience, and tools available today, a substantial percentage of software projects fail, often because requirements are not correctly determined and defined at the outset, or are not managed correctly as the project unfolds. This second edition of the popular text Managing Software Requirements focuses on this critical cause of failure and offers a practical, proven approach to building systems that meet customers' needs on time and within budget.
Using an accessible style, their own war stories, and a comprehensive case study, the authors show how analysts and developers can effectively identify requirements by applying a variety of techniques, centered on the power of use cases. The book illustrates proven techniques for determining, implementing, and validating requirements. It describes six vital Team Skills for managing requirements throughout the lifecycle of a project: Analyzing the Problem, Understanding User Needs, Defining the System, Managing Scope, Refining the System Definition, and Building the Right System. Managing Software Requirements, Second Edition, specifically addresses the ongoing challenge of managing change and describes a process for assuring that project scope is successfully defined and agreed upon by all stakeholders.
Topics covered include:
"A comprehensive solution to the requirements challenges faced by every development team. Full of insight and ideas all developers can learn from." Ivar Jacobson
Despite the wealth of development knowledge, experience, and tools available today, a substantial percentage of software projects fail, often because requirements are not correctly determined and defined at the outset, or are not managed correctly as the project unfolds. This second edition of the popular text Managing Software Requirements focuses on this critical cause of failure and offers a practical, proven approach to building systems that meet customers' needs on time and within budget.
Using an accessible style, their own war stories, and a comprehensive case study, the authors show how analysts and developers can effectively identify requirements by applying a variety of techniques, centered on the power of use cases. The book illustrates proven techniques for determining, implementing, and validating requirements. It describes six vital Team Skills for managing requirements throughout the lifecycle of a project: Analyzing the Problem, Understanding User Needs, Defining the System, Managing Scope, Refining the System Definition, and Building the Right System. Managing Software Requirements, Second Edition, specifically addresses the ongoing challenge of managing change and describes a process for assuring that project scope is successfully defined and agreed upon by all stakeholders.
Topics covered include:
The five steps in problem analysis
Business modeling and system engineering
Techniques for eliciting requirements from customers and stakeholders
Establishing and managing project scope
Applying and refining use cases
Product management
Transitioning from requirements to design and implementation
Transitioning from use cases to test cases
Agile requirements methods
800 pages, Hardcover
First published January 1, 1999
14 people are currently reading
330 people want to read
Ratings & Reviews
Friends & Following
Create a free account to discover what your friends think of this book!
Community Reviews
Displaying 1 - 7 of 7 reviews
May 14, 2017
This is THE book on managing requirements in Unified Process.This is certainly not the book of choice about how to manage requirements as a business analyst, for instance. However, this text presents a very broad range of tools and practices in this field. It's even probably the most comprehensive one that I know. Of course each topic can't be handled in depth, but each one is pretty well presented and it's abious that the author master his subject very well.
It would be not my book of choice on requirements management, but it's a very good introduction to each and every practice. The reading is relevant even outside the context of Unified Process.
It would be not my book of choice on requirements management, but it's a very good introduction to each and every practice. The reading is relevant even outside the context of Unified Process.
February 12, 2020
Biraz eski kafa, güncel grupların tercih etmesine gerek yok.
This entire review has been hidden because of spoilers.
December 17, 2014
Chapters Read: 1,3,4,5,6,7,10,11,12,13,14,22,23,27,29
Lefingwell describes requirements analysis and specification in great detail in this book. He tackles the process of understanding the problem, stakeholders, and coming up with a solution in a step by step guide (more or less), while addressing some of the common issues of eliciting and specifying requirements.
The author did tackle the issue of choosing the correct requirement methodology, and he did address the agile method. However, I do not believe that they were given justice. The book spends most of its chapters explaining the steps to produce an SRS document but this does not reflect most of the current industry standards, as most of them follow one of the agile methodologies and have left the traditional methods behind.
In the end, I would recommend this book to someone who is new to the software engineering field. But I don't think it holds a lot of information for a veteran.
Lefingwell describes requirements analysis and specification in great detail in this book. He tackles the process of understanding the problem, stakeholders, and coming up with a solution in a step by step guide (more or less), while addressing some of the common issues of eliciting and specifying requirements.
The author did tackle the issue of choosing the correct requirement methodology, and he did address the agile method. However, I do not believe that they were given justice. The book spends most of its chapters explaining the steps to produce an SRS document but this does not reflect most of the current industry standards, as most of them follow one of the agile methodologies and have left the traditional methods behind.
In the end, I would recommend this book to someone who is new to the software engineering field. But I don't think it holds a lot of information for a veteran.
August 21, 2012
The was one textbook I actually read completely in college. It was absolutely terrible. Its points were obvious. Its case study was imaginary so it wasn't really a case study. This is a poor model for a textbook.
August 7, 2007
This text was part of a graduate requirements course in software engineering
March 30, 2013
A should-read book on product management for knowledge workers and entrepreneurs.
September 12, 2013
very best for PG students
Displaying 1 - 7 of 7 reviews