• Avaloq Services
  • Implementation
    • Methodology
      • Project Set-up
      • Analysis & Design
      • Implementation & Development
      • Testing
      • Cut-over & Stabilisation
  • Release Management
  • Process and Product Enhancement
  • Change Management
  • Project Coaching
  • Project Management
• Services for Insurance
• Training Consulting Services
• Business Consulting Services

 

Implementation > Methodology > Implementation & Development

Implementation & Development

The detailed functional scope and work plan (as defined in the Analysis & Design phase) forms the main input of this phase. During implementation, the Avaloq Banking System is parameterised using table entries, code development, migration of data from legacy systems to Avaloq, etc.

Throughout implementation, it is essential to regularly test and validate progress in order to make sure that functionalities have been implemented correctly and expectations are being met. As such, we often adopt a prototype-based approach. A prototype can be considered an implementation in its own right, covering its corresponding scope with distinct project phases including unit testing, module testing and system integration testing.

Each prototype provides a checkpoint that helps management ensure that implementation is progressing at the right pace and in the right direction. As each prototype concludes with a formal testing phase, it provides the opportunity for our clients’ key business users to 'see and touch' the product and satisfy themselves that scope and test processes are on target. It is at this moment that any discrepancies become clear – and can be addressed.
The number of appropriate prototypes adopted during the implementation phase will depend on the final project scope and how it can be split.

During the implementation phase, one of the main challenges is to hold the scope constant and not let it grow or change. As such, it is important that any changes are limited to a strict minimum and should only be introduced to realign delivery to the client’s requirements. Therefore, during this phase, we enforce a strict change control process.

The inputs to subsequent prototypes are derived from the identified scope of the initial prototype and any feedback gathered, in the form of additional or changed requirements, from the prototype before.

Towards the end of this phase, we reach the final scope and code freeze. During the Testing phase, only changes to the code will be triggered by defects raised during test cycles.

 

Related Topics

Products -SecurEasy™

Case Studies -Avaloq Services Case Studies