1. 14-1 © Prentice Hall, 2004 Chapter 14: OOSAD Implementation and Operation Object-Oriented Systems Analysis and Design Joey F. George, Dinesh Batra, Joseph S. Valacich, Jeffrey A. Hoffer

2. Chapter 14 14-2 © Prentice Hall, 2004 Chapter Objectives Af ter studying this chapter you should be able to: – Describe the process of coding, testing, and converting an organizational information system. – Apply four installation strategies: direct, parallel, single-location, and phased.

3. Chapter 14 14-3 © Prentice Hall, 2004 Chapter Objectives (Continued) Af ter studying this chapter you should be able to: – List the deliverables for documenting the system and providing user training and support. – Compare various training modes. – Discuss the issues of providing support to end users.

4. Chapter 14 14-4 © Prentice Hall, 2004 Chapter Objectives (Continued) Af ter studying this chapter you should be able to: – Explain why systems implementation sometimes fails. – Explain and contrast four types of maintenance. – Describe factors that influence system maintenance costs.

5. Chapter 14 14-5 © Prentice Hall, 2004

6. Chapter 14 14-6 © Prentice Hall, 2004

7. Chapter 14 14-7 © Prentice Hall, 2004

8. Chapter 14 14-8 © Prentice Hall, 2004 What Is Coding? Translation of physical design specifications into working computer code Coding involves use of programming languages such as Java or Visual Basic eXtreme programming – an intensive coding and testing approach involving two-person teams and customer involvement

9. Chapter 14 14-9 © Prentice Hall, 2004 Reuse The use of previously written software resources, especially objects and components, in new applications Results in great savings of system development time Object-oriented systems are very conducive to reuse.

10. Chapter 14 14-10 © Prentice Hall, 2004 Approaches to Reuse Ad hoc – individual, unplanned use Facilitated – use informally managed and disseminated by expert guru evangelists Managed – organizationally enforced reuse policies and practices Designed – reusable components developed and maintained in-house Cost and commitment low high

11. Chapter 14 14-11 © Prentice Hall, 2004 What Is Software Application Testing? Manual and automated procedures for validating correctness of program code, including syntactical and execution issues Testing Syntax – grammatical rules applied to programming languages Testing Execution – logic and performance of the software during operation

12. Chapter 14 14-12 © Prentice Hall, 2004 Tests can be manual or automated, and may or may not involve code execution.

13. Chapter 14 14-13 © Prentice Hall, 2004 Tests Without Program Execution Inspections (manual) – Participants examine program code for predictable, language-specific errors Syntax checking (automated) – Compiler or interpreter tests source code for grammatical errors while translating to executable format

14. Chapter 14 14-14 © Prentice Hall, 2004 Manual Tests With Program Execution Desk checking – trace through the logic of the code, identifying possible logical errors Walkthroughs – Like desk-checking, but in a group-oriented, more structured process

15. Chapter 14 14-15 © Prentice Hall, 2004 Code walkthrough is one of many types of structured walkthroughs.

16. Chapter 14 14-16 © Prentice Hall, 2004 Automated Tests With Program Execution Unit tests – a module tested in isolation for internal consistency Integration tests – testing all modules and components of the application together for interaction compatibilities System tests – testing all programs and applications together to ensure performance and reliability Acceptance tests – user-satisfaction tests

17. Chapter 14 14-17 © Prentice Hall, 2004 A test case is a specific scenario of transactions, queries, or navigation paths that represent a typical, abnormal, or critical use of the system. Allows repeated testing with each application change

18. Chapter 14 14-18 © Prentice Hall, 2004 What Is Installation? The organizational process of turning over from the old information system to the new one Types: – Direct – Parallel – Single location – Phased

19. Chapter 14 14-19 © Prentice Hall, 2004 Direct – Cold turkey, low cost, greater impact of errors

20. Chapter 14 14-20 © Prentice Hall, 2004 Parallel – old and new coexist, minimize error impact, high cost in system resources

21. Chapter 14 14-21 © Prentice Hall, 2004 Single Location – Pilot approach, allows learning and minimizes error impact, lower resource demand than parallel, difficult to coordinate and maintain

22. Chapter 14 14-22 © Prentice Hall, 2004 Phased – Staged and incremental, supports phased system development, minimize error impact, difficult to coordinate old components and new components

23. Chapter 14 14-23 © Prentice Hall, 2004 Types of Documentation System – detailed information about a system’s design specifications, its inner workings, and its functionality User – written or other visual information about an application system, how it works, and how to use it.

24. Chapter 14 14-24 © Prentice Hall, 2004 Types of System Documentation Internal – comments in source code, generated during the coding process or automatically by software compilers or documenters External – outcomes of all structured diagrams, including use cases, design classes, activity and sequence diagrams, etc.

25. Chapter 14 14-25 © Prentice Hall, 2004 User documentation is often in the form of online help, sometimes with Web connections for further information.

26. Chapter 14 14-26 © Prentice Hall, 2004 What Is Training and Support? Providing on-going educational and problem-solving assistance to information systems users Training and support material and jobs must be designed along with the associated information systems

27. Chapter 14 14-27 © Prentice Hall, 2004 Training methods can be interpersonal, manual, or automated.

28. Chapter 14 14-28 © Prentice Hall, 2004 Electronic Performance Support Systems (EPSS), like Microsoft Office Assistant, are components of software applications that embed training and information for the user, in the form of tutorials, expert systems, and hyperlink jumps to reference topics.

29. Chapter 14 14-29 © Prentice Hall, 2004 Help Desks and Information Centers Help desk – a single point of contact for all user inquiries and problems about a particular information system or for all users in a particular department Information center – an organizational unit whose mission is to support users in exploiting information technology

30. Chapter 14 14-30 © Prentice Hall, 2004 What Is System Maintenance? Changes made to a system to fix or enhance its functionality

31. Chapter 14 14-31 © Prentice Hall, 2004 System maintenance operates as repeated, miniaturized systems development cycles.

32. Chapter 14 14-32 © Prentice Hall, 2004 Maintenance requests can be frequent. Priorities among requests should be made based on the type and urgency of the request.

33. Chapter 14 14-33 © Prentice Hall, 2004 Maintenance Cost Factors Latent defects Number of customers for the system Quality of system documentation Quality of maintenance personnel Availability of automated tools Quality of program code and system design

34. Chapter 14 14-34 © Prentice Hall, 2004 Recap After studying this chapter we learned to: – Describe coding, testing, and converting. – Apply four installation strategies. – Generate system and user documentation. – Compare training modes. – Discuss techniques of user support. – Discuss maintenance types. – Discuss maintenance cost factors.