In: Accounting
choose the conversion approach you would use if the company purchased a new AIS. Explain your choice, including the benefits. Discuss how you envision the testing process.
Analyze, Plan and Understand – Start at the beginning. The first step in the implementation process should begin with a thorough review of your business requirements and processes, to identify what is working well and which aspects of your business that may need improvement and refinement. These business requirements will then be mapped into your project plan, which will drive the remainder of the implementation.
Design, Develop and Build – Using the project plan produced in Step 1, your implementation team will next proceed to build your pilot system. This is used to validate those business processes and system functionality detailed in the project plan.
Train, Test and Accept – Building on the lessons learned in the pilot system and using test data migrated from your previous system, Step 3 includes teaching your staff the best practices and procedures to deliver the required functionality. Results from this testing and training period need to be reviewed and a sign-off should be secured, stating that the progress made to date is acceptable and in line with the overall goals of the implementation.
Implement and Go-Live – Working from the knowledge obtained in Steps 2 and 3, your new accounting system should now be complete. Your legacy data is migrated a final time to the new system and all of the experience and resources of the project team are on-site and ready to make the final transition to the new system.
Ongoing Support – With the successful launch of your new system, your technology partner should now continue to provide on-going support. This can be delivered through a help-desk, along with the application of any new updates. Many consulting companies cal also provide free webinars and user group sessions
TESTING PROCESS
4 STAGES OF TESTING
1. unit testing
2. integration testing
3. system testing
4. acceptance testing
unit testing
1. black box testing
2. white box testing
black box testing
* used in normal unit testing
* the tester checks if the unit meets the program specifcation requirements
White box testing
* used if the complexity is high
* time consuming
* tester checks the codes
integration testing
* user interface testing
* scenario testing
* data flow and system testing