Managing Baselined Artifacts with VeroTrace

 

Each filename of an artifact (design, code, tests, results, analyses, and their reviews) is known to VeroTrace along with the traceability relationships between them. However within VeroTrace, the location within your Configuration Management (CM) system of each artifact and their corresponding review checklists is also known. This is what VeroTrace refers to as the CM Location or CML.
A collection of artifacts can exist within one CML, e.g. all source code review checklists can be stored in the CML [Project]/Reviews/Code. Or, the artifacts of a certain type can exist in multiple CMLs, e.g. the source code files can be stored in [Project]/Source/API, [Project]/Source/AFDX, [Project]/Source/TCPIP, et al.
From these CMLs, VeroTrace can extract a specific artifact for review or VeroTrace can check-in a review checklist that it has generated for you after an online review.
VeroTrace also uses attributes of the CM system to keep track of the life cycle of each artifact by recording and maintaining its unique CM version number.
Click here to learn more about how VeroTrace manages artifact life cycles>>

Back to the VeroTrace main page

Copyright © 2000-2012 Verocel, Inc.