Pertemuan 6

Membeli aplikasi Teknologi Informasi

Matakuliah : H0402/PENGELOLAAN SISTEM KOMPUTER

Tahun : 2005

Versi : 1/0

Learning Outcomes

Pada akhir pertemuan ini, diharapkan mahasiswa

akan mampu :

• Menunjukkan cara-cara dalam membeli teknologi informasi pada dunia nyata

Outline Materi

• Keputusan membeli atau buat

• Metoda membeli

• Keputusan memberikan user tools untuk membuat aplikasi sendiri

SYSTEMS DEVELOPMENT APPROACHES

• SYSTEMS DEVELOPMENT LIFE CYCLE (SDLC)

• PROTOTYPING

• PURCHASED SOFTWARE

• OUTSOURCING (SYSTEMS INTEGRATOR)

• END USER DEVELOPMENT

*

MAKE-OR -BUY DECISION

• ASSESS RISKS & BENEFITS• MAKE: Use SDLC , prototyping, RAD if

organization has IS skills. Can save cost, speed implementation

• BUY: If vendor offers acceptable product and required support at lower cost, faster time than in-house development could provide. Usually system must be modified to meet organization’s needs

*

THE PURCHASING PROCESS

DEFINITION PHASE:• FEASIBILITY ANALYSIS• REQUIREMENTS DEFINITION• SHORT LIST OF PACKAGES• ESTABLISH EVALUATION CRITERIA• DEVELOP AND DISTRIBUTE RFP• CHOOSE PACKAGE• NEGOTIATE CONTRACT

*

THE PURCHASING PROCESS

CONSTRUCTION PHASE:• SYSTEM DESIGN: Package modification• SYSTEM BUILDING: Package modification• SYSTEM TESTING

IMPLEMENTATION PHASE:• INSTALLATION• OPERATIONS• MAINTENANCE

*

REQUEST FOR PROPOSAL (RFP)

• DOCUMENT SENT TO POTENTIAL VENDORS INVITING THEM TO SUBMIT A PROPOSAL TO FURNISH A SYSTEM

• PROVIDES DETAILED INFORMATION ABOUT THE DESIRED SYSTEM, ITS ENVIRONMENT, MATERIAL REQUIRED FROM VENDOR, AND GENERAL CRITERIA USED TO EVALUATE PROPOSALS

*

SAMPLE CONTENTS OF RFP

1. INTRODUCTION:A. STRUCTURE & SCOPE

B. OBJECTIVE

C. COMPANY BACKGROUND, PHILOSOPHY

D. HARDWARE/SOFTWARE ENVIRONMENT

E. CURRENT BUSINESS ENVIRONMENT

*

SAMPLE CONTENTS OF RFP

II. GUIDELINES FOR RESPONSE:A. GUIDELINES

B. VENDOR’S RESPONSE

C. GENERAL EVALUATION PROCESS

D. HARDWARE/SOFTWARE ENVIRONMENT

E. CURRENT BUSINESS ENVIRONMENT

*

SAMPLE CONTENTS OF RFP

III. REQUIREMENTS:A. VENDOR INFORMATION

B. VENDOR SUPPORT/TRAINING

C. DOCUMENTATION

D. PACKAGE HARDWARE & SYSTEM SOFTWARE ENVIRONMENT

E. APPLICATION & DATABASE ARCHITECTURE

F. TUNING & MEASUREMENT

G. FUNCTIONAL REQUIREMENTS

*

SAMPLE CONTENTS OF RFP

IV. COSTS:A. SUMMARY

B. NON-RECURRING

C. RECURRING

D. PRICE GUARANTEE

E. MAINTENANCE AGREEMENT

F. NEW RELEASES

V. SIGNATURE PAGE

*

MATCHING COMPANY NEEDS WITH PACKAGE CAPABILITIES

PACKAGE PACKAGE CAPABILITIESCAPABILITIES

COMPANY COMPANY NEEDSNEEDS

IDENTIFY IDENTIFY DISCREPANCIESDISCREPANCIES

CHOOSE CHOOSE ALTERNATIVESALTERNATIVES

MODIFY MODIFY PACKAGEPACKAGE

CHANGE CHANGE COMPANYCOMPANY

LIVE WITH LIVE WITH PROBLEMSPROBLEMS

ROLES FOR PURCHASING PACKAGED APPLICATIONS

• PROJECT MANAGER: Manages process, responsible for the success of the project, may be user but IS expertise required

• VENDOR: Must be responsive to customer’s needs

• PURCHASING SPECIALIST: Helps prepare RFP, assist in entire process

• ATTORNEYS: Oversee writing, approval of contract

*

PURCHASING SOFTWAREADVANTAGES:

• REDUCED TIME TO IMPLEMENT

• LOWER OVERALL ACQUISITION COSTS

• APPLICATION QUALITY

• REDUCED NEED FOR INTERNAL IS RESOURCES

• INFUSION OF EXTERNAL EXPERTISE

*

PURCHASING SOFTWAREDISADVANTAGES:

• RISKS DUE TO LACK OF PACKAGE KNOWLEDGE

• RISKS DUE TO EXTENT OF ORGANIZATIONAL CHANGES REQUIRED

• INITIAL & ONGOING DEPENDENCE ON VENDOR

*

SPECIAL CASE: ENTERPRISE RESOURCE PLANNING (ERP)

• INTERFACES CROSS SEPARATE FUNCTIONAL SYSTEMS

• MUST SUPPORT CROSS-FUNCTIONAL BUSINESS PROCESSES

• COMPLEX SYSTEMS TAKE YEARS TO COMPLETE

• REQUIRES EXTENSIVE TRAINING• HEAVY RELIANCE ON CONSULTANTS

*

END-USER COMPUTING

• HANDS-ON USE OF COMPUTERS BY EMPLOYEES

• ENTER DATA• MAKE INQUIRIES• PREPARE REPORTS• PERFORM STATISTICAL ANALYSIS• ANALYZE PROBLEMS• DEVELOP WEB PAGES

*

PRIMARY DRIVERS

• AVAILABILITY OF LOW-COST MICROCOMPUTERS:– HIGH-LEVEL LANGUAGES– COMPUTER LITERACY AMONG COLLEGE

GRADUATES, PROFESSIONALS

• INCREASED USER FRUSTRATIONS ABOUT NEW PROJECT BACKLOGS

*

USER APPLICATION DEVELOPMENT

• USE OF COMPUTER TOOLS

• DEVELOP BUSINESS APPLICATIONS

• USERS ARE NOT IS SPECIALISTS

• INVOLVES APPLICATION, TOOL & DEVELOPER

*

USER-DEVELOPED APPLICATIONSADVANTAGES

• INCREASED USER CONTROL OVER PROJECT

• INCREASED USER ACCEPTANCE OF SOLUTION

• FREES IS RESOURCES

• INCREASES USERS’ KNOWLEDGE OF IT

*

USER-DEVELOPED APPLICATIONSDISADVANTAGES

• LOSS OF QUALITY CONTROL

• INCREASES OPERATIONAL RISKS DUE TO DEVELOPED TURNOVER

• POTENTIAL LABOR/TIME INEFFICIENCIES

• LOSS OF INTEGRATION OPPORTUNITIES/CAPABILITIES

*

CHARACTERISTICS

• APPLICATION:– SCOPE: Personal, departmental,

organizational– CRITICALITY/IMPACT: Risk exposure– SIZE & USAGE: One-time, periodic, ongoing– PROBLEM COMPLEXITY: Structure, how

common is task?

*

CHARACTERISTICS

• TOOL:– SOPHISTICATION, COMPLEXITY– INTERCONNECTEDNESS

• DEVELOPER:– USER SKILLS, EXPERIENCE, AVAILABILITY– IS SPECIALIST SKILLS, EXPERIENCE,

AVAILABILITY

*

EXTENT OF INTERCONNECTEDNESS*STAGE EXTENT OF INTERCONNECTEDNESS

• ISOLATION: Application does not use or create data for another application

• STAND-ALONE: Application uses manually entered computer-generated data from reports, printouts

• MANUAL INTEGRATION: Data electronically transferred from another application, manually (e.g., file on disk)

*

* Adapted from Huff, Munro & Martin, 1988

EXTENT OF INTERCONNECTEDNESS*STAGE EXTENT OF INTERCONNECTEDNESS

• AUTOMATED INTEGRATION: Application electronically connected with one or more databases/applications using automated scripts

• DISTRIBUTED INTEGRATION: Application uses data created, stored, maintained by organization’s systems under control of IS specialists

*

* Adapted from Huff, Munro & Martin, 1988

GUIDELINES FOR CHOOSING DEVELOPMENT PROCESS

DEVELOPED DEVELOPED FOR OTHER FOR OTHER USERSUSERS

DEVELOPED DEVELOPED FOR SELF FOR SELF USER ONLYUSER ONLY

SMALL, SIMPLESMALL, SIMPLE LARGE, LARGE, COMPLEXCOMPLEX

1 2

3 4

1. SDLC OR 1. SDLC OR PROTOTYPING, PROTOTYPING, DISCIPLINED DISCIPLINED APPROACH TO APPROACH TO DEFINITION & DEFINITION & IMPLEMENTATIONIMPLEMENTATION

2. SDLC, CLEAR 2. SDLC, CLEAR “HANDS-OFF” “HANDS-OFF” BETWEEN PHASESBETWEEN PHASES

3. “COLLAPSED” LIFE 3. “COLLAPSED” LIFE CYCLECYCLE

4. DISCIPLINED, 4. DISCIPLINED, ITERATIVE ITERATIVE DEVELOPMENTDEVELOPMENT

LEVERAGING END-USER COMPUTING*

CONTEXT:CONTEXT:

ORGANIZATIONAL ORGANIZATIONAL LEVEL FACTORSLEVEL FACTORS

DEPARTMENTAL DEPARTMENTAL LEVEL FACTORSLEVEL FACTORS

STATUS OF STATUS OF IS/USER IS/USER PARTNERSHIPPARTNERSHIP

ORGANIZATION LEVELORGANIZATION LEVEL

SUPPORT & SUPPORT & CONTROL CONTROL ACTIONSACTIONS

STRATEGYSTRATEGY

TECHNOLOGYTECHNOLOGY

INDIVIDUAL LEVELINDIVIDUAL LEVEL

DEVELOPMENTDEVELOPMENT

PROCESSPROCESSTASKTASK

TOOLTOOL

USER USER DEVELOPERDEVELOPER

*Based on Branceau & Brown, 1993

ORGANIZATIONAL LEVEL

• STRATEGY: Strategic objectives and approach to end-user computing

• TECHNOLOGY: Range & accessibility of end-user tools

• SUPPORT & CONTROL ACTIONS: Support services, control policies & procedures

*

EXPANSION/CONTROL MATRIX*

ACCELERATIONCONTROLLED

GROWTH

LAISSEZ-FAIRE CONTAINMENT

HIGHHIGH

LOWLOW

LOWLOW HIGHHIGH

CONTROLCONTROL

EX

PA

NS

ION

EX

PA

NS

ION

*Based on Monroe et al., 1987-1988; Brancheau & Amoroso, 1990

EVOLUTION OF INFORMATION CENTERSTAGE ONE:

• REACTIVE SERVICES

• INDIVIDUAL SOLUTIONS

• PRODUCT TRAINING

• ALL NEEDS SUPPORTED

• COMPUTER LITERACY TRAINING

• ONE-WAY RELATIONSHIPS

*

EVOLUTION OF INFORMATION CENTERSTAGE TWO:

• PROACTIVE SERVICES

• DEPARTMENTAL SOLUTIONS

• BUSINESS PROBLEM-SOLVING

• HIGH-PAYOFF NEEDS SUPPORTED

• INFORMATION LITERACY EDUCATION

• ALLIANCE: IS/USER ALLIANCE

*

COMMON SUPPORT SERVICES

• TROUBLESHOOTING• CONSULTING• TRAINING & IS EDUCATION• PRODUCT RESEARCH & EVALUATION• INFORMATION SHARING• TOOL SELECTION & PURCHASING• TOOL INSTALLATION, MAINTENANCE &

UPGRADING

*

COMMON POLICIES & PROCEDURES

• PRODUCT STANDARDS• ERGONOMICS• PRODUCT PURCHASES• INVENTORY CONTROL• UPGRADE PROCEDURES• QUALITY REVIEW• IDENTIFYING CRITICAL APPLICATIONS &

DATA

*

COMMON POLICIES & PROCEDURES

• DATA ACCESS• BACKUP PROCEDURES• AUDIT TRAILS• DOCUMENTATION STANDARDS• UNAUTHORIZED ACCESS• UNAUTHORIZED SOFTWARE COPYING• VIRUS PROTECTION

*

• Membeli atau membuat

• Metoda membeli

• Cara-cara men-develop systems– SYSTEMS DEVELOPMENT LIFE CYCLE (SDLC)– PROTOTYPING– PURCHASED SOFTWARE– OUTSOURCING (SYSTEMS INTEGRATOR)– END USER DEVELOPMENT

Aplikasi Teknologi Informasi