Specific Module Software Versioning

This is the practice of assigning and managing version numbers. It also provides the details of software version requirements for specific system modules.

Feature Overview

The specific module software version approach ensures clarity, traceability, and control over the development, deployment, and maintenance of each module, independent of the overall system version. Each module has its own version identifier which has been updated independently of other modules.

Requirements

The following are the requirements to have specific module software versioning:

  1. Versioning Policy - Adopt widely accepted versioning scheme. Standardize versioning rules: Major, Minor, and Patch releases.
  2. Version Control System - Use version control system to track changes. Tag module releases with version numbers.

Considerations

This feature has no special considerations or limitations pertaining to feature enablement or usage.

Best Practices

The following are the best practices to implement specific module software versioning:

  1. Adopt clear version policy by using customized scheme that aligns with the project requirements.
  2. Use automated tools to handle dependencies and enforce version constraints.
  3. Maintain changelogs for each module to track changes across the version.

Prerequisites

This feature has no prerequisites to feature enablement or usage.

Module-Specific Software Versioning

From the current federal release the software versioning format follows a Semantic Versioning structure. The new format is explained with an example below:

Software Versioning New Format - Graphic User Interface

Software Versioning New Format - Command Line Interface

In the above software version (7.1.1.3) format structure is as follows:

  • Major Version (7)
  • Minor Version (1)
  • Patch Version (1)
  • Customer Specific Release Number (3)