for testing you need: test data and test cases test plans and controls

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. 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. 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. installing a system project initiation analysis design programming testing installation prepare hardware, network convert and load data train users and support staff complete the documentation

5. site 1 site 2 site 3 old system new system subsystem 1 subsystem 2 subsystem 3 implementation options direct parallel pilot/ location phased day one 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 new business old business

6. comparing implementation options direct parallel pilot phased day-one (ratings will vary with system and business) 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 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

7. training • management • users • IT support staff: • operations and technical support • hotline / help desk • manuals (reference) • training materials • online help

8. hardware or software vendors application package vendors professional trainers universities, colleges, professional associations in-house: trainers, information centre training • 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

9. data loading for testing for implementation • 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 new system (static and transaction) tables and files

10. manual operation hard copy document data entry automated process online storage data loading

11. post-implementation review (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?

12. maintenance process emergency repair process

13. maintenance and support activities • 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

14. responsibilitiesand options • 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

15. well managed maintenance • 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