Chapter 15 Systems Development

Slides:



Advertisements
Similar presentations
Fundamentals of Information Systems, Sixth Edition
Advertisements

Chapter 12 Systems Development Three common methods for MIS development: The systems development life cycle (SDLC) Prototyping End-user development Five.
The System Development Life Cycle
1 Chapter 15 Systems Development. 2 Learning Objectives  When you finish this chapter, you will: Understand the systems development life cycle. List.
Acquiring Information Systems and Applications
Acquiring Information Systems and Applications
Principles and Learning Objectives
Chapter 8 Information Systems Development & Acquisition
Chapter Extension 20 Outsourcing © 2008 Pearson Prentice Hall, Experiencing MIS, David Kroenke.
1 IS371 WEEK 8 Last and Final Assignment Application Development Alternatives to Application Development Instructor Online Evaluations.
Professor Michael J. Losacco CIS 1150 – Introduction to Computer Information Systems Systems Analysis and Design Chapter 12.
Pertemuan Matakuliah: A0214/Audit Sistem Informasi Tahun: 2007.
Management Information Systems, 4 th Edition 1 Chapter 16 Alternative Avenues for Systems Acquisitions.
SDLC. Information Systems Development Terms SDLC - the development method used by most organizations today for large, complex systems Systems Analysts.
The Agile vs. Waterfall Methodologies Systems Development:  the activity of creating new or modifying / enhancing existing business systems.  Objectives.
CHAPTER 19 Building Software.
Building and Maintaining Systems
Acquiring Information Systems and Applications
Chapter 17 Acquiring and Implementing Accounting Information Systems
Acquiring Information Systems and Applications
Introduction to Computer Technology
Systems Analysis and Design: The Big Picture
Initiating and Planning Systems Development projects
Succeeding with Technology Systems Development An Overview of Systems Development Tools and Techniques for Systems Development Systems Investigation Systems.
Management Information Systems, 4 th Edition 1 Chapter 15 Systems Development.
Chapter 15 Systems Development. 2 Learning Objectives When you finish this chapter, you will  Understand the systems development life cycle.  Be able.
1 Building and Maintaining Information Systems. 2 Opening Case: Yahoo! Store Allows small businesses to create their own online store – No programming.
SYSTEMS DEVELOPMENT Phases, Tools, and Techniques
Laudon & Laudon: Canadian Edition
Management Information Systems By Effy Oz & Andy Jones
8-1 Chapter 8 Information Systems Development & Acquisition.
Chapter 16 Alternative Avenues for Systems Acquisitions
Information Systems Analysis and Design
Information Systems Development. Outline  Information System  Systems Development Project  Systems Development Life Cycle.
Chapter 13: Developing and Implementing Effective Accounting Information Systems
1 ISA&D7‏/8‏/ ISA&D7‏/8‏/2013 Systems Development Life Cycle Phases and Activities in the SDLC Variations of the SDLC models.
Systems Development AIMS 2710 R. Nakatsu. Overview Why do IT projects succeed and fail? Two philosophies of systems development –Systems Development Life.
Software Engineering Management Lecture 1 The Software Process.
Systems Development MBAA 609 R. Nakatsu. Overview of Today’s Lecture Why do IT projects succeed and fail? Two philosophies of systems development –Systems.
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
Computers Are Your Future © 2008 Prentice Hall, Inc.
CHAPTER 13 Acquiring Information Systems and Applications.
1 Chapter 15 Systems Development I. Systems Development Life Cycle (SDLC) PlanningAnalysisDesignImplementationSupport How does the IS fit in firm’s plans?
The Traditional System Development Life Cycle There are a number of important steps in the creation of a system, regardless of which approach you use.
IS Analysis and Design. SDLC Systems Development Life Cycle Break problems into management review stages Control cost and time Works best with well understood.
Module 4: Systems Development Chapter 14: Design And Implementation.
Chapter 11: Alternative Approach - Purchasing Systems.
Systems Development AIMS 2710 R. Nakatsu. Overview Two philosophies of systems development –Systems Development Life Cycle (SDLC) –Prototyping Alternative.
Software Project Management Iterative Model & Spiral Model.
Chapter 8 Process Implementation Reference: Tan, A. (2007). Business Process Reengineering in Asia: A Practical Approach, Pearson Education, Singapore.
Chapter 6 SYSTEMS DEVELOPMENT Phases, Tools, and Techniques.
CHAPTER 13 Acquiring Information Systems and Applications.
10-1 McGraw-Hill/Irwin Copyright © 2007 by The McGraw-Hill Companies, Inc. All rights reserved.
Fundamentals of Information Systems, Third Edition2 Principles and Learning Objectives Effective systems development requires a team effort of stakeholders,
Management Information Systems by Prof. Park Kyung-Hye Chapter 13 (14th Week) Choices in Systems Acquisition 13.
Accounting systems design & evaluation 9434SB 18 March 2002.
Information Systems Development. Outline  Information System  Systems Development Project  Systems Development Life Cycle.
Information Systems Development
Software Engineering Management
Fundamentals of Information Systems, Sixth Edition
Fundamentals of Information Systems, Sixth Edition
Information Systems Development
Management Information Systems By Effy Oz & Andy Jones
Chapter 12 Information System Development
CHAPTER 10 METHODOLOGIES FOR CUSTOM SOFTWARE DEVELOPMENT
Chapter 8 Information Systems Development & Acquisition
Systems Development An Overview of Systems Development
Week 10 Systems Development
Presentation transcript:

Chapter 15 Systems Development

Why Develop an IS? Three phenomena that trigger IS development An opportunity (proactive) A problem (reactive) A directive

The Systems Development Life Cycle (SDLC)

The Systems Development Life Cycle (SDLC) Analysis Determines what need the system will satisfy Investigation Developers interview managers and perspective users to determine business needs. Three feasibility studies performed.

The Systems Development Life Cycle (SDLC) The Technical Feasibility Study Ensures hardware and software exist to build the system The Economic Feasibility Study Benefits of the system weighed against the cost The Operational Feasibility Study Determines if system will be used as intended

The Systems Development Life Cycle (SDLC) Design Logical Design Translation of user requirements into detailed functions of the system Physical Design Construction Systems Testing Phases in systems design

The Systems Development Life Cycle (SDLC) Implementation Training Conversion Parallel Conversion Phased Conversion Cold Turkey Pilot Conversion

The Systems Development Life Cycle (SDLC) Support Activities in systems support

Prototyping Systems developed using an Iterative Process Purpose is to develop a working model as quickly as possible, which can be tweaked and revised Significantly shortens systems development backlog Can increase risk of incompatibility and other unforeseen mishaps

Prototyping When to prototype and when not to prototype In prototyping, refinement of the system continues until users are satisfied. When to prototype and when not to prototype

Project Management Project Management Goals Complete the project on time. Complete the project within budget. Meet requirements. Meet expectations. Dimensions of project management IS development projects: challenges and failures

Project Management Project Management Functions Communication Management Schedule Management Quality Management Financial Management Resource Management

Systems Development Led by End Users JAD: An example of User-led Systems Development Joint Application Development (JAD): method to be used in SDLU Uses six-step process to take the team through planning and design The six steps of JAD

Systems Development Led by End Users JAD Critical Success Factors All participants must be committed to JAD process. Customers and IS people must agree on project’s scope. Sponsor must be supportive and involved. Team members must be empowered decision makers. Business objectives must be clearly defined. Business process must be understood. Team members must be able to meet two or more days per week. Members must be committed to the team.

Chapter-16 Alternative Avenues for Systems Acquisitions

Outsourcing Short-term contractual relationship with a service firm to develop a specific application Long-term contractual relationship with a service firm to take over all or some of an organization’s IS functions

Advantages of Outsourcing Improved financial planning Reduced license and maintenance fees Increased attention to core business Shorter implementation cycles Reduction of personal and fixed costs Increased access to highly qualified know-how? Increased security

Outsourcing Risks of Outsourcing Loss of control Loss of experienced employees Risks of losing a competitive advantage

Outsourcing Risks of outsourcing are higher at higher levels of management. IT 3133

The Information Systems Subsidiary IS service companies that are owned by and served by one large company Some grow large enough to service the market at large Some corporations purchase an IS consulting firm

Purchased Applications Why Purchase? Immediate system availability High quality Low price Available support

Purchased Applications Purchasing Risks Loose fit between needs and features Bankruptcy of the vendor High turnover of vendor personnel

Renting Software On-site Renting Renting Through the Web Client purchases a license to use a certain application for a specified time Renting Through the Web Application installed at vendor’s location; client accesses through the Web or leased line

Renting Software Benefits and risks of software rental through the Web

User Application Development Factors Encouraging User Application Development The widespread use of PCs The emergence of 4GLs Increasing popularity of prototyping Increasing popularity of client/server architecture

User Application Development Advantages of user application development Shortened lead times Good fit to needs Free IS staff time

User Application Development Risks of user application development Poorly developed applications Duplication Security problems Poor documentation