Successfully reported this slideshow.

Traceability: Why Connecting the Dots is Important

3,497 views

Published on

Overview of Enterprise Traceability and Requirements Traceability and the value they bring to projects.

Published in: Business, Technology
  • In my work I use Enterprise Architect. Traceability Matrix is very important for me because it allows tracking of changes and shows the true complexity of designed functions.
    Unfortunately, mapping the requirements to use cases is a very labor-intensive in the Enterprise Architect. Therefore, I use to build Traceability Matrix in Tormigo (http://tormigo.modesto.pl). Moreover Tormigo allows automatic versioning of changes in requirements.
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here

Traceability: Why Connecting the Dots is Important

  1. 1. Traceability:Traceability: Why Connecting the Dots isWhy Connecting the Dots is ImportantImportant International Project Management DayInternational Project Management Day Friday, November 5, 2010Friday, November 5, 2010
  2. 2. Jennifer C. Colburn, CBAP, PMPJennifer C. Colburn, CBAP, PMP  Senior Business Analyst at Kindred HealthcareSenior Business Analyst at Kindred Healthcare  CBAP (Certified Business Analysis Professional) by theCBAP (Certified Business Analysis Professional) by the IIBA (International Institute of Business Analysis)IIBA (International Institute of Business Analysis)  PMP (Project Management Professional) by PMIPMP (Project Management Professional) by PMI (Project Management Institute)(Project Management Institute)  VP of Education for Louisville Chapter of the IIBAVP of Education for Louisville Chapter of the IIBA 2009-20102009-2010  Member of the IIBA’s Business Analysis CompetencyMember of the IIBA’s Business Analysis Competency Model CommitteeModel Committee  Enjoys traveling to other countries.Enjoys traveling to other countries.
  3. 3. What is Traceability?What is Traceability? Traceable –adjectiveTraceable –adjective 1. capable of being traced.1. capable of being traced. 2. attributable or ascribable (usually fol.2. attributable or ascribable (usually fol. by to): a victory traceable to goodby to): a victory traceable to good coaching.coaching. http://dictionary.reference.com/browse/traceabilityhttp://dictionary.reference.com/browse/traceability
  4. 4. Connecting the DotsConnecting the Dots http://appraisalnewsonline.typepad.com/photos/uncategorized/2007/12/19/connect_the_dots.jpghttp://appraisalnewsonline.typepad.com/photos/uncategorized/2007/12/19/connect_the_dots.jpg
  5. 5. Traceability for IT ProjectsTraceability for IT Projects  Enterprise TraceabilityEnterprise Traceability  Understanding how the project traces back toUnderstanding how the project traces back to organizational goals.organizational goals.  Requirements TraceabilityRequirements Traceability  Tracing Business, Functional, and TechnicalTracing Business, Functional, and Technical Requirements and Use Cases/Test ScriptsRequirements and Use Cases/Test Scripts
  6. 6. Enterprise AnalysisEnterprise Analysis  Understanding the “big picture”Understanding the “big picture”  DefineDefine businessbusiness goals the solution must meetgoals the solution must meet  Integrate requirements into largerIntegrate requirements into larger businessbusiness architecturearchitecture  Support initiatives and long term planningSupport initiatives and long term planning  Strategic planning, business case development,Strategic planning, business case development, CBA, feasibility studiesCBA, feasibility studies  ““Why are we doing this?”Why are we doing this?” From the Business Analysis Body of Knowledge v 2.0From the Business Analysis Body of Knowledge v 2.0
  7. 7. Zachman FrameworkZachman Framework
  8. 8. Enterprise TraceabilityEnterprise Traceability http://www.clearbrick.com/blog/2007/07/every-lproject-should-connect-dots.htmhttp://www.clearbrick.com/blog/2007/07/every-lproject-should-connect-dots.htm Make sure that the project will address a critical business need and deliver tangible results that contribute to stakeholder value.
  9. 9. Where is the “Big Picture”?Where is the “Big Picture”?  Mission StatementMission Statement  Portfolio StrategyPortfolio Strategy  Business StrategyBusiness Strategy  Strategic InitiativesStrategic Initiatives  Success FactorsSuccess Factors  Balanced ScorecardsBalanced Scorecards  Business goals of your sponsorBusiness goals of your sponsor
  10. 10. Documenting EnterpriseDocumenting Enterprise TraceabilityTraceability  SponsorSponsor  Project CharterProject Charter  Clearly stated Business ObjectivesClearly stated Business Objectives  SMART (Specific, Measurable, Achievable, Relevant, Time-SMART (Specific, Measurable, Achievable, Relevant, Time- Bound)Bound)  Cost Benefit AnalysisCost Benefit Analysis  ROIROI  Change ControlChange Control  Relationship between project components and businessRelationship between project components and business goals/objectivesgoals/objectives
  11. 11. ResourcesResources http://www.thebamm.org/architecture/index.asphttp://www.thebamm.org/architecture/index.asp
  12. 12. Requirements TraceabilityRequirements Traceability "In the requirements engineering field,"In the requirements engineering field, traceability is about understanding how high-traceability is about understanding how high- level requirements -- objectives, goals, aims,level requirements -- objectives, goals, aims, aspirations, expectations, needs -- areaspirations, expectations, needs -- are transformed into low-level requirements. It istransformed into low-level requirements. It is therefore primarily concerned with thetherefore primarily concerned with the relationships between layers of information."relationships between layers of information." Requirements Engineering (Second Edition) Hull, Jackson & Dick.Requirements Engineering (Second Edition) Hull, Jackson & Dick.
  13. 13. Requirements TraceabilityRequirements Traceability  Prevent scope creep and/or gold platingPrevent scope creep and/or gold plating  Ensure a quality productEnsure a quality product  ““Does the solution do what it is suppose to do?”Does the solution do what it is suppose to do?”  Facilitates Change ControlFacilitates Change Control  Assists in prioritization and future planningAssists in prioritization and future planning ““The ability to describe and follow the life of a requirement, in bothThe ability to describe and follow the life of a requirement, in both a forward and backward direction (i.e. from its origins, througha forward and backward direction (i.e. from its origins, through its development and specification, to its subsequent deploymentits development and specification, to its subsequent deployment and use, and through periods of ongoing refinement andand use, and through periods of ongoing refinement and iteration in any of these phases).”iteration in any of these phases).” http://www.projectperfect.com.au/info_requirements_traceability.phphttp://www.projectperfect.com.au/info_requirements_traceability.php
  14. 14. Traceability MatrixTraceability Matrix  Associates the business and functional requirementsAssociates the business and functional requirements with the use cases and test scripts that will be usedwith the use cases and test scripts that will be used to validate them.to validate them.  Ensures completeness of testing and provides theEnsures completeness of testing and provides the basis for test planning.basis for test planning.  Can be a stand-alone document or part of theCan be a stand-alone document or part of the requirements document or test plan.requirements document or test plan.  Change Control- when a business requirementChange Control- when a business requirement changes (or changes priority)- it can be identifiedchanges (or changes priority)- it can be identified and updated easily throughout all documentation.and updated easily throughout all documentation.  http://www.slideshare.net/jennifercolburnhttp://www.slideshare.net/jennifercolburn
  15. 15. Traceability Matrix Example 1Traceability Matrix Example 1 Each Business Requirement decomposed to smallest package andEach Business Requirement decomposed to smallest package and assigned a unique identifier. BR 001assigned a unique identifier. BR 001 Each Business Requirement will have one or more functionalEach Business Requirement will have one or more functional requirements. FR 001.01, FR 001.02requirements. FR 001.01, FR 001.02 The relationship of driver (i.e. requirement) to satisfier (i.e. use case or test script) can be one-to-one, one-to- many, or many-to-one. Traceability requires unique identifiers for each requirement and use case/test script.
  16. 16. Traceability Matrix Example 2Traceability Matrix Example 2 http://lh5.ggpht.com/_vdqOsYKAf0Y/Sjw5tKW4EyI/AAAAAAAAAXM/YoRVMRxsOgUhttp://lh5.ggpht.com/_vdqOsYKAf0Y/Sjw5tKW4EyI/AAAAAAAAAXM/YoRVMRxsOgU /Sample%20Traceability%20Matrix2_thumb%5B2%5D.jpg/Sample%20Traceability%20Matrix2_thumb%5B2%5D.jpg
  17. 17. Traceability to Test ScriptsTraceability to Test Scripts
  18. 18. SummarySummary  Projects that are aligned with business goalsProjects that are aligned with business goals provide value.provide value.  Enterprise Traceability proves alignment toEnterprise Traceability proves alignment to business goals.business goals.  Requirements Traceability assists inRequirements Traceability assists in qualityquality solutions that meet the business needs.solutions that meet the business needs.  Traceability allows for greater control ofTraceability allows for greater control of inevitable changes during a project.inevitable changes during a project.

×