IT Performance Improvement
Networking and Telecommunications
Enter E-mail Address:
Powered by VerticalResponse
Gathering and documenting requirements can be difficult. Knowing how to create a structure that
enhances comprehension and makes it easier to divide and conquer the analysis phase can be useful and is actually
critical for success on large and complex undertakings. There are many approaches to categorizing requirements and this chapter from Determining
Project Requirements explores some of the more common ones. It reviews the International Institute
of Business Analysis (IIBA) approach to classification and other, equally good approaches. It is not the intent in
this chapter to promote one specific classification system; my view is that different projects and
different business situations need different classification approaches, and I also explain the reasoning for this.
Sometimes starting to capture and document requirements seems like a daunting task. It is hard to know where to begin, what level of detail to get into, and it is almost impossible to know when a complete set of requirements has been captured. A well-defined classification system, or taxonomy, can help with these issues. It is similar to going to an automotive dealer to buy a car. It helps to organize the discussion into categories. For buying a car those categories may be interior, exterior, and performance related. For a system it will be different categories, but the purpose is the same: to enhance communication.
Read entire chapter
© Copyright 2008-2010 Auerbach Publications