20-1 Systems support is the on-going technical support for users, as well as the maintenance required to fix any errors, omissions, or new requirements.

Slides:



Advertisements
Similar presentations
McGraw-Hill/Irwin Copyright © 2007 by The McGraw-Hill Companies, Inc. All rights reserved. Chapter 20 Systems Operations and Support.
Advertisements

Software Configuration Management
Database Administration Chapter Six DAVID M. KROENKE’S DATABASE CONCEPTS, 2 nd Edition.
Reliability Week 11 - Lecture 2. What do we mean by reliability? Correctness – system/application does what it has to do correctly. Availability – Be.
Managing the Information Technology Resource Jerry N. Luftman
DAVID M. KROENKE’S DATABASE PROCESSING, 10th Edition © 2006 Pearson Prentice Hall 4-1 David M. Kroenke Database Processing Chapter 9 Managing Multi- User.
McGraw-Hill/Irwin Copyright © 2007 by The McGraw-Hill Companies, Inc. All rights reserved. Chapter 19 Systems Construction and Implementation.
MSIS 110: Introduction to Computers; Instructor: S. Mathiyalakan1 Systems Design, Implementation, Maintenance, and Review Chapter 13.
Chapter 8 : Transaction Management. u Function and importance of transactions. u Properties of transactions. u Concurrency Control – Meaning of serializability.
SIM5102 Software Evaluation
© 2002 by Prentice Hall 1 David M. Kroenke Database Processing Eighth Edition Chapter 11 Managing Multi-User Databases.
Chapter 1 The Systems Development Environment 1.1 Modern Systems Analysis and Design Third Edition.
Database Administration Part 2 Chapter Six CSCI260 Database Applications.
Pertemuan Matakuliah: A0214/Audit Sistem Informasi Tahun: 2007.
Computer Security: Principles and Practice
Irwin/McGraw-Hill Copyright © 2004 The McGraw-Hill Companies. All Rights reserved Whitten Bentley DittmanSYSTEMS ANALYSIS AND DESIGN METHODS6th Edition.
Transaction Management WXES 2103 Database. Content What is transaction Transaction properties Transaction management with SQL Transaction log DBMS Transaction.
Introduction to Systems Analysis and Design
Academic Year 2014 Spring. MODULE CC3005NI: Advanced Database Systems “DATABASE RECOVERY” (PART – 1) Academic Year 2014 Spring.
Managing Multi-User Databases AIMS 3710 R. Nakatsu.
Term 2, 2011 Week 3. CONTENTS The physical design of a network Network diagrams People who develop and support networks Developing a network Supporting.
System Construction and Implementation
Module CC3002 Post Implementation Issues Lecture for Week 6 AY 2013 Spring.
11 SECURITY TEMPLATES AND PLANNING Chapter 7. Chapter 7: SECURITY TEMPLATES AND PLANNING2 OVERVIEW  Understand the uses of security templates  Explain.
Copyright Irwin/McGraw-Hill Systems Support Prepared by Kevin C. Dittman for Systems Analysis & Design Methods 4ed by J. L. Whitten & L. D. Bentley.
Reliability Andy Jensen Sandy Cabadas.  Understanding Reliability and its issues can help one solve them in relatable areas of computing Thesis.
Irwin/McGraw-Hill Copyright © 2000 The McGraw-Hill Companies. All Rights reserved Whitten Bentley DittmanSYSTEMS ANALYSIS AND DESIGN METHODS5th Edition.
INFO 503Lecture #101 Introduction to Information Systems Analysis Systems Operations and Support Review INFO 503 Glenn Booker.
ITIL Process Management An Overview of Service Management Processes Thanks to Jerree Catlin, Sue Silkey & Thelma Simons University of Kansas.
Principles of Information Systems, Sixth Edition Systems Design, Implementation, Maintenance, and Review Chapter 13.
© 2001 by Prentice Hall11-1 Local Area Networks, 3rd Edition David A. Stamper Part 4: Installation and Management Chapter 11 LAN Administration: Backup.
1 Systems Analysis & Design Systems Implementation & Support IS 431: Lecture 11 CSUN Information Systems.
1 BTEC HNC Systems Support Castle College 2007/8 Systems Analysis Lecture 13 Post-Implementation Training.
The Handover Process P6.
System Implementation 1. Software and Hardware Acquisition  Recognize Need, Appoint Committee and/or Project Manager: For large systems, the majority.
D ATABASE A DMINISTRATION L ECTURE N O 3 Muhammad Abrar.
Principles of Information Systems, Sixth Edition Systems Design, Implementation, Maintenance, and Review Chapter 13.
Transactions and Locks A Quick Reference and Summary BIT 275.
IFS310: Module 13 Implementation and Support - Construction, Conversion and Maintenance of the New System.
© 2002 by Prentice Hall 1 Database Administration David M. Kroenke Database Concepts 1e Chapter 6 6.
1 Systems Support Introduction  The chapter will address the following questions:  What is systems support?  What is the role of a repository in systems.
14 Copyright © 2005, Oracle. All rights reserved. Backup and Recovery Concepts.
Principles of Information Systems, Sixth Edition 1 Systems Design, Implementation, Maintenance, and Review Chapter 13.
Irwin/McGraw-Hill Copyright © 2000 The McGraw-Hill Companies. All Rights reserved Whitten Bentley DittmanSYSTEMS ANALYSIS AND DESIGN METHODS5th Edition.
Presented by, MySQL & O’Reilly Media, Inc. Top considerations for backup of MySQL Dmitri Joukovski, Zmanda.
NERC Lessons Learned Summary LLs Published in September 2015.
Systems Analysis & Design AUTHOR: PROFESSOR SUSAN FUSCHETTO 10/24/
1 Object-Oriented Analysis and Design with the Unified Process Figure 13-1 Implementation discipline activities.
Irwin/McGraw-Hill Copyright © 2000 The McGraw-Hill Companies. All Rights reserved Whitten Bentley DittmanSYSTEMS ANALYSIS AND DESIGN METHODS5th Edition.
Chapter 5 Managing Multi-user Databases 1. Multi-User Issues Database Administration Concurrency Control Database Security Database Recovery Page 307.
 Software reliability is the probability that software will work properly in a specified environment and for a given amount of time. Using the following.
Computer Security: Principles and Practice First Edition by William Stallings and Lawrie Brown Lecture slides by Lawrie Brown Chapter 17 – IT Security.
Dr. Gerry Firmansyah CID Business Continuity and Disaster Recovery Planning for IT (W-XIV)
Software Engineering — Software Life Cycle Processes — Maintenance
Local Area Networks, 3rd Edition David A. Stamper
Chapter 1 The Systems Development Environment
NERC Published Lessons Learned Summary
NERC Lessons Learned Summary
Software Configuration Management
Software Project Configuration Management
Chapter 1 The Systems Development Environment
Regression Testing with its types
System Design, Implementation and Review
Chapter 10 Recover System
Chapter 1 The Systems Development Environment
Managing Multi-user Databases
Systems Design, Implementation, and Operation
Database Administration
Systems Operations and Support
Chapter 1 The Systems Development Environment
Presentation transcript:

20-1 Systems support is the on-going technical support for users, as well as the maintenance required to fix any errors, omissions, or new requirements that may arise. Systems operation is the day-to-day, week-to-week, month-to-month, and year-to-year execution of an information system’s business processes and application programs. An operational system is a system that has been placed into operation. Frequently called a production system. Support versus Operation

20-2 System Support Activities System maintenance corrects “bugs” or errors that slipped through the system development process. System recovery is the restoration of the system and data after a system failure. Technical support is any assistance provided to users in response to inexperience or unanticipated situations. System enhancement is the improvement of the system to handle new business problems, new technical problems, or new technology requirements.

20-3 System Maintenance Objectives To make predictable changes to existing programs to correct errors. To preserve those aspects of the programs that were correct, and to avoid “ripple effects” of changes that may adversely affect the correctly functioning aspects. To avoid, as much as possible, the degradation of system performance. To complete the task as quickly as possible without sacrificing quality and reliability of the system.

20-4 Testing Unit testing (essential) ensures that the stand-alone program fixes the bug without undesirable side effects to the program. System testing (essential) ensures that the entire application, of which the modified and unit tested program was a part, still works as a complete system. Regression testing (recommended) extrapolates the impact of the changes on system performance (throughput and response time) by analyzing before- and-after performance against the test script. Version control - a process whereby a librarian program keeps track of changes made to programs to facilitate backtracking.

20-5 System Recovery Activities 1.Recover from user’s terminal. Menu option Reboot 2.Systems operations personnel correct server problem (network admin, database admin, webmaster). 3.Data administrator recovers lost data or corrupted files. Lost transactions must be reprocessed (roll forward) Partially processed transactions must be undone (roll back) 4.Network administrator fixes LAN or WAN problem. 5.Technicians or vendor reps fix hardware problem. 6.Software bug must be trapped and fixed.

20-6 Technical Support Being on call to assist users Typical tasks: Routinely observing use of system Conducting user-satisfaction surveys and meetings Changing business procedures for clarification Providing additional training Logging enhancement ideas and requests in repository

20-7 System Enhancement Tasks 1. Analyze enhancement request. 2. If appropriate, make the quick fix. Changes that can be made without Restructuring stored data Updating stored data Inputting new data In other words, reports and outputs Requirements that exceed this should be subjected to systems analysis and design to consider implications. Can be written in 4GLs

20-8 System Obsolescence All systems degrade over time At some point, not cost-effective to support and maintain Leads to a new systems development project Full circle to chapters 3-19