BAConf - Requirement Traceability - Julen Mohanty


Published on

BAConf - Requirement Traceability - Julen Mohanty

  • Be the first to comment

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

BAConf - Requirement Traceability - Julen Mohanty

  1. 1. Business Analyst Conference<br />Saturday, July 17, 2010<br />Julen C Mohanty<br />Citigroup Technology Services<br />Requirement Traceability<br />
  2. 2. Table of Content<br /><ul><li> What is Traceability Matrix
  3. 3. Components of Requirement
  4. 4. How to Trace
  5. 5. Traceability Matrix Example
  6. 6. Why is it Required
  7. 7. The Myth</li></ul>2<br />BA Conference<br />7/17/2010<br />
  8. 8. What is Traceability Matrix<br />3<br />BA Conference<br />7/17/2010<br />A Traceability Matrix is a document, usually in the form of a table, that correlates any two baselined documents that require a many to many relationship to determine the completeness of the relationship. - WIKI<br />I would say: Traceability Matrix is a document, where we would like to be able to trace back and forth how and where any work product fulfills the directions of the preceding (source) product.<br />Contd..<br />
  9. 9. 4<br />BA Conference<br />7/17/2010<br />What is Traceability Matrix<br />User Rqmt<br />Functional Rqmt<br />Business Rqmt<br />Test Rqmt<br />Contextual links between the various Requirements<br />&<br />Relationship between Work Products developed <br />CODE<br />Test Plan<br />TDD<br />BRD<br />FRD<br />Test Cases<br />Effective Implementation and Verification of Requirements<br />
  10. 10. Components of Software Requirements<br />5<br />BA Conference<br />7/17/2010<br />Business Requirements<br />Vision & Scope Document<br />User Requirements<br />Quality Attributes<br />Nonfunctional Requirements<br />Use Case Document<br />Constraints<br />Functional Requirements<br />System Requirements<br />Software Requirement Specification<br />
  11. 11. How to Trace<br />6<br />BA Conference<br />7/17/2010<br /><ul><li> Has at least one to one relationship
  12. 12. Makes relationship between requirements & within requirements
  13. 13. Document the functions next to each of the Requirements they are related to
  14. 14. Same way Tech Design next to each functions and that’s how till implementation
  15. 15. Customer can give inputs when things are ambiguous. </li></li></ul><li>Traceability Matrix - Example<br />7<br />BA Conference<br />7/17/2010<br />Level 1<br />
  16. 16. 8<br />BA Conference<br />7/17/2010<br />Traceability Matrix - Example<br />Level 2<br />
  17. 17. 9<br />BA Conference<br />7/17/2010<br />Traceability Matrix - Example<br />Level 3 – Working <br />Attached Template for use, by Audience<br />
  18. 18. Why to use Traceability Matrix<br />10<br />BA Conference<br />7/17/2010<br /><ul><li> Has relationship back & forth from Requirement to Implementation
  19. 19. Makes relationship between requirements & within requirements
  20. 20. Traces back a function to it’s requirements, or technical design to it’s function, or even a code to it’s technical design/ function / requirement
  21. 21. Can check whether any requirement has at least one design solution and by checking the solution(s) you may see whether the requirement is sufficiently solved by this (or the set of) connected design(s)
  22. 22. If you have to change any requirement, you can see which designs are affected. And if you change any design, you can check which requirements may be affected and see what the impact is.
  23. 23. Identify those areas with a higher number of defects and analyze the root causes</li></ul>Contd..<br />
  24. 24. 11<br />BA Conference<br />7/17/2010<br />Why to use Traceability Matrix<br /><ul><li>In a Design-Code Traceability Matrix you can do the same to keep track of how and which code solves a particular design and how changes in design or code affect each other. </li></ul> Take e.g. the Requirement of UserFriendliness (UF). <br /><ul><li>If a design solution does not solve any requirement, it should be deleted, as it is of no value
  25. 25. It shows has the system been adequately tested
  26. 26. It helps to minimize scope creep
  27. 27. Customer requirements through development and testing verifies that the customer requirements are implemented and tested
  28. 28. Most important : It says things that can be reused
  29. 29. It’s a Six Sigma project management matrix table</li></li></ul><li>Previous Stage v/s Current Stage<br />12<br />BA Conference<br />7/17/2010<br />Previous Stage<br /><ul><li> Traceability is just to check required Capabilities
  30. 30. Check system Capabilities
  31. 31. Mere Exercise in Thoroughness & Completeness in project
  32. 32. To show the delivered features & functionalities
  33. 33. Sometime as just Customer asks </li></ul>Current Stage<br /><ul><li> Advent of Requirement Management tools it has helped support project management
  34. 34. Helps in Impact Analysis
  35. 35. Takes care of change management
  36. 36. Easy to handle Defect management
  37. 37. Process improvement substantially
  38. 38. Effective team communication
  39. 39. Better Project Control
  40. 40. Assured quality</li></li></ul><li>Summary<br />13<br />BA Conference<br />7/17/2010<br />Traceability is “the ability to follow the life of a requirement, in both forwards and backwards direction, i.e., from its origins, through its development and specification, to its subsequent deployment and use, and go through periods of ongoing refinement and iteration in any of these phases”.<br />
  41. 41. The Myth<br />14<br />BA Conference<br />7/17/2010<br />Do your duty to the best of your ability, result will automatically follow. <br />You may be doing your duty to the best of your ability, but without proper direction it maybe of no use. Use traceability Matrix…<br />
  42. 42. Thank You<br /><br /><br />Julen C Mohanty<br /><br />15<br />BA Conference<br />7/17/2010<br />