Transcript Session 3232: Traceability and Linking with CaliberRM

Session 3232:
Traceability and Linking
with CaliberRM
Leigh Crawford
Project Leader
Dunn Solutions Group
Agenda
• Why Trace?
• CaliberRM’s role in effective requirement
tracing
• Built-in CaliberRM traceability tools
• Linking to other artifacts besides
requirements
• Putting it all together
The Importance of Tracing
• Provides a forward and backward view into a
requirement, from onset to implementation and
testing
• Eases requirements change management
• Scope creep seems to be contagious
– Tracing provides a key mechanism to demonstrate
the potential scope of any change
• The impact of one small change can cause a ripple
throughout the entire development cycle
Forward and Backward Tracing
Product Focus
Change
Client Need
Business
Requirements
Functional
Requirements
Code
Test Plans / Test
Scripts
Documentation
User Interface
Activity Diagrams /
Class Diagrams
CaliberRM and Tracing
• CaliberRM has a highly robust tracing
functionality
• Tracing is very simple
– Simply “drag and drop” to create a trace
• There are several tracing tools built-in
providing several ways to create, view, and
modify traces
• UI identifies “suspect links” that occur due
to requirement changes
CaliberRM Traceability Tools
• Traceability Diagram
– Highly visual representation of impact
of a requirement change
– Provides a branched view of the links
between requirements and all other
artifacts
– Allows user to navigate through linked
artifacts to view full affect of traces
– Can be customized to display key
fields
CaliberRM Traceability Tools
• Traceability Matrix
– Provides a highly visual view at
requirement coverage
– Can be used to perform requirement
coverage gap analyses
– Filterable and printable
– Views can be saved and reopened
What can I link to?
Caliber permits links to almost anything
Frequently used integrations are:
– Other requirements
– SCM tools
– StarTeam
– Together
– TestDirector
– Segue SilkPlan/SilkCentral
– MS Project
Other integrations can be built via the CaliberRM SDK
Linking to Other Requirements
Link to other requirements to
show:
• A parent/child relationship
• A cause/effect relationship
• Requirements that might
be suspect if the root
requirement changes.
Linking to SCM Tools
The SCM linking allows
you to link to source
files in StarTeam, Visual
SourceSafe, or PVCs.
Linking to StarTeam: Enhanced
The StarTeam Integration is
different from the SCM
integration
This integration permits you to
link to any:
– Project
– File
– Change Request
– StarTeam Requirement
– Task
– Topic
Linking to Together
• Together traceability
happens within the
Together client
• CaliberRM is
launched within the
Together UI
• Traces are setup the
same way as in
CaliberRM
Linking to TestDirector
In CaliberRM, the user
can link to any
TestDirector project.
A user can link to Test
Plan or Test Lab
The trace displays the
current status
Linking to Segue SilkCentral
CaliberRM links to
SilkCentral Test Plans or Test
Runs
The trace displays the status
and the last run date
Any link done in CaliberRM is
propagated back to
SilkCentral and vice versa
Linking to MS Project
Questions?
Thank You!
Session #3232
Traceability and Linking with CaliberRM
Please fill out the speaker evaluation
You can contact me further at …
[email protected]