Home Up

Requirements

wpe1.jpg (4007 bytes)Assisting enterprises in learning, exploring, reengineering, and implementing component-based/object-oriented software solutions using best-in-class methods.

Problem Solving ] [ Requirements ] OO / Component Reading ] Architecture ] Design ] Data Modeling/Database ]                                             

 

 

Requirements Reading List

Requirements gathering is more an art than a science. The quality of requirements gathering is truly a human interaction endeavor and we all know the vagaries of that.  The recommendations below do a good job at addressing the various human aspects, cognitive aspects, and techniques to facilitate and gathering requirements.

TITLE AUTHOR PUBLISHER DATE ISBN DESCRIPTION

REQUIREMENTS

Exploring Requirements D. Gause

G. Weinberg

Dorset House 1989 0-932633-13-7 A clearly written volume on how to approach any development effort. This book on gathering requirements is required reading. It covers everything from determining the problem, teams, setting expectations, and minimizing the risk of failure. Another collaborative piece, "Are Your Lights On"- ISBN 0-932633-16-1, is also a good read. Frankly, anything written by Gerald Weinberg is worth reading. His writing spans many topics, from Systems Thinking to Consulting. Always entertaining and highly instructive.
Requirements Engineering I. Sommervile

P. Sawyer

John Wiley 1997 0-471-97444-7 Well written explanation of the various components and topics that comprise a complete requirements specification. They partitiion requirements into three levels: Basic, Intermediate, and Advanced. I found myself disagreeing at times with the authors regarding their view as to what level a particular component was. Nevertheless, it is nice to see a breakdown.

I would have liked to have seen more examples since the requirements specification deliverable is often the most difficult to develop.

Managing Software Requirements D. Leffingwell

D. Widrig

Addison Wesley 2000 0-201-61593-2 Part of AW's "Object Technology Series, this book does a good job of following the requirements gathering process from problem definition to problem solution. They also work within the scope of the Rational Unified Process (RUP). The book is clearly written and is directed at requirements analysts.
Improving Performance G. Rummler

A. Brache

Jossey-Bass 1995 0-7879-0090-7 This is an important work in documenting workflow.  Rummler and Brache provide clear diagramming models for articulating current processes with techniques that lend themselves to "aha!" revelations. These techniques work well for communicating with the business partners their workflows.

The second updated edition incorporates key learnings. The RB diagrams are also called "swimlane" diagrams. These diagrams are now popularized as "Activity" diagrams in the UML (the aspect is Portrait rather than Landscape).

           
 
Send mail to smarcus@MarcusSoftwareDesigns.com with questions or comments about this web site.
Copyright © 1998 Marcus Software Designs, Inc.
Last modified: July 14, 2006

Reading Lists ] What's The Problem ] Elements of Systems Development ] Developing Software as if Your Life ] The Customer Is Always Wrong ] Ruminations ]