The DOI matches its Crossref record.
DIVERSIFY: Ecology-inspired software evolution for diversity emergence
Open accessAbstract
DIVERSIFY is an EU funded project, which aims at favoring spontaneous diversification in software systems in order to increase their adaptive capacities. This objective is founded on three observations: software has to constantly evolve to face unpredictable changes in its requirements, execution environment or to respond to failure (bugs, attacks, etc.): the emergence and maintenance of high levels of diversity are essential to provide adaptive capacities to many forms of complex systems, ranging from ecological and biological systems to social and economical systems; diversity levels tend to be very low in software systems. DIVERSIFY explores how the biological evolutionary mechanisms, which sustain high levels of biodiversity in ecosystems (speciation, phenotypic plasticity and natural selection) can be translated in software evolution principles. In this work, we consider evolution as a driver for diversity as a means to increase resilience in software systems. In particular, we are inspired by bipartite ecological relationships to investigate the automatic diversification of the server side of a client-server architecture. This type of software diversity aims at mitigating the risks of software monoculture. The consortium gathers researchers from the software-intensive, distributed systems and the ecology areas in order to transfer ecological concepts and processes as software design principles.
Overview
Integrity signals
Registry
Cites
Statistics
Verification
Claims the paper makes
Claims other papers make about this one
Each is checked against this paper’s own text: does it say what the citing paper says it does?
Unpredictable evolution and changes of software requirements complicate architecture design.
“Unpredictable evolution and changes of software requirements complicate architecture design ( group , calendar ).”
From Software Architecture in Practice: Challenges and Opportunities (2023) · cites this paper as [8]
Citations
Cites
No references could be resolved yet.
Research works printed but not linked: 31
- 10.1109/32.825767 · DOI · Paper page
- 10.2307/1930126 · DOI · Paper page
- 10.1038/35012234 · DOI
- 10.1109/TSE.2011.104 · DOI
- lin, 2009, Polymorphing software by randomizing data structure layout, Detection of Intrusions and Malware and Vulnerability Assessment, 107, 10.1007/978-3-642-02918-9_7 · DOI
- 10.1145/948109.948146 · DOI
- 10.1109/TSE.1986.6312924 · DOI
- 10.1126/science.1157966 · DOI · Paper page
- 10.1109/ICSE.2013.6606607 · DOI
- 10.1109/SCAM.2013.6648183 · DOI
- 10.1371/journal.pcbi.1000892 · DOI
- 10.1109/ICSE.2009.5070514 · DOI
- 10.1145/1370175.1370181 · DOI
- 10.1145/1278201.1278232 · DOI
- 10.1109/TSE.1975.6312842 · DOI
- 10.1145/2228360.2228526 · DOI
- 10.1007/s10710-013-9195-8 · DOI
- sidiroglou-douskos, 2011, Managing performance vs, Accuracy Trade-offs with Loop Perforation in Proc of the Symp on Foundations of Software Engineering (FSE'11) ESEC/FSE '11, 124
- 10.1145/971617.971650 · DOI
- 10.1145/1053283.1053286 · DOI
- 10.1145/1592681.1592686 · DOI
- 10.1109/HOTOS.1997.595185 · DOI
- 10.1109/TSE.1985.231893 · DOI
- 10.1109/2.825699 · DOI
- 10.2174/1874213000902010007 · DOI
- 10.2307/2261158 · DOI
- chen, 1978, N-version programming a fault-tolerance approach to reliability of software operation, Proc of the Int Symp on Fault-Tolerant Computing (FTCS'78), 3
- 10.1073/pnas.96.4.1463 · DOI · Paper page
- baudry, 2012, Towards ecology-inspired software engineering, CoRR
- feldt, 1998, generating diverse software versions with genetic programming: an experimental study, Software IEE Proceedings-, 145, 228, 10.1049/ip-sen:19982444 · DOI
- 10.1046/j.1461-0248.2002.00354.x · DOI
Cited by
Sorted by citations
Software Architecture in Practice: Challenges and Opportunities
Wan, Z., Zhang, Y., Xia, X., Jiang, Y., & Lo, D. (2023) · Proceedings of the 31st ACM Joint European Software Engineering Conference and Symposium on the Foundations of Software Engineering · doi:10.1145/3611643.3616367 · Cited by 30
“The unpredictable evolution and changes of requirements sometimes make it infeasible to deliver new features or meet the quality requirements with current architectures, as frequently mentioned in the literature [3, 8, 22, 24, 60, 90, 92].”
Background
Metadata
- Authors
- Baudry, B., Monperrus, M., Mony, C., Chauvel, F., Fleurey, F., & Clarke, S.
- Affiliations
- Institut national de recherche en sciences et technologies du numérique (FR)
- Université Rennes 1 (FR)
- SINTEF (NO)
- Venue
- 2014 Software Evolution Week - IEEE Conference on Software Maintenance, Reengineering, and Reverse Engineering (CSMR-WCRE)
- Publisher
- IEEE
- Published
- 2014-02
- Pages
- 395-398
- OpenAlex
- W2055233297
- Cited by
- 14
- References
- 0
- Citations by year
- 2026: 1 · 2023: 1 · 2022: 1 · 2019: 3 · 2018: 2 · 2017: 2 · 2016: 1 · 2015: 2 · 2014: 1
- FWCI
- 1.18
- Type
- conference paper
- Language
- en
- Open access
- green
- inria.hal.science
- Licence
- other-oa
- Locations
- IEEE International Conference on Software Analysis, Evolution and Reengineering (SANER) (publishedVersion)
- HAL (submittedVersion, other-oa)
- LillOA (Université de Lille (University Of Lille)) (submittedVersion, other-oa)
- Topics
- Physical Sciences › Computer Science › Software › Advanced Software Engineering Methodologies
- Physical Sciences › Computer Science › Information Systems › Software Engineering Research
- Physical Sciences › Computer Science › Artificial Intelligence › Evolutionary Algorithms and Applications
- Keywords
- software diversity, software evolution, software resilience, client-server architecture, speciation, phenotypic plasticity, natural selection, adaptive software, distributed systems
About these checks
Registry, retraction, Cites and statistics results are computed, not judged, with one exception: a printed reference that no index lists is read once by a model before it counts as a citation error. Claims are extracted by a model and kept only when their quote appears verbatim in the text; each cited source is then checked, with a model’s help, for whether it says what the claim relies on. Those verdicts can be wrong — read the claim’s quote and the cited source before relying on one.
Statistics and arithmetic are recomputed, not judged.
Confidence bands are shown only for fields calibrated on our annotated test set. None is calibrated yet, so no band is shown.
What counts as a claim ›How we measure confidence ›How we check this ›
Are you an author, or do you see a problem with this page? Request a review