[encreate] [encreate]
[encreate]
[encreate] [encreate] [encreate] [encreate] [encreate] [encreate] [encreate] [encreate] [encreate] [encreate] [encreate] [encreate]
[encreate] [encreate]
[encreate] [encreate]

Gap analysis is the end of selection process and the start of implementation process. We assess the gap between what a client requires and what the new system has to offer. Gap Analysis can be both functional and technical. During the Gap analysis phase, all the features and capabilities of the solution are studied in detail. Then a comparison is made with detailed client needs documented in BRD (Business Requirement Document). The vendor and the client agrees on the customizations required as per the analysis document. This helps the client as well as vendor to understand mutual strengths and limitations and makes the outcome of the system implementation more predictable

System Implementation: Introduce a new system into real business situation without adequate testing can be a recipe for disaster. Whether it is a new system implementation or a replacement for legacy system, the new software needs adequate testing before it can become functional. Pilots, User Acceptance Tests (UATs), Stress Tests, Integration Tests & User Training are all part of a well crafted change management exercise.

User Acceptance Testing begins with identifying test scenarios and test cases specific to the module or function. This is followed by planning test data and deploying it, Form testing, Business Process testing and Report Testing. The failures are documented and provided to the system vendor for rectification. In large systems testing exercise is conducted at module levels as well as at the system level.

 

 
[encreate]