Connecting and packaging this changed information against the change controls automates the correction process. Faster testing turnaround times. Reduced compilation and linkage cycles. Improved quality over the contents of a release. Faster generation of release notes and product errata.
Migration often fails because of poor change packaging.
Testing builds fail because the correct set of changed objects cannot be created. Changes are left behind in development directories, and engineering hours are lost trying to diagnose the reason that test builds fail. This increases the impact of the compile on the machine and adds effort to each testing cycle. Much wasted time is eliminated by repository tracking and controlling these packaged changes. If the dependencies between the programming, quality assurance, and documentation are tracked and packaged, overall quality improves with each change activity.