D3S requires traceability of configuration for all software systems and related hardware. These include D3S software products delivered to customers, as well as installed systems on servers and other infrastructure components.
In all cases, we require the following configuration elements to be fully described:
- required configuration settings or parameters
- reasons for each setting, with reference to controlling specifications
- tools or methods use to set the required options
- dependencies and impacts on other modules or systems
- infrastructure items (e.g. OS, layer software)
- security of settings
For infrastructure components, the basic rule for configuration is to apply custom configurations and not use default settings, especially those governing access and user authentication. For software products, configuration reflects customer needs, and changes are performed on the basis of customer demands.
We manage all changes to our software applications and their supporting environments through our ticketing and issue tracking system. We typically handle these changes as new features or change requests. Each ticket has an author, specification, approval clause (if necessary) and version number. Per our release policy, all requested changes are assigned to a new software version.
When the scope of the version is final and we’ve implemented all included features, we prepare the version for the quality assurance (QA) process. If the version has an impact on documentation, the relevant documents are also updated. Each revision includes a version number, date, author and description of changes for traceability of changes.