BSBIMN501A QUEENSLAND INTERNATIONAL BUSINESS ACADEMY.

Slides:



Advertisements
Similar presentations
Testing Relational Database
Advertisements

Test process essentials Riitta Viitamäki,
INFORMATION TECHNOLOGY
P5, M1, D1.
System Construction and Implementation Objectives:
ORGANIZATION. 2 Problem scenario  Develop an organizational chart for your laboratory showing lines of authority from the head of the organization to.
Learning Objectives LO5 Document an accounting system to identify key controls and weaknesses in order to assess control risk. LO6 Write key control tests.
Chapter 10 Schedule Your Schedule. Copyright 2004 by Pearson Education, Inc. Identifying And Scheduling Tasks The schedule from the Software Development.
BSBIMN501A QUEENSLAND INTERNATIONAL BUSINESS ACADEMY.
Changeover Lecture 12 Change-Over Strategies for Implementation 1 BTEC HNC Systems Support Castle College 2007/8.
System Design and Analysis
System Implementations American corporations spend about $300 Billion a year on software implementation/upgrade projects.
System Development Life Cycle (SDLC)
System Implementations American corporations spend about $300 Billion a year on software implementation/upgrade projects.
4 types of implementing information systems
Imran Ghaznavi Course Code: MGT557 COMSATS Strategic Human Resource Management.
Irwin/McGraw-Hill Copyright © 2000 The McGraw-Hill Companies. All Rights reserved Whitten Bentley DittmanSYSTEMS ANALYSIS AND DESIGN METHODS5th Edition.
Introduction to Computer Technology
Welcome ISO9001:2000 Foundation Workshop.
Systems Life Cycle A summary of what needs to be done.
Chapter 22 Systems Design, Implementation, and Operation Copyright © 2012 Pearson Education, Inc. publishing as Prentice Hall 22-1.
Introduction to Systems Analysis and Design Trisha Cummings.
Information Security Governance 25 th June 2007 Gordon Micallef Vice President – ISACA MALTA CHAPTER.
Chapter 10.
BSBIMN501A QUEENSLAND INTERNATIONAL BUSINESS ACADEMY.
PHASE 4 SYSTEMS IMPLEMENTATION Application Development SYSTEMS ANALYSIS & DESIGN.
LESSON 8 Booklet Sections: 12 & 13 Systems Analysis.
1 BTEC HNC Systems Support Castle College 2007/8 Systems Analysis Lecture 9 Introduction to Design.
Testing phases. Test data Inputs which have been devised to test the system Test cases Inputs to test the system and the predicted outputs from these.
BSBIMN501A QUEENSLAND INTERNATIONAL BUSINESS ACADEMY.
End HomeWelcome! The Software Development Process.
 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.
Testing Methods Carl Smith National Certificate Year 2 – Unit 4.
1 Introduction to Software Engineering Lecture 1.
Systems Analysis and Design
Handbook of Informatics for Nurses and Healthcare Professionals Copyright ©2009 by Pearson Education, Inc. Upper Saddle River, New Jersey All rights.
 System Development Life Cycle System Development Life Cycle  SDLC Phases SDLC Phases Phase 1: Preliminary Investigation Phase 2: Feasibility Study.
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.
PROGRAM DEVELOPMENT CYCLE. Problem Statement: Problem Statement help diagnose the situation so that your focus is on the problem, helpful tools at this.
GCSE ICT Systems Analysis. Systems analysis Systems analysis is the application of analytical processes to the planning, design and implementation of.
National Enrolment Service (NES) Overview October 2015 – June 2016.
A BRIEF LOOK AT THE COMPONENTS THAT MAKE UP THE SYSTEM LIFE CYCLE.
第 11 組 MIS 報告. Phases of any information system ~ recognition of a business problem or opportunity ~ recognition of a business problem or opportunity.
Organisations, Goals and Information Systems ORGANISATION A group of people, supported by a collection of physical resources and procedures, who work.
IS2210: Systems Analysis and Systems Design and Change Twitter:
Bina Nusantara 19 C H A P T E R SYSTEM CONSTRUCTION AND IMPLEMENTATION.
A brief look at the components that make up the system life cycle.
Irwin/McGraw-Hill Copyright © 2000 The McGraw-Hill Companies. All Rights reserved Whitten Bentley DittmanSYSTEMS ANALYSIS AND DESIGN METHODS5th Edition.
 Problem Analysis  Coding  Debugging  Testing.
MANAGEMENT INFORMATION SYSTEM
© 2017 by McGraw-Hill Education. This proprietary material solely for authorized instructor use. Not authorized for sale or distribution in any manner.
Coupling and Cohesion Rajni Bhalla.
Information Systems Development
System.
Coupling and Cohesion 1.
System Design.
Systems Analysis and Design
System Development Life Cycle (SDLC)
Software Requirements
FORMAL SYSTEM DEVELOPMENT METHODOLOGIES
System Development Life Cycle (SDLC)
CHAPTER 2 Testing Throughout the Software Life Cycle
CLINICAL INFORMATION SYSTEM
Introduction to Systems Analysis and Design
Proposed Software Development Process
System Development Life Cycle (SDLC)
SYSTEMS ANALYSIS & DESIGN
Systems Construction and Implementation
System Construction and Implementation
Systems Construction and Implementation
Presentation transcript:

BSBIMN501A QUEENSLAND INTERNATIONAL BUSINESS ACADEMY

2.2 Address implementation issues and problems as they arise

 When a new information or knowledge management system is implemented into an organisation, there is more than just the issue of new technology to address.  The system must also support the business processes and the people that carry out those processes-it is the relationships between the elements of technology, process and people that provides the key to a successful system implementation.

 Implementation issues arise when interaction between those elements is lacking in some way

 If you think of technology, processes and people as each being one leg on a three- legged stool, with each leg needing to be equal in strength, length and sturdiness, you can begin to picture how each element is dependent upon the other for optimum functionality.

 If one leg falls short, or if it has not been properly secured, the stool will wobble; if one of the essential elements of an information or knowledge management system has been neglected, the system will be unstable. It is important to get the balance right.

 Processes describe how a goal or objective is achieved by following a sequence of actions.  They are useful tools for standardising what is required to achieve the desired end result.  Fostering a solid understanding of new processes will enhance efficiency and productivity as well as ensure compliance with standards and codes of practice.

 Every time a new process is implemented in an organisation, it must also be documented.  This way, all the people that are required to perform the process share a common understanding of it.

 Because processes are rarely explained in one stream of actions, but rather as more than one action branching off from another action, the workflow in a process is often demonstrated with the help of flowcharts.  Flow charts help to define the process, standardise it, and highlight areas that need to be improved.

 It is important for workers in an organisation not only to have a thorough understanding of new processes and technology, but also for the processes to be meaningful to them on both a personal and organisational level.

 They must be clear about their new roles or responsibilities and be committed to carrying them out, as well as willing to cooperate with others in working towards successful implementation.

 New processes associated with the information or knowledge management system should help workers to:  gain access to current and accurate information perform their tasks more efficiently  participate in achieving organisational goals share knowledge and information with others  have contingencies in place for technical problems

 Once you have developed and clarified your processes, and workers are appropriately aligned with them, it is down to the new information or knowledge management system to support the other two elements in the equation.  For this to happen, there are some basic principles that should be adhered to.

 These principles require that the new system should:  incorporate familiar, standard tools for processing information have security procedures in place  perform processes and produce outputs as planned integrate with existing information systems  be stable-free from hardware or software problems.

 The process of changing from one information or knowledge management system to another is often referred to as the 'changeover'.  It can be an unsettling process and requires a careful approach.

 There a number of ways it can be done:  Shut off the old system and begin with the new  this is not the best approach as there are likely to be bugs in the new system that will need to be worked out.

 Phase in the new system  this approach implements components of the new system in stages while the other components of the old system are still running.  If the new components don't function properly, the old system can be reinstated until the problems have been sorted out.  This process occurs in stages with new system components being implemented one at a time until all the new system components function as required.

 Run in parallel  in this approach, both the old and the new system are used at the same time.  This means that all the inputs have to be duplicated so that identical information is held in both systems.  Running in parallel continues until all processes have been tested and no more problems occur.

 Proper planning and testing are the keys to addressing issues and problems with the system.  The reality is that implementation is unlikely to run without glitches, but if you are prepared, you will catch errors before they become large problems.  We must ensure that we have addressed the relationship issues between processes, people and technology, and part of that equation involves developing procedures for data processing and testing.

 An information or knowledge manage system is of little use if the procedures for processing data and keeping it up-to-date are ineffective.  Therefore, it is essential that all workers who are responsible for processing data have a current procedures manual available to them for reference.

 The manual should include instructions for:  inputting accurate and complete data periodically checking data for currency, accuracy and completeness of information  reporting software faults  security procedures.

 Before you go 'live' with a new system, it is essential to test it first to iron out any problems that may be present.  As we have seen, testing should also occur at different stages of implementation such as testing form design and testing workers after training.

 Before you begin any testing, think about:  What will be tested?  What are the testing objectives?  Where will the testing occur?  Who will participate in the testing?  What methods will be used for testing?  How long will it take to complete the testing phase?