Abstract
Many technical products and systems nowadays have functionality that is largely determined by software, so called software-intensive systems. The requirements for software-intensive systems change over time, causing the system to evolve. We define evolvability as the ability of the system to respond to such changes. Improving evolvability of software-intensive systems was the goal of the Darwin project. The vision of this project consisted of four cornerstones. In this paper we share the obtained experiences, insights, and results. We have collected some evidence that three of the vision’s cornerstones, which are about knowledge, i.e., extracting knowledge, representing knowledge, and economic decision making, improve evolvability. The representation of knowledge in A3 architecture overviews is the result with the most evidence that it is useful in practice.
Sign-in/Register to access full text options 
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Schedule a callDisclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.
