Scribd
Upload
22 views8 pages

14 Traceability

Uploaded by

comodidev-store
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
22 views8 pages

14 Traceability

Uploaded by

comodidev-store
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 8

Prof.

Philip Koopman
Traceability

There is never enough time to do it right the first time


… but there is always enough time to do it over.
© 2020 Philip Koopman 1
Traceability
 Anti-Patterns:
 Tests don’t map to requirements
 Requirements aren’t tested
 Reqts/design elements missing
 Gold plating (extra functionality)

 Traceability
 Creating something traces to a quality check on the result
– Verification: you did something the way you said you’d do it
– Validation: the thing you created behaves the way it should
 Ensure nothing left out; nothing added that shouldn’t be there
© 2020 Philip Koopman 2
YOU ARE HERE
SPECIFY TRACEABILITY & VALIDATION ACCEPTANCE
PRODUCT
PRODUCT Test Plan & Test Results TEST
Product Software Test
Requirements Results

SPECIFY SOFTWARE
SOFTWARE Test Plan & Test Results TEST

Software Requirements VALIDATION Integration Test Results

CREATE SW INTEGRATION
ARCHITECTURE Test Plan & Test Results TEST

High Level Design Unit Test Results


Test

VERIFICATION DESIGN
MODULES
Plan & UNIT
TEST
Test
Results
Detailed Design Source Code

IMPLEMENT
© 2020 Philip Koopman 3
Traceability Examples
 Design traceability
 Requirement  design  implementation
 Requirement  test

 SQA traceability
 Confirm process is being carried out
 Process step  document/artifact  quality metric

 Safety analysis traceability


 Confirm all hazards successfully mitigated
 Hazard  requirement  mitigation  validation

 Defect traceability
 Ensure that all bugs are fixed
 Bug report  defect identified  fix task  code check-in  regression test

© 2020 Philip Koopman 4


https://goo.gl/yuFYby © 2020 Philip Koopman 5
Traceability for
Hazard Mitigation

Mader et al. 2013:


http://doi.ieeecomputersociety.org/10.1109/MS.2013.60

© 2020 Philip Koopman 6


Traceability Best Practices
 Trace everything in design package
 Even simple traceability checks can find problems
– Gold plating: design item not traced to a requirement
 Everything in design has an ID tag for traceability
– Map left and right sides of V to each other
– Map each layer of V upward and downward
 Trace changes to see what else they affect

 Traceability pitfalls
 Making granularity of trace IDs too big causes problems
 Re-numbering breaks auto-generated document sections used as trace IDs
 Don’t use the wrong tool
– Spreadsheets don’t scale to big projects
– Big project tools might be overkill where a spreadsheet approach will do
© 2020 Philip Koopman 7
https://xkcd.com/552/
© 2020 Philip Koopman 8

You might also like