Implementation_Process

Implementation Process Odessa follows an industry-leading implementation process for the deployment of Lease Wave. The complexity and scope of each installation determines how elaborate this process would be. For large implementations, the process can be broken down into five basic phases: (1) Needs Analysis Documentation, (2) Low Level Design, (3) Configuration / Development, (4) User Acceptance Testing and (5) Deployment. Each of these phases consists of clearly demarcated sub-phases that give accountability, control and structure to progress. The main objective of the process is an implementation that is tailored specifically to each customer while remaining extremely predictable in terms of time and cost. Implementations range from 3-18 months, based on scope and complexity. Not all implementations require all phases listed. Need analysis documentation * Comprehensive analysis of business processes and requirements * Business Process Analysis: documents all processes by roles and users * Gap Analysis: determines gaps between requirements and system functionality * Requirements: specifies exact requirements implementation needs to deliver * Software-industry standard documentation * Customer signs off on every set of documents * Full assistance given for review and understanding of documents Low level design * Functional Specifications * Business requirements are translated into specific system-requirements * Design Specifications * Database, screen and other system changes are documented * Design documentation complements functional documentation * Test Planning * Test and use cases that will be used during testing are determined * Test artifacts available for client review * Full assistance is given for review and understanding of documents * “Non-technical persons” can review and understand documentation * Customer signs off on every set of documents Configuration/Development * Complete Low Level Design documents are used to carry out requirements * Requirements are carried out through configuration or through development * Lease workflow management is configured in system to automate processes * Phased delivery of completed modules allows for progressive testing * Customer sign-off of successful completion is required to end the phase User acceptance testing * User Acceptance Testing (UAT) documentation provided with delivery of software * Key test cases are put together to comprehensively test the system * The customer is provided with testing documents * Systematic testing carried out to accept the system * Unit testing is carried out on individual modules in isolation * Integration testing is carried out on concentrically larger groups of modules * System-wide integration is also carried out following completion of delivery * Automated testing tools are provided for regression tests and tests with repeated actions * Testing is only considered complete when tested with actual migrated data * An Odessa test team assists customer’s Subject Matter Experts and designated testers * All lease workflow management process flows are tested for each activity carried out * Customer sign-off is required for acceptance of system