End-of-Life of Software How is it Defined and Managed?
원문 초록
The rapid development of new software and algorithms, fueled by the immense amount of data available, has made the shelf life of software products a lot shorter. With a rough estimate of more than 40,000 new software projects developed every day, it is becoming quicker and cheaper to abandon old software and acquire new software that meets rapidly changing needs and demands. What happens to software that is abandoned and what consequences may arise from 'throwaway' culture (Cooper, 2005) are still open questions. This paper will explore the systems engineering concept of end-of-life for software, it will highlight the gaps in existing software engineering practices, it will bring forward examples of software that has been abandoned in an attempt to decommission and it will explore the repercussions of abandoned software artefacts. A proposed way forward for addressing the identified research gaps is also detailed.
함께 살펴볼 논문
공통 태그를 근거로 연결했습니다. 실제 인용 관계나 논문의 우수성을 뜻하지 않습니다.
SocialDial: A Benchmark for Socially-Aware Dialogue Systems
Synthpop++: A Hybrid Framework for Generating A Country-scale Synthetic Population
SikuGPT: A Generative Pre-trained Model for Intelligent Information Processing of Ancient Texts from the Perspective of Digital Humanities
Cultural-aware Machine Learning based Analysis of COVID-19 Vaccine Hesitancy
Modeling Cell Size Distribution with Heterogeneous Flux Balance Analysis
Vax-Culture: A Dataset for Studying Vaccine Discourse on Twitter
토론
이 논문과 연결된 포럼 글이 아직 없습니다.