Setup - Change Management/Version Control Strategy

There are many facets to change management within LANSA. There may be Third Party change management systems that suit your needs. See Third Party Packages in the Visual LANSA Administration Guide

Ensure that you understand all the following concepts and how they fit in with your development needs.

Impact Analysis – As objects that require change are identified, Impact Analysis can be used to assess the effect on related objects. See Impact Analysis Concepts in the Visual LANSA Administration Guide

Tasks – Tasks are created per the Task Tracking approach chosen. See Task Tracking Concepts in the Visual LANSA Administration Guide

Object History & Movement – As work is performed and objects are moved in and out of Development and Testing, a history of the changes made and an object's movements should be retained.

Synchronization – If multiple developers are working with the same group of objects, a strategy to ensure that they are working with current versions of objects, including changes, must be established. See Repository Synchronization Concepts in the Visual LANSA Administration Guide

Testing – A clear and concise procedure must be established for testing at each stage, and movement to the next phase of testing. This will include a comprehensive test plan which will change to accommodate new features and scenarios. This should include error reporting and correction.

Migration between environments – As changes are made, testing performed and work is completed, procedures to move between development, testing, acceptance and production environments are established.

Deployment – Once all work is completed and testing has been signed-off on, how will the final product be delivered? See Deployment Concepts in the Visual LANSA Administration Guide

Also See

Change Management in the Visual LANSA Administration Guide