Philico’s analysis and design methodology starts by identifying business needs and business processes. Knowing the way users work and understanding their key needs is essential to parameterize correctly the final solution and met the expectations. Once the target objectives are set, the effort estimations and the required tasks are formally defined and documented.
- As is and to be analysis of the business processes and its IT applications
- Software evaluation, Avaloq modules and third party applications
- Effort estimations
- Project setup organisation
- Requirement gathering
- Requirement analysis
After having defined the scope and specific requirements, the implementation phase start. Philico’s expert will adapt and parameterize the Avaloq Banking System according to the A&D documentation. When performing the implementation, user’s feedbacks as well as validating the progression are our key factors to guarantee that deliverables will meet requirements. Therefore key users are involved at the very beginning of the implementation and along the whole project phase.
- Deep technical and functional Avaloq Banking System know-how
- Modules parameterization
- Interfaces parameterization
- Data migration support
- Stream leading
- Change request management
- Progress tracking
Before starting the testing phase, final user acceptance criteria will be agreed and specified. These criteria will guarantee that the implementation fulfilled the requirements, the solution being in accordance with the specification. At Philico, the testing phase is seen as an ongoing process, which starts already during the implementation, when modules tests and functionalities tests are completed assuring the quality of the development. The process goes ahead with the integration test where all modules are tested simultaneously assuring that no side affects arise. Finally, user acceptance tests are performed to assure all the functionalities are in line with business requirements.
- Test strategy definition
- Acceptance criteria definition
- Test case definition
- Modules test implementation
- Code review according to best practices
- Integration tests
- User acceptation test
- Bugs & Issues prioritisation, categorisation and review
At Philico, we believe that the know-how is the force which drives every organizations. Therefore, when new processes and news functionalities are implemented in the organisation, it is essential to allow the people to acquire the know-how as fast as possible. Philico’s expert will help you to define and implement the appropriate coaching strategy based and organizational and business needs.
- Coaching strategy definition
- Develop coaching plan
- Implement coaching method
- Develop coaching material
- Organize Avaloq modules coaching lessons
- Assess coaching results
The final phase before going live with the new core banking system is called the cutover. This phase involves the complex coordination of many people and many individual tasks to ensure a smoothly transition between both systems. This phase should be planned and prepared well in advance to reduce any unforeseen events. Therefore Philico will help you to plan your cutover and to organise cutover rehearsals and simulations with actual timing.
- Cutover rehearsal & simulation strategy and planning
- Cutover plan definition
- Contingency and fallback planning
- Resources planning
- Communication planning
- Post production release plan
Following a success full go-live, post-production support is the final phase of an ABS implementation and is as important as any other phases. This phase is intended to manage the daily system operations and ensure the system is doing exactly what it needs to. This phase may also include additional development on requirements not in scope of initial delivery.
- Immediate resolution of high category issues
- Additional development
- Data correction
- Identifying and managing production support issues
- Post Implementation review