Presentation is loading. Please wait.

Presentation is loading. Please wait.

Systems maintenance Asper School of Business University of Manitoba Systems Analysis & Design Instructor: Bob Travica Updated: November 2009.

Similar presentations


Presentation on theme: "Systems maintenance Asper School of Business University of Manitoba Systems Analysis & Design Instructor: Bob Travica Updated: November 2009."— Presentation transcript:

1 Systems maintenance Asper School of Business University of Manitoba Systems Analysis & Design Instructor: Bob Travica Updated: November 2009

2 2 of 9 Outline Maintenance concept Maintenance types Maintenance costs System adoption Counter-Adoption methods Management of Counter-Adoption

3 3 of 9 System Operation Systems operation (production stage) – period after deployment (cutover, rollout, going live) in which a system is used in daily work Technical activities : Fine-tuning & upgrading of the system - maintenance activities Management activities: Promoting system adoption

4 4 of 9 System Maintenance More human resources are involved in maintaining systems than in developing new systems. Upgrades can accumulate over time to the extent that a resulting system is significantly different from the initial system - hard to differentiate between maintenance and development.

5 Corrective maintenance - Fixing software bugs (70% of all maintenance) Responsive maintenance - Respond to business needs (add a function, user interface feature fix, add storage, etc.) Preventive maintenance – Anticipate business needs (examples as for responsive maintenance) Maintenance types

6 6 of 9 Maintenance Cost Factors Quality of code & overall design Number of clients (users) of the system Quality of system documentation Quality of maintenance personnel Availability of automated tools

7 7 of 9 Process of making a system part of routine work. Includes motivating end-users. System Adoption End-users Early Adopters Later Adopters Resistors Speed of adoption:

8 8 of 9 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

9 9 of 9 Managing Counter-Adoption Involve end-users in system development Educate end-users and managers on benefits from the system. Note that each group may have different benefits. Deal with costs: End-users (learning new skills; loss of old skills) Managers (reactions to power loss) Organizational costs (time, operations efficiency, moral) Promote change agents (managers giving incentives, train users motivated to educate others)


Download ppt "Systems maintenance Asper School of Business University of Manitoba Systems Analysis & Design Instructor: Bob Travica Updated: November 2009."

Similar presentations


Ads by Google