1. 1 Developing Business/Information Technology Solutions 10

2. 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 propose information systems solutions to simple business problems. 10 Learning Objectives

3. 3 Describe 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. 10 Learning Objectives (continued)

4. 4 Identify the activities involved in the implementation of new information systems. Describe evaluation factors that should be considered in evaluating the acquisition of hardware, software, and IS services. 10 Learning Objectives (continued)

5. 5 Developing e-Business Systems 10 Section I

6. 6 The systems approach to problem solving applied to the development of information system solutions to business problems. 10 Information Systems Development

7. 7 The systems approach to problem solving –Recognize and define a problem or opportunity using systems thinking –Develop and evaluate alternative system solutions 10 The Systems Approach

8. 8 Systems approach to problem solving (continued) –Select the system solution that best meets your requirements –Design the selected system solution –Implement and evaluate the success of the designed system 10 The Systems Approach (continued)

9. 9 Systems Thinking –“seeing the forest AND the trees” Seeing “interrelationships” among “systems” rather than linear cause-and- effect chains when events occur Seeing “processes” of change among “systems” rather than discrete “snapshots” of change, whenever change occurs. 10 The Systems Approach (continued)

10. 10 –Systems thinking (continued) Use a systems context –Try to find systems, subsystems, and components of systems in any situation you are studying 10 The Systems Approach (continued)

11. 11 Investigation Analysis Design Implementation Maintenance 10 The Systems Development Cycle

12. 12 The rapid development and testing of working models of new applications in an interactive, iterative process. Sometimes called rapid application design (RAD). Simplifies and accelerates systems design. 10 Prototyping

13. 13 The prototyping process 10 Prototyping (continued)

14. 14 Systems Investigation Phase –Feasibility studies Organizational feasibility Economic feasibility Technical feasibility Operational feasibility 10 Starting the Systems Development Process

15. 15 10 Starting the Systems Development Process (continued)

16. 16 10 Starting the Systems Development Process (continued)

17. 17 –Cost/Benefit Analysis Tangible costs Intangible costs Tangible benefits Intangible benefits 10 Starting the Systems Development Process (continued)

18. 18 10 Starting the Systems Development Process (continued)

19. 19 Systems analysis is an in-depth study of end user information needs that produces functional requirements. 10 Systems Analysis

20. 20 Traditionally involves a detailed study of… –Information needs of the company & end users –Activities, resources, & products of one or more of the present information systems –The IS capabilities required to meet information needs of the company, the end users, and all business stakeholders that may use the system 10 Systems Analysis (continued)

21. 21 Organizational analysis –Study Management structure The people Business activities Environmental systems The current information system 10 Systems Analysis (continued)

22. 22 Analysis of the present system –Analyze how the present system.. Uses hardware Uses software Is networked Uses people resources to convert data resources into information products. How the IS activities of input, processing, output, storage, and control are accomplished. 10 Systems Analysis (continued)

23. 23 Functional requirements analysis –What type of information does each business activity require? Format, volume, frequency, response times –What are the information processing capabilities required? Input, processing, output, storage, control 10 Systems Analysis (continued)

24. 24 Functional requirements analysis (continued) –Finally, develop functional requirements End user information requirements that are not tied to the hardware, software, network, data, and people resources –Goal – identify what should be done, not how to do it. 10 Systems Analysis (continued)

25. 25 Specifies HOW the system will meet the information needs of users Focuses on three major products –User interface design –Data design Database structures –Process design Processing and control procedures 10 Systems Design

26. 26 User interface design –Focuses on supporting the interactions between end users and the computer- based applications Display screens Interactive user/computer dialogues Audio responses Forms, documents, and reports 10 Systems Design (continued)

27. 27 System specifications –Formalizes the design of the application’s user interface methods & products –Formalizes database structures –Formalizes processing and control procedures 10 Systems Design (continued)

28. 28 IS professionals play a consulting role –Training in the use of application packages –Assistance with the selection of hardware and software –Assistance in gaining access to organization databases –Assistance in the analysis, design, and implementation of your application 10 End User Development

29. 29 The application development process –Output What information is needed and in what form? –Input What data are available? From what sources? In what form? 10 End User Development (continued)

30. 30 The application development process (continued) –Processing What operations or transformation processes will be required to convert available inputs into the desired output? What software package can best perform the required operations? 10 End User Development (continued)

31. 31 The application development process (continued) –Storage –Control How will you protect against accidental loss or damage to end user files? 10 End User Development (continued)

32. 32 10 End User Development (continued)

33. 33 Implementing e-Business Systems 10 Section II

34. 34 This is the actual deployment of the information technology system. Follows the investigation, analysis, and design stages of the systems development cycle. 10 Implementation

35. 35 10 Implementing New Systems

36. 36 May require suppliers to present bids and proposals based on system specifications –Minimum acceptable physical & performance characteristics for all hardware and software requirements are established –Large businesses and government agencies formalize requirements by listing them in a Request for Proposal (RFP) or a Request for Quotation (RFQ) 10 Evaluating Hardware, Software, & Services

37. 37 May use a scoring system for evaluation –Determine evaluation factors and assign points Performance of hardware and software must be demonstrated and evaluated –May use benchmark test programs 10 Evaluating Hardware, Software, and Services (continued)

38. 38 Hardware evaluation factors –Performance Speed, capacity, throughput –Cost Lease or purchase price Cost of operations and maintenance 10 Evaluating Hardware, Software, and Services (continued)

39. 39 Hardware evaluation factors (continued) –Reliability Risk of malfunction & maintenance requirements Error control and diagnostic features –Compatibility With existing hardware and software? With hardware & software provided by competing suppliers? 10 Evaluating Hardware, Software, and Services (continued)

40. 40 Hardware evaluation factors (continued) –Technology Year of product life cycle Does it use a new, untested technology? Does it run the risk of obsolescence? –Ergonomics “human factors engineered”? User-friendly? Safe, comfortable, easy to use? 10 Evaluating Hardware, Software, and Services (continued)

41. 41 Hardware evaluation factors (continued) –Connectivity Easily connected to WANs and LANs that use different types of network technologies and bandwidth alternatives? –Scalability Can it handle the processing demands of end users, transactions, queries, & other processing requirements? 10 Evaluating Hardware, Software, and Services (continued)

42. 42 Hardware evaluation factors (continued) –Software Is system and application software available that can best use this hardware? –Support Is support available? 10 Evaluating Hardware, Software, and Services (continued)

43. 43 Software evaluation factors –Quality Bug free? –Efficiency Well-developed system of program code that does not use much CPU time, memory capacity, or disk space? 10 Evaluating Hardware, Software, and Services (continued)

44. 44 Software evaluation factors (continued) –Flexibility Can it handle our processes easily without major modification? –Security Does it provide control procedures for errors, malfunctions, and improper use? 10 Evaluating Hardware, Software, and Services (continued)

45. 45 Software evaluation factors (continued) –Connectivity Web-enabled? –Language Is the programming language familiar to internal software developers? 10 Evaluating Hardware, Software, and Services (continued)

46. 46 Software evaluation factors (continued) –Documentation Well-documented? Help screens and helpful software agents? –Hardware Does existing hardware have the features required to best use this software? 10 Evaluating Hardware, Software, and Services (continued)

47. 47 Software evaluation factors (continued) –Other factors Performance, cost, reliability, availability, compatibility, modularity, technology, ergonomics, scalability, and support characteristics 10 Evaluating Hardware, Software, and Services (continued)

48. 48 Evaluating IS Services –Performance Past performance in view of past promises –Systems development Are website and other e-business developers available? Quality and cost 10 Evaluating Hardware, Software, and Services (continued)

49. 49 Evaluating IS services (continued) –Maintenance Is equipment maintenance provided? Quality and cost –Conversion What systems development & installation services will they provide during the conversion period? 10 Evaluating Hardware, Software, and Services (continued)

50. 50 Evaluating IS services (continued) –Training Provided? Quality and cost –Backup Are similar computer facilities available nearby for emergency backup purposes? 10 Evaluating Hardware, Software, and Services (continued)

51. 51 Evaluating IS services (continued) –Accessibility Services from local or regional sites? Customer support center? Customer hot line? –Business position Financially strong with good industry market prospects? 10 Evaluating Hardware, Software, and Services (continued)

52. 52 Evaluating IS services (continued) –Hardware Provide a wide selection of compatible hardware devices and accessories? –Software Offer a variety of useful e-business software and application packages? 10 Evaluating Hardware, Software, and Services (continued)

53. 53 Testing –May involve website performance testing –Testing and debugging software –Testing new hardware –Reviewing prototypes of displays, reports, and other output –Should occur throughout the development process 10 Other Implementation Activities

54. 54 Documentation –Sample data entry screens, forms, and reports are examples. –Serves as a method of communication among the people responsible for developing, implementing, and maintaining the system –A detailed record of the system’s design –Important in diagnosing errors & making changes 10 Other Implementation Activities (continued)

55. 55 Training –End users must be trained to operate a new e-business system or implementation will fail –May be limited in scope or may involve all aspects of the proper use of the new system –Managers and end users must be educated in how the new technology impacts business operations and management 10 Other Implementation Activities (continued)

56. 56 Conversion methods –Parallel Both old and new systems are operated until the project development team and end users agree to switch completely –Phased Only parts of the new application or only a few locations at a time are converted 10 Other Implementation Activities (continued)

57. 57 Conversion methods (continued) –Pilot One department or other work site serves as a test site –Plunge A direct cutover to the newly developed system 10 Other Implementation Activities (continued)

58. 58 10 Other Implementation Activities (continued)

59. 59 IS Maintenance –Systems maintenance –Postimplementation review 10 Other Implementation Activities (continued)

60. 60 Why has prototyping become a popular way to develop e-business applications. What are prototyping’s advantages and disadvantages? What are the three most important factors you would use in evaluating computer hardware? Computer software? 10 Discussion Questions

61. 61 Assume that in your first week on a new job you are asked to use a type of business software that you have never used before. What kind of user training should your company provide to you before you start? What is the difference between the parallel, plunge, phased, and pilot forms of IS conversion? Which strategy is best? 10 Discussion Questions (continued)

62. 62 What are several key factors in designing a successful e-commerce or internet website? 10 Discussion Questions (continued)

63. 63 References James A. O'Brien; George M. Marakas. Management Information Systems: Managing Information Technology in the Business Enterprise 6th Ed., Boston: McGraw-Hill/ Irwin,2004 10