Pertemuan 4

Membangun Teknologi Informasi

Matakuliah : H0402/PENGELOLAAN SISTEM KOMPUTER

Tahun : 2005

Versi : 1/0

Learning Outcomes

Pada akhir pertemuan ini, diharapkan mahasiswa

akan mampu :

• Menjelaskan metodologi pengembangan teknologi informasi, metodologi pembelian sistem aplikasi serta penerapan end user computing

Outline Materi

• Mengembangkan Sistem Aplikasi

• Membeli Sistem Aplikasi

• Memfasilitasi User menggunakan komputer untuk mengembangkan sistem aplikasi

SYSTEMS DEVELOPMENT LIFE CYCLE (SDLC)

• DEFINITION PHASE: – Feasibility analysis– Requirement definition

• CONSTRUCTION PHASE:– System design– System building– System testing

• IMPLEMENTATION PHASE:– Installation– Operations– Maintenance

*

PROTOTYPING LIFE CYCLE

1. IDENTIFY REQUIREMENTS

2. DEVELOP INITIAL PROTOTYPE

3. USE PROTOTYPE, NOTE CHANGES

4. REVISE, ENHANCE PROTOTYPE: Return to Step 3 as needed

5. EVALUATE OPERATIONAL SYSTEM

6. MAKE CHANGES OR ABANDON

7. INSTALL, OPERATE, MAINTAIN

*

JOINT APPLICATION DESIGN (JAD)

• TECHNIQUE INVOLVING TEAM OF USERS, IS SPECIALISTS

• INTENSE, STRUCTURED PROCESS

• DEVELOP REQUIREMENTS OR REVIEW DESIGN PROPOSAL

• CAN LAST HOURS, DAYS, OFTEN AT LOCATION REMOVED FROM WORKPLACE

*

COMPUTER-AIDED SOFTWARE ENGINEERING (CASE)

COLLECTION OF SOFTWARE TOOLS TO AUTOMATE SDLC PROCESSES:

• DIAGRAMMING TOOLS• COMPUTER DISPLAY, REPORT GENERATORS• ANALYSIS TOOLS• CENTRAL REPOSITORY• DOCUMENTATION GENERATORS• CODE GENERATORS

*

RAPID APPLICATION DEVELOPMENT (RAD)

• HYBRID OF SDLC, PROTOTYPING, JAD, CASE

• PRODUCE SYSTEM IN 6 MONTHS OR LESS

• STEPS:– PLANNING – USER DESIGN – CONSTRUCTION– IMPLEMENTATION (CUTOVER)

*

OBJECT-ORIENTED METHODS (O-O)

• HOLD GREAT PROMISE TO PRODUCE BETTER SYSTEMS AT LESS COST

• OBJECTS HIGHLY COHESIVE, LOOSELY COUPLED, REUSABLE

• CAN REDUCE ERRORS, IMPROVE MAINTENANCE

*

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

• CONSTRUCTION PHASE

• IMPLEMENTATION PHASE

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

2. GUIDELINES FOR RESPONSE

3. REQUIREMENTS

4. COSTS

5. 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

*

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

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

*

• Mengembangkan Sistem Aplikasi

• Membeli Sistem Aplikasi

• Memfasilitasi User menggunakan komputer untuk mengembangkan sistem aplikasi

Membangun Teknologi Informasi