Systems Development MBAA 609 R. Nakatsu. Overview of Today’s Lecture Why do IT projects succeed and fail? Two philosophies of systems development –Systems.

Slides:



Advertisements
Similar presentations
Information Systems Systems Development Chapter 6.
Advertisements

Managing Information Technology 6th Edition
E. Wainright Martin Carol V. Brown Daniel W. DeHayes Jeffrey A. Hoffer William C. Perkins MANAGINGINFORMATIONTECHNOLOGY FIFTH EDITION CHAPTER 10 M ETHODOLOGIES.
Chapter 12 Systems Development Three common methods for MIS development: The systems development life cycle (SDLC) Prototyping End-user development Five.
C H A P T E R 10 Developing Business/IT Solutions.
Sixth Edition 1 M a n a g e m e n t I n f o r m a t i o n S y s t e m s M a n a g I n g I n f o r m a t i o n T e c h n o l o g y i n t h e E – B u s i.
Steps, Tools, and Techniques
Systems Development Infsy 570 Dr. Ocker. What we Mean by Software Quality Software Quality Effective- ness UsabilityEfficiencyReliability Maintain- ability.
Acquiring Information Systems and Applications
McGraw-Hill/Irwin © 2002 The McGraw-Hill Companies, Inc. All rights reserved. C H A P T E R Haag Cummings McCubbrey Third Edition 7 Developing IT Systems.
6-1 Management Information Systems for the Information Age Copyright 2004 The McGraw-Hill Companies, Inc. All rights reserved Chapter 6 Systems Development.
Principles and Learning Objectives
Lab/Sessional -CSE-374. SYSTEM DEVELOPMENT LIFE CYCLE.
Chapter 8 Information Systems Development & Acquisition
© Prentice Hall CHAPTER 9 Application Development by Information Systems Professionals.
Eleventh Edition 1 Introduction to Information Systems Essentials for the Internetworked E-Business Enterprise Irwin/McGraw-Hill Copyright © 2002, The.
System Implementations American corporations spend about $300 Billion a year on software implementation/upgrade projects.
Fundamentals of Information Systems, Second Edition
Pertemuan Matakuliah: A0214/Audit Sistem Informasi Tahun: 2007.
7.2 System Development Life Cycle (SDLC)
DECISION SUPPORT SYSTEM DEVELOPMENT
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.
CHAPTER 19 Building Software.
Acquiring Information Systems and Applications
OUTSOURCING AND CROWDSOURCING AIMS 2710 R. Nakatsu.
CORE 1: PROJECT MANAGEMENT Overview TECHNIQUES FOR MANAGING A PROJECT Communication Skills Active Listening Mirroring Paraphrasing Summarizing Clarifying.
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 14: Redesigning the Organization with Information Systems Instructor: Kevin Brabazon.
MIS CHAPTER 10 BUILDING SUCCESSFUL INFORMATION SYSTEMS Hossein BIDGOLI.
Succeeding with Technology Systems Development An Overview of Systems Development Tools and Techniques for Systems Development Systems Investigation Systems.
Chapter 15 Systems Development
1 Building and Maintaining Information Systems. 2 Opening Case: Yahoo! Store Allows small businesses to create their own online store – No programming.
INFORMATION SYSTEM APPLICATIONS System Development Life Cycle.
SYSTEMS DEVELOPMENT Phases, Tools, and Techniques
Pertemuan 5 Pengembangan Teknologi Informasi Matakuliah: H0402/PENGELOLAAN SISTEM KOMPUTER Tahun: 2005 Versi: 1/0.
1.1 © 2007 by Prentice Hall 11 Chapter Building Information Systems.
Laudon & Laudon: Canadian Edition
Computers Are Your Future Eleventh Edition Chapter 13: Systems Analysis & Design Copyright © 2011 Pearson Education, Inc. Publishing as Prentice Hall1.
11.1 © 2007 by Prentice Hall 11 Chapter Building Information Systems.
Information Systems Technology Ross Malaga "Part III - Building and Managing Information Systems" III 11 Copyright © 2005 Prentice Hall, Inc MANAGING.
Computers Are Your Future © 2006 Prentice Hall, Inc.
Systems Development AIMS 2710 R. Nakatsu. Overview Why do IT projects succeed and fail? Two philosophies of systems development –Systems Development Life.
6-1 Management Information Systems for the Information Age Copyright 2004 The McGraw-Hill Companies, Inc. All rights reserved Chapter 6 Systems Development.
Acquiring Information Systems and Applications
Systems Analysis and Design
CHAPTER 13 Acquiring Information Systems and Applications.
Fundamentals of Information Systems, Second Edition 1 Systems Development.
11.1 © 2007 by Prentice Hall 6 Chapter Building Information Systems.
Systems Development AIMS 2710 R. Nakatsu. Overview Two philosophies of systems development –Systems Development Life Cycle (SDLC) –Prototyping Alternative.
Chapter 7 DEVELOPING INFORMATION TECHNOLOGY SYSTEM.
第 11 組 MIS 報告. Phases of any information system ~ recognition of a business problem or opportunity ~ recognition of a business problem or opportunity.
Systems Development Life Cycle (SDLC)
Chapter 6 SYSTEMS DEVELOPMENT Phases, Tools, and Techniques.
Fundamentals of Information Systems, Third Edition2 An Overview of Systems Development: Participants in Systems Development Development team –Responsible.
Ondřej Přibyl L3: System Development Life Cycle page 1 Lecture 3: System Development Life Cycle Doc.Ing. Ondřej Přibyl, Ph.D. Department of applied mathematics.
Fundamentals of Information Systems, Third Edition2 Principles and Learning Objectives Effective systems development requires a team effort of stakeholders,
Accounting systems design & evaluation 9434SB 18 March 2002.
Building Information Systems
Information Systems Development
Building Information Systems
Fundamentals of Information Systems, Sixth Edition
Developing Information Systems
Building Information Systems
Information Systems Development
CHAPTER 10 METHODOLOGIES FOR CUSTOM SOFTWARE DEVELOPMENT
MANAGING THE DEVELOPMENT AND PURCHASE OF INFORMATION SYSTEMS
Chapter 13 Building Systems.
Presentation transcript:

Systems Development MBAA 609 R. Nakatsu

Overview of Today’s Lecture Why do IT projects succeed and fail? Two philosophies of systems development –Systems Development Life Cycle (SDLC) –Prototyping Outsourcing and Crowdsourcing

Why do IT projects fail? PricewaterhouseCoopers surveyed 200 companies and found that: Over half of IT projects fail. Only 2.5% of corporations consistently meet their targets of scope, time and cost goals for all types of projects.

Defining Project Success The project met scope, time and cost goals The project satisfied the customer and sponsor The results of the project met its main objectives. For example: –Saving the company money –Making the firm more efficient/productive –Providing a good return on investment

What helps projects succeed? Critical Success Factors 1.User Involvement 2. Executive support 3. Clear business objectives 4. Emotional maturity 5. Optimizing scope 6. Agile process 7. Project management expertise 8.Skilled resources 9.Execution 10. Tools and infrastructure Source: The Standish Group, “Chaos Activity News” (August 2011).

The Traditional Systems Development Life Cycle TRADITIONAL SDLC – A traditional method for developing I.S. that partitions the system development process into stages that must be completed sequentially. A key characteristic of the SDLC approach is extensive formal reviews by project team members and business management at the end of each major step.

1. Systems Analysis Analyze the problem that the organization is trying to solve with an information system. Address key business issues during this phase: what is the system supposed to do from a business perspective? Key Tasks During Analysis: –Define the problem and identify its causes. –Specify the solution –Define new information and processing requirements (Create a data flow diagram—see example on Class Notes page).

2. Systems Design Build a technical blueprint of how the proposed system will work. IT specialists complete most of the tasks here. The end user (i.e., the business user) reviews the technical specifications. Issues to consider: programs; user interfaces; database design (e.g., create the ER Diagram); reports; manual procedures; security and controls

3. Implementation Bring the proposed system to life and place it in the organization. Monitor the budget and schedule and look for “runaway” projects. Manage scope creep! Key Tasks During Implementation: –Hardware acquisition and installation –Software development and testing –Training –System documentation

4. Conversion The process of changing from the old system to the new system. DIRECT CUTOVER - immediately using the new PARALLEL - using the old and new simultaneously PILOT - converting only a group of people first PIECEMEAL (or phased) – introduce the new system in phases either by functions or by organizational units

5. Production and Maintenance Production is the stage after the new system is installed and the conversion is complete; during this time the system should be reviewed by user and technical specialists. Maintenance is necessary for failures and problems that arise during the operation of the system. You may need to make minor modifications or completely overhaul the system at some point.

Advantages of the SDLC Uses a structured step-by-step approach. Thorough requirements definition in which problems are addressed early on in the analysis stage. Requires key deliverables before proceeding to the next step. Rigorous methods for analysis, design, and testing of a system.

Alternative to the SDLC: Prototyping PROTOTYPING involves the building of an experimental system rapidly for end users to evaluate A PROTOTYPE is a model of a proposed product, service, or system. It is an interactive, iterative process in which you get plenty of feedback from users of the system.

The Prototyping Process 1.Identify Basic Requirements 2.Develop Working Prototype 3.Get feedback from End Users 4.Revise and Enhance the Prototype Continue the iterative process between steps 3 and 4 until the end user is satisfied with the prototype.

Prototyping Advantages Encourages active end-user participation. Can lead to a speedier implementation. Gives end-users a feel for the final system. Helps determine technical feasibility. Helps sell the idea of a proposed system. Question for discussion: What are the disadvantages of prototyping?

Outsourcing Forms Of Systems Development Outsourcing 1. Purchase existing application software package. 2. Outsource development of a system for which no application software package exists. Offshore outsourcing of IT development is predicted to grow in size and importance in the coming years. is hiring an outside organization to develop the system.

Questions for Discussion: What are the advantages and disadvantages of outsourcing (compared to in-house development)? What does Apple outsource? Why? When do we use outsourcing, and what types of IT projects are most suitable to outsourcing?

Crowdsourcing Definition: Crowdsourcing is a distributed problem-solving and production model. Problems are broadcast to an unknown group of solvers in the form of an open call for solutions. Users—also known as the crowd—typically form into online communities, and the crowd submits solutions. The crowd also sorts through the solutions, finding the best ones.

Varieties of Crowdsourcing Rote, simple tasks (Mechanical Turk) R&D, solving intractable problems (Innocentive) User-generated content (Wikipedia, istockphoto) New idea generation (Kraft, Cisco) Open source design