Manajemen Resiko Proyek Pengembangan Perangkat Lunak Berbasis Open/Free Source dengan Menggunakan Metode AS/NZS 4360 dan Analytical Hierarchy Process (AHP)
Article Sidebar
Main Article Content
Abstract
The increasing needs of information and communication technology affects the emerge of information and communication technology projects. One type of its project is software application development project, which this kind of project often totally or partially fails. Indonesia, as one of developing country requires various software types for their business environment in all aspects such as government, private sector or also personal use. The high use of information technology was not followed by awareness and financial ability to use proprietary technology, which is costly and monopolized by some certain vendor. The needs of uncostly and monopolized software was responsed by a software development community and some software vendor which later produced some softwares that are free to use and developed. These kind of softwares are called free and open source software (FOSS). Open source technology that emerged and boomed since few years lately still have various weakness and need to be accomodated by software developers and consumers. Differ from proprietary software, product support from vendor or community isn’t always available. This research’s aim is to identify, structuring and also analyze risk factors of open source-based software development.First stage of this research is to identify risk factors based on Carr et al, (1993) an approach named taxonomy-based risk identification. Combinined with risk identification by Peer, (2006) and FFIEC, (2004), it resulted new factor atribute. Second stage of research is risk assessment of identified risk factors. Most of risk assessment influenced by perception from expert, therefore, the assessment methods is needed to accomodated expert perception. This research used two perception-based methods, qualitative assessment by AS/NZS 4360, (1999) and Analytical Hierarchy Process proposed by Saaty, (1996). Both of this methods was assumed able to map expert’s perception and yield classification and priorities of risk factors.As a conclusion, risk factors identification by Carr et al, (1993) need to be enhanced by new atribute, which is the license options. This atribute becomes an important matter in course of software development because it can influence project succes and software legal attitude. AS/NZS 4360 Qualitative risk assessment classifies risk factors into three classification: extreme, high and moderate (while the low classification isn’t present). AHP risk assesment yields risk factors priority and classification by converting risk weight into four classification : extreme, high, moderate and low.
Keywords : Risk Assessment, Taxonomy Software Development, Qualitative Analysis, Pairwise Comparison, analytical Hierarchy Process.
Downloads
Article Details
References
D. F. Cooper, S. Grey, and G. Raymond, “Project Risk Management Guidelines: Managing Risk in Large Projects and Complex Procurements,” 2005.
R. E. Fairley, “Software Risk Management.”
R. P. Higuera and Y. Y. Haimes, “Software Risk Management,” 1996. [Online]. Available: http://www.rai.com
D. Brandon, Project management for modern information systems. IRM Press, 2006.
J. Masso, F. J. Pino, C. Pardo, F. García, and M. Piattini, “Risk management in the software life cycle: A systematic literature review,” Computer Standards and Interfaces, vol. 71. Elsevier B.V., Aug. 01, 2020. doi: 10.1016/j.csi.2020.103431.
K. Irfandhi, “Risk Management in Information … (Kornelius Irfandhi) RISK MANAGEMENT IN INFORMATION TECHNOLOGY PROJECT: AN EMPIRICAL STUDY.”
P. L. Bannerman, “Risk and risk management in software projects: A reassessment,” Journal of Systems and Software, vol. 81, no. 12, pp. 2118–2133, Dec. 2008, doi: 10.1016/j.jss.2008.03.059.
M. Boban, Ž. Požgaj, and H. Serti?, “STRATEGIES FOR SUCCESSFUL SOFTWARE DEVELOPMENT RISK MANAGEMENT,” 2003.
P. L. Bannerman, “Risk and risk management in software projects: A reassessment,” Journal of Systems and Software, vol. 81, no. 12, pp. 2118–2133, Dec. 2008, doi: 10.1016/j.jss.2008.03.059.
M. J. Carr, S. L. Konda, I. Monarch, F. Carol, U. Clay, and F. Walker, “Taxonomy-Based Risk Identification,” 1993.
B. Edwin Peer, “Solutions to Open Source Risk Assessment: How and When Can Open Source Projects Be Classified As Mature?” [Online]. Available: http://www.groklaw.net
Federal Financial Institutions Examination Council, “Risk Management in Projects Based on Open-Source Software.” [Online]. Available: www.opensource.org.[End
Kindinger, “Risk Factor Analysis-New qualitative model,” 2000.
N. D. Linh, P. D. Hung, V. T. Diep, and T. D. Tung, “Risk management in projects based on open-source software,” in ACM International Conference Proceeding Series, Association for Computing Machinery, 2019, pp. 178–183. doi: 10.1145/3316615.3316648.
J. Emblemsvåg and L. E. Kjølstad, “Qualitative risk analysis: Some problems and remedies,” Management Decision, vol. 44, no. 3. pp. 395–408, 2006. doi: 10.1108/00251740610656278.
T. L. Saaty, “Decision making with the analytic hierarchy process,” 2008.