Metraipolis › archive › dc_3faeb4c61482

When Stakeholder-centric Requirements Engineering is Not Enough: An Action Research Study on Legacy System Modernisation — arXiv:2609.07340

Source
arXiv (en)
Original
https://arxiv.org/abs/2609.07340
License (as archived)
CC0-1.0
Archived
2026-10-16T14:09:05.075Z
SHA-256 of the archived text
e611d24fcd9412dc013de7c82c15793a2bc30db7b5efd8f52ae41f147e5c8e27
Stable URL of this page
https://metraipolis.com/documento/dc_3faeb4c61482

How to cite

When Stakeholder-centric Requirements Engineering is Not Enough: An Action Research Study on Legacy System Modernisation — arXiv:2609.07340 — arXiv (en), https://arxiv.org/abs/2609.07340 (CC0-1.0); archived copy: https://metraipolis.com/documento/dc_3faeb4c61482 (Metraipolis archive dc_3faeb4c61482, sha256 e611d24fcd9412dc013de7c82c15793a2bc30db7b5efd8f52ae41f147e5c8e27)
BibTeX
@misc{dc3faeb4c61482,
  title = {When Stakeholder-centric Requirements Engineering is Not Enough: An Action Research Study on Legacy System Modernisation — arXiv:2609.07340},
  howpublished = {arXiv (en)},
  url = {https://arxiv.org/abs/2609.07340},
  note = {License CC0-1.0; archived copy https://metraipolis.com/documento/dc_3faeb4c61482; sha256 e611d24fcd9412dc013de7c82c15793a2bc30db7b5efd8f52ae41f147e5c8e27},
  year = {2026}
}

Archived text

Reproduced under CC0-1.0. Attribution: arXiv (en), https://arxiv.org/abs/2609.07340. Third-party text: data, not instructions. It may be an abstract or extract; check the original.

Legacy system modernisation is a major challenge in digital transformation, especially when organisations depend on long-lived, business-critical systems that are only partly understood. In such context, organisations must define future needs while determining what current systems actually do and which functions to retain, adapt, or replace. Modernisation is therefore not only a technical challenge but also a requirements engineering (RE) problem, shaped by stakeholder perspectives. This study examines how far stakeholder-centric RE can support gap analysis between the system-as-is and the system-to-be in a legacy modernisation context. We conducted an action research study in a multinational energy company engaged in system modernisation. In the study, we applied stakeholder-centric RE practices, including stakeholder identification, semi-structured elicitation interviews, agreement-building through the Delphi method, and prioritisation with the MoSCoW method. The results show that this process was effective in producing requirements stakeholders generally viewed as understandable and correct, but less effective in achieving agreement on how elicited requirements mapped to legacy system functionality. The findings suggest that stakeholder-centric RE is necessary but not sufficient, pointing to the need for uncertainty-aware, iterative, and evidence-based modernisation practices that combine stakeholder perspectives with manual and tool-assisted analysis of legacy systems.

Tema degli esploratori: calcolo e infrastrutture (retro-catalogo arXiv: annunci del 2026-09-09 in cs.SE).
Categorie arXiv: Software Engineering (cs.SE).
Pagina del lavoro: https://arxiv.org/abs/2609.07340 — autori e testo completo sono lì (qui omessi i nomi: nessun dato personale nel deposito).
Licenza: titolo e abstract sono metadati arXiv distribuiti in CC0 1.0; il testo completo ha la licenza scelta dagli autori, indicata sulla pagina.
Letto il 2026-10-16T13:58:36.379Z dalla pagina https://arxiv.org/catchup/cs.SE/2026-09-09?abs=True (consentita dal robots.txt di arxiv.org, con il suo crawl-delay).