Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Tracing Data Requirements

1,586 views

Published on

Just as functional requirements are traced from business need to implementation, data requirements should be traced to eliminate redundancy and ensure coverage. The following procedure facilitates the tracing of data requirements to their source.

Published in: Technology
  • Be the first to comment

  • Be the first to like this

Tracing Data Requirements

  1. 1. Tracing Data Requirements<br />By Declan Chellar<br />
  2. 2. Assumptions<br />© Declan Chellar 2011<br />
  3. 3. Assumptions<br />Thedata requirements of any software developmentshouldbebasedontwokeyartefacts:<br /><ul><li>The Data Dictionary
  4. 4. TheLogical Data Model</li></ul>Recording data requirementswithoutreference to thoseartefacts leads to data redundancy<br />Data redundancy leads to poorphysical data modelling and ultimately to poor DB performance<br />© Declan Chellar 2011<br />
  5. 5. Thedata requirements of any software developmentshouldbebasedontwokeyartefacts:<br /><ul><li>The Data Dictionary
  6. 6. TheLogical Data Model</li></ul>Recording data requirementswithoutreference to thoseartefacts leads to data redundancy<br />Data redundancy leads to poorphysical data modelling and ultimately to poor DB performance<br />© Declan Chellar 2011<br />Assumptions<br />
  7. 7. Thedata requirements of any software developmentshouldbebasedontwokeyartefacts:<br /><ul><li>The Data Dictionary
  8. 8. TheLogical Data Model</li></ul>Recording data requirementswithoutreference to thoseartefacts leads to data redundancy<br />Data redundancy leads to poorphysical data modelling and ultimately to poor DB performance<br />© Declan Chellar 2011<br />Assumptions<br />
  9. 9. Thedata requirements of any software developmentshouldbebasedontwokeyartefacts:<br /><ul><li>The Data Dictionary
  10. 10. TheLogical Data Model</li></ul>Recording data requirementswithoutreference to thoseartefacts leads to data redundancy<br />Data redundancy leads to poorphysical data modelling and ultimately to poor DB performance<br />© Declan Chellar 2011<br />Assumptions<br />
  11. 11. Thedata requirements of any software developmentshouldbebasedontwokeyartefacts:<br /><ul><li>The Data Dictionary
  12. 12. TheLogical Data Model</li></ul>Recording data requirementswithoutreference to thoseartefacts leads to data redundancy<br />Data redundancy leads to poorphysical data modelling and ultimately to poor DB performance<br />© Declan Chellar 2011<br />Assumptions<br />
  13. 13. © Declan Chellar 2011<br />Proposal<br />
  14. 14. Just as functionalrequirements are tracedfrombusinessneed to implementation, data requirementsshouldbetraced to eliminateredundancy and ensurecoverage.<br />Thefollowingprocedurefacilitatesthetracing of data requirements to theirsource.<br />© Declan Chellar 2011<br />Proposal<br />
  15. 15. Just as functionalrequirements are tracedfrombusinessneed to implementation, data requirementsshouldbetraced to eliminateredundancy and ensurecoverage.<br />Thefollowingprocedurefacilitatesthetracing of data requirements to theirsource.<br />© Declan Chellar 2011<br />Proposal<br />
  16. 16. © Declan Chellar 2011<br />Tracing Data Requirements<br />
  17. 17. © Declan Chellar 2011<br />Tracing Data Requirements<br />
  18. 18. © Declan Chellar 2011<br />Tracing Data Requirements<br />
  19. 19. © Declan Chellar 2011<br />Tracing Data Requirements<br />
  20. 20. © Declan Chellar 2011<br />Tracing Data Requirements<br />
  21. 21. © Declan Chellar 2011<br />Tracing Data Requirements<br />
  22. 22. © Declan Chellar 2011<br />Tracing Data Requirements<br />
  23. 23. © Declan Chellar 2011<br />Tracing Data Requirements<br />
  24. 24. © Declan Chellar 2011<br />Tracing Data Requirements<br />
  25. 25. © Declan Chellar 2011<br />Tracing Data Requirements<br />
  26. 26. © Declan Chellar 2011<br />Tracing Data Requirements<br />
  27. 27. © Declan Chellar 2011<br />Tracing Data Requirements<br />
  28. 28. © Declan Chellar 2011<br />Tracing Data Requirements<br />
  29. 29. © Declan Chellar 2011<br />Tracing Data Requirements<br />
  30. 30. © Declan Chellar 2011<br />Tracing Data Requirements<br />
  31. 31. © Declan Chellar 2011<br />Tracing Data Requirements<br />
  32. 32. © Declan Chellar 2011<br />Tracing Data Requirements<br />
  33. 33. © Declan Chellar 2011<br />Tracing Data Requirements<br />
  34. 34. © Declan Chellar 2011<br />Tracing Data Requirements<br />
  35. 35. © Declan Chellar 2011<br />Tracing Data Requirements<br />
  36. 36. © Declan Chellar 2011<br />Tracing Data Requirements<br />
  37. 37. © Declan Chellar 2011<br />Tracing Data Requirements<br />
  38. 38. © Declan Chellar 2011<br />Tracing Data Requirements<br />
  39. 39. © Declan Chellar 2011<br />Tracing Data Requirements<br />
  40. 40. Scenario 1<br />© Declan Chellar 2011<br />
  41. 41. Scenario 2<br />© Declan Chellar 2011<br />
  42. 42. Scenario 3<br />© Declan Chellar 2011<br />
  43. 43. Scenario 4<br />© Declan Chellar 2011<br />
  44. 44. Scenario 5<br />© Declan Chellar 2011<br />
  45. 45. Scenario 6<br />© Declan Chellar 2011<br />
  46. 46. Scenario 7<br />© Declan Chellar 2011<br />
  47. 47. Scenario 8<br />© Declan Chellar 2011<br />
  48. 48. Scenario 9<br />© Declan Chellar 2011<br />
  49. 49. Scenario 10<br />© Declan Chellar 2011<br />
  50. 50. Scenario 11<br />© Declan Chellar 2011<br />
  51. 51. Scenario 12<br />© Declan Chellar 2011<br />
  52. 52. For a free JPG of thisflow chart, pleasecontact me via my blog.<br />
  53. 53. www.chellar.com/blog<br />

×