Phase 4 System Implementation

1. Phase 4System Implementation Chapter 10 – Application development Chapter 11 – Installation and Evaluation

2. CHAPTER 10 Application Development (Software Engineering)

3. Application Development • Process of creating the programs needed to satisfy IS processing requirements

4. Quality Assurance • Objective: • Avoid problems • Detect them as soon as possible • Use Software Engineering to manage and improve quality • ISO certified

5. Application Development

6. Application Development • Review Program documentation • from design phase • Design Program • structure charts, program flowcharts, pseudocode

8. Structure Charts • Module: rectangle • Data Couple: arrow with empty circle • Control Couple: arrow with filled circle • Condition: line with a diamond

14. Application Development • Code Program • Write the program instructions (source code) • Distinction between source, object and executable code

15. Object Oriented App Development • Easier and faster than structured because work is already done in Analysis phase.

16. Application Development • Test Program • syntax errors, clean compile, desk checking • structured walkthrough , code review • unit test, logic errors, execution errors • test data • debugging • test plan

17. Application Development • Complete Documentation • Written material that explains what the IS does and how people interact with the system

18. Testing, Testing, Testing • Logic errors / syntax errors • Unit test • Desk checking • Structured walkthrough • Test data • Link test • test two or more programs together that depend on one another • System test • Stress test

19. Testing, Testing, Testing • System test • test of entire IS using live data supplied by end user • attempt to process all situations • end user part of system test

20. DOCUMENTATION • Program documentation • System documentation • Operations documentation • program run sheet • End User documentation • initial learning and ongoing use • user manual, tutorial, on-line help

21. Application Development • Management approval!!!

22. CHAPTER 11 SYSTEMS IMPLEMENTATION AND EVALUATION

23. Systems implementation and evaluation • All software and hardware for new IS is complete and available • First step is to prepare production environment and transfer programs and procedures

24. Operational and Test Environments • Operational ---Production • Test environment • Separate environments MUST be maintained and strictly controlled

26. Training Plan • Training of end users takes place in systems implementation and evaluation phase • Planning for training begins during development phase • Everyone who will interact with IS must understand their role in operation of IS

27. Training Plan • Identify who needs training • Identify specific training needs for each group • Identify who will perform the training • in-house (IS staff or end user) • Vendors • Outside training resources

28. Training Plan • Train people in groups • Develop separate training programs for distinct employee groups • Consider most effective place • Provide for learning by hearing, seeing, and doing • Prepare training manual or tutorial • Rely on previous trainees

30. Data Conversion • Activities necessary to transfer operations from old information system to new system • All existing system data is loaded into new IS files or databases

31. Data Conversion • Automate old manual system, must enter all data • Update old automated system, transfer old system files • Do not relax system controls in order to speed up conversion

32. System Changeover • Process of putting new IS into production and retiring old system • can be either rapid or slow process • 4 typical changeover methods

33. CHANGEOVER METHODS • DIRECT CUTOVER • PARALLEL OPERATION • PILOT OPERATION • PHASED CHANGEOVER

35. DIRECT CUTOVER • Change from old system to new system occurs overnight • least expensive • risk is high (no going back!!!) • must consider timing carefully

36. PARALLEL OPERATION • Both old and new IS are in full operation for some time • Data generated and collected during parallel period input to both systems • extra code is required

37. PARALLEL OPERATION • Advantages -- minimize risk • Disadvantages -- cost • both systems are in operation at same time • end users support both systems • extra programs required • May not work for all projects

38. PILOT OPERATION • First implement new IS for a small part of company • pilot site • direct cutover at that pilot site • smaller group to deal will any problems • WHO

39. PILOT OPERATION • Less expensive than parallel • More expensive than direct • More risk than direct • Less risk than parallel

40. PHASED CHANGEOVER • Implement new IS in pieces (modules) • Purchasing first, followed by warehousing …… • Can narrow down any problems introduced overnight to smaller section of modules

41. PHASED CHANGEOVER • Less expensive than parallel • More expensive than direct • More risk than direct • Less risk than parallel

43. Post Implementation Tasks • Once new system is operational: • Prepare post implementation evaluation • Deliver a final report to management

44. POST IMPLEMENTATION EVALUATION • Quality of IS and developmental effort assessed • Verifies that new IS meets specified requirements • evaluation of end product as well as process (within time, budget …) • WHO • WHEN

45. Evaluation • Accuracy, completeness and timeliness • User satisfaction • System reliability and maintainability • Adequacy of system controls • Hardware efficiency • Effectiveness of Database • Performance of the IT team • Completeness and quality of documentation • Quality and effectiveness of training • Accuracy of cost-benefit estimates and development schedule

47. FINAL REPORT TO MANAGEMENT • REQUIRED!!! • Signals end of systems development work

48. FINAL REPORT TO MANAGEMENT • Final version of all system documentation • Planned modifications and enhancements • Recap of systems development costs and schedules • Results of post-implementation evaluation

49. Ready to move on to… System Operation and Support