Managing Artifact Life Cycles with VeroTrace
VeroTrace maintains 5 different life cycle "states":
| Incomplete | A requirement or file is under development and not yet ready to be reviewed. |
| Ready for Review | A requirement or file has completed development and is ready to be reviewed. The requirement or file cannot be changed while in this state. |
| Failed | A requirement or file has failed to meet the review criteria for the project. Any review comments are recorded within VeroTrace for the requirement or file. The requirement or file can be changed while in this state. |
| Passed | A requirement or file has successfully met the review criteria for the project. Any review comments are recorded within VeroTrace for the requirement or file. A review checklist can now be generated for this requirement or file. The requirement or file cannot be changed while in this state. In this state, the requirement or file is considered baselined. |
| Signed | A review checklist has been generated for this requirement or file and has been checked into CM. The requirement or file cannot be changed while in this state. Once in this state, the requirement or file is considered to have completed its life cycle. |
Once a file has completed its development, VeroTrace attaches a baseline identifier to the file in CM and tracks that value within its database. The baseline identifier includes the file's unique CM version number. There are baseline identifiers for each state except 'Incomplete'. While in the 'Incomplete' state, the life cycle of a requirement or file has not officially begun for VeroTrace.
A final common baseline identifier is placed on all artifacts when all their life cycles have completed. It is from this final baseline identifier that VeroTrace extracts the artifacts from CM and combines them with hyperlinked traceability for its delivery of the verification evidence.