1. University of Toronto at Scarborough © Kersti Wain-Bantin CSCC40 testing and installation 1 for testing you need: test data and test cases test plans and controls types of testing: validation- does the system do the right thing? verification- is the system constructed correctly? black box- without considering the construction white box- specifically checking the construction

2. University of Toronto at Scarborough © Kersti Wain-Bantin CSCC40 testing and installation 2 levels of testing: desk checking - at programmed unit level unit testing -one component at a time integration testing - start to combine components sub-system testing - testing subsystems and interfaces system testing - test performance: volumes, timing... acceptance testing -users involved in final testing testing tools: test harnesses (for unit, top-down and bottom-up testing), file comparators, execution analyzers, code analyzers, etc.

3. University of Toronto at Scarborough © Kersti Wain-Bantin CSCC40 testing and installation 3 test plans: test id. and description test data used expected results for each test: date, time, personnel involved for each problem found: description of symptoms resolution (fix) repeated until all actual results match the expected ones sources of test data and test cases: pre- and post-conditions, use cases, state charts, etc.

4. University of Toronto at Scarborough © Kersti Wain-Bantin CSCC40 testing and installation 4 project initiation analysis design programming testing installation prepare hardware, network convert and load data train users and support staff complete the documentation installing a system

5. University of Toronto at Scarborough © Kersti Wain-Bantin CSCC40 testing and installation 5 site 1 site 2 site 3 subsystem 1 subsystem 2 subsystem 3 new business old business new system old system direct parallel pilot/ location phased day one implementation options in pilot entire system is installed at site 1, then site 2, then... in phased everyone gets subsystem 1, then subsystem 2 then... in day-one all new business is done on the new system and old business is wrapped up on the old system

6. University of Toronto at Scarborough © Kersti Wain-Bantin CSCC40 testing and installation 6 immediate benefit to user operations relatively low cost separation of old/new systems ease of planning simple fall-back options few/simple contingency plans low level of risk continued testing capability high user commitment simplicity of operation good corporate-wide reporting Y Y N Y N Y N Y Y Y Y N N N N Y Y Y N Y N Y Y N N N Y Y Y Y N Y Y N N Y N Y N Y Y N Y Y N Y N N N N direct parallel pilot phased day-one (ratings will vary with system and business) comparing implementation options

7. University of Toronto at Scarborough © Kersti Wain-Bantin CSCC40 testing and installation 7 management users IT support staff: operations and technical support hotline / help desk manuals (reference) training materials online help training

8. University of Toronto at Scarborough © Kersti Wain-Bantin CSCC40 testing and installation 8 in-house: trainers, information centre hardware or software vendors professional trainers universities, colleges, professional associations application package vendors train people in groups with tailored training programs select the most effective place to do the training provide for learning by seeing, hearing and doing prepare a training manual develop interactive tutorials and training tools rely on previous trainees wrap up with full system simulation train just in time training

9. University of Toronto at Scarborough © Kersti Wain-Bantin CSCC40 testing and installation 9 new system (static and transaction) tables and files old system data: static and transaction tables and files hard copy data from previously manual operations users’ and management business knowledge check and clean up old data test new system data architecture write conversion and data entry programs load and check new system data for testing for implementation data loading

10. University of Toronto at Scarborough © Kersti Wain-Bantin CSCC40 testing and installation 10 data loading manual operation hard copy document data entry automated process online storage

11. University of Toronto at Scarborough © Kersti Wain-Bantin CSCC40 testing and installation 11 (approx. 6 months after installation) Are originally planned benefits being achieved? Were originally estimated costs exceeded? Are functional requirements satisfied? Are non-functional requirements satisfied? Are users satisfied? What are the outstanding problems and issues? What did we learn from the project that we can use in future? Did we achieve planned reusability? What do we do next? post-implementation review

12. University of Toronto at Scarborough © Kersti Wain-Bantin CSCC40 testing and installation 12 maintenance process emergency repair process

13. University of Toronto at Scarborough © Kersti Wain-Bantin CSCC40 testing and installation 13 fix problems add or change features/functionality handle volumes/capacity maintain performance levels keep documentation up to date adapt to changes in business environment: adapt to changes in technology provide training for new users and support staff recover from disasters backup/restore system monitor system performance conduct system audits maintenance and support activities

14. University of Toronto at Scarborough © Kersti Wain-Bantin CSCC40 testing and installation 14 fix problems add or change features/functionality handle volumes/capacity maintain performance levels keep documentation up to date adapt to changes in business environment adapt to changes in technology provide training for new users and support staff recover from disasters backup/restore system monitor system performance conduct system audits users user management developers maintenance department help desk operations technical support in-house or outsourced responsibilities and options

15. University of Toronto at Scarborough © Kersti Wain-Bantin CSCC40 testing and installation 15 all calls/requests are logged system changes completed according to priorities system changes fully tested and documented status of all calls/requests known to all parties system monitored and problems anticipated well managed maintenance