Approach description | Risks and benefits |
|---|
Full HAL code transfer and testing on a test server: | Includes: full HAL code check against the latest standard code including window definitions removal of any temporary fixes that might have been applied while waiting for a fix in the standard code deployment on a test server full testing of the agreed critical acceptance tests which should include all the customisations deployment on live server
 The best option ensuring all customisations are aligned with the newest standard code and working as originally intended
Reduces risk of server or client crashes or clashes with standard functionality to minimum When done regularly no technical debt is accumulated and costs for each version change are predictable  It can be quite expensive, especially with large amounts of customisation
|
Partial HAL code transfer and testing on a test server: | Includes partial HAL code checking excluding customisations that have a low risk of conflict with standard code e.g. window and interface changes, totally custom functionality etc. deployment on a test server full testing of the agreed critical acceptance tests which should include all the customisations deployment on live server
Cheaper in terms of developer time required Minimizes risks of server or client crashes or clashes with standard functionality Standard product improvement might not be available in cases when they require interface changes that are effectively overwritten with your customisation Over time technical debt is accumulated and with each time next full HAL code transfer can become more expensive
|
No HAL code transfer and testing on a test server: | Includes no HAL code checking is performed assuming there will be no clashes with the standard code deployment on a test server partial testing of the agreed critical acceptance tests which should include all the customisations deployment on live server
Cheaper in terms of consulting hours required Standard product improvements might not be available in cases when they require interface changes that are effectively overwritten with your customisation High risk of unexpected clashes between the customised and standard code that can cause server crashes and even data corruptions that can cost many downtime and consulting hours after go live
|
No HAL code transfer and testing on a live server: | Includes Fast and cheap Requires longer downtime of the live system which can be an issue if downtimes during business hours are expensive for the business Standard product improvements might not be available in cases when they require interface changes that are effectively overwritten with your customisation Very high risk of unexpected issues of any sort and thus unpredictable and high consulting and downtime costs to find and solve them after go-live
|
