2026-07-20T05:03:37Z https://drops.dagstuhl.de/oai

oai:drops-oai.dagstuhl.de:559 2024-03-06T11:06:24Z ddc:004 open_access

05261 Summary – Multi-Version Program Analysis Ball, Thomas Diehl, Stephan Notkin, David Zeller, Andreas Software engineering data minig software processes software archives version control bug database experimantation measurement verification Change is an inevitable part of successful software systems. Software changes induce costs, as they force people to repeat earlier assessments. On the other hand, knowing about software changes can also bring benefits, as changes are artifacts that can be analyzed. In the last years, researchers have begun to analyze software together with its change history. There is a huge amount of historical information that can be extracted, abstracted, and leveraged: - Knowing about earlier versions and their properties can lead to incremental assessments. - Analyzing the history of a product can tell how changes in software are related to other changes and features. - Relating properties to changes can help focusing on changes that cause specific properties. In this Dagstuhl seminar, researchers that analyze software and its history have met and discussed for a full week, exchanging their ideas, and combining and integrating the techniques to build a greater whole. Clearly, understanding history can play a major role when it comes to understand software systems. Schloss Dagstuhl – Leibniz-Zentrum für Informatik Thomas Ball and Stephan Diehl and David Notkin and Andreas Zeller 2006 Is Part Of Dagstuhl Seminar Proceedings, Volume 5261, Multi-Version Program Analysis (2006) InProceedings Text doc-type:ResearchArticle publishedVersion application/pdf doi:10.4230/DagSemProc.05261.2 urn:nbn:de:0030-drops-5591 https://drops.dagstuhl.de/entities/document/10.4230/DagSemProc.05261.2 eng https://creativecommons.org/licenses/by/4.0/legalcode