How to define traceability requirements and establish stucture for traceability in software projects? Some ideas.

1. Traceability – ways to
ensure better
management and
consistency
Karolina Zmitrowicz

3. There was a Change Request raised...

5. Is there any hope?

6. How to foresee the
impact of change?
How to deal with
complexity?

7. Traceability as a solution

8. Artifacts

9. Relationships

10. Back to IT
c Manage Inventory Requirement Traces
Inventory Manager
responsibilities
Provides services forthe
management of Titles.
REQ019 - Manage InventoryREQ032 - Update Inventory
Manage Titles
«realize» «realize»
«trace»
custom Fulfill Orders Use Case x Test Case Detail
(from Fulfill Orders)
List Current Orders
(from Fulfill Orders)
Package Order
«testcase»
Open Orders
test scripts
System: : (Not Run) Customer has no current orders
System: : (Deferred) Customer has one order all items are in stock
System: : (Pass) Customer has two orders all items are in stock
System: : (Fail) Customer has two orders one order all items are in stock the other only one of t...
«validates»«validates»
class Class Model
Projekt
+ ID: int {id}
+ nazwa: char
+ opis: long
+ prefix: char
Wersja
Srodowisko
Komponent
Enterprise Architect v13, sample project

11. Traceability – application

12. Do you know where to look for information?
Do you know the structure of deliverables?
Do you know the source of information?
Information structure
clarity
Coverage analysis
Impact analysis

14. Traceability – how to?

15. Information architecture
Business
goals
Stakeholders
Business
processes
Business
requirements
System
requirements
Data
UI mockups
InterfacesTest cases
Risks
BusinesscontextDeisgn

16. Coverage analysis
Are your business goals covered by project
deliverables?
Are your business requirements covered by system
requirements?
Are your requirements covered by test cases?

17. Coverage analysis
lfillOrders Use Case x TestCase
(from Fulfill Orders)
ListCurrentOrders
Open Orders
(from Fulfill Orders)
Package Order
«validates»
«validates»
http://www.softwaretestingmagazine.com/knowledge/choosing-a-test-case-management-solution-for-jira/

18. Change impact analysis
Enterprise Architect v13, sample project

19. Summary
Managing complexity requires traceability
Building the right approach to manage traceability:
• Understand what information you need in your
project
• Understand relationships between artifacts
• Create proper structure of information
• Select options for managing traceability
• Maintain traceability – on continuous basis

20. Thank you!
Polish Testing Board
Stowarzyszenie Jakości Systemów Informatycznych
www.sjsi.org
Karolina Zmitrowicz k.zmitrowicz@sjsi.org