View in EDS

Data Schema Evolution for the Self‐Adaptive Software Domain: A Systematic Mapping Study.

Saved in:
Bibliographic Details
Title: Data Schema Evolution for the Self‐Adaptive Software Domain: A Systematic Mapping Study.
Authors: Campos, Gabriel Nagassaki1 (AUTHOR), de Moraes, Fernando Rodrigues1 (AUTHOR), de Almeida, Nathalia Rodrigues1 (AUTHOR), de Almeida, Daniel1 (AUTHOR), Affonso, Frank José1 (AUTHOR) f.affonso@unesp.br
Source: Software: Practice & Experience. Aug2026, Vol. 56 Issue 8, p1034-1062. 29p.
Subjects: Self-adaptive software, Database management, Data modeling, Software maintenance
Abstract: Context: Self‐adaptive Software (SaS) is a special category of software systems that enables adaptation at runtime to address new user requirements or changes in its execution environment. This article focuses on a specific category of SaS named SaS2DB, which encompasses systems that require the storage of data in a database. In short, a SaS2DB must understand the changing needs and implement a strategy to execute the evolution of its data schema. The evolution of data schema is a complex issue that encompasses data schema migration, data migration, and other non‐functional requirements. Motivation: Despite the importance of this research topic, there is a lack of understanding of how the design of data schema evolution for the SaS domain has been conducted. Objective: The main purpose of this article is to provide an overview of data schema evolution for the SaS domain based on 19 relevant studies. Methods: To do so, a Systematic Mapping Study (SMS) was conducted, following the guidelines proposed by Petersen et al. Results: This SMS offers a comprehensive overview of the aforementioned research area, presenting key evidence on the main non‐functional attributes, data models, application domains, and migration strategies adopted in the design of data schema evolution for SaS. Conclusion: Moreover, this SMS presents the main findings and several open challenges, highlighting a deep relationship between the design of a SaS and the choice of a suitable solution to support the evolution of its data schema. [ABSTRACT FROM AUTHOR]
Copyright of Software: Practice & Experience is the property of Wiley-Blackwell and its content may not be copied or emailed to multiple sites without the copyright holder's express written permission. Additionally, content may not be used with any artificial intelligence tools or machine learning technologies. However, users may print, download, or email articles for individual use. This abstract may be abridged. No warranty is given about the accuracy of the copy. Users should refer to the original published version of the material for the full abstract. (Copyright applies to all Abstracts.)
Database: Engineering Source
Description
Abstract:Context: Self‐adaptive Software (SaS) is a special category of software systems that enables adaptation at runtime to address new user requirements or changes in its execution environment. This article focuses on a specific category of SaS named SaS2DB, which encompasses systems that require the storage of data in a database. In short, a SaS2DB must understand the changing needs and implement a strategy to execute the evolution of its data schema. The evolution of data schema is a complex issue that encompasses data schema migration, data migration, and other non‐functional requirements. Motivation: Despite the importance of this research topic, there is a lack of understanding of how the design of data schema evolution for the SaS domain has been conducted. Objective: The main purpose of this article is to provide an overview of data schema evolution for the SaS domain based on 19 relevant studies. Methods: To do so, a Systematic Mapping Study (SMS) was conducted, following the guidelines proposed by Petersen et al. Results: This SMS offers a comprehensive overview of the aforementioned research area, presenting key evidence on the main non‐functional attributes, data models, application domains, and migration strategies adopted in the design of data schema evolution for SaS. Conclusion: Moreover, this SMS presents the main findings and several open challenges, highlighting a deep relationship between the design of a SaS and the choice of a suitable solution to support the evolution of its data schema. [ABSTRACT FROM AUTHOR]
ISSN:00380644
DOI:10.1002/spe.70083