pertemuan 3 apsi - studi kelayakan dan manaj resiko
DESCRIPTION
studi kelayakan apsiTRANSCRIPT
Studi Kelayakan dan Manajemen Resiko
Pertemuan 3
Analisis dan Perancangan Sistem Informasi
Kendall & Kendall 3-2
Feasibility/KelayakanFeasibility study/Studi kelayakan
merupakan upaya untuk meninjau manfaat operasional, teknis, dan ekonomi dari suatu proyek yang diusulkan.
Jenis Studi KelayakanKelayakan teknisKelayakan ekonomisKelayakan operasional
Kendall & Kendall 3-3
Kendall & Kendall 3-4
Kelayakan TeknisKelayakan teknis meninjau apakah
sumberdaya teknis saat ini sesuai untuk sistem yang baru
Jika sumberdaya teknis tidak tersedia, maka perlu diupgrade sampai memenuhi level teknologi untuk sistem yang baru
Kendall & Kendall 3-5
Kelayakan EkonomiKelayakan ekonomi menentukan
apakah waktu dan uang tersedia untuk mengembangkan sistem
Meliputi pembayaran:Peralatan baruPerangkat kerasPerangkat lunak
Kendall & Kendall 3-6
Kelayakan OperasionalKelayakan operasional menentukan
apakah sumber daya manusia cukup tersedia untuk mengoperasikan sistem setelah diinstal
Pengguna yang tidak memerlukan sistem baru berpotensi untuk menghalang-halangi sistem dioperasionalkan
Manajemen Resiko Manajemen resiko berkaitan dengan aktifitas
untuk identifikasi resiko dan membuat rencana untuk meminimalkan efek rasiko pada suatu proyek.
Resiko adalah kemungkinan terjadinya suatu gangguan dalam proyek.Resiko proyek mempengaruhi jadwal dan
sumber daya;Resiko produk mempengaruhi kualitas atau
kinerja dari PL yang dikembangkan;Resiko bisnis mempengaruhi pengembangan
organisasi atau pengadaan PL.
22/04/23 Eva Hariyanti, MT
Contoh Resiko Perangkat Lunak
22/04/23 Eva Hariyanti, MT
Risk Affects Description
Staff turnover Project Experienced staff will leave the project before it is finished.
Management change Project There will be a change of organisational management withdifferent priorities.
Hardware unavailability Project Hardware that is essential for the project will not bedelivered on schedule.
Requirements change Project andproduct
There will be a larger number of changes to therequirements than anticipated.
Specification delays Project andproduct
Specifications of essential interfaces are not available onschedule
Size underestimate Project andproduct
The size of the system has been underestimated.
CASE tool under-performance
Product CASE tools which support the project do not perform asanticipated
Technology change Business The underlying technology on which the system is built issuperseded by new technology.
Product competition Business A competitive product is marketed before the system iscompleted.
Proses Manajemen Resiko Identifikasi resiko
Identifikasi resiko proyek, resiko produk, dan reiko bisnis.
Analisis resikoMeninjau dampak dan akibat dari terjadinya
resiko. Perencanaan resiko
Membuat rencana untuk menghindari atau meminimalkan dampak resiko.
Monitoring resikoMonitor resiko-resiko yang terjadi pada proyek.
22/04/23 Eva Hariyanti, MT
22/04/23 Eva Hariyanti, MT
Proses Manajemen Resiko
22/04/23 Eva Hariyanti, MT
Risk avoidanceand contingency
plans
Risk planning
Prioritised risklist
Risk analysis
List of potentialrisks
Riskidentification
Riskassessment
Riskmonitoring
Identifikasi ResikoResiko teknologi.Resiko orang.Resiko organisasi.Resiko requirement.Resiko estimasi
22/04/23 Eva Hariyanti, MT
Contoh Resiko dan Jenis Resiko
22/04/23 Eva Hariyanti, MT
Risk type Possible risks
Technology The database used in the system cannot process as many transactions per secondas expected.Software components that should be reused contain defects that limit theirfunctionality.
People It is impossible to recruit staff with the skills required.Key staff are ill and unavailable at critical times.Required training for staff is not available.
Organisational The organisation is restructured so that different management are responsible forthe project.Organisational financial problems force reductions in the project budget.
Tools The code generated by CASE tools is inefficient.CASE tools cannot be integrated.
Requirements Changes to requirements that require major design rework are proposed.Customers fail to understand the impact of requirements changes.
Estimation The time required to develop the software is underestimated.The rate of defect repair is underestimated.The size of the software is underestimated.
Analisis Resiko Meninjau peluang terjadinya resiko dan
tingkat keseriusan setiap resiko. Peluang terjadinya resiko bisa:
Sangat rendah,Rendah,Sedang,Tinggi,Atau sangat tinggi.
Efek resiko mungkin bersifat katrostopik, serius, dapat ditoleransi, atau mungkin tidak signifikan.
22/04/23 Eva Hariyanti, MT
Contoh Analisis Resiko (1)
22/04/23 Eva Hariyanti, MT
Risk Probability Effects
Organisational financial problems force reductions inthe project budget.
Low Catastrophic
It is impossible to recruit staff with the skills requiredfor the project.
High Catastrophic
Key staff are ill at critical times in the project. Moderate Serious
Software components that should be reused containdefects which limit their functionality.
Moderate Serious
Changes to requirements that require major designrework are proposed.
Moderate Serious
The organisation is restructured so that differentmanagement are responsible for the project.
High Serious
Contoh Analisis Resiko (2)
22/04/23 Eva Hariyanti, MT
Risk Probability Effects
The database used in the system cannot process asmany transactions per second as expected.
Moderate Serious
The time required to develop the software isunderestimated.
High Serious
CASE tools cannot be integrated. High Tolerable
Customers fail to understand the impact ofrequirements changes.
Moderate Tolerable
Required training for staff is not available. Moderate Tolerable
The rate of defect repair is underestimated. Moderate Tolerable
The size of the software is underestimated. High Tolerable
The code generated by CASE tools is inefficient. Moderate Insignificant
Perencanaan Resiko Menimbang setiap resiko, dan membuat strategi untuk mengelola resiko tersebut. Ada 3 jenis strategi:
Strategi menghindar (Avoidance strategies)○ Memperkecil peluang terjadinya resiko.
Startegi meminimalkan resiko (Minimisation strategies)○ Mengurangi dampak dari resiko pada proyek atau produk.
Rencana kontingensi○ Jika resiko terjadi, maka rencana kontingensi dijalankan untuk menghadapi/ menanggulangi resiko tersebut.
22/04/23 Eva Hariyanti, MT
Strategi Manajemen Resiko (1)
22/04/23 Eva Hariyanti, MT
Risk Strategy
Organisational financial problems
Prepare a briefing document for senior management showing how the project is making a very important contribution to the goals of the business.
Recruitment problems
Alert customer of potential difficulties and the possibility of delays, investigate buying-in components.
Staff illness Reorganise team so that there is more overlap of work and people therefore understand each other’s jobs.
Defective components
Replace potentially defective components with bought-in components of known reliability.
Strategi Manajemen Resiko (2)
22/04/23 Eva Hariyanti, MT
Risk Strategy
Requirementschanges
Derive traceability information to assess requirementschange impact, maximise information hiding in thedesign.
Organisationalrestructuring
Prepare a briefing document for senior managementshowing how the project is making a very importantcontribution to the goals of the business.
Databaseperformance
Investigate the possibility of buying a higher-performance database.
Underestimateddevelopment time
Investigate buying in components, investigate use of aprogram generator
Monitoring ResikoMeninjau setiap resiko yang
teridentifikasi secara periodik, untuk menentukan naik atau turunnya peluang terjadinya resiko tersebut.
Juga meninjau apakah ada perubahan dari dampak.
Setiap resiko “kunci” perlu didiskusikan pada pertemuan/ rapat manajemen.
22/04/23 Eva Hariyanti, MT
Indikator Resiko
22/04/23 Eva Hariyanti, MT
Risk type Potential indicators
Technology Late delivery of hardware or support software, many reportedtechnology problems
People Poor staff morale, poor relationships amongst team member,job availability
Organisational Organisational gossip, lack of action by senior management
Tools Reluctance by team members to use tools, complaints aboutCASE tools, demands for higher-powered workstations
Requirements Many requirements change requests, customer complaints
Estimation Failure to meet agreed schedule, failure to clear reporteddefects
TUGASLengkapi proposal proyek Anda
dengan analisis studi kelayakan. Untuk setiap kebutuhan fungsional dan non-fungsional yang diusulkan, sertakan alasan-alasan kelayakan yang ditinjau dari kelayakan teknis, ekonomi, dan operasional.
Kendall & Kendall 3-22