Managing Software Requirements 2nd Edition

"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:

• 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

032112247XB05082003

(Computer Bookshops Limited)

Bli först med att recensera och betygsätt boken Managing Software Requirements 2nd Edition - du kan vinna 200 kr varje månad i tävlingen "Månadens recension".

Foreword. Preface to the Second Edition. Preface to the First Edition. Introduction. 1. The Requirements Problem. The Goal of Software Development.A Look at the Data.The Root Causes of Project Success and Failure.The Frequency of Requirements Errors.The High Cost of Requirements Errors.Summary.2. Introduction to Requirements Management. Definitions.What Is a Software Requirement?What Is Requirements Management?Application of Requirements Management Techniques.Types of Software Applications.Systems Applications.The Road Map.The Problem Domain.Stakeholder Needs.Moving Toward the Solution Domain.Features of the System.Software Requirements.Summary.3. Requirements and the Software Lifecycle. Traditional Software Process Models.The Waterfall Model.The Spiral Model.The Iterative Approach.Lifecycle Phases.Iterations.Disciplines.Requirements in the Iterative Model.Summary.4. The Software Team. Software Development as a Team Activity.Requisite Team Skills for Effective Requirements Management.Team Members Have Different Skills.The Organization of Software Teams.The Case Study.Background for the Case Study.The HOLIS Software Development Team.Summary.Team Skill 1 Analyzing the Problem.5. The Five Steps in Problem Analysis. Step 1: Gain Agreement on the Problem Definition.The Problem Statement.Step 2: Understand the Root Causes-The Problem Behind the Problem.Addressing the Root Cause 48Step 3: Identify the Stakeholders and the Users.Step 4: Define the Solution System Boundary.Step 5: Identify the Constraints to Be Imposed on the Solution.Summary.Looking Ahead.6. Business Modeling. The Purpose of Business Modeling.Using Software Engineering Techniques for Business Modeling.Choosing the Right Technique.The Unified Modeling Language.Business Modeling Using UML Concepts.From the Business Model to the Systems Model.When to Use Business Modeling.Summary.Looking Ahead.7. Systems Engineering of Software-Intensive Systems. What Is Systems Engineering?Pragmatic Principles of Systems Engineering.The Composition and Decomposition of Complex Systems.Requirements Allocation in Systems Engineering.On Derived Requirements.A Quiet Revolution.When Generations Collide: Graying Baby Boomer Meets Generation X-er.Avoiding the Stovepipe System Problem.When Subsystems Are Subcontracts.Addressing the Conundrum.The Case Study: Systems Engineering for HOLIS.Preliminary User Needs.Problem Analysis.HOLIS: The System, Actors, and Stakeholders.HOLIS Systems Engineering.The Subsystems of HOLIS.Summary.Team Skill 1 Summary.Team Skill 2 Understanding User and Stakeholder Needs.8. The Challenge of Requirements Elicitation. Barriers to Elicitation.The Yes, But Syndrome.The Undiscovered Ruins Syndrome.The User and the Developer Syndrome.Summary.9. The Features of a Product or System. Stakeholder and User Needs.Features.Managing Complexity by Picking the Level of Abstraction.Attributes of Product Features.Summary.10. Interviewing. Context-Free Questions.Solutions-Context Questions.The Moment of Truth: The Interview.Compiling the Needs Data.The Analyst's Summary: 10 + 10 + 10 pi 30.The Case Study.A Note on Questionnaires.Summary.11. Requirements Workshops. Accelerating the Decision Process.Preparing for the Workshop.Selling the Concept.Ensuring the Participation of the Right Stakeholders.Attending to Logistics.Providing Warm-Up Materials.Choosing the Facilitator.Setting the Agenda.Running the Workshop.Problems and Tricks of the Trade.Brainstorming and Idea Reduction.Production and Follow-Up.Summary.12. Brainstorming and Idea Reduction. Live Brainstorming.Idea Reduction.Pruning Ideas.Grouping Ideas.Defining Features.Prioritizing Ideas.Web-Based Brainstorming.The Case Study: The HOLIS Requirements Workshop.The Attendees.The Workshop.The Session.The Analysis of Results.Summary.13. Storyboarding. Types of Storyboards.What Storyboards Do.Tools for Storyboarding.Tips for Storyboarding.Summary.Team Skill 2 Summary.Team Skill 3 Defining the System.14. A Use Case Primer. The Benefits o

(Computer Bookshops Limited)

Foreword.


Preface to the Second Edition.


Preface to the First Edition.


Introduction.


1. The Requirements Problem.

The Goal of Software Development.

A Look at the Data.

The Root Causes of Project Success and Failure.

The Frequency of Requirements Errors.

The High Cost of Requirements Errors.

Summary.

2. Introduction to Requirements Management.

Definitions.

What Is a Software Requirement?

What Is Requirements Management?

Application of Requirements Management Techniques.

Types of Software Applications.

Systems Applications.

The Road Map.

The Problem Domain.

Stakeholder Needs.

Moving Toward the Solution Domain.

Features of the System.

Software Requirements.

Summary.

3. Requirements and the Software Lifecycle.

Traditional Software Process Models.

The Waterfall Model.

The Spiral Model.

The Iterative Approach.

Lifecycle Phases.

Iterations.

Disciplines.

Requirements in the Iterative Model.

Summary.

4. The Software Team.

Software Development as a Team Activity.

Requisite Team Skills for Effective Requirements Management.

Team Members Have Different Skills.

The Organization of Software Teams.

The Case Study.

Background for the Case Study.

The HOLIS Software Development Team.

Summary.

Team Skill 1 Analyzing the Problem.

5. The Five Steps in Problem Analysis.

Step 1: Gain Agreement on the Problem Definition.

The Problem Statement.

Step 2: Understand the Root Causes-The Problem Behind the Problem.

Addressing the Root Cause 48

Step 3: Identify the Stakeholders and the Users.

Step 4: Define the Solution System Boundary.

Step 5: Identify the Constraints to Be Imposed on the Solution.

Summary.

Looking Ahead.

6. Business Modeling.

The Purpose of Business Modeling.

Using Software Engineering Techniques for Business Modeling.

Choosing the Right Technique.

The Unified Modeling Language.

Business Modeling Using UML Concepts.

From the Business Model to the Systems Model.

When to Use Business Modeling.

Summary.

Looking Ahead.

7. Systems Engineering of Software-Intensive Systems.

What Is Systems Engineering?

Pragmatic Principles of Systems Engi...

(Computer Bookshops Limited)