17-1 Anup Kumar Saha AIS Development Strategies. 17-2Anup Kumar Saha Learning Objectives 1. Describe how organizations purchase application software,

Slides:



Advertisements
Similar presentations
Copyright © 2015 Pearson Education, Inc. AIS Development Strategies Chapter
Advertisements

Pertemuan 4 Membangun Teknologi Informasi Matakuliah: H0402/PENGELOLAAN SISTEM KOMPUTER Tahun: 2005 Versi: 1/0.
Acquiring Information Systems and Applications
Acquiring Information Systems and Applications
Principles and Learning Objectives
Designing new systems or modifying existing ones should always be aimed at helping an organization achieve its goals State the purpose of systems design.
Chapter 8 Information Systems Development & Acquisition
1 California State University, Fullerton Chapter 13 Developing and Managing Information Systems.
©2003 Prentice Hall Business Publishing, Accounting Information Systems, 9/e, Romney/Steinbart 17-1 Accounting Information Systems 9 th Edition Marshall.
MSIS 110: Introduction to Computers; Instructor: S. Mathiyalakan1 Systems Design, Implementation, Maintenance, and Review Chapter 13.
Fundamentals of Information Systems, Second Edition
Chapter 1 The Systems Development Environment 1.1 Modern Systems Analysis and Design Third Edition.
©2003 Prentice Hall Business Publishing, Accounting Information Systems, 9/e, Romney/Steinbart 18-1 Accounting Information Systems 9 th Edition Marshall.
Lead Black Slide. © 2001 Business & Information Systems 2/e2 Chapter 13 Developing and Managing Information Systems.
Management Information Systems, 4 th Edition 1 Chapter 16 Alternative Avenues for Systems Acquisitions.
MSIS 110: Introduction to Computers; Instructor: S. Mathiyalakan1 Systems Investigation and Analysis Chapter 12.
13.1 © 2007 by Prentice Hall 13 Chapter Building Systems.
SDLC. Information Systems Development Terms SDLC - the development method used by most organizations today for large, complex systems Systems Analysts.
System Implementations American corporations spend about $300 Billion a year on software implementation/upgrade projects.
Introduction to Systems Analysis and Design
©2003 Prentice Hall Business Publishing, Accounting Information Systems, 9/e, Romney/Steinbart 16-1 Accounting Information Systems 9 th Edition Marshall.
©2003 Prentice Hall Business Publishing, Accounting Information Systems, 9/e, Romney/Steinbart 17-1 Accounting Information Systems 9 th Edition Marshall.
1 Principles of Information Systems, Ninth Edition Chapter 13 Systems Development: Design, Implementation, Maintenance, and Review.
Welcome to CMPE003 Personal Computer Concepts: Hardware and Software Winter 2003 UC Santa Cruz Instructor: Guy Cox.
Acquiring Information Systems and Applications
Acquiring Information Systems and Applications
Copyright © 2003 by Prentice Hall Computers: Tools for an Information Age Chapter 14 Systems Analysis and Design: The Big Picture.
1.Database plan 2.Information systems plan 3.Technology plan 4.Business strategy plan 5.Enterprise analysis Which of the following serves as a road map.
Chapter 8: Systems Development Please turn your cell phone off.
Systems Analysis and Design: The Big Picture
Chapter 14: Redesigning the Organization with Information Systems Instructor: Kevin Brabazon.
Succeeding with Technology Systems Development An Overview of Systems Development Tools and Techniques for Systems Development Systems Investigation Systems.
1 Building and Maintaining Information Systems. 2 Opening Case: Yahoo! Store Allows small businesses to create their own online store – No programming.
Source: J. Hoffer ,J. George, J. Valacich
Managing the development and purchase of information systems (Part 1)
Moving into Design SYSTEMS ANALYSIS AND DESIGN, 6 TH EDITION DENNIS, WIXOM, AND ROTH © 2015 JOHN WILEY & SONS. ALL RIGHTS RESERVED. 1 Roberta M. Roth.
Copyright 2002 Prentice-Hall, Inc. Chapter 1 The Systems Development Environment 1.1 Modern Systems Analysis and Design.
11.1 © 2007 by Prentice Hall 11 Chapter Building Information Systems.
Copyright 2002 Prentice-Hall, Inc. Chapter 1 The Systems Development Environment 1.1 Modern Systems Analysis and Design Third Edition Jeffrey A. Hoffer.
Chapter 13: Developing and Implementing Effective Accounting Information Systems
Introduction to Systems Development Life Cycle
Chapter 14 Information System Development
©2003 Prentice Hall Business Publishing, Accounting Information Systems, 9/e, Romney/Steinbart 1 AIS Development Strategies.
Acquiring Information Systems and Applications
Principles of Information Systems, Sixth Edition Systems Design, Implementation, Maintenance, and Review Chapter 13.
AIS Development Strategies. Lecture 4-2 ©2003 Prentice Hall Business Publishing, Accounting Information Systems, 9/e, Romney/Steinbart Introduction This.
Lecture 31 Introduction to System Development Life Cycle - Part 2.
Fundamentals of Information Systems, Third Edition1 Systems Design Answers the question “How will the information system do what it must do to solve a.
Acquiring Information Systems and Applications
Copyright 2002 Prentice-Hall, Inc. 1.1 Modern Systems Analysis and Design Jeffrey A. Hoffer Joey F. George Joseph S. Valacich Chapter 1 The Systems Development.
Development Strategies Development Strategies Dr. Yan Xiong College of Business CSU Sacramento 10/12/03.
CHAPTER 13 Acquiring Information Systems and Applications.
Fundamentals of Information Systems, Second Edition 1 Systems Development.
Chapter 6 CASE Tools Software Engineering Chapter 6-- CASE TOOLS
Principles of Information Systems, Sixth Edition 1 Systems Design, Implementation, Maintenance, and Review Chapter 13.
Chapter 1 Introduction to Systems Design and Analysis Systems Analysis and Design Kendall and Kendall Sixth Edition.
© 2008 Prentice Hall Business Publishing Accounting Information Systems, 11/e Romney/Steinbart1 of 172 C HAPTER 19 AIS Development Strategies.
© 2005 Prentice Hall, Decision Support Systems and Intelligent Systems, 7th Edition, Turban, Aronson, and Liang 6-1 Chapter 6 Decision Support System Development.
Lecture 2 The Sources of Software. Copyright © 2011 Pearson Education, Inc. 2 Chapter 2 Introduction There are various sources of software for organizations.
Building Information Systems
Fundamentals of Information Systems, Sixth Edition
Principles of Information Systems Eighth Edition
Deck 12 Accounting Information Systems Romney and Steinbart
Accounting Information Systems 9th Edition
Systems analysis and design, 6th edition Dennis, wixom, and roth
Systems analysis and design, 6th edition Dennis, wixom, and roth
Chapter 13 Building Systems.
Presentation transcript:

17-1 Anup Kumar Saha AIS Development Strategies

17-2Anup Kumar Saha Learning Objectives 1. Describe how organizations purchase application software, vendor services, and hardware. 2. Explain how information system departments develop custom software. 3. Explain how end-users develop, use, and control computer- based information systems.

17-3Anup Kumar Saha Learning Objectives 4. Explain why organizations outsource their information systems, and evaluate the benefits and risks of this strategy. 5. Explain the principles and challenges of business process reengineering.

17-4Anup Kumar Saha Learning Objectives 6. Describe how prototypes are used to develop an AIS, and discuss the advantages and disadvantages of doing so. 7. Explain what computer-aided software engineering is and how it is used in systems development.

17-5Anup Kumar Saha Introduction Ann Christy was elated that the new system Shoppers Mart (SM) needed was approved. She needed answers to the following questions: Was the software she needed available for her to purchase? If so, how should she approach the process of buying hardware and software and selecting a vendor?

17-6Anup Kumar Saha Introduction How do companies go about developing software in-house, and is this the best approach for SM? How extensively should the system make use of end-user-developed software? If the company decided to develop the system in-house, should it try and speed up the development process by using prototyping or computer-assisted software engineering?

17-7Anup Kumar Saha Introduction Should SM just make the needed improvements to its existing system, or should it consider reengineering its business processes and then develop a system to support the new processes? Was outsourcing the information system a viable alternative to obtaining a new system? Did the benefits outweigh its risks?

17-8Anup Kumar Saha Introduction This chapter discusses three ways to obtain a new information system: purchasing prewritten software, developing software in-house, and hiring an outside company (outsourcing). It also presents ways of speeding up or improving the development process – business process reengineering, prototyping and computer-aided software engineering (CASE) tools.

17-9Anup Kumar Saha Learning Objective 1 Describe how organizations purchase application software, vendor services, and hardware.

17-10Anup Kumar Saha Purchase Software Canned software is written by software development companies and is sold on the open market to a broad range of users with similar requirements. Turnkey systems are a combination of software and hardware sold as a package. The vendor installs the entire system and user needs only to “turn the key”.

17-11Anup Kumar Saha Purchase Software, continued The Internet has given companies a new way to acquire software: Application service providers (ASPs) host Web-based software on their computers and deliver the software to their clients over the Internet.

17-12Anup Kumar Saha Purchasing Software and The SDLC Companies that buy rather than develop AIS software still go through the systems development life cycle (SDLC). 1. Systems analysis 2. Conceptual design 3. Physical design 4. Implementation and conversion 5. Operation and maintenance

17-13Anup Kumar Saha The Systems Acquisition Process Will package meet needs? Develop software internally Send RFP for hardware, if necessary Evaluate proposal No Yes Investigate software packages Can package be modified? Send RFP for software and hardware No Yes Select best combination Yes

17-14Anup Kumar Saha Learning Objective 2 Explain how information system departments develop custom software.

17-15Anup Kumar Saha Development by In-House IS Department Most often, organizations develop their own custom software, because canned software that fit their specific needs is not available. Developing custom software is difficult and error-prone. It also consumes a great deal of time and resources.

17-16Anup Kumar Saha Custom Software Development by an Outside Company When contracting with an outside organization, a company should maintain control over the development process. Some guidelines: Carefully select a developer Sign a contract Plan and monitor each step Maintain effective communication Control all costs

17-17Anup Kumar Saha Learning Objective 3 Explain how end users develop, use, and control computer-based information systems.

17-18Anup Kumar Saha End-User-Developed Software End-user computing (EUC) is the hands-on development, use, and control of computer- based information systems by users. With the advent of inexpensive PCs and powerful, inexpensive software, users began developing their own systems to create and store data, access and download company data, and share data and computer resources in networks.

17-19Anup Kumar Saha End-User-Developed Software Examples of end user development uses: Retrieving information from company databases to produce simple reports or to answer one-time queries Performing “what if” sensitivity or statistical analyses Developing applications using prewritten software (spreadsheet or database system) Preparing schedules and lists, such as depreciation schedules, accounts receivable aging, and loan amortizations

17-20Anup Kumar Saha Benefits of End-User- Developed Software Benefits of End-User Computing User creation, control, and implementation Systems that meet user needs Timeliness Freeing up IS resources Versatility and ease of use

17-21Anup Kumar Saha Risks of End-User- Developed Software Risks of End-User Computing Logic and development errors Inadequately tested applications Inefficient systems Poorly controlled and documented systems Systems incompatibility Duplication of systems Increased costs

17-22Anup Kumar Saha Managing and Controlling End-User Computing Organizations use several different approaches to mange and control end-user computing. For example, a help desk can encourage, support, coordinate and control end-user activities.

17-23Anup Kumar Saha Functions of a Help Desk What are some duties of the help desk? – Providing hot-line assistance to help resolve problems – Serving as a clearinghouse for information, coordination, and assistance training end users, and providing corresponding technical maintenance and support – Evaluating new end-user hardware and software products – Assisting with application development – Developing and implementing standards – Controlling corporate data

17-24Anup Kumar Saha Learning Objective 4 Explain why organizations outsource their information systems, and evaluate the benefits and risks of this strategy.

17-25Anup Kumar Saha Outsource the System What is outsourcing? It is hiring an outside company to handle all or part of an organization’s data processing activities. In a mainframe outsourcing agreement, the outsourcers buy their client’s computers and hire all or most of the client’s employees.

17-26Anup Kumar Saha Outsource the System In a client/server or PC outsourcing agreement, an organization outsources a particular service, a segment of its business, a particular function, or PC support.

17-27Anup Kumar Saha Outsource the System Benefits of Outsourcing A business and information solution Asset utilization Access to greater expertise and more advanced technology Lower costs Improved development time Elimination of peaks and valleys usage Facilitation of downsizing

17-28Anup Kumar Saha Outsource the System Risks of Outsourcing Inflexibility Loss of control of system and/or data Reduced competitive advantage Locked-in system Unfulfilled goals Possibility of poor service

17-29Anup Kumar Saha Learning Objective 5 Explain the principles and challenges of business process reengineering.

17-30Anup Kumar Saha Business Processes Reengineering What is business process reengineering (BPR)? It is the thorough analysis and complete redesign of business process and information systems to achieve performance improvements. It is a process that challenges traditional organizational values and cultures associated with underperformance.

17-31Anup Kumar Saha Business Processes Reengineering BPR reduces a company to its essential business processes and focuses on why they are done rather than on the details of how they are done. It completely reshapes organizational work practices and information flows to take advantage of technological advancements.

17-32Anup Kumar Saha Principles of Reengineering What are the seven principles of business processing reengineering? 1. Organize around outcomes, not tasks. 2. Require those who use the output to perform the process. 3. Require those who produce information to process it.

17-33Anup Kumar Saha Principles of Reengineering 4. Centralize and disperse data. 5. Integrate parallel activities 6. Empower workers, use built-in controls, and flatten the organization chart. 7. Capture data once, at its source.

17-34Anup Kumar Saha Challenges Faced by Reengineering Efforts What are some of the obstacles to reengineering efforts? Tradition Resistance Time requirements Risk Lack of management support Skepticism Retraining Controls

17-35Anup Kumar Saha Learning Objective 6 Describe how prototypes are used to develop an AIS, and discuss the advantages and disadvantages of doing so.

17-36Anup Kumar Saha Prototyping What is prototyping? – an approach to systems design in which a simplified working model of a system is developed. A prototype, or “first draft,” is quickly and inexpensively built and provided to users for testing.

17-37Anup Kumar Saha Prototyping What four steps are involved in developing a prototype? 1. Identify basic systems requirements. 2. Develop an initial prototype that meets the agreed-on requirements. 3. Users identify changes, developers make changes, and the system is turned over to the user. 4. Use the system approved by the users.

17-38Anup Kumar Saha Benefits of Prototyping Advantages of Prototyping Better definition of user needs Higher user involvement and satisfaction Faster development time Fewer errors More opportunity for changes Less costly

17-39Anup Kumar Saha Disadvantages of Prototyping Disadvantages of Prototyping Significant user time Less efficient use of system resources Incomplete systems development Inadequately tested and documented systems Negative behavioral reactions Unending development

17-40Anup Kumar Saha Learning Objective 7 Explain what computer-aided software engineering is and how it is used in systems development.

17-41Anup Kumar Saha Computer-Aided Software Engineering (CASE) CASE is an integrated package of computer-based tools that automate important aspects of the software development process. CASE tools are used to plan, analyze, design, program, and maintain an information system. They are also used to enhance the efforts of managers, users, and programmers in understanding information needs.

17-42Anup Kumar Saha Computer-Aided Software Engineering (CASE) CASE tools do not replace skilled designers; instead they provide a host of self-integrated tools that give developers effective support for all SDLC phases. CASE software typically has tools for strategic planning, project and system management, database design, screen and report layout, and automatic code generation.

17-43Anup Kumar Saha Computer-Aided Software Engineering (CASE) Advantages of CASE Technology Improved productivity Improved program quality Cost savings Improved control procedures Simplified documentation

17-44Anup Kumar Saha Computer-Aided Software Engineering (CASE) Disadvantages of CASE Technology Incompatibility Cost Unmet expectations

17-45Anup Kumar Saha Case Conclusion What did Ann Christy decide? – against outsourcing the AIS What did she think about prototyping? – that it would not work well What did she think about reengineering? – that the system did not need reengineering

17-46Anup Kumar Saha Case Conclusion What were her options? – purchase a system or design one in-house. No matter which approach she chose, Ann wanted to facilitate as much end-user development as was practical and useful.

17-47Anup Kumar Saha End