Traceability is a necessary component for complete and accurate requirements. Traceability is used in many aspects of requirements development and management. A simple definition is that “tracing requirements” means that we show relationships or links between different requirements components. Examples include:
Which data requirements are used in each process?
Which business objectives are supported by each business rule?
Which technical requirements are derived from each business requirement?
This is one area where a requirements development or management tool can be very useful. But even with a tool, tracing requirements can be complex and time consuming. An effective BA plans for the types of relationships that are going to be documented and maintained before getting started with requirements elicitation. It is easiest to “trace as you go” and the only way to accomplish this is to know ahead of time what type of tracing you are planning to perform and maintain.
- Selecting a Vendor Package (COTS) - June 7, 2010
- When do you learn the business? - April 6, 2010
- Free podcast on Application Modernization - March 15, 2010
- IIBA and Business Rules Community 2010 Conference - January 11, 2010
- BAs NEED management support - December 4, 2009
- WIBADD is really Great!! - October 22, 2009
- Why status reports? - September 25, 2009
- BA Interns - July 20, 2009
- Who performs business analysis work in your organization? - June 26, 2009
- User Stories - April 14, 2009