Traceability How Expectations handle traceability Agenda Structure Where
Traceability How “Expectations” handle traceability
Agenda Structure Where do we need traceability Holistic traceability Traceability is not restricted to requirements 01 03 02 04 Corporate Memory How must the data be stored How you know it works The benefit you should enjoy
01 Structure Where do we need traceability?
Why traceability was not established Root causes for lack of established traceability: The complexity of development is always higher than expected We tend to focus on functionality, not integrity We only had poor tools to handle it
How traceability is established The traceability solution builds on Data structure Corporate Memory Expectation Engineering
Data structure We need to know all information that is design input to the final solution We need to add structure to this surprisingly complex matter We must apply a classic analysis technique: Logical Data Modelling. Learn more in <link to LDM module>
Data structure - Entities Step one: Identify the entities you need to store information on! The name differs a lot, but we typically see at least these levels: • Needs, user stories, business requirements, … • Requirements, many types[functional reqm, Needs Requirements performance reqm, regulatory reqm, ……] • Solution definitions, specifications, designs, architecture • Construction/coding/…. . The physical implementation of the solution Solution definition
Data structure - Relationships Step two: Establish the relationships between the entities Needs That is the data structure that must be established to manage the traceability! Requirements If the employees skillfully uses this structure for the development activities, then traceability is established. Solution definition
02 Corporate Memory Where do we keep/store the traceability?
Corporate Memory When the structure is in place, there still need to be only one place to store the information. The concept required is a “Corporate Memory” The place where all stakeholders contribute to the development of the knowledge that eventually will become the solution The significant benefit comes from the comfort of knowing that all employees are working on the best version of corporate knowledge. This benefit is due to well established traceability Corporate Memory
03 Holistic view What disciplines are supported by the traceability?
“Expectation Engineering” & Traceability Expectation Engineering is a holistic approach. Including the classical disciplines of • Requirements Engineering • Verification & Validation • Risk Management • Configuration Management Holistic, because • It is! • Treating it like separate disciplines has proven not to work • All of the entities is needed to establish traceability • Improvements just does not provide any efficiency before all the disciplines are coordinated
04 How you know it works These are among the benefits you should expect from traceability?
What you know when you have traceability Why does this item look like it does? Who cares about it? When was it changed? • And why? • Who wanted the change? • Who approved the change? How is it tested? Which version of the item fits to which versions of the other items?
When you have traceability: Confidence ∙ You can trust the information at hand Integrity ∙ Your information “fits together” Courage ∙ You dare to change when needed ∙ You don’t forget a stakeholder
Well done You have now completed “Traceability” Learn more in these modules : <Logical Datamodelling> <Corporate Memory> <Implementing traceability> <Expectation Engineering storyline>
- Slides: 16