1 / 82

Developing Business/IT Solutions

Module IV – Development Processes. Developing Business/IT Solutions. Learning Objectives.

berg
Télécharger la présentation

Developing Business/IT Solutions

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Module IV – Development Processes Developing Business/IT Solutions

  2. Learning Objectives • 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 an e-business system. • Explain how prototyping improves the process of systems development for end users and IS specialists. • Identify the activities involved in the implementation of new information systems. • Describe several evaluation factors that should be considered in evaluating the acquisition of hardware, software, and IS services. • Identify several change management solutions for end user resistance to the implementation of new information systems.

  3. Developing Business/IT Solutions Section I • The Systems Approach • Information Systems Development or Application Development • Real World Case 1- Blue Cross, AT&T Wireless, and CitiStreet Click to go to Case 1

  4. The Systems Approach • Recognize and Define Problem Using Systems Thinking • Develop and Evaluate Alternatives • Select a Solution • Design the System Solution • Implement and Evaluate the Success of the Designed System

  5. The Systems Approach • Using Systems Thinking • The Fifth Discipline • Seeing Relationships Among Systems • Seeing Processes of Change Among Systems • Systems Context • An Example of Systems Thinking…

  6. Poor Sales Management ? Inadequate Selling Effort ? Out-of-Date Sales Procedures ? Poor Sales Performance ? The Systems Approach An Example of Systems Thinking Control Incorrect Sales Information? Feedback Input Processing Output

  7. Systems Investigation Product Feasibility Study Systems Analysis Product Functional Requirements Systems Design Product System Specifications Systems Implementation Product Operational System Systems Maintenance Product Improved System The Systems Approach IS Development Cycle Understand the Business Problem or Opportunity Develop an Information System Solution Implement the Information System Solution

  8. Identify an End User’s Business Requirements Develop Business System Prototypes Revise the Prototypes to Better Meet End User Requirements Use and Maintain the Accepted Business System Systems Development Cycle Systems Development Life Cycle The Prototyping Process • Investigation/Analysis • Analysis/Design Prototyping Cycle • Design/ Implementation Maintenance Cycle • Implementation/ Maintenance

  9. Systems Development Cycle Agile Systems Development Typical Prototyping-Based Systems Development Process

  10. Systems Development Cycle Frito-Lay Inc.: Failure and Success in Systems Development • National Sales Team Collaboration Difficult • Development of Web-Based Enterprise Knowledge Management Portal • Support for Collaboration • Omitted Features Had to be Added • Resulted in Better Collaboration and Improved Access to Knowledge

  11. Systems Development Process Starting the Process • Feasibility Studies • Organizational Feasibility • Economic Feasible • Technical Feasibility • Cost/Benefit Analysis • Intangible Costs • Intangible Benefits

  12. IT Proposals for Addressing Strategic Business Priorities Planning for Application Development and Implementation Business Case for Investing in e-Business Projects Systems Development Process Starting the Process Key Objectives Action Plan Feedback Feedback

  13. Systems Development Process Starting the Process Feasibility Factors

  14. Systems Development Process Starting the Process How a Feasibility Study Might Measure a Proposal

  15. Systems Development Process Starting the Process Possible Benefits of New System

  16. Systems Analysis • Organizational Analysis • Analysis of the Present System • Hardware • Software • Network • People Resources • Document Activities of Input, Processing, Output, Storage, and Control Systems

  17. Systems Analysis Buyer Zone and OfficeMax: Evaluating Customer Website Experiences

  18. Systems Analysis Buyer Zone and OfficeMax: Evaluating Customer Website Experiences • Websites Failed to Support the Purchase-or-Lease Decision Process • Should Support Decision Processes Before Pushing Product • Provide the Right Tools at the Right Time • Integrate Related Tasks

  19. Systems Analysis Functional Requirements for a Proposed e-Commerce System What Should be Done – Not How…

  20. User Interface Design Data Design Process Design Systems Design Systems Analysis Describes What is to be Done… Systems Design Specifies How Systems Design • Screen, Form, Report, and Dialog Design • Data Element Structure Design • Program and Procedure Design

  21. Systems Design User Interface Design

  22. Systems Design User Interface Design Examples…

  23. Systems Design Priceline.com: Designing a User Interface • Simplifying the Web Interface • Simpler and More Compelling Site Brought 50% Increase in Visitors • Less Decision Making by User is a Good Thing • Much More Successful Design

  24. Systems Design Examples of Systems Specifications for a New e-Commerce System

  25. Control What controls are needed to protect against accidental loss or damage? Is there a need to control access to data used by the application? Processing What operations on the inputs are needed to produce the desired output? What software can most effectively support those operations? Input What data are available, in what form? Output What information is needed by end users and in what form should the output be presented? Storage Does the application use previously stored data? Does it create data that must be stored for future use by this or other applications? End User Development Focus on Processing Activity Components

  26. End User Development Focus on Processing Activity Components • Inputs • Outputs • Processing • Storage • Control • Doing End User Development

  27. End User Development MS FrontPage Development Tool

  28. End User Development Encouraging Intranet Website Development

  29. End User Development Providence Health System: End User Web Development • Had Outdated and Incorrect Website Content • IT Gave Up Control to Encourage Group Content to be Added to Internet and Intranet Sites Using Development Tools • MS FrontPage Used to Empower Other Departments at Little Cost

  30. ImplementingBusiness Systems Section II • System Design • Implementation • Maintenance • Challenges and Strategies Real World Case 2- Intercontinental Hotels, Del Taco, and Cardinal Health Click to go to Case 2

  31. Implementation Activities Acquisition of Hardware, Software, and Services • Conversion • Parallel • Pilot • Phased • Plunge Software Development or Modification Data Conversion End User Training Implementing New Systems Overview of the Implementation Process

  32. Implementing New Systems Zurich North America: IT Project Management • Desire for Full Project Transparency Through Intranets • 10-20% of Incomes Based Upon Company Success • Wanted Project Management Agreements in Writing • No Projects Without a Paying Customer

  33. Implementing New Systems Evaluating Hardware, Software, and Services

  34. Implementing New Systems Examples from IBM of Hardware, Software, and IS Services

  35. Implementing New Systems Ten Major Hardware Evaluation Factors

  36. Implementing New Systems Select Software Evaluation Factors

  37. Implementing New Systems Evaluating IS Service Factors

  38. Implementing New Systems OshKosh B’Gosh, Inc.: Evaluating IT Vendors and Products • Used System to Connect Vendors • Work to Design Requirements First – Then Seek Solutions • Check References on Vendor Applications • Involve End-User in the System Selection Process

  39. Implementing New Systems Other Implementation Activities • Testing • Data Conversion • Documentation • Computer-Aided Systems Engineering (CASE) • Training

  40. Implementing New Systems Clarke American Checks: Web-Based ERP Training • Use of Website For Collaborative Training on New ERP Software • Watching or Performing Simulated Transactions • Self-Paced Training Well Liked and Costs Less • 75% Savings Over Instructor-Led Training

  41. Implementing New Systems Example Implementation Plan

  42. Implementing New Systems Conversion Methods • Parallel Conversion • Phased Conversion • Pilot Conversion • Plunge or Direct Cutover • Graphically…

  43. Implementing New Systems Conversion Methods Old System Parallel New System Pilot Old System New System Phased Old System New System Plunge Old System New System

  44. Implementing New Systems IS Maintenance Systems Maintenance Post-Implementation Review

  45. Implementing New Systems GM Locomotive Group: Failure in System Implementation • Builder of Diesel-Electric Locomotives • Failure in Launch of ERP Application in 2001 • Parts Business Virtually Stopped • Undertook Emergency 6 Month Turnaround • SAP System Reconfigured, Flushed and Replaced Data • Legacy Mainframe Couldn’t Handle New System • System Didn’t Perform • Some Outsourcing Occurring

  46. Managing Organizational Change Resistance to Change • End-User Resistance • End-User Involvement

  47. Managing Organizational Change Resistance to Change Obstacles to Knowledge Management 3% 9% User Resistance to Sharing Knowledge Immaturity of Technology Immaturity of Knowledge Management Industry 15% 53% Cost Lack of Need 20%

  48. Change Management Crane Engineering: Overcoming User Resistance to CRM • Difficulty in Changing Habits of Sales Persons • Fear of Windows and CRM • Sell Advantages to Sales Staff to Win Acceptance • Move From Product to a Customer Centered Approach • Requires Structural Changes Throughout All Aspects of the Firm

  49. Change Management Focus is on People • Change Action Plan • Change Sponsors • Change Teams • Encouraging Open Communications • Receiving Feedback • Work Within the Company Culture

  50. Change Management Duke Energy: A Guerilla Approach to Business Change • e-Team of Advocates Went Throughout Company Launching Internet Initiatives • In 18 Months Team Had Saved $52 Million • Search for Other Activities for the Internet • New Team Launched Initiatives • Used Mantra “Invest Little-Save Big” • Launched Many Projects

More Related