Pertemuan – 17-18 Matakuliah: M0304/Corporate Information System Management Tahun: 2008.

Slides:



Advertisements
Similar presentations
Information Systems Systems Development Chapter 6.
Advertisements

Managing Information Technology 6th Edition
Pertemuan – 16a Matakuliah: M0304/Corporate Information System Management Tahun: 2008.
E. Wainright Martin Carol V. Brown Daniel W. DeHayes Jeffrey A. Hoffer William C. Perkins MANAGINGINFORMATIONTECHNOLOGY FIFTH EDITION CHAPTER 10 M ETHODOLOGIES.
Alternate Software Development Methodologies
Copyright 2004 Prentice-Hall, Inc. Essentials of Systems Analysis and Design Second Edition Joseph S. Valacich Joey F. George Jeffrey A. Hoffer Appendix.
COMPONENT-BASED DEVELOPMENT
C H A P T E R 10 Developing Business/IT Solutions.
Steps, Tools, and Techniques
Pertemuan 4 Membangun Teknologi Informasi Matakuliah: H0402/PENGELOLAAN SISTEM KOMPUTER Tahun: 2005 Versi: 1/0.
Acquiring Information Systems and Applications
Chapter 6 SYSTEMS DEVELOPMENT Phases, Tools, and Techniques
6-1 Management Information Systems for the Information Age Copyright 2004 The McGraw-Hill Companies, Inc. All rights reserved Chapter 6 Systems Development.
Copyright © 2009 Pearson Education, Inc. Publishing as Prentice Hall Essentials of Systems Analysis and Design Fourth Edition Joseph S. Valacich Joey F.
Chapter 1 The Systems Development Environment
Chapter 8 Information Systems Development & Acquisition
© Prentice Hall CHAPTER 9 Application Development by Information Systems Professionals.
Chapter 6 Prototyping, RAD, and Extreme Programming
Slide 1 INTRODUCTION Chapter 1. Slide 2 Key Ideas Many failed systems were abandoned because analysts tried to build wonderful systems without understanding.
Chapter 1 The Systems Development Environment
Unit Five – Transforming Organizations
Fundamentals of Information Systems, Second Edition
Copyright 2004 Prentice-Hall, Inc. Essentials of Systems Analysis and Design Second Edition Joseph S. Valacich Joey F. George Jeffrey A. Hoffer Chapter.
Chapter 6 Systems Development: Phases, Tools, and Techniques
Copyright 2006 Prentice-Hall, Inc. Essentials of Systems Analysis and Design Third Edition Joseph S. Valacich Joey F. George Jeffrey A. Hoffer Chapter.
SDLC. Information Systems Development Terms SDLC - the development method used by most organizations today for large, complex systems Systems Analysts.
Introduction to Systems Analysis and Design
Information Systems Development : Overview. Information systems development practice Concept and role of a systems development methodology Approaches.
SDLC and alternative methodologies 1/14/2015 © Abdou Illia MIS Spring 2015.
Chapter 1 The Systems Development Environment
Acquiring Information Systems and Applications
Acquiring Information Systems and Applications
Copyright 2001 Prentice-Hall, Inc. Essentials of Systems Analysis and Design Joseph S. Valacich Joey F. George Jeffrey A. Hoffer Chapter 1 The Systems.
The Systems Development Environment. Learning Objectives Define information systems analysis and design. Describe the different types of information systems.
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.
Chapter 1 The Systems Development Environment
Computers Are Your Future Eleventh Edition Chapter 13: Systems Analysis & Design Copyright © 2011 Pearson Education, Inc. Publishing as Prentice Hall1.
8-1 Chapter 8 Information Systems Development & Acquisition.
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.
S YSTEM D EVELOPMENT M ETHODS 노형종, 문정곤, 허승구 Class Term Project 2005 Spring POSTECH IE 381 Management Information Systems.
Acquiring Information Systems and Applications
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.
Systems Development MBAA 609 R. Nakatsu. Overview of Today’s Lecture Why do IT projects succeed and fail? Two philosophies of systems development –Systems.
Acquiring Information Systems and Applications
McGraw-Hill/Irwin ©2005 The McGraw-Hill Companies, All rights reserved ©2005 The McGraw-Hill Companies, All rights reserved McGraw-Hill/Irwin.
CHAPTER 13 Acquiring Information Systems and Applications.
Systems Development MIS 503 Management Information Systems MBA Program.
Chapter 1 The Systems Development Environment Modern Systems Analysis and Design Fifth Edition Jeffrey A. Hoffer Joey F. George Joseph S. Valacich.
Chapter 6 Prototyping, RAD, and Extreme Programming Systems Analysis and Design Kendall & Kendall Sixth Edition.
© 2005 by Prentice Hall Chapter 1 The Systems Development Environment Modern Systems Analysis and Design Fourth Edition Jeffrey A. Hoffer Joey F. George.
Chapter 6 CASE Tools Software Engineering Chapter 6-- CASE TOOLS
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.
1 - 1 Systems Analysis and Design, Key Ideas Many failed systems were abandoned because analysts tried to build wonderful systems without understanding.
Chapter 7 DEVELOPING INFORMATION TECHNOLOGY SYSTEM.
Chapter 6 SYSTEMS DEVELOPMENT Phases, Tools, and Techniques.
Chapter 1 Assuming the Role of the Systems Analyst.
Information Systems Development
Building Information Systems
Systems Development Chapter 6
Information Systems Development
CHAPTER 10 METHODOLOGIES FOR CUSTOM SOFTWARE DEVELOPMENT
MANAGING THE DEVELOPMENT AND PURCHASE OF INFORMATION SYSTEMS
Presentation transcript:

Pertemuan – Matakuliah: M0304/Corporate Information System Management Tahun: 2008

Fakultas Ilmu Komputer Modul-17-2 M ETODOLOGI P ENGEMBANGAN S OFTWARE M ANDIRI

Fakultas Ilmu Komputer Modul-17-3 S YSTEMS D EVELOPMENT L IFE C YCLE M ETHODOLOGY Systems development life cycle (SDLC) – a highly structured approach for development of new customized software applications

Fakultas Ilmu Komputer Modul-17-4 S YSTEMS D EVELOPMENT L IFE C YCLE M ETHODOLOGY The SDLC Steps Figure 17.1 The Systems Development Life Cycle Key characteristic is extensive formal reviews required at end of each major step

Fakultas Ilmu Komputer Modul-17-5 S YSTEMS D EVELOPMENT L IFE C YCLE M ETHODOLOGY The SDLC Steps Figure 17.2 Cost Breakdown for $1 Million SDLC Project Hallmark of SDLC approach: extensive up- front time spent determining requirements to avoid expensive changes later

Fakultas Ilmu Komputer Modul-17-6 S YSTEMS D EVELOPMENT L IFE C YCLE M ETHODOLOGY The SDLC Steps SDLC: – Most often requires a lot of documentation – Outputs from one step inputs to next – Often referred to as the “waterfall” model

Fakultas Ilmu Komputer Modul-17-7

Fakultas Ilmu Komputer Modul-17-8 S YSTEMS D EVELOPMENT L IFE C YCLE M ETHODOLOGY Definition Phase – Requirements Definition Focuses on logical design: processes, data flows, and data interrelationships – not specific physical implementation Deliverable – system requirements document: – Detailed descriptions of inputs and outputs, processes used to convert input data to outputs – Formal diagrams and output layouts – Revised cost/benefit analysis – Revised plan for remainder of project

Fakultas Ilmu Komputer Modul-17-9 S YSTEMS D EVELOPMENT L IFE C YCLE M ETHODOLOGY Construction Phase System Design System Building System Testing Figure 17.3 Characteristics of High Quality Systems Documentation is a major mechanism of communication during development process

Fakultas Ilmu Komputer Modul S YSTEMS D EVELOPMENT L IFE C YCLE M ETHODOLOGY Implementation Phase Installation Operations Maintenance

Fakultas Ilmu Komputer Modul Implementation Phase – Installation Figure 17.4 Implementation Strategies Parallel Strategy

Fakultas Ilmu Komputer Modul Implementation Phase – Maintenance Figure 17.5 Percent of Development Resources Devoted to Maintenance

Fakultas Ilmu Komputer Modul Implementation Phase – Maintenance Figure 17.6 The Widening Gap Between Organization’s Needs and System’s Performance

Fakultas Ilmu Komputer Modul S YSTEMS D EVELOPMENT L IFE C YCLE M ETHODOLOGY The SDLC Project Team Usually temporary Includes personnel from IS and business units Has a project manager – Traditionally from IS – Can be from business unit – May be one from each – Responsible for success of project – delivering quality system on time and within budget

Fakultas Ilmu Komputer Modul S YSTEMS D EVELOPMENT L IFE C YCLE M ETHODOLOGY The SDLC Project Team Includes systems analysts – Have critical roles – Work closely with business managers and end users – Have problem-solving skills, knowledge of IT capabilities, strong business understanding Has a business sponsor and a champion

Fakultas Ilmu Komputer Modul S YSTEMS D EVELOPMENT L IFE C YCLE M ETHODOLOGY Managing an SDLC Project Characteristics critical for success: – Manageable project size – Accurate requirements definition – Executive sponsorship

Fakultas Ilmu Komputer Modul S YSTEMS D EVELOPMENT L IFE C YCLE M ETHODOLOGY Figure 17.7 Costs of Error Correction by SDLC Step Managing an SDLC Project (Adapted from Boehm, 1976)

Fakultas Ilmu Komputer Modul S YSTEMS D EVELOPMENT L IFE C YCLE M ETHODOLOGY SDLC Advantages and Disadvantages Figure 17.8 Advantages and Disadvantages of Traditional SDLC Approach

Fakultas Ilmu Komputer Modul P ROTOTYPING M ETHODOLOGY Prototyping approach: – Takes advantage of availability of fourth generation procedural languages and relational database management systems – Enables creation of system (or part of system) more quickly, then revise after users have tried it – Is a type of evolutionary development process

Fakultas Ilmu Komputer Modul P ROTOTYPING M ETHODOLOGY Prototyping examples: – Input and output screens developed for users to test as part of requirements definition – “First-of-a-series” – a completely operational prototype used as a pilot – “Selected features” – only some essential features included in prototype, more added later – Prototyping used as a complete alternative to traditional SDLC methodology

Fakultas Ilmu Komputer Modul P ROTOTYPING M ETHODOLOGY Prototyping used as a complete alternative to traditional SDLC methodology: – Good when requirements hard to define – Good when system needed quickly – Impractical for large, complex applications

Fakultas Ilmu Komputer Modul The Prototyping Steps Figure 17.9 The Prototyping Life Cycle

Fakultas Ilmu Komputer Modul P ROTOTYPING M ETHODOLOGY Representatives from IS and user management necessary Need team members who can quickly build systems using advanced tools Requires dedicated business user roles The Prototyping Project Team

Fakultas Ilmu Komputer Modul P ROTOTYPING M ETHODOLOGY Advantages: – Only basic requirements needed at front end – Used to develop systems that radically change how work is done, so users can evaluate – Allows firms to explore use of new technology – Working system available for testing more quickly – Less strong top-down commitment needed at front end – Costs and benefits can be derived after experience with initial prototype – Initial user acceptance likely higher Prototyping Advantages and Disadvantages

Fakultas Ilmu Komputer Modul P ROTOTYPING M ETHODOLOGY Disadvantages: – End prototype often lacks security and control features – May not undergo as rigorous testing – Final documentation may be less complete – More difficult to manage user expectations Prototyping Advantages and Disadvantages

Fakultas Ilmu Komputer Modul P ROTOTYPING M ETHODOLOGY Prototyping within an SDLC Process Figure SDLC with Prototyping to Define Requirements

Fakultas Ilmu Komputer Modul P ROTOTYPING M ETHODOLOGY Prototyping within an SDLC Process Figure Prototyping/Piloting Replaces SDLC Definition Phase

Fakultas Ilmu Komputer Modul N EWER A PPROACHES Rapid Application Development (RAD) Figure Four-Step RAD Cycle Hybrid methodology – aspects of SDLC and prototyping Goal is to produce a system in less than a year

Fakultas Ilmu Komputer Modul N EWER A PPROACHES Rapid Application Development (RAD) Joint application design (JAD) – a technique in which a team of users and IS specialists engage in an intense and structured process in order to minimize the total time required for gathering information from multiple participants

Fakultas Ilmu Komputer Modul N EWER A PPROACHES Rapid Application Development (RAD) Joint application design (JAD) – a technique in which a team of users and IS specialists engage in an intense and structured process in order to minimize the total time required for gathering information from multiple participants Computer-aided software engineering (CASE) – any software tool used to automate one or more steps of a software development methodology

Fakultas Ilmu Komputer Modul N EWER A PPROACHES Rapid Application Development (RAD) Figure Types of CASE Tools (Adapted from Valacich, George, and Hoffer, 2001)

Fakultas Ilmu Komputer Modul N EWER A PPROACHES Rapid Application Development (RAD) Figure RAD Advantages and Disadvantages

Fakultas Ilmu Komputer Modul N EWER A PPROACHES Agile Software Development Discipline Alternative methodology for smaller projects Based on four key values: – Simplicity – Communication – Feedback – Courage One type: Extreme Programming (XP) – Programmers write code in pairs – Use simple design and frequent testing

Fakultas Ilmu Komputer Modul M ANAGING S OFTWARE P ROJECTS U SING O UTSOURCED S TAFF Advantages: – Helps keep software development costs down – Uses technical expertise not available in-house – Can often complete projects more quickly Off-site outsourcing: – Onshore – within same country or region – Offshore – not within same country or region

Fakultas Ilmu Komputer Modul M ANAGING S OFTWARE P ROJECTS U SING O UTSOURCED S TAFF Offshore alternative good option when: – System requirements well-defined and remain stable – Time is of essence and 7x24 hour availability of resources a good idea – Cost of project important

Fakultas Ilmu Komputer Modul M ANAGING S OFTWARE P ROJECTS U SING O UTSOURCED S TAFF Guidelines for managing offsite outsourcer: – Manage expectations, not staff – Take explicit actions to integrate the offsite workers – Communicate frequently – Abandoning informal ways may result in increased rigor

Fakultas Ilmu Komputer Modul Reff-Haag Prosedure Outsource

Modul OUTSOURCING Developing strategic partnerships Outsourcing - the delegation of specific work to a third party for a specified length of time, at a specified cost, and at a specified level of service

Modul Developing Strategic Partnerships

Modul Developing Strategic Partnerships IT outsourcing takes on 1 of 4 forms: 1. Purchasing existing software 2. Purchasing existing software and pay the publisher to make certain modifications 3. Purchasing existing software and pay the publisher for the right to make modifications yourself 4. Outsourcing the development of an entirely new and unique system for which no software exists

Modul The Outsourcing Process

Modul The Outsourcing Process Steps of the outsourcing process 1. Planning 2. Define project scope 3. Select a target system 4. Establish logical requirements

Modul The Outsourcing Process 5. Develop a request for proposal Request for proposal (RFP) - a formal document that describes in detail your logical requirements for a proposed system and invites outsourcing organizations to submit bids for its development 6. Evaluate request for proposal returns and choose a vendor 7. Test and accept solution 8. Monitor and reevaluate

Modul The Outsourcing Process – an RFP

Modul Offshore Outsourcing  Offshore outsourcing - using organizations from other countries to write code and develop systems

Modul The Advantages of Outsourcing Focus on unique core competencies Exploit the intellect of another organization Better predict future costs Acquire leading-edge technology Reduce costs Improve performance accountability

Modul The Disadvantages of Outsourcing Reduces technical know-how for future innovation Reduces degree of control Increases vulnerability of strategic information Increases dependency on other organizations