Amazon no longer offers textbook rentals. We do!

Managing Software Requirements: A Unified Approach

by: Leffingwell, Dean; Widrig, Don

Managing Software Requirements: A Unified Approach

by: Leffingwell, Dean; Widrig, Don

ISBN 13:
9780201615937
ISBN 10:
0201615932
Format: Hardcover
Copyright: 01/01/2000
Publisher: Addison-Wesley Professional
Newer Edition

Rent

Sorry, this item is currently unavailable.

Note: Supplemental materials are not guaranteed with Rental or Used book purchases.

Extend or Purchase Your Rental at Any Time

Need to keep your rental past your due date? At any time before your due date you can extend or purchase your rental through your account.

Summary

Focuses on software requirements, a critical cause of failure, and offers a practical, proven approach to building systems that meet customers' need-on time and within budget. Addresses the on- going challenge of managing change and describes a process for assuring that project scope is successfully defined. DLC: Computer software--Development--Management.

Foreword

Preface

xxi

Introduction

(1)

Team Skill 1 Introduction

(30)

The Requirements Problem

(10)

The Goal

(1)

A Look at the Data

(1)

Root Causes of Project Success and Failure

(8)

The Frequency of Requirements Errors

(1)

The High Cost of Requirements Errors

(3)

Conclusion

(2)

Introduction to Requirements Management

(8)

Definitions

(2)

What Is Requirements Management?

(1)

Application of Requirements Management Techniques

(1)

Systems Applications

(1)

The Road Map

(3)

The Problem Domain

(1)

Stakeholder Needs

(1)

Moving Toward the Solution Domain

(1)

Features of the System

(1)

Software Requirements

(1)

An Introduction to Use Cases

(1)

Summary

(2)

The Software Team

(8)

Software Development as a Team Activity

(2)

Requisite Team Skills for Effective Requirements Management

(1)

Team Members Have Different Skills

(1)

The Organization of Software Teams

(1)

The Case Study

(2)

Background for the Case Study

(1)

The HOLIS Software Development Team

(1)

Summary

(3)

Team Skill 2 Analyzing the Problem

(48)

The Five Steps in Problem Analysis

(16)

Gain Agreement on the Problem Definition

(1)

The Problem Statement

(1)

Understand the Root Causes---The Problem Behind the Problem

(3)

Addressing the Root Cause

(1)

Identify the Stakeholders and the Users

(2)

Define the Solution System Boundary

(3)

Identify the Constraints to Be Imposed on the Solution

(2)

Summary

(1)

Looking Ahead

(3)

Business Modeling

(8)

Purpose of Business Modeling

(1)

Using Software Engineering Techniques for Business Modeling

(4)

Choosing the Right Technique

(1)

The Unified Modeling Language (UML)

(1)

Business Modeling Using UML Concepts

(2)

From the Business Models to the Systems Model

(1)

When to Use Business Modeling

(1)

Summary

(1)

Looking Ahead

(1)

Systems Engineering of Software-Intensive Systems

(22)

What Is Systems Engineering?

(3)

Pragmatic Principles of Systems Engineering

(1)

The Composition and Decomposition of Complex Systems

(2)

Requirements Allocation in Systems Engineering

(7)

On Derived Requirements

(1)

A Quiet Revolution

(1)

When Generations Collide: Graybeard Meets Young Whippersnapper

(2)

Avoiding the Stovepipe System Problem

(1)

When Subsystems Are Subcontracts

(1)

Making It Work Out Right

(2)

The Case Study

(11)

Preliminary User Needs

(1)

Problem Analysis

(2)

HOLIS: The System, Actors, and Stakeholders

(2)

HOLIS Systems Engineering

(1)

The Subsystems of HOLIS

(6)

Team Skill 3 Understanding User Needs

(76)

The Challenge of Requirements Elicitation

(6)

Barriers to Elicitation

(2)

The ``Undiscovered Ruins'' Syndrome

(1)

The ``User and the Developer'' Syndrome

(1)

Techniques for Requirements Elicitation

(3)

The Features of a Product or System

(6)

Stakeholder and User Needs

(1)

Features

(5)

Managing Complexity by Picking the Level of Abstraction

(1)

Attributes of Product Features

(2)

Interviewing

(10)

The Interview Context

(1)

Value-Added Context

(1)

The Moment of Truth: The Interview

(4)

Compiling the Need Data

(2)

The Analyst's Summary: 10 + 10 + 10 ≠ 30

(1)

The Case Study

100

(1)

A Note on Questionnaires

101

(2)

Requirements Workshops

103

(10)

Preparing for the Workshop

104

(2)

Selling the Concept

104

(1)

Ensuring the Participation of the Right Stakeholders

105

(1)

Logistics

105

(1)

``Warm-Up Materials''

105

(1)

Role of the Facilitator

106

(2)

Setting the Agenda

108

(1)

Running the Workshop

109

(4)

Brainstorming and Idea Reduction

109

(1)

Production and Follow-Up

109

(4)

Brainstorming and Idea Reduction

113

(12)

Live Brainstorming

114

(2)

Idea Reduction

116

(4)

Pruning

116

(1)

Grouping Ideas

117

(1)

Feature Definition

117

(1)

Prioritization

118

(2)

Web-Based Brainstorming

120

(1)

The Case Study: The HOLIS 2000 Requirements Workshop

120

(5)

Attendees

121

(1)

The Workshop

122

(1)

The Session

122

(1)

Analysis of Results

122

(3)

Storyboarding

125

(10)

Types of Storyboards

126

(1)

What Storyboards Do

127

(1)

Tools and Techniques for Storyboarding

128

(1)

Tips for Storyboarding

129

(1)

Summary

130

(5)

Applying Use Cases

135

(6)

Building the Use-Case Model

136

(2)

Applying Use Cases to Requirements Elicitation

138

(1)

Case Study: The Use Cases for HOLIS

139

(1)

Summary

140

(1)

Role Playing

141

(6)

How to Role Play

142

(1)

Techniques Similar to Role Playing

143

(2)

Scripted Walkthroughs

143

(1)

CRC (Class-Responsibility-Collaboration) Cards

144

(1)

Summary

145

(2)

Prototyping

147

(8)

Types of Prototypes

147

(2)

Requirements Prototypes

149

(1)

What to Prototype

150

(1)

Building the Prototype

150

(1)

Evaluating the Results

151

(1)

Summary

151

(4)

Team Skill 4 Defining the System

155

(32)

Organizing Requirements Information

159

(10)

Organizing Requirements of Complex Hardware and Software Systems

161

(2)

Organizing Requirements for Product Families

163

(2)

On ``Future'' Requirements

165

(1)

Business and Marketing Requirements versus Product Requirements

165

(1)

The Case Study

166

(1)

Summary

167

(2)

The Vision Document

169

(10)

Components of the Vision Document

170

(4)

The ``Delta Vision'' Document

174

(5)

Vision Document for Release 1.0

174

(1)

Vision Document for Version 2.0

175

(2)

The Delta Vision Document in a Legacy System Environment

177

(2)

The Champion

179

(8)

The Role of the Product Champion

180

(1)

The Product Champion in a Software Product Environment

180

(3)

The Product Champion in an IS/IT Shop

183

(4)

Team Skill 5 Managing Scope

187

(38)

The Problem of Project Scope

191

(4)

Components of Project Scope

191

(3)

The Hard Question

194

(1)

Establishing Project Scope

195

(12)

Setting Priorities

197

(1)

Assessing Effort

197

(2)

Adding the Risk Element

199

(1)

Reducing Scope

200

(3)

A Reasonable First Estimate

200

(3)

The Case Study

203

(4)

Managing Your Customer

207

(6)

Engaging Customers to Manage Their Project Scope

207

(1)

Communicating the Result

208

(1)

Negotiating with the Customer

208

(1)

Managing the Baseline

209

(4)

Official Change

210

(1)

Unofficial Change

211

(2)

Scope Management and Software Development Process Models

213

(12)

The Waterfall Model

214

(1)

The Spiral Model

215

(3)

The Iterative Approach

218

(4)

Lifecycle Phases

219

(1)

Iterations

219

(1)

Workflows

220

(2)

What to Do, What to Do ...

222

(3)

Team Skill 6 Refining the System Definition

225

(86)

Software Requirements

227

(22)

Definition of Software Requirements

228

(2)

Relationship between Features and Software Requirements

230

(1)

The Requirements Dilemma: What versus How

231

(3)

Exclude Project Information

231

(1)

Exclude Design Information

232

(2)

Amazon no longer offers textbook rentals. We do!

Managing Software Requirements: A Unified Approach

Managing Software Requirements: A Unified Approach

9780201615937

0201615932

Summary

Table of Contents

Supplemental Materials

Excerpts

Write a Review

Amazon no longer offers textbook rentals. We do!

Managing Software Requirements: A Unified Approach

Managing Software Requirements: A Unified Approach

9780201615937

0201615932

Summary

Table of Contents

Supplemental Materials

Excerpts

Write a Review

Related Products