Just Enough Requirements Management: Where Software Development Meets Marketing [NOOK Book]

Overview

This is the digital version of the printed book (Copyright © 2005).

If you develop software without understanding the requirements, you're wasting your time.

On the other hand, if a project spends too much time trying to understand the ...
See more details below
Just Enough Requirements Management: Where Software Development Meets Marketing

Available on NOOK devices and apps  
  • NOOK Devices
  • Samsung Galaxy Tab 4 NOOK
  • NOOK HD/HD+ Tablet
  • NOOK
  • NOOK Color
  • NOOK Tablet
  • Tablet/Phone
  • NOOK for Windows 8 Tablet
  • NOOK for iOS
  • NOOK for Android
  • NOOK Kids for iPad
  • PC/Mac
  • NOOK for Windows 8
  • NOOK for PC
  • NOOK for Mac

Want a NOOK? Explore Now

NOOK Book (eBook)
$11.49
BN.com price
(Save 42%)$19.99 List Price

Overview

This is the digital version of the printed book (Copyright © 2005).

If you develop software without understanding the requirements, you're wasting your time.

On the other hand, if a project spends too much time trying to understand the requirements, it will end up late and/or over-budget. And products that are created by such projects can be just as unsuccessful as those that fail to meet the basic requirements.

Instead, every company must make a reasonable trade-off between what's required and what time and resources are available.

Finding the right balance for your project may depend on many factors, including the corporate culture, the time-to-market pressure, and the criticality of the application. That is why requirements management—gathering requirements, identifying the "right" ones to satisfy, and documenting them—is essential.

Just Enough Requirements Management shows you how to discover, prune, and document requirements when you are subjected to tight schedule constraints. You'll apply just enough process to minimize risks while still achieving desired outcomes. You'll determine how many requirements are just enough to satisfy your customers while still meeting your goals for schedule, budget, and resources.

If your project has insufficient resources to satisfy all the requirements of your customers, you must read Just Enough Requirements Management.
Read More Show Less

Product Details

  • ISBN-13: 9780133491319
  • Publisher: Pearson Education
  • Publication date: 8/1/2013
  • Series: Dorset House eBooks
  • Sold by: Barnes & Noble
  • Format: eBook
  • Edition number: 1
  • Pages: 144
  • File size: 13 MB
  • Note: This product may take a few minutes to download.

Meet the Author

ALAN M. DAVIS is Professor of Business Strategy and Entrepreneurship at the University of Colorado at Colorado Springs and president of Offtoa, Inc. He was a member of the board of directors of Requisite, Inc., acquired by Rational Software Corporation in February, 1997, and subsequently acquired by IBM in 2003. He has consulted for many corporations during the past 27 years, including Boeing, Cigna Insurance, Federal Express, General Electric, IBM, Mitsubishi Electric, and many more. Editor-in-Chief of IEEE Software from 1994 to 1998, he has published numerous books and more than 100 articles in journals, conference proceedings, and trade press, and has lectured 2,000-plus times in 28 countries.
Read More Show Less

Table of Contents

&>

Preface

Chapter One: Introduction 3

Requirements 3

Requirements Management 6

Just Enough 8

The Context of Requirements 10

The Relationship Between Schedule and Requirements 18

The Components of Requirements Management 23

The Importance of Requirements Management 36


Chapter Two: Requirements Elicitation 40

Definitions and Terminology 40

Why Do Elicitation? 45

Elicitation Techniques 45

The Result of Elicitation 59

The Secrets of Just Enough Elicitation 61


Chapter Three: Requirements Triage 63

Definitions and Terminology 63

Why Do Triage? 67

Basic Triage Techniques 68

Advanced Triage Techniques 97

The Result of Triage 115

The Secrets of Just Enough Triage 116


Chapter Four: Requirements Specification 119

Definitions and Terminology 119

Classic Requirements Documentation Styles 122

The Content of a Requirements Document 125

The Role of a Requirements Document 127

Qualities of a Requirements Document 128

Specification Techniques 136

The Result of Specification 156

The Secrets of Just Enough Specification 161


Chapter Five: Requirements Change 163

Where Do Changes Come From? 164

How to Keep Track of Requested Changes 165

Choices for Handling the Changes 165

The CCB Meeting 170

The Secrets of Just Enough Change 171

Chapter Six: Summary 172

Requirements Elicitation 173

Requirements Triage 174

Requirements Specification 175

Requirements Change Management 176


Appendix A: Quick Recipes 177

Brainstorm 178

Decide What Is or Isn't a Requirement 183

Decide What to Build 185

Produce a Requirements Document 188

Assess the Quality of a Requirements Document 190

Baseline the Requirements 192

Ensure That Everybody Knows the Requirements 192

Handle New Requirements After Baselining 194

Handle Multiple Customers 196


Appendix B: A Set of Documented Requirements 200


References and Additional Readings 209

Index 227

About the Author 239


Read More Show Less

Customer Reviews

Be the first to write a review
( 0 )
Rating Distribution

5 Star

(0)

4 Star

(0)

3 Star

(0)

2 Star

(0)

1 Star

(0)

Your Rating:

Your Name: Create a Pen Name or

Barnes & Noble.com Review Rules

Our reader reviews allow you to share your comments on titles you liked, or didn't, with others. By submitting an online review, you are representing to Barnes & Noble.com that all information contained in your review is original and accurate in all respects, and that the submission of such content by you and the posting of such content by Barnes & Noble.com does not and will not violate the rights of any third party. Please follow the rules below to help ensure that your review can be posted.

Reviews by Our Customers Under the Age of 13

We highly value and respect everyone's opinion concerning the titles we offer. However, we cannot allow persons under the age of 13 to have accounts at BN.com or to post customer reviews. Please see our Terms of Use for more details.

What to exclude from your review:

Please do not write about reviews, commentary, or information posted on the product page. If you see any errors in the information on the product page, please send us an email.

Reviews should not contain any of the following:

  • - HTML tags, profanity, obscenities, vulgarities, or comments that defame anyone
  • - Time-sensitive information such as tour dates, signings, lectures, etc.
  • - Single-word reviews. Other people will read your review to discover why you liked or didn't like the title. Be descriptive.
  • - Comments focusing on the author or that may ruin the ending for others
  • - Phone numbers, addresses, URLs
  • - Pricing and availability information or alternative ordering information
  • - Advertisements or commercial solicitation

Reminder:

  • - By submitting a review, you grant to Barnes & Noble.com and its sublicensees the royalty-free, perpetual, irrevocable right and license to use the review in accordance with the Barnes & Noble.com Terms of Use.
  • - Barnes & Noble.com reserves the right not to post any review -- particularly those that do not follow the terms and conditions of these Rules. Barnes & Noble.com also reserves the right to remove any review at any time without notice.
  • - See Terms of Use for other conditions and disclaimers.
Search for Products You'd Like to Recommend

Recommend other products that relate to your review. Just search for them below and share!

Create a Pen Name

Your Pen Name is your unique identity on BN.com. It will appear on the reviews you write and other website activities. Your Pen Name cannot be edited, changed or deleted once submitted.

 
Your Pen Name can be any combination of alphanumeric characters (plus - and _), and must be at least two characters long.

Continue Anonymously

    If you find inappropriate content, please report it to Barnes & Noble
    Why is this product inappropriate?
    Comments (optional)