I'm trying to establish a documentation numbering standard for my team,
and there is some initial resistance to the approach I've used for
years. I'm wondering what approach you all use, or what your opinions
are on the merits and drawbacks of these two approaches.
Approach A: Every revision of a document is given a new integer-value
version number. For instance, Site Map v6 is updated and becomes Site
Approach B: Every version of a document made during the "Define" phase
of a project is numbered 0.x. For example, Site Map v0.3 is revised;
some new pages are added, some deleted, and some changes to the site
hierarchy are made. The new version is Site Map 0.4. Some additional
changes are made, but they are very minor...a spelling correction or a
label change on some elements, but no change to scope or functionality.
The new version is Site Map v0.4.1.
Once a project is well defined, the project enters "Design" phase and a
baseline version 1.0 is published. From this point forward a detailed
revision history is kept. The same numbering guidelines apply as in the
Once the design is approved and the project enters the "Build" phase,
the design document is again baselined at version 2.0. Any revisions to
version 2.0 (or higher) should be managed through a change order.
Looking forward to your feedback.
Dante Murphy | Director of Information Architecture
Medical Broadcasting Company | A D I G I T A S INC. COMPANY