Baseline Management

When a project team receives the SDE from Aras, a baseline is established, which acts as the starting point for all future changes to the software. The execution of the setup script (BuildAndDeploy.ps1) installs an initial database and sets up all required files in the code tree directory.

The established baseline then becomes the foundation over which changes are layered each time the setup scripts are run.

As these changes accumulate over time, they may grow significantly larger. Therefore, generally, when the solution enters production, a fresh baseline incorporating all customizations can be set. This new baseline will then be the starting point for the setup scripts.

After Aras has provided an initial baseline, the project team can make modifications as needed. This may include:

  • Add new application to the platform: Adding applications to a platform involves enhancing the functionality and broadening the capabilities of the system. An example of integrating an application into Aras Innovator is demonstrated in the section Appendix III: Adding Applications to a Project. 

  • Add Language packs: Adding language packs to software is a crucial step in making applications accessible and user-friendly to a diverse global audience.

  • Establish new baselines: A new baseline provides a snapshot of the project's status, including what has been achieved and the resources expended to reach this point. Once established, this new baseline serves as the starting point for subsequent phases or steps in the project. See section 7.2 Generate New Baseline for more details. 

  • Deploy build to SIT (for QA): SIT involves testing the system as a whole in an environment that closely mirrors production to ensure that all integrated components work together as expected. This includes making sure new applications function correctly with the existing system and that language packs work as intended. See section 7.1 Deploy to System Integration Testing (SIT) Environment for more details.

When an SDE from Aras is received, and a baseline is established, it isn't a final process. It is instead an ongoing effort, and modifications to the software are carried out over time as the project requirements evolve. These modifications might include integrating new applications, adding new features, fixing bugs, and improving system performance among other things.

However, this process should be handled appropriately. Changes to the software must align with the project's goals, and they should not introduce new issues or conflicts. Therefore, comprehensive testing should be performed after each modification to verify that the changes are working as expected.

Reducing build time is another important aspect of this process. When modifications are organized and managed properly, the time required to build the software can be significantly reduced. This efficiency can lead to quicker deployments and an overall shorter time to market, which can be a significant advantage for the project.

Finally, it is essential that all these activities be carried out as part of a deployment policy. A deployment policy outlines the standards and procedures for making changes to the software, testing those changes, and deploying the software to the production environment. This policy helps ensure that all changes are carried out in a controlled and consistent manner, which can contribute to the overall quality and success of the project.