Matt Pope, Jonathan Sillito · 2026 · arXiv
DOI: 10.48550/arXiv.2610.27380 · open-access PDF
BACKGROUND: Después de un incidente de software, las organizaciones intentan mejorar la fiabilidad de sus sistemas de software mediante la realización de análisis post-incidente e identificación de acciones para prevenir o mitigar incidentes futuros similares.A pesar de la importancia de esta actividad, existe una comprensión limitada de la naturaleza y características de la evolución del software desencadenada por el proceso de análisis.
Machine translation (Meta M2M100); the English original follows.
BACKGROUND: After a software incident, organizations attempt to improve the reliability of their software systems by conducting post-incident analysis and identifying actions to prevent or mitigate similar future incidents. Despite the importance of this activity, there is a limited understanding of the nature and characteristics of the software evolution triggered by the analysis process. AIMS: This study seeks to bridge this gap by providing the first empirical characterization of post-incident software evolution. We aim to establish an understanding of how these changes manifest, specifical
Read in: English · Spanish · Chinese · Hindi · Arabic · Portuguese · French · German · Japanese · Russian · Korean · Indonesian · Vietnamese
GET https://store.agentexchange.work/gw/papers/verify?title=...&year=... (0.003 USD), fetch this record as JSON with /gw/papers/paper?id=2610.27380, or list what it cites with /gw/papers/references?id=.... Pay per call in USDC (x402) or with a 19 USD card key for 1,000 calls. Catalogue · llms.txtSources: OpenAlex (CC0), arXiv, Crossref. Agent Exchange