Pertemuan – 17-18

Matakuliah : M0304/Corporate Information System ManagementTahun : 2008

Fakultas Ilmu Komputer Modul-17-2

METODOLOGI PENGEMBANGAN SOFTWARE MANDIRI

SYSTEMS DEVELOPMENT LIFE CYCLE METHODOLOGY

Systems development life cycle (SDLC) – a highly structured approach for development of new customized software applications

SYSTEMS DEVELOPMENT LIFE CYCLE METHODOLOGYThe SDLC Steps

Figure 17.1 The Systems Development Life Cycle

Key characteristic is extensive formal reviewsrequired at end of each major step

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

SDLC:– Most often requires a lot of documentation– Outputs from one step inputs to next– Often referred to as the “waterfall” model

SYSTEMS DEVELOPMENT LIFE CYCLE METHODOLOGYDefinition 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

SYSTEMS DEVELOPMENT LIFE CYCLE METHODOLOGYConstruction 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

SYSTEMS DEVELOPMENT LIFE CYCLE METHODOLOGYImplementation Phase

• Installation• Operations• Maintenance

Implementation Phase – Installation

Figure 17.4 Implementation Strategies

Parallel Strategy

Implementation Phase – Maintenance

Figure 17.5 Percent of Development Resources Devoted to Maintenance

Implementation Phase – Maintenance

Figure 17.6 The Widening Gap BetweenOrganization’s Needs and System’s Performance

SYSTEMS DEVELOPMENT LIFE CYCLE METHODOLOGYThe 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

SYSTEMS DEVELOPMENT LIFE CYCLE METHODOLOGYThe 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

SYSTEMS DEVELOPMENT LIFE CYCLE METHODOLOGYManaging an SDLC Project

• Characteristics critical for success: – Manageable project size– Accurate requirements definition– Executive sponsorship

SYSTEMS DEVELOPMENT LIFE CYCLE METHODOLOGY

Figure 17.7 Costs of Error Correction by SDLC Step

Managing an SDLC Project

(Adapted from Boehm, 1976)

SYSTEMS DEVELOPMENT LIFE CYCLE METHODOLOGYSDLC Advantages and Disadvantages

Figure 17.8 Advantages and Disadvantages of Traditional SDLC Approach

PROTOTYPING METHODOLOGY• 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

PROTOTYPING METHODOLOGY

• 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

PROTOTYPING METHODOLOGY• 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

The Prototyping Steps

Figure 17.9 The Prototyping Life Cycle

• 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

• 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

• 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

PROTOTYPING METHODOLOGYPrototyping within an SDLC Process

Figure 17.10 SDLC with Prototyping to Define Requirements

PROTOTYPING METHODOLOGYPrototyping within an SDLC Process

Figure 17.11 Prototyping/Piloting Replaces SDLC Definition Phase

NEWER APPROACHESRapid Application Development (RAD)

Figure 17.12 Four-Step RAD Cycle

• Hybrid methodology – aspects of SDLC and prototyping

• Goal is to produce a system in less than a year

NEWER APPROACHES

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

Figure 17.13 Types of CASE Tools

(Adapted from Valacich, George, and Hoffer, 2001)

Figure 17.14 RAD Advantages and Disadvantages

NEWER APPROACHES

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

MANAGING SOFTWARE PROJECTS USING OUTSOURCED STAFF

• 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

• 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

• 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

• Reff-Haag

Prosedure Outsource

Modul-17-38

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-17-39

Developing Strategic Partnerships

Modul-17-40

Developing Strategic Partnerships• IT outsourcing takes on 1 of 4 forms:

1. Purchasing existing software2. Purchasing existing software and pay the publisher to

make certain modifications3. Purchasing existing software and pay the publisher for

the right to make modifications yourself4. Outsourcing the development of an entirely new and

unique system for which no software exists

Modul-17-41

The Outsourcing Process

Modul-17-42

• Steps of the outsourcing process1. Planning2. Define project scope3. Select a target system4. Establish logical requirements

Modul-17-43

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 solution8. Monitor and reevaluate

Modul-17-44

The Outsourcing Process – an RFP

Modul-17-45

Offshore Outsourcing

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

Modul-17-46

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-17-47

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

Pertemuan – 17-18

Documents

Pertemuan 17(EventHeader)

Pertemuan 14

POKOK BAHASAN Pertemuan 18 Matakuliah: Sistem Informasi Manajemen Tahun: 2008

Penyajian Data Statistik - PERTEMUAN 17 Okt 11

Purchasing Process Pertemuan 15 – 16 – 17 Matakuliah: F0204 / Sistem Akuntansi Tahun: 2007

Pertemuan ke2

Pertemuan 13

Abraham Maslow Holistic-Dynamic Theory Pertemuan 18

Pertemuan 18 The Sales/Collection Business Process

18 18 18 18 18 18 18 18 18 18 18 18 18 17 17 17 17 17 17 ... · Created Date: 00020000000000Z

Pendugaan Parameter Varians dan Rasio Varians Pertemuan 18 Matakuliah: I0134/Metode Statistika Tahun: 2007

Pertemuan 3

Pertemuan 1

Pertemuan 18 & 19 Semantic Analyzer (type checking)

Materi Pertemuan 1: Type of academic writing Pertemuan 2: Plagiarism Pertemuan 3: Penulisan artikel jurnal (sosial-lingkungan) Pertemuan 4: Penulisan

Words and Language used in Broadcasting Pertemuan 17 – 18 Matakuliah: O0394 – Teknik Reportase dan News Caster Tahun: 2010

Pertemuan 18 Programming Languages for E-Business/E-commerce

CONSUMER BEHAVIOR AND UTILITY MAXIMIZATION Pertemuan 17 Matakuliah: J0114-Teori Ekonomi Tahun: 2009

Web viewPERANCANGAN WEB : Pertemuan 1. Pertemuan 2. Pertemuan 3. Pertemuan 4. Pertemuan 5. Pertemuan 6. Author: STAFF PENGAJAR

Pertemuan 17 - 18 Open Channel 1. Bina Nusantara