Chapter 12 Implementing BusinessIT Solutions Mc GrawHillIrwin Copyright

Learning Objectives v Use the systems development process outlined in this chapter and the model of IS components from Chapter 1 as problem– solving frameworks to help you propose information systems solutions to simple business problems. v Describe and give examples to illustrate how you might use each of the steps of the information systems development life cycle to develop and implement a buiness information system. Mc. Graw-Hill/Irwin Copyright © 2013 by The Mc. Graw-Hill Companies, Inc. All rights reserved.

Learning Objectives v Explain how prototyping can be used as an effective technique to improve the process of systems development for end users and IS specialists. v Understand the basics of project management and its importance to a successful systems development effort. v Identify the activities involved in the implementation of new information systems. Mc. Graw-Hill/Irwin Copyright © 2013 by The Mc. Graw-Hill Companies, Inc. All rights reserved.

Learning Objectives v Compare and Contrast the four basic information system conversion strategies. v Describe several evaluation factors that should be considered in evaluating the acquisition of hardware, software, and IS services. Mc. Graw-Hill/Irwin Copyright © 2013 by The Mc. Graw-Hill Companies, Inc. All rights reserved.

Section 1 Developing Business Systems Mc. Graw-Hill/Irwin Copyright © 2013 by The Mc. Graw-Hill

II. The Systems Approach v Uses a systems orientation to defining and solving problems and opportunities v Problem Solving – there are specific steps in solving any problem v Recognize/Define a Problem or Opportunity – recognize it exists v Develop and Evaluate Alternative System Solutions – what are the different ways to solve this problem? v Select the Best System Solution – decide which alternative is best v Design the Selected System Solution – design the system for the chosen solution v Implement and Evaluate the Success of the Designed System – put the solution into effect and monitor results for the outcome Mc. Graw-Hill/Irwin Copyright © 2013 by The Mc. Graw-Hill Companies, Inc. All rights reserved.

IV. Starting the Systems Development Process The Systems Development Life Cycle Mc. Graw-Hill/Irwin Copyright

V. Systems Analysis • A detailed study of the current system and organizational needs • Organizational Analysis – you must have a thorough understanding of the organization to make the system work well • Analysis of the Present System – “those who fail to study history are doomed to repeat it”, a complete understanding of the current system is critical • Logical Analysis – create logical models the current system, WHAT the system does without regard to HOW • Functional Requirements Analysis and Determination – what Information is required for each business activity and what Processing is required in the system Mc. Graw-Hill/Irwin Copyright © 2013 by The Mc. Graw-Hill Companies, Inc. All rights reserved.

VI. Systems Design • Create a new system to solve the problem/opportunity • Prototyping – create working models of the proposed system • The Prototyping Process – prototypes are developed quickly for trial by users to obtain user feedback • User Interface Design – critical because the interface is the part of the systems closest to the user • System Specifications – listing of elements that formalize the design Mc. Graw-Hill/Irwin Copyright © 2013 by The Mc. Graw-Hill Companies, Inc. All rights reserved.

VI. Systems Design The Prototyping Process Mc. Graw-Hill/Irwin Copyright © 2013 by The Mc.

VII. Technical Note: Overview of Object. Oriented Analysis and Design v Objects – anything a programmer wants to manage or manipulate v Object-Oriented Programming (OOP) v Inheritance – ability to inherit properties of a higherorder object v Modularity – a series of interlinked yet stand-alone modules v Polymorphism – different behavior based on conditions v Encapsulation – concealing all the properties inside the object v Object-Oriented Analysis (OOA) – modeling the problem domain as an object-oriented system v Object-Oriented Design (OOD) – create solutions using objects Mc. Graw-Hill/Irwin Copyright © 2013 by The Mc. Graw-Hill Companies, Inc. All rights reserved.

Section 2 Implementing Strategic Business Systems Mc. Graw-Hill/Irwin Copyright © 2013 by The Mc.

III. Project Management v What Is a Project? – a set of activities with a beginning and an end, has goals and tasks, may have constraints (limitations) v The Process of Project Management – five phases: v Initiation and Defining – state the problem and identify objectives and resources, explore costs/benefits v Planning – identify and sequence objectives/activities v Executing – put plans into motion v Controlling – ensure project objectives and deadlines are met v Closing – install deliverables, release resources, end the project Mc. Graw-Hill/Irwin Copyright © 2013 by The Mc. Graw-Hill Companies, Inc. All rights reserved.

V. Other Implementation Activities v Testing – testing and debugging are important, does the system work as it should? v Data Conversion – new implementations often require replacing software and databases v Documentation – an important means of communication, often overlooked v Training – training users is vital, usually underbudgeted, and expensive Mc. Graw-Hill/Irwin Copyright © 2013 by The Mc. Graw-Hill Companies, Inc. All rights reserved.

V. Other Implementation Activities v Postimplementation Activities – Use and Maintenance – the longest and most costly phase of a system’s life; correct errors, improve performance, adapt to changes in the business environment v Systems Maintenance – making changes to the system v Corrective – fix errors v Adaptive – adding new functionality v Perfective – improve performance v Preventative – reduce chances of future system failure v Postimplementation Review – ensure the new system meets established business objectives Mc. Graw-Hill/Irwin Copyright © 2013 by The Mc. Graw-Hill Companies, Inc. All rights reserved.