1 Chapter 13 (Week 13) SYSTEMS MAINTENANCE AND EVALUATION Chapter 13: SYSTEMS MAINTENANCE AND EVALUATION Throughout its life, a system should operate effectively.

Slides:



Advertisements
Similar presentations
DME PANEL CONTRACTS John Fisher Program Manager – Procurement.
Advertisements

Systems Implementation and Operation
Overview of IS Controls, Auditing, and Security Fall 2005.
Lesson 5 Computer-Related Issues
Chapter 5: Common Support Problems
IT Technical Support Policies and Procedures South Nottingham College.
Reliability Week 11 - Lecture 2. What do we mean by reliability? Correctness – system/application does what it has to do correctly. Availability – Be.
ISO General Awareness Training
MSIS 110: Introduction to Computers; Instructor: S. Mathiyalakan1 Systems Design, Implementation, Maintenance, and Review Chapter 13.
ASPEC Internal Auditor Training Version
1 Principles of Information Systems, Ninth Edition Chapter 13 Systems Development: Design, Implementation, Maintenance, and Review.
4 types of implementing information systems
Chapter 17 Acquiring and Implementing Accounting Information Systems
Hazard Analysis Critical Control Point (HACCP)
Chapter 9 – Software Evolution and Maintenance
David Halldearn, ERGEG Conference on Implementing the 3 rd Package 11 th December 2008 Implementating the 3rd Package: An ERGEG Consultation paper.
S3: Module D Physikalisch-Technische Bundesanstalt Session 3: Conformity Assessment Module D Peter Ulbig, Harry Stolz Belgrade, 31 October.
Term 2, 2011 Week 3. CONTENTS The physical design of a network Network diagrams People who develop and support networks Developing a network Supporting.
Outsourcing Louis P. Piergeti VP, IIROC March 29, 2011.
Module CC3002 Post Implementation Issues Lecture for Week 6 AY 2013 Spring.

Chapter 2: Software Process Omar Meqdadi SE 2730 Lecture 2 Department of Computer Science and Software Engineering University of Wisconsin-Platteville.
Software – Acquisition & Testing. ICT5 How to acquire software There are several options: The software may be written by the end-user; A specialist department.
1 Maintain System Integrity Maintain Equipment and Consumables ICAS2017B_ICAU2007B Using Computer Operating system ICAU2231B Caring for Technology Backup.
Principles of Information Systems, Sixth Edition Systems Design, Implementation, Maintenance, and Review Chapter 13.
 Once the system has been installed it will be monitored to check whether it is working correctly. Sometimes problems with a system will not be found.
Computer Maintenance and Troubleshooting
1 Unit 1 Information for management. 2 Introduction Decision-making is the primary role of the management function. The manager’s decision will depend.
University of Palestine software engineering department Testing of Software Systems Testing throughout the software life cycle instructor: Tasneem.
Systems Development: Design, Implementation, Maintenance, and Review
Principles of Information Systems, Sixth Edition Systems Design, Implementation, Maintenance, and Review Chapter 13.
I Power Higher Computing Software Development The Software Development Process.
System Analysis (Part 3) System Control and Review System Maintenance.
Systems Life Cycle A2 Module Heathcote Ch.38.
 System Development Life Cycle System Development Life Cycle  SDLC Phases SDLC Phases Phase 1: Preliminary Investigation Phase 2: Feasibility Study.
Intermediate 2 Software Development Process. Software You should already know that any computer system is made up of hardware and software. The term hardware.
PLANNING ENGINEERING AND PROJECT MANAGEMENT By Lec. Junaid Arshad 1 Lecture#03 DEPARTMENT OF ENGINEERING MANAGEMENT.
IT Essentials: PC Hardware and Software v4.0. Chapter 4 Objectives 4.1 Explain the purpose of preventive maintenance 4.2 Identify the steps of the troubleshooting.
Post Implementation Review The Post Implementation Review is carried out once the system is fully operational. The Post Implementation Review is carried.
A European campaign on Risk Assessment Common errors in Risk Assessment.
IFS310: Module 13 Implementation and Support - Construction, Conversion and Maintenance of the New System.
Module 4: Systems Development Chapter 14: Design And Implementation.
1 Kingsley Karunaratne, Department of Accounting, University of Sri Jayewardenepura, Colombo - Sri Lanka Practice Management.
Principles of Information Systems, Sixth Edition 1 Systems Design, Implementation, Maintenance, and Review Chapter 13.
HNDIT23082 Lecture 06:Software Maintenance. Reasons for changes Errors in the existing system Changes in requirements Technological advances Legislation.
Requirements engineering The process of establishing the services that the customer requires from a system and the constraints under which it operates.
Implementation of legislation (Chapter 47) By Haley Court.
ISO 9001:2015 Subject: Quality Management System Clause 8 - Operation
WORKSHOP ON ACCREDITATION OF BODIES CERTIFYING MEDICAL DEVICES INT MARKET TOPIC 9 CH 8 ISO MEASUREMENT, ANALYSIS AND IMPROVEMENT INTERNAL AUDITS.
Software Maintenance1 Software Maintenance.
© Food – a fact of life 2009 Hazard Analysis Critical Control Point (HACCP) HACCP is a system which looks for and prevents potential problems before they.
MANAGEMENT INFORMATION SYSTEM
Software Development Module Code: CST 240 Chapter 6: Software Maintenance Al Khawarizmi International College, AL AIN, U.A.E Lecturer: Karamath Ateeq.
1 Determining a client’s peripheral requirements  Determine current business practices  Determine peripheral requirements  Analyse and document existing.
Software Engineering — Software Life Cycle Processes — Maintenance
Principles of Information Systems Eighth Edition
Fundamentals of Information Systems, Sixth Edition
Chapter 18 Maintaining Information Systems
The Software Quality Challenge
Initiating systems development
Developing Information Systems
Software Engineering (CSI 321)
Lesson 5 Computer-Related Issues
Systems Analysis and Design
Chapter 9 – Software Evolution and Maintenance
Information Systems, Ninth Edition
CS310 Software Engineering Lecturer Dr.Doaa Sami
Chapter 8 Software Evolution.
Lecture 06:Software Maintenance
Software Maintenance Part1 Introduction. Outlines What Is Software Maintenance Purposes of Maintenance Why We Need It Maintenance Difficilties Some Tips.
Presentation transcript:

1 Chapter 13 (Week 13) SYSTEMS MAINTENANCE AND EVALUATION Chapter 13: SYSTEMS MAINTENANCE AND EVALUATION Throughout its life, a system should operate effectively and efficiently. To do this, the system needs to be maintained and its users need to be supported. This should be an ongoing process to make sure that the system continues to meet requirements. The operational characteristics of the system will be reviewed continually.

2 Types of maintenance There are three types of maintenance activity. a) Corrective Maintenance is action taken in response to a problem. CM is carried out when there is a systems failure of some kind, for example in processing or in an implementation procedure or when errors are detected in a system and need to be corrected. Its objective is to ensure that systems remain operational. Chapter 13: SYSTEMS MAINTENANCE AND EVALUATION

3 b) Perfective Maintenance is carried out in order to perfect the software, or to improve software so that the processing inefficiencies are eliminated and performance is enhanced. Perfective Maintenance is carried out to include new capabilities/modifications to existing functions and thereby bringing general enhancements to the system. The replacement of a word processing package written for DOS by a package which offers a Windows environment is an example of perfective maintenance. Chapter 13: SYSTEMS MAINTENANCE AND EVALUATION

4 c) Adaptive Maintenance is carried out to take account of anticipated changes in the processing environment. For example new taxation legislation might require change to be made to payroll software. AM occurs when the environment changes. For e.g, when the regulations for the number of of local leaves entitled to staff changes – the system needs to be modified to reflect those new regulations. d) Preventive Maintenance when necessary actions are taken to improve future maintainability or reliability OR to provide a better basis for future enhancements. For e.g, preventive maintenance may be accomplished by replacing the cell every 2-3 years, cleaning the motherboard (removal of dust), performing a disk scan on the HD etc.

5 Chapter 13: SYSTEMS MAINTENANCE AND EVALUATION The causes of systems maintenance Besides environmental changes, three factors contribute to the need for maintenance. Errors:However carefully and diligently the systems development staff carry out systems testing and program testing, it is likely that bugs will exist in a newly implemented system. Changes in requirements: Although users should be consulted at all stages of systems development, problems may arise after a system is implemented because users may have found it difficult to express their requirements.

6 Poor documentation: If old systems are accompanied by poor documentation, or even a complete lack of documentation, it may be very difficult to understand their programs. It will be hard to update or maintain such programs. Chapter 13: SYSTEMS MAINTENANCE AND EVALUATION In-house maintenance With large computer systems, developed by the organisation itself, in-house systems analysts and programmers might be given the responsibility for software maintenance.

7 Chapter 13: SYSTEMS MAINTENANCE AND EVALUATION To ensure that maintenance is carried out efficiently, the principles of good programming practice should be applied. – a)The new program requirements must be specified in full and in writing. These specifications will be prepared by a systems analyst. A programmer should use these specifications to produce an amended version of the program. b)In developing a new program version, a programmer should keep working papers. He or she can refer back to these papers later to check in the event that there is an error in the new program.

8 c)The new program version should be tested when it has been written. A programmer should prepare test data and establish whether the program will process the data according to the specifications given by the systems analyst. d)Each version of a program should be separately identified, to avoid a mix-up about what version of a program should be used for ‘live’ operating. Chapter 13: SYSTEMS MAINTENANCE AND EVALUATION

9 Software maintenance Chapter 13: SYSTEMS MAINTENANCE AND EVALUATION With purchased software (whether off the shelf or bespoke), the software house or supplier is likely to provide details of any new versions of the software as they are produced, simply for marketing purposes. Maintenance contracts There is also likely to be an agreement between the supplier of software and the customer for the provision of a software support service.

10 A maintenance contract typically includes the following services. (a)Help When a customer runs into difficulties operating the system help will initially be given by a telephone hot line’. If a telephone call does not resolve the problem, the software expert may arrange to visit the customer’s premises, although this would be rare for standard packages. (b)Information Extra information about using the package may be provided through factsheets or a magazine sent free to subscribers. Chapter 13: SYSTEMS MAINTENANCE AND EVALUATION

11 (c)Updates Free updates are provided to correct errors in part of a package, or if there is something inevitable that will mean that some aspect of a package has to be changed. (d) Upgrades When the whole package/hardware is revised just after purchase of it, the contract provides for customers to get the NEW version at a heavily discounted price. Upgrades often include new features not found in the previous versions of the software/hardware. Chapter 13: SYSTEMS MAINTENANCE AND EVALUATION

12 (e) Legal Conditions There should be provisions about the duration of the contract and in what circumstances the contract may be TERMINATED. This covers: the customer’s obligations to use the software in the way it was intended to be used (not to make ILLEGAL copies of the CDs or manuals), on the right sort of hardware. The liability of the supplier will also be set out, especially regarding consequential loss.

13 Hardware maintenance Computer hardware should be kept serviced and maintained too. Maintenance services are provided: (a)by the computer manufacturers themselves; or (b)by third-party maintenance companies. Maintenance of hardware can be obtained in two ways. On a contract basis. PC maintenance contracts are usually negotiated annually. On an ad hoc basis - ie calling in a maintenance company whenever a fault occurs. Chapter 13: SYSTEMS MAINTENANCE AND EVALUATION