Merancang Perangkat Lunak Sistem Penjaminan Mutu Internal (SPMI) Perguruan Tinggi yang Memiliki Daya Adaptasi Terhadap Perubahan Kebutuhan Pengguna secara Cepat dan Sering
DOI:
https://doi.org/10.36722/sst.v5i3.372Abstract
Abstrak – Salah satu permasalahan mendasar proses pengembangan perangkat lunak adalah kebutuhan yang tidak tertangkap lengkap saat awal pengembangan, atau abstraksi kebutuhan pengguna yang kurang terpetakan secara sistematis, runut oleh pengembang. Ketidaksempurnaan pengungkapan kebutuhan pengguna tersebut dapat mengakibatkan produk perangkat lunak yang kurang lengkap bahkan bisa tidak sesuai dengan kebutuhan pengguna. Ketidaksesuaian baru dapat diamati oleh pengguna setelah pengembang menyelesaikan setiap rilis produk. Pada paper ini akan ditunjukkan bagaimana sebuah perangkat lunak SPMI dirancang, diterima oleh pengguna, diberikan masukan oleh pengguna atas masukan perbaikan pada kurun waktu tertentu. Metode yang digunakan dalam proses pengembangan perangkat lunak adalah metode DevOps yang memiliki kemampuan untuk mensinkronkan kebutuhan pengguna dengan pengembangan aplikasi yang berkelanjutan, cepat selama pengembangan dan pengoperasian berlangsung. Metode DevOps tidak hanya mengelola bagian pengembangan tetapi juga mengelola bagian pengoperasian. Hasil perancangan menunjukkan bahwa DevOps menjadi pendekatan tepat agar perangkat lunak pengembangan SPMI dikembangkan dari kecil menjadi besar, step by step tetapi tanpa kehilangan penelusuran antara rilis produk. Dan yang lebih mendasar, DevOps mampu memperkecil gap antara pengembang dengan pengguna aplikasi SPMI-PT. Melalui metode DevOps, pengembangan dan pengoperasian memiliki keterhubungan sebagai timbal balik antara pengembangan dengan pengoperasian maupun sebaliknya.
Abstract – One of the fundamental problems of the software development process is the requirement that is not completely captured at the beginning of development, or the abstraction of user requirements that are less systematically mapped out, by the developer. Imperfections in disclosing the requirements of these users can result in incomplete software products that may not even match the user's needs. New nonconformities can be observed by users after the Developer completes each product release. In this paper, we will show how an SPMI software is designed, accepted by the user, given input by the user for input improvement in a certain period time. The method used in the software development process is the DevOps method which can synchronize user requirements with rapid, rapid application development during development and operation. The DevOps method not only manages the development part but also manages the operation part. The design results show that DevOps is the right approach so that SPMI development software is developed from small to large, step by step but without losing traces between product releases. And more fundamentally, DevOps can reduce the gap between developers and SPMI-PT application users. Through the DevOps method, development and operation have a relationship as a trade-off between development and operations and vice versa.
Keywords – Software engineering, Devops, Continuous improvementReferences
Anonim, Buku Pedoman Sistem Penjaminan Mutu Internal (SPM-PT), Jakarta: Dirjen DIKTI.https://spmi.ristekdikti.go.id/uploads/publications/1.%20Kebijakan%20Nasional%20SPM%20Dikti.pdf.
A. D. Lestari, “Kampus Disruptif - Pusat.†.
R. de Feijter, “Towards the adoption of DevOps in software product organizations: A Maturity Model Approach,†Tech. Rep., 2017.
CaTechnology, “TechInsights Report : What Smart Businesses Know About DevOps.†p. 300, 2013.
R. Wilsenach, “DevOpsCulture,†vol. 4, no. 1, pp. 75–84, 2015.
L. Ellen, L. R.- Kalliosaari, S. Mäkinen, and L. E. Lwakatare, “DevOps Adoption Benefits and Challenges in Practice : A Case Study,†pp. 590 – 597, 2016.
A. Taryana, I. Setiawan, A. Fadli, and E. Murdyantoro, “Pioneering the automation of lnternal quality assurance system of higher education (IQAS-HE) using DevOps approach,†Proc. - 2017 Int. Conf. Sustain. Inf. Eng. Technol. SIET 2017, vol. 2018-Janua, no. August 2018, pp. 259–264, 2018.
J. Wettinger, U. Breitenbücher, and F. Leymann, “Standards-based DevOps Automation and Integration Using TOSCA Institute of Architecture of Application Systems Standards - based DevOps Automation and Integration Using TOSCA,†Proc. 7th Int. Conf. Util. Cloud Comput. (UCC 2014), 2014.
J. Wettinger, U. Breitenbücher, and F. Leymann, “DevOpSlang - Bridging the gap between development and operations,†Lect. Notes Comput. Sci. (including Subser. Lect. Notes Artif. Intell. Lect. Notes Bioinformatics), vol. 8745 LNCS, pp. 108–122, 2014.
S. Carrizo, S. Cucu, and S. Modir, Using Liberty for DevOps, Continuous Delivery, and Deployment. 2015.
W. Workflow and T. Binz, “web extra Portable Cloud Services Using TOSCA,†IEEE Internet Comput., p. 16, 2012.
T. Binz et al., “Institute of Architecture of Application Systems TOSCA : Portable Automated Deployment and Management of Cloud Applications The original publication will be available at www.springerlink.com TOSCA: Portable Automated Deployment and Management of Cloud Ap,†2014.
T. Binz, C. Fehling, F. Leymann, A. Nowak, and D. Schumm, “Formalizing the cloud through enterprise topology graphs,†Proc. - 2012 IEEE 5th Int. Conf. Cloud Comput. CLOUD 2012, pp. 742–749, 2012.
R. Barry and H. Jay, Operation Management. New Jersey: Prentice Hall, 2005.
A. Taryana, B. Wijayanto, and N. UBayashi, “Model-Driven Development : Fase Awal Verifikasi Model Design Rekam Medis Elektronis Menggunakan Graf Lengkap,†JMP FMIPA Unsoed, vol. 6, pp. 53–64, 2014.
