1. Developing Business/IT Solutions Chapter 12 McGraw-Hill/IrwinCopyright © 2011 by The McGraw-Hill Companies, Inc. All rights reserved.

2. 12-2 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 Describe and give examples to illustrate how you might use each of the steps of the information systems development cycle to develop and implement a business information system Learning Objectives

3. 12-3 Learning Objectives Explain how prototyping can be used as an effective technique to improve the process of systems development for end users and IS specialists Understand the basics of project management and their importance to a successful system development effort Identify the activities involved in the implementation of new information systems

4. 12-4 Learning Objectives Compare and contrast the four basic system conversation strategies Describe several evaluation factors that should be considered in evaluating the acquisition of hardware, software, and IS services

5. 12-5 The Systems Approach Problem solving technique Interrelated activities –Recognize and define a problem or opportunity using systems thinking –Develop and evaluate alternative system solutions –Select the solution that best meets your requirements –Design the selected system solution –Implement and evaluate the success of the system

6. 12-6 Types of Feasibility Studies Operational –Fix the problem, fit the organization Economic –Cost/Benefit Analysis Technical –Components and time available Human Factors –Right people and roles available Legal/Political –Government, patent, or license restrictions

7. 12-7 Types of Analysis Organizational –Structure, people, activities Present System –Hardware, software, network, input, output, processing Logical –What the current system does –Not concerned with how it works

8. 12-8 User Interface Design Supports interactions between end users and computer-based applications –Get help from end-users –Designers create attractive and efficient forms –Frequently a prototyping process –Produces detailed design specifications

9. 12-9 System Specifications Components of formal design –User interface methods and products –Database structures –Processing procedures –Control procedures Examples of System Specifications –User interface specifications –Database specifications –Software specifications –Hardware and network specifications –Personnel specifications

10. 12-10 Object-Oriented Analysis and Design Object – anything a programmer needs manipulated Object-Oriented Programming (OOP) techniques: –Inheritance –Modularity –Polymorphism –Encapsulation Object-Oriented Analysis (OOA) –Model of object interaction, not solution Object-Oriented Design (OOD) –Solution based on constraints

11. 12-11 What is a Project? Every project has –A set of activities with a clear beginning and end –Goals –Objectives –Tasks –Limitations or constraints –A series of steps or phases Managing a project effectively requires –Process –Tools –Techniques

12. 12-12 Hardware Evaluation Factors Performance Cost Reliability Compatibility Technology Ergonomics Connectivity Scalability Software Support

13. 12-13 Software Evaluation Factors Most Hardware Evaluation Factors Apply Quality Efficiency Flexibility Security Connectivity Maintenance Documentation Hardware Overall Rating –Software that is slow, hard to use, bug-filled, or poorly documented is not a good choice at any price

14. 12-14 IS Service Evaluation Factors IS evaluation factors include –Performance –Systems development –Maintenance –Conversion –Training –Backup facilities and services –Accessibility to sales and support Business position and financial strength –Hardware selection and compatibility –Software packages offered

15. 12-15 Post-Implementation Activities System Maintenance –Corrective: fix bugs and logical errors –Adaptive: add new functionality –Perfective: improve performance –Preventive: reduce chances of failure Post Implementation Review –Correct Errors –Periodic review/audit Single most costly activity