You are here: Development Standards > OSAS Standards > Version Numbers

# Version Numbers

The product version number is made up of three parts:

- The integer stands for the design level of the OSAS product. Change it only when significant enhancements are made to the entire set of applications and when programs or data files are incompatible at the interpreter level. These changes cause major compatibility problems with previous levels of the product.
- The tenths decimal place is reserved for system-wide major enhancements. Change it when significant changes cause minor compatibility problems with previous major revisions. Data file conversion programs are provided, but program files must be compatible from 6.(n) to 6.(n+1).
- The hundredths decimal place indicates small changes to the software. Give correction cycle upgrades and minor enhancements a new version number to make sure that the upgraded product is installed and handled as a unique item. All data is compatible if only the minor revision number changes.

The version numbers given to products must be in sync with the OSAS products for two reasons:

- The Resource Manager makes some assumptions about version numbers during installation.
- The functionality of a program depends on the common routines that it uses. The version number also reflects the standards that the product carrying it contains.

Reinstallations and enhancements must be controllable. We attain some control by forcing compatible products to be in particular version number ranges. A product’s version numbers must match the version number of the standards to which it adheres.

If a product is an enhancement to an OSAS product, it must use a version number greater than or equal to the version number of the OSAS product it modifies.