Version Control
Last Updated on Tuesday, 13 April 2010 09:26 Written by Phil Bailey Monday, 12 April 2010 20:31
The management of the different versions of each document we produce is a key part of the BA role and must conform to the Requirements Management standards followed by the department. Each template has a section to enable you to record the details of the various versions of the document as it changes throughout its lifetime. It is important that this section is kept up-to-date at all times and that you ensure that everyone on the approval and distribution lists are provided with the latest copy each time the document is updated.
Details Captured
The following information must be captured for each version of the document:
| Field Name | Description |
|---|---|
| Revision Date | The date of the changed document is created / issued. |
| Version# | The current version number. Please see the next section for guidance |
| Summary of Changes | A summary of the changes made to the document |
| Author | Name of the person that made the change or issued the document |
| Changes Marked | A "Y" or "N" answer to confirm whether the document issued has its changes marked using standard Microsoft Word change control functionality |
Version Numbering
The numbering of documentation is sometimes set by the project or programme you are working on. However the following standards should be applied if this is not in place:
- The version number for the document should start at 0.1 and increase by 0.1 until a version is issued for formal sign off
- The first version issued for sign off must be assigned 1.0 as the version number
- If a change is made to a signed off document without it being formally reissued or signed off, the version number should increase by 0.1
- If a signed off document is reissued either for clarification or for another sign off following a change, the version number should be rounded up to the next whole number
