What are the characteristics of a good requirement?

I've started compiling these requirements, but I'm not sure I'm doing it the right way. How can I tell a good requirement from one that won't be useful?

The IIBA Business Analyst Body of Knowledge lists the following characteristics of a good requirement: "cohesive, complete, consistent, correct, feasible, modifiable, unambiguous, and testable." How can you tell if a requirement you've documented is good?…

Log in or Subscribe now to read the full answer...

This resource requires a Premium Subscription

Please log in. Don't have a log-in? Sign up now. Already a Member? Log in to upgrade immediately and get the full answer! A Premium subscription is only $14.95/month or $149/year and gets you over 200 templates, guidelines, and checklists.

15-day free trial period for new Premium subscribers! Learn more

©Copyright 2000-2012 Emprend, Inc. All Rights Reserved.
About us Site Map View current sponsorship opportunities (PDF)
Contact us for more information or e-mail info@projectconnections.com
Terms of Service and Privacy Policy