Free Trial

Safari Books Online is a digital library providing on-demand subscription access to thousands of learning resources.

  • Create BookmarkCreate Bookmark
  • Create Note or TagCreate Note or Tag
  • PrintPrint
Share this Page URL
Help

Chapter 4. Learning What People Need > Feedback Using Requirements

Feedback Using Requirements

An atomic requirement is perhaps the most precise and powerful device a business analyst can use to communicate with requirers. By atomic requirement we mean the requirement must be written to build a communication bridge. Snow cards, shown in Figure 4.11, are a low-tech but highly immediate technique to record requirements. If your project is large, you will naturally use some kind of automated requirements tool. Most of our clients configure their tool to look somewhat like the original snow card. Let's demonstrate three of the attributes we record when gathering requirements. These are Description, Rationale, and Fit Criterion.

The Description is whatever the requirer says he wants or needs. Suppose your analyst is working on the requirements for a home financial management product and your requirer asks for a product “that allows him to write provisional checks.” That's the Description. We suggest you record whatever the requirer says, then consider the next part of the requirement. Rationale is a justification of the requirement. To find it, ask “Why?”


  

You are currently reading a PREVIEW of this book.

                                                                                                                    

Get instant access to over $1 million worth of books and videos.

  

Start a Free Trial


  
  • Safari Books Online
  • Create BookmarkCreate Bookmark
  • Create Note or TagCreate Note or Tag
  • PrintPrint