Forums for the Business Analyst

 
  Modern Analyst Forums  Business and Sy...  Structured Anal...  The Good, Better, Best of Requirements Traceability
Previous Previous
 
Next Next
New Post 5/7/2014 6:09 PM
User is offline Meta BA
17 posts
9th Level Poster


The Good, Better, Best of Requirements Traceability 
Modified By Adrian M.  on 5/12/2014 11:09:54 PM)

 

 

 First, there are two purposes for tracing requirements. 

  1. One is allocating requirements within the scope of a projects. It would answer a questions like, "Do these solutions requirements meet all the stakeholder and business requirements?"
  2. The other is is creating relationships between things to assess impact. This may not be during a project, it may be at enterprise analysis. It answers a question like, "I want to change this aspect of the system, what are all the impacted processes, business rules, functions, etc" 

 

 

The Good: In Document Requirements Tracebility

If you working in your standard Word document you start with your high level required capabilites at the top of the document, you can either list each requirement that relates to it that exist in the sub requirements or you can list the related high level requirements within the sub-level requirements 

The Better: Excel Requirements Tracebility

One way to trace requirements, is by creating a requirements traceability matrix in excel. This would be most likely be used to determine if maybe every solution requirement is aligned to a design specification. See excel requirements traceability matrix example

The Best: Requirements Management Tool Traceability

Requirements management tools not only give you the ability to create relationships on the fly. You could trace busines requirements to solution requirements, to business rules, to business process, etc. Then some time after the fact you can create reports that are actually valuable to someone and can be used to make informed decision about your solution. See business requirements tool requirements traceability matrix example

Good luck with your future tracing and please share any other recommendations for requirements traceability management

 
Previous Previous
 
Next Next
  Modern Analyst Forums  Business and Sy...  Structured Anal...  The Good, Better, Best of Requirements Traceability

Community Blog - Latest Posts

Neetu
Neetu
As a business analyst, we capture client requirements in different documents like BRD (business requirement document), FSD (functional specification document) and SRS (software requirement specification). If we are capturing the requirements in these documents, then why the document nomenclature is different? The answer is Yes. We are capturing the...
2 Responses
Jason White
Jason White
With time, we have evolved from oiled lamps to ever-present electricity, printing every page manually to now producing thousands of copies a day and so on. But what is the one thing these distinct things have in common? Yes, technology.One such branch of technology that has crossed leaps and bounds and turned into a  working technology fr...
1 Responses
Digital Business Analysis
Digital Business Analysis
Nowadays, companies like Audi and HSBC, use IT systems in everything they do. Does that make them to be IT companies rather than banks? Most would probably agree that HSBC is a bank, just as Audi is a car manufacturer. But what about digital banks such as Chime or companies offering digital products? In digital companies, most of the employees work...
1 Responses






Latest Articles

Business Analysts Can Play a Central Role in Solving the Coronavirus Pandemic
Mar 29, 2020
1 Comments
As the pandemic continues to upend life around the world, data, big and small, takes a central role in mobilizing the right efforts to prevent a much ...
Copyright 2006-2020 by Modern Analyst Media LLC