SYSTEMS IMPLEMENTATION. Planning/Control Site Preparation New Equipment Education and Training Changeover.

Slides:



Advertisements
Similar presentations
Testing Relational Database
Advertisements

DATA PROCESSING SYSTEMS
Quality Management Training Quality circles Bench Mark Kaizen.
Systems Implementation and Operation
Advanced Database Projects In Access © Hodder Education 2008 Access Projects – Problem Specification.
Chapter 10 Schedule Your Schedule. Copyright 2004 by Pearson Education, Inc. Identifying And Scheduling Tasks The schedule from the Software Development.
Alford Academy Business Education and Computing1 Advanced Higher Computing Based on Heriot-Watt University Scholar Materials Implementation and Testing.
Case Tools Trisha Cummings. Our Definition of CASE  CASE is the use of computer-based support in the software development process.  A CASE tool is a.
1 SYS366 Week 1 - Lecture 2 How Businesses Work. 2 Today How Businesses Work What is a System Types of Systems The Role of the Systems Analyst The Programmer/Analyst.
Chapter 8 System Implementation and Operation. Learning Objectives l To discover which activities take place during the third and fourth phases of the.
MSIS 110: Introduction to Computers; Instructor: S. Mathiyalakan1 Systems Design, Implementation, Maintenance, and Review Chapter 13.
Change is a Process Organizational Stages Individual Stages (ADKAR) Business Need Concept and Design Implementation Post-Implementation Awareness Desire.
©2003 Prentice Hall Business Publishing, Accounting Information Systems, 9/e, Romney/Steinbart 18-1 Accounting Information Systems 9 th Edition Marshall.
Computers: Tools for an Information Age
7.2 System Development Life Cycle (SDLC)
SYSTEM ANALYSIS AND DESIGN
Electronic Health Records
Process Engineer’s Role in Project Management Dr Abdullah Malik.
Library Automation: Planning and Implementation
Release & Deployment ITIL Version 3
Software Evolution Planning CIS 376 Bruce R. Maxim UM-Dearborn.
IT CAREERS Prepared by: Careene McCallum-Rodney. Computer Technician  Computer technicians:  install,  repair,  maintain,  and analyze many different.
Risk Assessment – An Essential Standard
Systems Life Cycle A summary of what needs to be done.
Copyright © 2003 by Prentice Hall Computers: Tools for an Information Age Chapter 14 Systems Analysis and Design: The Big Picture.
Chapter 22 Systems Design, Implementation, and Operation Copyright © 2012 Pearson Education, Inc. publishing as Prentice Hall 22-1.
Chapter 10.
INFORMATION SYSTEM APPLICATIONS System Development Life Cycle.
Computers & Employment By Andrew Attard and Stephen Calleja.
The Islamic University of Gaza
LESSON 8 Booklet Sections: 12 & 13 Systems Analysis.
BSBIMN501A QUEENSLAND INTERNATIONAL BUSINESS ACADEMY.
SYSTEMS ANALYSIS FORM 4 Included in this topic: Information Systems Systems Analysts System Life Cycle (incl. Case Study) Documentation.
Chapter 8: Systems analysis and design
WORKING EFFECTIVELY IN AN INFORMATION TECHNOLOGY ENVIRONMENT
DISCUSS ANY FOUR APPROACHES TO SYSTEM CHANGEOVER
Moving into Implementation SYSTEMS ANALYSIS AND DESIGN, 6 TH EDITION DENNIS, WIXOM, AND ROTH © 2015 JOHN WILEY & SONS. ALL RIGHTS RESERVED.Roberta M. Roth.
Fundamentals of Information Systems, Third Edition1 Systems Design Answers the question “How will the information system do what it must do to solve a.
 To help you understand and describe a range of methods for installing a new computer-based system; › Parallel › Phased › Direct › Pilot  Also, to help.
Systems Analysis and Design
 2001 Prentice Hall Business Publishing, Accounting Information Systems, 8/E, Bodnar/Hopwood Chapter 10 Electronic Data Processing Systems.
1 Technical & Business Writing (ENG-315) Muhammad Bilal Bashir UIIT, Rawalpindi.
Systems Life Cycle A2 Module Heathcote Ch.38.
Introduction to Software Development. Systems Life Cycle Analysis  Collect and examine data  Analyze current system and data flow Design  Plan your.
Test and Review chapter State the differences between archive and back-up data. Answer: Archive data is a copy of data which is no longer in regular.
Topics Covered Phase 1: Preliminary investigation Phase 1: Preliminary investigation Phase 2: Feasibility Study Phase 2: Feasibility Study Phase 3: System.
Safety Management System Implementation Michael Niels Thorsen Moscow 15 September 2005.
Systems Development Life Cycle
GCSE ICT Systems Analysis. Systems analysis Systems analysis is the application of analytical processes to the planning, design and implementation of.
Copyright 2010, The World Bank Group. All Rights Reserved. Statistical Work Plan Development Section A 1.
Thepul Ginige Lecture-7 Implementation of Information System Thepul Ginige.
1 The System life cycle 16 The system life cycle is a series of stages that are worked through during the development of a new information system. A lot.
Slide 10-1 Chapter 10 Systems Development Procedures Introduction to Information Systems Judith C. Simon.
The information systems lifecycle Far more boring than you ever dreamed possible!
Welcome. Contents: 1.Organization’s Policies & Procedure 2.Internal Controls 3.Manager’s Financial Role 4.Procurement Process 5.Monthly Financial Report.
Accounting systems design & evaluation 9434SB 18 March 2002.
Systems Analysis Lecture 5 Requirements Investigation and Analysis 1 BTEC HNC Systems Support Castle College 2007/8.
Core Concepts of ACCOUNTING INFORMATION SYSTEMS Moscove, Simkin & Bagranoff John Wiley & Sons, Inc. Developed by: S. Bhattacharya, Ph.D. Florida Atlantic.
MANAGEMENT INFORMATION SYSTEM
ADMINISTRATIVE STRUCTURE OF A COMPUTER CENTRE. The administrative structure is being organized in such a way that a skilled professional personnel is.
Information Systems Development
Principles of Information Systems Eighth Edition
System Conversion.
Systems Implementation,
Information Systems Development
Project Management Process Groups
Chapter 22, Part
3.3.5: Implementing computer-based information systems
Joint Application Development (JAD)
What is a System? A system is a collection of interrelated components that work together to perform a specific task.
Presentation transcript:

SYSTEMS IMPLEMENTATION

Planning/Control Site Preparation New Equipment Education and Training Changeover

Planning and Control - requires user personnel no line management authority additional to normal work - two possibilities allocate junior user manager as interface form steering committee

Steering Committee - chairman with authority - user management - user staff - trade union representative - D.P. manager - systems analyst Advantages - meet as required, authority, user involvement Disadvantage - decisions slower to arrive at

Site Preparation Power supply Heat dissipation Office alterations layout furniture

New Equipment Hardware Software Telecommunications Supplies (Consumables)

Hardware Lead Time Transport Siting Arrival Cables Engineer

Software Lead time (usually short) Tapes etc. compatibility Completeness Expertise Licensing

Telecommunications Lead time Termination equipment Circuit testing

Consumables Tapes Discs Line printer stationary Pre-printed stationary Ribbons Toner

Education and Training Education - why Training - how

Education Explain philosophy Eliminate fear and misunderstandings Emphasise removal of onerous tasks Motivate users Open discussion

Training to teach specific skills practical where possible Common Methods formal lectures informal discussions or seminars computer based training (CBT) user manuals quick reference manuals 'on the job' training Train 'top down' - knowledge can be passed on

The Changeover Two Possibilities Manual system to computerised system Old computerised system to new computerised system Several methods of changeover exist

Changeover may be a committee responsibility consisting of technical staff and users or the role of a project manager must schedule tasks and consult with users monitor progress communicate progress to all concerned

Main tasks immediately prior to changeover: data conversion file set up procedure conversion control procedures documentation

Data Conversion master files must be set up, e.g. stock file may involve many thousands of records two stages: planning and scheduling data capture and control

Planning and Scheduling estimate work involved decide who does it and when importance must be emphasised

Data Capture data should be as accurate as possible data may be in use - may require out of hours collection special input documents may be necessary multiple formats may exist – either decide between or create new data may not exist on record - may have to be created - e.g. postcodes

best if user personnel key data in - lower error rate, due to familiarity with data - useful training exercise - however, volumes and keyboard skills may be a problem

static data e.g. partno, description, supplier code can be entered well in advance dynamic data e.g. stock-in-hand may be added much nearer live date. shut-down period may be best but impossible, therefore update over first few weeks of live running.

File Set Up Assumes data ready in machine-readable form Options are: file creation program utility program normal master file programs Errors could be caused by: original documents clerical transcriptions keying errors the conversion program itself

Procedure Conversion (Actual Changeover) When end of financial year end of month end of week least busy time of year over weekend overnight

How Parallel running Pilot running Direct changeover

Parallel Running process data by both old and new systems - cross check results essentially an extension of testing requires resources to run two systems and do the checks any errors found may also be present in old system the old system will have to go one day! AdvantagesDisadvantages SafestHeavy on resource Better trainingUsers may never want to change Better testing Anytime

Pilot running Either make a small section of the system live and introduce more sections over time Or make entire new system available to a small number of users and expand toall users over time useful but have to choose sections carefully and make it absolutely clear to all which is which. AdvantagesDisadvantages Damage limitationDifficult to split Possible confusion

Direct Changeover replace old system by new one in one go data transfer may take place over a period cheapest but riskiest ensure rigorous testing choose a slack period weigh up the consequences of mistakes carefully allow for reversion to old system in emergency AdvantagesDisadvantages CheapestRiskiest Need to choose time

Department Manager support and commitment Supervisors extra work feedback User Involvement

Control procedures Auditors will have to be convinced that data integrity has been maintained. Controls that existed on the old system will have to be maintained or improved upon for the new system.

Documentation Likely to differ from normal running - differences must be highlighted Instructions needed before changeover saying how changeover should be carried out. Changeover documentation should include: sections relevant to specific departments brief introduction to new system reasons for change outline of method of changeover schedule dates availability of ancillary services during changeover user responsibility

Further sections could include: clerical and terminal input procedures computer input documentation computer output documentation non-computer documentation

SUMMARY Planning/Control Site Preparation New Equipment Education and Training Changeover main tasks immediately prior different methods user involvement