A Version identifier can be made from any symbols. It is useful to indicate unique instances of a specification, also probably the sequence of changes, and perhaps even exact time of change.
Version: January 9, 2003.
Edition: 1.02 [Feb 21 03 3:54:36 pm].
Usability: 9-Jan-03. Scale: Time to <learn>. Goal: 6 hours or less.
Or (more explicitly)
Usability: Version = 9-Jan-03. Scale: Time to <learn>. Goal: 6 hours or less.
Usability: [Version = 9-Jan-03] Scale: Time to <learn>. Goal: 6 hours or less.
1. The Version should be specified at the Level of individual Elementary Requirement and Design-Specifications.
Rationale: This aids change control. It allows reviewers, to focus mainly on the changes themselves, rather than the entirety of large Documents, which contain perhaps only a few changes. It also enables us to treat individual Elementary specifications as relatively independent objects, which are electronically grouped as needed into useful views, rather than the traditional “Documents”.
This Concept entered by Sailendra.