Configuration Management and Version Control
Keep Track of Changes
This is a project critical function for any design activity. As an aircraft design evolves, keeping track of the changes and ensuring that all results are up to date can become a large problem. Current methodology in working with spreadsheets and coded solutions results in multiple copies of files being made and stored, but there is no guarantee that any one set of results is applicable to the latest version or when running an analysis there is no guarantee that the latest set of conditions and model are being used. Historically, this challenge has resulted in a lot of re-work and the resulting cost overruns associated with the same.
The integrated Configuration Management and Version Control aspect of the j2 Universal Framework means that multiple files and out of synch results are a thing of the past. As a model is saved, the j2 Universal Framework prompts the user to save as a Major, Minor or Revision version. The relevant number is then automatically incremented.
Each project can define what constitutes a Major, Minor or Revision.
The history of the project and all changes made can then be tracked. This shows what changes were made, by whom and when.
These changes are then tracked through to the analysis where the user is notified immediately when the model they are working on has been updated. It highlights the version number the analysis was performed with and what is the current version number.
The Aircraft Model used (Baseline and Delta Model) defines the aircraft under test and the Analysis Model defines the test case or manoeuvre. Both have independent version numbers.
These are combined when the resulting data sets are stored to the central database. As well as the version numbers, the user, date and time are also logged. The use of a relational database ensures that everything is linked and can be tracked throughout the project lifecycle.