doctrace - traceability matrix tool

1

Robinson Associates ©2008 www.robinsons.co.uk

Robinson AssociatesDocTrace Tool

An Overview Presentation of a Requirements Traceability Tool

Stuart Doyle2008

2


Robinsons Associates

• Established in 1976 … 15 staff• An experienced Software Systems

professional team Business and process analysts System and product designers Skilled builders and testers Trainers and sustainers Project managers

• Specialists in dependable systems and tools• Matching software to business needs• ISO 9001 (TickIT), BS EN50128

3


What is Requirements Traceability?

• Requirements tracing is the process of ensuring that system requirements are met in the design, source & test documents as part of system verification

• The Traceability Matrix is a cross reference table that traces each system requirement to its associated design, source code and test documents

• In effect it provides a statement of completeness of a system against its documented requirements

4


DocTrace Design Goals

• To provide an automated means of producing a Traceability Matrix from project documentation and source code

• To provide a means of easily extending a projects documentation with trace markers

• To support trace markers within multiple document types – Word, Visio, Text, Excel ..

• To produce a Traceability Matrix that provides forwards / backward traceability to requirements, and a concise representation of completeness

• To make traceability a real project benefit rather than a burden!

5


DocTrace Process

System Requirements

(with traceability markers)

Test Documents

Design Documents

DocTrace Tool

SourceCode Modules

Design Documents

(referencing markers)

Test Documents

(referencing markers)

SourceCode Modules(referencing markers)

Excel based Traceability

Matrix

6


Requirements Markers

• Traceability markers are placed after each requirement including Field 1 – Unique identifier Field 2 – How requirement shall be verified (test or inspection) Field 3 – Issue of document in which requirement was

introduced Field 4 – Earliest system version the requirement applies to

• The markers can be hidden if necessary

7


Sample Design Markers

• Trace markers in design and test documents reference back to system requirements Field 1 – The unique reference no. (e.g. 001) assigned to

the document containing the requirement Field 2 - The unique identifier (e.g. #12.0010) of the

requirement the design covers

8


Sample Design & Code Markers

• Trace markers similarly placed in Test documents and Code modules

9


DocTrace Operation

• The project requirements, design, source code and test documents are identified to DocTrace and also saved to a project configuration file

• The Traceability Matrix is produced in Excel format when Start is pressed

10


Resulting Traceability Matrix

• Example showing traceability across requirements, design & code

• Colour (yellow) is used to identify missing coverage • Summary line gives overall % coverage achieved• Key identifies document filename, issue and date stamp

11


Thanks for your time

• If would like to find out more about DocTrace please contact

Stuart DoyleRobinson AssociatesWeavers HouseFriday StreetPainswickStroud GL6 6QJTel: 01452 813699 Fax: 01452 812 912Email us on [email protected]

doctrace - traceability matrix tool

Technology