What do you think?
Rate this book
Addison-Wesley Object Technology Series
Managing Software Requirements: A Use Case Approach
Description This Second Edition ofthe popular text Managing Software Requirements focuses on this critical cause of failure and offers apractical, proven approach to building systems that meet customers'needs on time and within budget. Using an approachable style, their own war stories and acomprehensive case study, the authors show how students caneffectively identify requirements by applying a variety oftechniques, centered on the power of use cases. The bookillustrates proven techniques for determining, implementing, andvalidating requirements. For Sale in Indiansubcontinent only New content, new theme, new subtitle! The use case approach is a cornerstone technique, and a more prescriptive approach is employed. Proven "team skills" exercises help the reader roll the requirements process out to the rest of the team. The Requirements Problem. Introduction to Requirements Management. Requirements and the Software Lifecycle. The Software Team. The Five Steps in Problem Analysis. Business Modeling. Systems Engineering of Software-Intensive Systems. The Challenge of Requirements Elicitation. The Features of a Product or System. Interviewing. Requirements Workshops. Brainstorming and Idea Reduction. Storyboarding. A Use Case Primer. Organizing Requirements Information. The Vision Document. Product Management. Establishing Project Scope. Managing Your Customer. Software Requirements-A More Rigorous Look. Refining the Use Cases. Developing the Supplementary Specification. On Ambiguity and Specificity. Technical Methods for Specifying Requirements. From Use Cases to Implementation. From Use Cases to Test Cases. Tracing Requirements. Managing Change. Assessing Requirements Quality in Iterative Development. Agile Requirements Methods.
540 pages, Paperback
First published January 1, 1999
14 people are currently reading
331 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