1. 14-1 © Prentice Hall, 2004 Chapter 14: Production Stage 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 System Operation Systems operation (production stage) – period after implementation in which a system is used for work purposes. Technical activities : Fine-tuning of the system called system maintenance Management activities: Promoting system adoption

3. Chapter 14 14-3 © Prentice Hall, 2004 System Maintenance Changes (upgrades) made to a system to fix or enhance its functionality, user interface and/or data. Today, more human resources involved in maintaining systems than in developing new systems.

4. Chapter 14 14-4 © Prentice Hall, 2004 System maintenance can be understood as repeated, miniaturized systems development cycles. Upgrades can accumulate over time to the extent that a resulting system is significantly different from the initial system. So, hard to differentiate between maintenance and development. Same with perfective maintenance.

5. Chapter 14 14-5 © Prentice Hall, 2004 Maintenance Cost Factors Latent (unknown) defects Number of clients (users) of the system Quality of system documentation Quality of maintenance personnel Availability of automated tools Quality of program code and system design - Assessment: Look at errors – number, frequency, types

6. Chapter 14 14-6 © Prentice Hall, 2004 Process of making a system part of organization. Includes motivating end users to use the system. System Adoption End Users Early Adopters Late Adopters Resistors

7. Chapter 14 14-7 © Prentice Hall, 2004 Counter-Adoption Methods Not-Invented Here Syndrome (“system developers don’t really understand our needs”) Blame on the system (“System is hard to use”) Withholding resources needed for adoption (end user support, time for learning, money+time for training for upgrades) Cutting on money for software, hardware, labor

8. Chapter 14 14-8 © Prentice Hall, 2004 Managing Counter-Adoption Involve end users in system development Inform end users and managers on benefits from the system. Note that each group may have different benefits. Deal with costs of end users and managers. - Learning - Skills Loss Power Loss More 

9. Chapter 14 14-9 © Prentice Hall, 2004 Know thy organization and act accordingly - culture, structure, processes Ideally, these should be accounted for in systems development, but not always are - new types of IT and systems - imitating others - managers’ oversights and divisions