1 / 23

Pertemuan 4 Membangun Teknologi Informasi

Matakuliah : H0402/PENGELOLAAN SISTEM KOMPUTER Tahun : 2005 Versi : 1/0. Pertemuan 4 Membangun Teknologi Informasi. Learning Outcomes. Pada akhir pertemuan ini, diharapkan mahasiswa akan mampu :

svea
Télécharger la présentation

Pertemuan 4 Membangun Teknologi Informasi

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Matakuliah : H0402/PENGELOLAAN SISTEM KOMPUTER Tahun : 2005 Versi : 1/0 Pertemuan 4Membangun Teknologi Informasi

  2. Learning Outcomes Pada akhir pertemuan ini, diharapkan mahasiswa akan mampu : • Menjelaskan metodologi pengembangan teknologi informasi, metodologi pembelian sistem aplikasi serta penerapan end user computing

  3. Outline Materi • Mengembangkan Sistem Aplikasi • Membeli Sistem Aplikasi • Memfasilitasi User menggunakan komputer untuk mengembangkan sistem aplikasi

  4. SYSTEMS DEVELOPMENT LIFE CYCLE (SDLC) • DEFINITION PHASE: • Feasibility analysis • Requirement definition • CONSTRUCTION PHASE: • System design • System building • System testing • IMPLEMENTATION PHASE: • Installation • Operations • Maintenance *

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

  6. 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 *

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

  8. RAPID APPLICATION DEVELOPMENT (RAD) • HYBRID OF SDLC, PROTOTYPING, JAD, CASE • PRODUCE SYSTEM IN 6 MONTHS OR LESS • STEPS: • PLANNING • USER DESIGN • CONSTRUCTION • IMPLEMENTATION (CUTOVER) *

  9. 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 *

  10. SYSTEMS DEVELOPMENT APPROACHES • SYSTEMS DEVELOPMENT LIFE CYCLE (SDLC) • PROTOTYPING • PURCHASED SOFTWARE • OUTSOURCING (SYSTEMS INTEGRATOR) • END USER DEVELOPMENT *

  11. 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 *

  12. THE PURCHASING PROCESS • DEFINITION PHASE • CONSTRUCTION PHASE • IMPLEMENTATION PHASE

  13. 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 *

  14. SAMPLE CONTENTS OF RFP • INTRODUCTION • GUIDELINES FOR RESPONSE • REQUIREMENTS • COSTS • SIGNATURE PAGE

  15. PACKAGE CAPABILITIES COMPANY NEEDS IDENTIFY DISCREPANCIES CHOOSE ALTERNATIVES MODIFY PACKAGE LIVE WITH PROBLEMS CHANGE COMPANY MATCHING COMPANY NEEDS WITH PACKAGE CAPABILITIES

  16. ROLES FOR PURCHASING PACKAGED APPLICATIONS • PROJECT MANAGER:Manages process, responsible for the success of the project, may be user butISexpertise required • VENDOR:Must be responsive to customer’s needs • PURCHASING SPECIALIST:Helps prepareRFP, assist in entire process • ATTORNEYS:Oversee writing, approval of contract *

  17. END-USER COMPUTING • HANDS-ON USE OF COMPUTERS BY EMPLOYEES • ENTER DATA • MAKE INQUIRIES • PREPARE REPORTS • PERFORM STATISTICAL ANALYSIS • ANALYZE PROBLEMS • DEVELOP WEB PAGES *

  18. PRIMARY DRIVERS • AVAILABILITY OF LOW-COST MICROCOMPUTERS: • HIGH-LEVEL LANGUAGES • COMPUTER LITERACY AMONG COLLEGE GRADUATES, PROFESSIONALS • INCREASED USER FRUSTRATIONS ABOUT NEW PROJECT BACKLOGS *

  19. USER APPLICATION DEVELOPMENT • USE OF COMPUTER TOOLS • DEVELOP BUSINESS APPLICATIONS • USERS ARE NOT IS SPECIALISTS • INVOLVES APPLICATION, TOOL & DEVELOPER

  20. DEVELOPED FOR OTHER USERS DEVELOPED FOR SELF USER ONLY SMALL, SIMPLE LARGE, COMPLEX GUIDELINES FOR CHOOSING DEVELOPMENT PROCESS 1. SDLC OR PROTOTYPING, DISCIPLINED APPROACH TO DEFINITION & IMPLEMENTATION 2. SDLC, CLEAR “HANDS-OFF” BETWEEN PHASES 3. “COLLAPSED” LIFE CYCLE 4. DISCIPLINED, ITERATIVE DEVELOPMENT

  21. ORGANIZATION LEVEL CONTEXT: ORGANIZATIONAL LEVEL FACTORS DEPARTMENTAL LEVEL FACTORS STATUS OF IS/USER PARTNERSHIP STRATEGY SUPPORT & CONTROL ACTIONS TECHNOLOGY INDIVIDUAL LEVEL USER DEVELOPER DEVELOPMENT PROCESS TASK TOOL LEVERAGING END-USER COMPUTING *Based on Branceau & Brown, 1993

  22. 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 *

  23. Membangun Teknologi Informasi • Mengembangkan Sistem Aplikasi • Membeli Sistem Aplikasi • Memfasilitasi User menggunakan komputer untuk mengembangkan sistem aplikasi

More Related