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

Gen1us2k
Gen1us2k
Most of the IT projects imply constant cooperation between the team members and customers. Although it might be often overlooked, the role and the importance of the client within the project is very crucial. Thus, it is in your interest to build a strong relationship based on trust. However, gaining trust on a single occasion is not a dealmaker &md...
0 Responses
emorphistechno
emorphistechno
Introduction In today's world, most enterprises work aggressively to achieve a higher level of business growth, which is made possible by leveraging one of the best automation technologies. One such technology is Robotic Process Automation (RPA) that plays a vital role in streamlining the customer experience in the most profitable manner.&nb...
0 Responses
Nick Stowers
Nick Stowers
Introduction   When I was introduced to scrum, the burndown chart was a tool that was highly emphasised however I feel the purpose has changed from it being a tool to predict (to a certain level) timescales for delivery to a tool that measures a team’s productivity…..in other words, the focus is on the number of points clear...
0 Responses






Copyright 2006-2020 by Modern Analyst Media LLC