Melola Discovery

← Melola Discovery

Akses terbuka Jurnal SINTA 1

Exposing Causative Factors on Software Discontinuity using an Elaborative Qualitative Method

Journal of Information Systems Engineering and Business Intelligence · Vol. 11 No. 2 (2025) · hlm. 103–114

DOI
10.20473/jisebi.11.2.103-114
ISSN
2443-2555, 2598-6333
Terbit
2025-07-22
Penerbit
Universitas Airlangga
Bahasa
eng
Lisensi
creativecommons.org/licenses/by/4.0

Abstrak

Background: Software discontinuity due to the inability to accommodate the needs of users is a the significant challenge facing the software development life cycle. This implied that the development team must be capable of producing software with extended lifespan, including the ability to detect outages early, to maintain continuity. Organizations need to determine the contributing and inhibiting factors responsible for discontinuity usage. Objective: This research aimed to explore the factors that contribute and inhibit the discontinuation of software use in organizations as well as the prevention strategies. Methods: The summative content analysis technique was used to capture, codify, and classify statements from respondents to discover usage pattern. Data were collected through interview and questionnaire techniques with 10 respondents from various Indonesian companies. The respondents had various sectoral backgrounds in software usage for more than a year. The data collected were compared, contrasted, and synthesized to deliver a holistic pattern among respondents. Results: The result showed that 10 key factors contributed to software discontinuity, namely Loss of Perceived Usefulness (LUS), Loss of Perceived Ease of Use (LEU), Decreased Effort Expectancy (DEX), Decreased Performance Expectancy (DPX), Social Influence (SOI), Lack of Facilitating Conditions (LFC), Decreased Price Value (DPV), Lack of Habit (LHB), Hedonic Motivation (HDM), and Loss of Perceived Behavioral Control (LBC). The factors were further categorized into three big issues, including Software Usability (LUS, LEU, DEX, and DPX), External Triggers (DPV, SOI, and LBC), and Risk Management after Discontinuity (LFC, LHB, and SOI). Furthermore, the results indicated that nine factors contributed to software discontinuity except HDM with LEU and LUS having weak significance since most respondents stated partial agreement and disagreements. Conclusion: This research employed a rigorous qualitative method to validate the factors in the proposed software discontinuity model with 10 causative factors. The acquired knowledge is expected to aid organizations or related development units to build software that accommodates user needs, including meeting long-term business targets. Keywords: Software, Software Discontinuity, Influencing Factors, Qualitative Method

Jaringan kolaborasi para penulis

12 penulis · 34 tautan kepenulisan bersama

Arahkan kursor atau ketuk sebuah nama untuk menyorot rekan penulisnya. Klik dua kali untuk membuka halaman penulis.

  • Telkom University
  • Afiliasi tidak diketahui
  • Organisasi berbeda
  • Organisasi sama
  • Afiliasi tidak diketahui
  • Garis lebih tebal = lebih banyak artikel bersama · lingkaran lebih besar = lebih banyak artikel
Tampilkan sebagai tabel
Rekan penulisOrganisasiArtikel bersama
Mira Kania SabariahAfiliasi tidak diketahui1
Kemas Rahmat Saleh WiharjaTelkom University1
Prasti Eko YunantoTelkom University1
Untari Novia WisestyTelkom University1
Febryanti SthevanieTelkom University1
Gamma KosalaTelkom University1
Aditya Firman IhsanTelkom University1
Mahmud Dwi SulistiyoTelkom University1
Donni RichasdyTelkom University1

Afiliasi berasal dari OpenAlex; metadata OAI-PMH jurnal tidak memuatnya. Penulis tanpa ID OpenAlex dicocokkan berdasarkan nama, sehingga dua orang bisa tergabung atau satu orang bisa terpisah.

Sumber metadata: OAI-PMH (metadata jurnal) https://e-journal.unair.ac.id/JISEBI/oai, pertama di-harvest 29 Okt 2026, terakhir terlihat 15 Nov 2026.
Metadata asli (oai_dc)
<oai_dc:dc xmlns="http://www.openarchives.org/OAI/2.0/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:oai_dc="http://www.openarchives.org/OAI/2.0/oai_dc/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.openarchives.org/OAI/2.0/oai_dc/  http://www.openarchives.org/OAI/2.0/oai_dc.xsd">
	<dc:title xml:lang="en-US">Exposing Causative Factors on Software Discontinuity using an Elaborative Qualitative Method</dc:title>
	<dc:creator>Gandhi, Arfive</dc:creator>
	<dc:creator>Kusumo, Dana Sulistiyo</dc:creator>
	<dc:creator>Sardi, Indra Lukmana</dc:creator>
	<dc:description xml:lang="en-US">Background: Software discontinuity due to the inability to accommodate the needs of users is a the significant challenge facing the software development life cycle. This implied that the development team must be capable of producing software with extended lifespan, including the ability to detect outages early, to maintain continuity. Organizations need to determine the contributing and inhibiting factors responsible for discontinuity usage. 
Objective: This research aimed to explore the factors that contribute and inhibit the discontinuation of software use in organizations as well as the prevention strategies. 
Methods: The summative content analysis technique was used to capture, codify, and classify statements from respondents to discover usage pattern. Data were collected through interview and questionnaire techniques with 10 respondents from various Indonesian companies. The respondents had various sectoral backgrounds in software usage for more than a year. The data collected were compared, contrasted, and synthesized to deliver a holistic pattern among respondents. 
Results: The result showed that 10 key factors contributed to software discontinuity, namely Loss of Perceived Usefulness (LUS), Loss of Perceived Ease of Use (LEU), Decreased Effort Expectancy (DEX), Decreased Performance Expectancy (DPX), Social Influence (SOI), Lack of Facilitating Conditions (LFC), Decreased Price Value (DPV), Lack of Habit (LHB), Hedonic Motivation (HDM), and Loss of Perceived Behavioral Control (LBC). The factors were further categorized into three big issues, including Software Usability (LUS, LEU, DEX, and DPX), External Triggers (DPV, SOI, and LBC), and Risk Management after Discontinuity (LFC, LHB, and SOI). Furthermore, the results indicated that nine factors contributed to software discontinuity except HDM with LEU and LUS having weak significance since most respondents stated partial agreement and disagreements. 
Conclusion: This research employed a rigorous qualitative method to validate the factors in the proposed software discontinuity model with 10 causative factors. The acquired knowledge is expected to aid organizations or related development units to build software that accommodates user needs, including meeting long-term business targets. 
Keywords: Software, Software Discontinuity, Influencing Factors, Qualitative Method</dc:description>
	<dc:publisher xml:lang="en-US">Universitas Airlangga</dc:publisher>
	<dc:date>2025-07-22</dc:date>
	<dc:type>info:eu-repo/semantics/article</dc:type>
	<dc:type>info:eu-repo/semantics/publishedVersion</dc:type>
	<dc:format>text/xml</dc:format>
	<dc:format>application/pdf</dc:format>
	<dc:identifier>https://e-journal.unair.ac.id/JISEBI/article/view/56129</dc:identifier>
	<dc:identifier>10.20473/jisebi.11.2.103-114</dc:identifier>
	<dc:source xml:lang="en-US">Journal of Information Systems Engineering and Business Intelligence; Vol. 11 No. 2 (2025): June; 103-114</dc:source>
	<dc:source>2443-2555</dc:source>
	<dc:source>2598-6333</dc:source>
	<dc:language>eng</dc:language>
	<dc:relation>https://e-journal.unair.ac.id/JISEBI/article/view/56129/33621</dc:relation>
	<dc:relation>https://e-journal.unair.ac.id/JISEBI/article/view/56129/33430</dc:relation>
	<dc:rights xml:lang="en-US">Copyright (c) 2025 The Authors. Published by Universitas Airlangga.</dc:rights>
	<dc:rights xml:lang="en-US">http://creativecommons.org/licenses/by/4.0</dc:rights>
</oai_dc:dc>