Proceedings of the 5th International Workshop on Software Clones, May 23, 2011
Existing algorithms for model clone detection operate in batch mode. Consequently, if a small par... more Existing algorithms for model clone detection operate in batch mode. Consequently, if a small part of a large model changes during maintenance, the entire detection needs to be recomputed to produce updated cloning information. Since this can take several hours, the lack of incremental detection algorithms hinders clone management, which requires up-to-date cloning information. In this paper we present an
Proceedings of the 32nd Acm Ieee International Conference on Software Engineering Volume 2, May 1, 2010
Cloned code is considered harmful for two reasons: (1) multiple, possibly unnecessary, duplicates... more Cloned code is considered harmful for two reasons: (1) multiple, possibly unnecessary, duplicates of code increase maintenance costs and, (2) inconsistent changes to cloned code can create faults and, hence, lead to incorrect program behavior. Likewise, duplicated parts of models are problematic in model-based development. Recently, we and other authors proposed multiple approaches to automatically identify duplicates in graphical models. While it has been demonstrated that these approaches work in principal, a number of challenges remain for application in industrial practice. Based on an industrial case study undertaken with the BMW Group, this paper details on these challenges and presents solutions to the most pressing ones, namely scalability and relevance of the results. Moreover, we present tool support that eases the evaluation of detection results and thereby helps to make clone detection a standard technique in modelbased quality assurance.
We argument three positions: 1) independently devel- oped semantically similar code is unlikely t... more We argument three positions: 1) independently devel- oped semantically similar code is unlikely to be represen- tationally similar, 2) existing clone detection approaches are ill-suited for detecting such similarities and 3) dynamic clone detection is a promising approach to detect semanti- cally similar yet representationally different code. Numerous clone detection approaches have been pro- posed (4). They differ in many
Proceedings of the 11th Working Conference on Mining Software Repositories - MSR 2014, 2014
Code review is the manual assessment of source code by humans, mainly intended to identify defect... more Code review is the manual assessment of source code by humans, mainly intended to identify defects and quality problems. Modern Code Review (MCR), a lightweight variant of the code inspections investigated since the 1970s, prevails today both in industry and open-source software (OSS) systems. The objective of this paper is to increase our understanding of the practical benefits that the MCR process produces on reviewed source code. To that end, we empirically explore the problems fixed through MCR in OSS systems. We manually classified over 1,400 changes taking place in reviewed code from two OSS projects into a validated categorization scheme. Surprisingly, results show that the types of changes due to the MCR process in OSS are strikingly similar to those in the industry and academic systems from literature, featuring the similar 75:25 ratio of maintainability-related to functional problems. We also reveal that 7-35% of review comments are discarded and that 10-22% of the changes are not triggered by an explicit review comment. Patterns emerged in the review data; we investigated them revealing the technical factors that influence the number of changes due to the MCR process. We found that bug-fixing tasks lead to fewer changes and tasks with more altered files and a higher code churn have more changes. Contrary to intuition, the person of the reviewer had no impact on the number of changes.
2011 15th European Conference on Software Maintenance and Reengineering, 2011
Regression testing analyzes whether software maintenance has inadvertently broken existing functi... more Regression testing analyzes whether software maintenance has inadvertently broken existing functionality. Since it is costly-especially for manual testing-it is typically limited to a subset of test cases. Since impact analysis of code modifications on test cases is far from trivial for real world software, regression test selection is hard. However, if it misses affected test cases, bugs may remain unnoticed. In response, the research community has proposed numerous test selection approaches. Regression test selection is especially relevant for manual tests, since their execution costs limit the number of tests that can be executed in practice. However, evaluations of existing work focus on automated tests. Its applicability to manual tests is thus unclear. We present an industrial case study that demonstrates the challenges that regression test selection techniques face when applied to manual system tests. Furthermore, we sketch how, given these challenges, manual regression test selection can be improved.
2009 IEEE 31st International Conference on Software Engineering, 2009
The area of clone detection has considerably evolved over the last decade, leading to approaches ... more The area of clone detection has considerably evolved over the last decade, leading to approaches with better results, but at the same time using more elaborate algorithms and tool chains. In our opinion a level has been reached, where the initial investment required to setup a clone detection tool chain and the code infrastructure required for experimenting with new heuristics and algorithms seriously hampers the exploration of novel solutions or specific case studies. As a solution, this paper presents CloneDetective, an open source framework and tool chain for clone detection, which is especially geared towards configurability and extendability and thus supports the preparation and conduction of clone detection research.
Proceedings of the 4th International Workshop on Software Clones - IWSC '10, 2010
Cloned code is considered harmful for two reasons: (1) multiple, possibly unnecessary, duplicates... more Cloned code is considered harmful for two reasons: (1) multiple, possibly unnecessary, duplicates of code increase maintenance costs and, (2) inconsistent changes to cloned code can create faults and, hence, lead to incorrect program behavior. Likewise, duplicated parts of models are problematic in model-based development. Recently, we and other authors proposed multiple approaches to automatically identify duplicates in graphical models. While it has been demonstrated that these approaches work in principal, a number of challenges remain for application in industrial practice. Based on an industrial case study undertaken with the BMW Group, this paper details on these challenges and presents solutions to the most pressing ones, namely scalability and relevance of the results. Moreover, we present tool support that eases the evaluation of detection results and thereby helps to make clone detection a standard technique in modelbased quality assurance.
Proceedings of the 32nd ACM/IEEE International Conference on Software Engineering - ICSE '10, 2010
Cloned code is considered harmful for two reasons: (1) multiple, possibly unnecessary, duplicates... more Cloned code is considered harmful for two reasons: (1) multiple, possibly unnecessary, duplicates of code increase maintenance costs and, (2) inconsistent changes to cloned code can create faults and, hence, lead to incorrect program behavior. Likewise, duplicated parts of models are problematic in model-based development. Recently, we and other authors proposed multiple approaches to automatically identify duplicates in graphical models. While it has been demonstrated that these approaches work in principal, a number of challenges remain for application in industrial practice. Based on an industrial case study undertaken with the BMW Group, this paper details on these challenges and presents solutions to the most pressing ones, namely scalability and relevance of the results. Moreover, we present tool support that eases the evaluation of detection results and thereby helps to make clone detection a standard technique in modelbased quality assurance.
Proceedings of the 32nd ACM/IEEE International Conference on Software Engineering - ICSE '10, 2010
The architecture of software systems is known to decay if no counter-measures are taken. In order... more The architecture of software systems is known to decay if no counter-measures are taken. In order to prevent this architectural erosion, the conformance of the actual system architecture to its intended architecture needs to be assessed and controlled; ideally in a continuous manner. To support this, we present the architecture conformance assessment capabilities of our quality analysis framework ConQAT. In contrast to other tools, ConQAT is not limited to the assessment of use-dependencies between software components. Its generic architectural model allows the assessment of various types of dependencies found between different kinds of artifacts. It thereby provides the necessary tool-support for flexible architecture conformance assessment in diverse contexts.
Proceedings of the 1st International Workshop on Rapid Continuous Software Engineering - RCoSE 2014, 2014
Bad requirements quality can have expensive consequences during the software development lifecycl... more Bad requirements quality can have expensive consequences during the software development lifecycle. Especially, if iterations are long and feedback comes late -the faster a problem is found, the cheaper it is to fix.
Proceedings of the 5th International Workshop on Software Clones, May 23, 2011
Existing algorithms for model clone detection operate in batch mode. Consequently, if a small par... more Existing algorithms for model clone detection operate in batch mode. Consequently, if a small part of a large model changes during maintenance, the entire detection needs to be recomputed to produce updated cloning information. Since this can take several hours, the lack of incremental detection algorithms hinders clone management, which requires up-to-date cloning information. In this paper we present an
Proceedings of the 32nd Acm Ieee International Conference on Software Engineering Volume 2, May 1, 2010
Cloned code is considered harmful for two reasons: (1) multiple, possibly unnecessary, duplicates... more Cloned code is considered harmful for two reasons: (1) multiple, possibly unnecessary, duplicates of code increase maintenance costs and, (2) inconsistent changes to cloned code can create faults and, hence, lead to incorrect program behavior. Likewise, duplicated parts of models are problematic in model-based development. Recently, we and other authors proposed multiple approaches to automatically identify duplicates in graphical models. While it has been demonstrated that these approaches work in principal, a number of challenges remain for application in industrial practice. Based on an industrial case study undertaken with the BMW Group, this paper details on these challenges and presents solutions to the most pressing ones, namely scalability and relevance of the results. Moreover, we present tool support that eases the evaluation of detection results and thereby helps to make clone detection a standard technique in modelbased quality assurance.
We argument three positions: 1) independently devel- oped semantically similar code is unlikely t... more We argument three positions: 1) independently devel- oped semantically similar code is unlikely to be represen- tationally similar, 2) existing clone detection approaches are ill-suited for detecting such similarities and 3) dynamic clone detection is a promising approach to detect semanti- cally similar yet representationally different code. Numerous clone detection approaches have been pro- posed (4). They differ in many
Proceedings of the 11th Working Conference on Mining Software Repositories - MSR 2014, 2014
Code review is the manual assessment of source code by humans, mainly intended to identify defect... more Code review is the manual assessment of source code by humans, mainly intended to identify defects and quality problems. Modern Code Review (MCR), a lightweight variant of the code inspections investigated since the 1970s, prevails today both in industry and open-source software (OSS) systems. The objective of this paper is to increase our understanding of the practical benefits that the MCR process produces on reviewed source code. To that end, we empirically explore the problems fixed through MCR in OSS systems. We manually classified over 1,400 changes taking place in reviewed code from two OSS projects into a validated categorization scheme. Surprisingly, results show that the types of changes due to the MCR process in OSS are strikingly similar to those in the industry and academic systems from literature, featuring the similar 75:25 ratio of maintainability-related to functional problems. We also reveal that 7-35% of review comments are discarded and that 10-22% of the changes are not triggered by an explicit review comment. Patterns emerged in the review data; we investigated them revealing the technical factors that influence the number of changes due to the MCR process. We found that bug-fixing tasks lead to fewer changes and tasks with more altered files and a higher code churn have more changes. Contrary to intuition, the person of the reviewer had no impact on the number of changes.
2011 15th European Conference on Software Maintenance and Reengineering, 2011
Regression testing analyzes whether software maintenance has inadvertently broken existing functi... more Regression testing analyzes whether software maintenance has inadvertently broken existing functionality. Since it is costly-especially for manual testing-it is typically limited to a subset of test cases. Since impact analysis of code modifications on test cases is far from trivial for real world software, regression test selection is hard. However, if it misses affected test cases, bugs may remain unnoticed. In response, the research community has proposed numerous test selection approaches. Regression test selection is especially relevant for manual tests, since their execution costs limit the number of tests that can be executed in practice. However, evaluations of existing work focus on automated tests. Its applicability to manual tests is thus unclear. We present an industrial case study that demonstrates the challenges that regression test selection techniques face when applied to manual system tests. Furthermore, we sketch how, given these challenges, manual regression test selection can be improved.
2009 IEEE 31st International Conference on Software Engineering, 2009
The area of clone detection has considerably evolved over the last decade, leading to approaches ... more The area of clone detection has considerably evolved over the last decade, leading to approaches with better results, but at the same time using more elaborate algorithms and tool chains. In our opinion a level has been reached, where the initial investment required to setup a clone detection tool chain and the code infrastructure required for experimenting with new heuristics and algorithms seriously hampers the exploration of novel solutions or specific case studies. As a solution, this paper presents CloneDetective, an open source framework and tool chain for clone detection, which is especially geared towards configurability and extendability and thus supports the preparation and conduction of clone detection research.
Proceedings of the 4th International Workshop on Software Clones - IWSC '10, 2010
Cloned code is considered harmful for two reasons: (1) multiple, possibly unnecessary, duplicates... more Cloned code is considered harmful for two reasons: (1) multiple, possibly unnecessary, duplicates of code increase maintenance costs and, (2) inconsistent changes to cloned code can create faults and, hence, lead to incorrect program behavior. Likewise, duplicated parts of models are problematic in model-based development. Recently, we and other authors proposed multiple approaches to automatically identify duplicates in graphical models. While it has been demonstrated that these approaches work in principal, a number of challenges remain for application in industrial practice. Based on an industrial case study undertaken with the BMW Group, this paper details on these challenges and presents solutions to the most pressing ones, namely scalability and relevance of the results. Moreover, we present tool support that eases the evaluation of detection results and thereby helps to make clone detection a standard technique in modelbased quality assurance.
Proceedings of the 32nd ACM/IEEE International Conference on Software Engineering - ICSE '10, 2010
Cloned code is considered harmful for two reasons: (1) multiple, possibly unnecessary, duplicates... more Cloned code is considered harmful for two reasons: (1) multiple, possibly unnecessary, duplicates of code increase maintenance costs and, (2) inconsistent changes to cloned code can create faults and, hence, lead to incorrect program behavior. Likewise, duplicated parts of models are problematic in model-based development. Recently, we and other authors proposed multiple approaches to automatically identify duplicates in graphical models. While it has been demonstrated that these approaches work in principal, a number of challenges remain for application in industrial practice. Based on an industrial case study undertaken with the BMW Group, this paper details on these challenges and presents solutions to the most pressing ones, namely scalability and relevance of the results. Moreover, we present tool support that eases the evaluation of detection results and thereby helps to make clone detection a standard technique in modelbased quality assurance.
Proceedings of the 32nd ACM/IEEE International Conference on Software Engineering - ICSE '10, 2010
The architecture of software systems is known to decay if no counter-measures are taken. In order... more The architecture of software systems is known to decay if no counter-measures are taken. In order to prevent this architectural erosion, the conformance of the actual system architecture to its intended architecture needs to be assessed and controlled; ideally in a continuous manner. To support this, we present the architecture conformance assessment capabilities of our quality analysis framework ConQAT. In contrast to other tools, ConQAT is not limited to the assessment of use-dependencies between software components. Its generic architectural model allows the assessment of various types of dependencies found between different kinds of artifacts. It thereby provides the necessary tool-support for flexible architecture conformance assessment in diverse contexts.
Proceedings of the 1st International Workshop on Rapid Continuous Software Engineering - RCoSE 2014, 2014
Bad requirements quality can have expensive consequences during the software development lifecycl... more Bad requirements quality can have expensive consequences during the software development lifecycle. Especially, if iterations are long and feedback comes late -the faster a problem is found, the cheaper it is to fix.
Uploads
Papers by Elmar Juergens