2022
DOI: 10.1145/3542823
|View full text |Cite
|
Sign up to set email alerts
|

Code and Data Synthesis for Genetic Improvement in Emergent Software Systems

Abstract: Emergent software systems are assembled from a collection of small code blocks, where some of those blocks have alternative implementation variants; they optimise at run-time by learning which compositions of alternative blocks best suit each deployment environment encountered. In this paper we study the automated synthesis of new implementation variants for a running system using genetic improvement (GI) . Typical GI approaches, however, r… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
6
0

Year Published

2024
2024
2024
2024

Publication Types

Select...
1

Relationship

0
1

Authors

Journals

citations
Cited by 1 publication
(6 citation statements)
references
References 26 publications
0
6
0
Order By: Relevance
“…Response time and responsiveness Filho et al [8], [9], [12], [18], [19] Response time and responsiveness Cardozo [4] X Wang et al [20]- [22] Responsiveness, availability, throughput, successability, reliability Younes [6] Hybrid (user's feedback) Mannava and Ramesh [23] Process CPU time, heap memory Ding et al [24] X Rosa et al [25] X Tan et al [26] Dependability and responsiveness Gonçalves et al [27] Responsiveness Yan et al [28] Responsiveness Belhaj et al [29] Availability, responsiveness, service calls Schneider et al [30], [31] Throughput, energy costs, efficiency Ganguly and Sakib [32] Failure rate, responsiveness Deshpande et al [33] Response time, availability, throughput, successability Kulkarni et al [34] Response time, model confidence, and CPU consumption Rainford et al [35] Response time, Resource utilization Silva et al [36] Resource utilization…”
Section: Approaches Non-functional Requirement Functional Requirement...mentioning
confidence: 99%
See 4 more Smart Citations
“…Response time and responsiveness Filho et al [8], [9], [12], [18], [19] Response time and responsiveness Cardozo [4] X Wang et al [20]- [22] Responsiveness, availability, throughput, successability, reliability Younes [6] Hybrid (user's feedback) Mannava and Ramesh [23] Process CPU time, heap memory Ding et al [24] X Rosa et al [25] X Tan et al [26] Dependability and responsiveness Gonçalves et al [27] Responsiveness Yan et al [28] Responsiveness Belhaj et al [29] Availability, responsiveness, service calls Schneider et al [30], [31] Throughput, energy costs, efficiency Ganguly and Sakib [32] Failure rate, responsiveness Deshpande et al [33] Response time, availability, throughput, successability Kulkarni et al [34] Response time, model confidence, and CPU consumption Rainford et al [35] Response time, Resource utilization Silva et al [36] Resource utilization…”
Section: Approaches Non-functional Requirement Functional Requirement...mentioning
confidence: 99%
“…As seen in Table 3, most ESS approaches are based on nonfunctional adaptation goals, including response time [8], [9], [12], [15]- [19], [33], [35], responsiveness [20]- [22], [27]- [29], availability [20]- [22], [29], throughput [20]- [22], [30], [31], [33], successability [20]- [22], [33], reliability [20]- [22], process CPU time [23], [34], heap memory [23], dependability [26], service calls [29], energy cost [30], [31] and failure rate [32]. Some approaches only target one adaptation goal at a time such as [27], [28], while others tackle multiple adaptation goals.…”
Section: ) Non-functional Adaption Goalsmentioning
confidence: 99%
See 3 more Smart Citations