H. Gall, K. Hajek, and M. Jazayeri. Detection of logical coupling based on product release history. In Proceedings of the International Conference on Software Maintenance, pages 190--198, Nov. 1998. Home/Search Document Details and Download
Summary Related Articles Check |
This paper is cited in the following contexts:
How History Justifies System Architecture (or not) - Zimmermann, Diehl, Zeller (2003) (Correct)
....other. In the ideal case, every evolutionary coupling should also be a analytical coupling, thus justifying the system architecture. Mismatches indicate possible targets for restructuring. Earlier work has leveraged release or revision histories to detect coarse grained coupling between modules [2], files [5] or classes [1] The present work is the first, though, that relates changes to individual program entities like functions, methods, and attributes. It thus detects fine grained coupling between these entities, allowing for a much better understanding of commonalities and anomalies as ....
....detect coupling between changes. Nonetheless, NORA RECS relies uniquely on variants, while we use the much richer revision history to detect coupling. To our knowledge, the first work that leverages the product history to detect coupling within a system is the paper of Gall, Hajek, and Jazayeri [2]. They have used their CAESAR system to analyze the coupling within a large telecommunication switching system, and found that the history of 20 releases can indeed show up coupling within a system. A similar work was conducted by Bieman, Andrews and Yang on classes [1] using 39 releases of a ....
H. Gall, K. Hajek, and M. Jazayeri. Detection of logical coupling based on product release history. In Proc. International Conference on Software Maintenance (ICSM '98), Washington D.C., USA, Nov. 1998. IEEE.
Understanding Software Evolution using a Combination of.. - Lanza, Ducasse (2002) (4 citations) (Correct)
....conspicuous changes in the gathered size metrics and to identify candidate subsystems for restructuring and reengineering. A second effort on the same system focused on identifying logical coupling among subsystems in a way that potential structural shortcomings could be identified and examined [GAL 98] Sahraroui et al. SAH 00, LOU 98] present another aspect of the research on software evolution which is the prediction of the evolution. Our current focus is to understand the evolution even if our long term goal is to gain a better prediction on which parts of the system will cause problems. ....
GALL H., HAJEK K., JAZAYERI M., "Detection of Logical Coupling Based on Product Release History", Proceedings of the International Conference on Software Maintenance
Understanding Software Evolution Using a Combination of.. - Lanza, Ducasse (2002) (4 citations) (Correct)
....conspicuous changes in the gathered size metrics and to identify candidate subsystems for restructuring and reengineering. A second effort on the same system focused on identifying logical coupling among subsystems in a way that potential structural shortcomings could be identified and examined [GAL 98] Sahraroui et al. SAH 00, LOU 98] present another aspect of the research on software evolution which is the prediction of the evolution. Our current focus is to understand the evolution even if our long term goal is to gain a better prediction on which parts of the system will cause problems. ....
GALL H., HAJEK K., JAZAYERI M., "Detection of Logical Coupling Based on Product Release History", Proceedings of the International Conference on Software Maintenance
The Evolution Matrix: Recovering Software Evolution using Software .. - Lanza (2001) (5 citations) (Correct)
....conspicuous changes in the gathered size metrics and to identify candidate subsystems for restructuring and reengineering. A second effort on the same system focused on identifying logical coupling among subsystems in a way that potential structural shortcomings could be identified and examined [8]. Most publications and tools that tackle the problem of software evolution using software visualization work at higher abstraction levels, i.e. systems, subsystems, etc. We provide a visualization of classes as well as a categorization of classes based on that. 5.3 Future Work In the future we ....
K. H. H. Gall and M. Jazayeri. Detection of logical coupling based on product release history. In ICSM'98 Proceedings (International Conference on Software Maintenance), pages 190--198. IEEE Computer Society, 1998.
Deriving Fault Architectures from Defect History - von Mayrhauser, al. (2000) (2 citations) (Correct)
....software architecture that is fault prone. This is called the fault architecture. Section 2 reports on existing work related to identifying (repeatedly) fault prone components. It also summarises existing classes of reverse architecting approaches. Few researchers have tried to combine the two [17][18] We preferred two steps rather than a combination, because we wanted to use the reverse architecting approach both for building a fault architecture and a reverse architecture. Section 3 details our approach. Section 4 reports on its application to a sizable embedded system across 4 releases. ....
....would include their recognition. 11] describes an environment that uses recognisers that know about architectural cliches to produce different architectural views of the system. Other ways to look at reverse architecting a system include using state machine information [18] or release history [17]. CAESAR [17] uses the release history for a system. It tries to capture logical dependencies instead of syntactic dependencies by analysing common change patterns for components. This allows identication of dependencies that would not have been discovered through source code analysis. It ....
[Article contains additional citation context not shown here]
H. Gall, K. Hajek and M. Jazayeri, Detection of Logical Coupling Based on Product Release History, Proceedings of the International Conference on Software Maintenance, ICSM98, pp. 190-198, November 1998, Bethesda, Washington D.C.
Deriving a Fault Architecture from Defect History - von Mayrhauser, Wang.. (Correct)
....and highlight the worst architectural problems. It makes sense to solve those first. Section 2 reports on existing work related to identifying (repeatedly) fault prone components. It also summarizes existing classes of reverse architecting approaches. Few researchers have tried to combine the two [12][13] We preferred two steps rather than a combination, because we wanted to use the reverse architecting approach both for building a fault architecture and a reverse architecture. Section 3 details our approach. Section 4 reports on its application to a sizable embedded system across 4 releases. ....
....would include their recognition. 4] describes an environment that uses recognizers that know about architectural cliches to produce different architectural views of the system. Other ways to look at reverse architecting a system include using state machine information [13] or release history [12]. CAESAR [12] uses the release history for a system. It tries to capture logical dependencies instead of syntactic dependencies by analysing common change patterns for components. This allows identification of dependencies that would not have been discovered through source code analysis. It ....
[Article contains additional citation context not shown here]
H. Gall, K. Hajek and M. Jazayeri, "Detection of Logical Coupling Based on Product Release History", Proceedings of the International Conference on Software Maintenance, ICSM98, November 1998, Bethesda, Washington D.C.
Detection of Logical Coupling Based on Product Release History - Gall, Hajek, Jazayeri (1998) (33 citations) Self-citation (Hajek) (Correct)
....reports. If the change was a bug fix and several programs refer to a specific bug report number, this change verifies a real logical coupling. Other types of changes (e.g. further development etc. can be analyzed for commonalities accordingly. For more details about the specific examples see [10]. 5 Results In our case study, we examined different subsequences to identify change patterns in different programs and subsystems. The length of a subsequence is important when analyzing the coupling. As a consequence, our technique detects a stronger logical coupling of subsystems (or ....
Hajek K., "Detection of Logical Coupling Based on Product Release History," Master's Thesis, Technical University of Vienna, Austria, March 1998.
DynaMine: Finding Common Error Patterns by Mining Software .. - Livshits, Zimmermann (2005) (Correct)
No context found.
H. Gall, K. Hajek, and M. Jazayeri. Detection of logical coupling based on product release history. In Proceedings of the International Conference on Software Maintenance, pages 190--198, Nov. 1998.
Mining Co-Change Clusters from Version Repositories - Beyer, Noack (2005) (Correct)
No context found.
H. Gall, K. Hajek, and M. Jazayeri. Detection of logical coupling based on product release history. In Proceedings of the International Conference on Software Maintenance (ICSM 1998.
Effective Work Practices for Software Engineering.. - Crowston, Annabi, al. (Correct)
No context found.
Gall, H., Hajek, K. and Jazayeri, M. Detection of Logical Coupling Based on Product Release History. in Maintenance (ICSM '98), 1998.
DynaMine: Finding Common Error Patterns by Mining Software .. - Livshits, Zimmermann (2005) (Correct)
No context found.
H. Gall, K. Hajek, and M. Jazayeri. Detection of logical coupling based on product release history. In Proceedings of the International Conference on Software Maintenance, pages 190--198, Nov. 1998.
The Chaos of Software Development - Ahmed Hassan And (2003) (3 citations) (Correct)
No context found.
H. Gall, K. Hajek, and M. Jazayeri. Detection of Logical Coupling Based on Product Release History. In IEEE International Conference on Software Maintenance (ICSM98), Bethesda, Washington D.C., Nov. 1998.
Studying the Chaos of Code Development - Hassan, Holt (2003) (Correct)
No context found.
H. Gall, K. Hajek, and M. Jazayeri. Detection of logical coupling based on product release history. In IEEE International Conference on Software Maintenance (ICSM98), Bethesda, Washington D.C., Nov. 1998.
Mining Software Repositories to Guide Software Development - Hassan (2005) (1 citation) (Correct)
No context found.
H. Gall, K. Hajek, and M. Jazayeri. Detection of logical coupling based on product release history. In IEEE International Conference on Software Maintenance (ICSM98), Bethesda, Washington D.C., Nov. 1998.
C-REX: An Evolutionary Code Extractor for C - Ahmed Hassan And (Correct)
No context found.
H. Gall, K. Hajek, and M. Jazayeri. Detection of logical coupling based on product release history. In IEEE International Conference on Software Maintenance (ICSM98), Bethesda, Washington D.C., Nov. 1998.
Studying the Evolution of Software Systems Using Evolutionary.. - Hassan, Holt (2004) (Correct)
No context found.
H. Gall, K. Hajek, and M. Jazayeri. Detection of logical coupling based on product release history. In IEEE International Conference on Software Maintenance (ICSM98), Bethesda, Washington D.C., Nov. 1998.
Predicting Change Propagation in Software Systems - Ahmed Hassan And (2004) (1 citation) (Correct)
No context found.
H. Gall, K. Hajek, and M. Jazayeri. Detection of logical coupling based on product release history. In IEEE International Conference on Software Maintenance (ICSM98), Bethesda, Washington D.C., Nov. 1998.
Modeling Software Evolution by Treating History as a First .. - Ducasse, Girba, Favre (2004) (Correct)
No context found.
Harald Gall, Karin Hajek, and Mehdi Jazayeri. Detection of logical coupling based on product release history. In Proceedings of the International Conference on Software Maintenance 1998.
Mining Version Histories to Guide Software Changes - Thomas Zimmermann Tz (2004) (6 citations) (Correct)
No context found.
H. Gall, K. Hajek, and M. Jazayeri. Detection of logical coupling based on product release history. In Proc. International Conference on Software Maintenance (ICSM '98), pages 190--198, Washington D.C., USA, Nov. 1998. IEEE.
Evolution Metrics - Mens, Demeyer (2001) (5 citations) (Correct)
No context found.
H. Gall, K. Hajek, and M. Jazayeri. Detection of logical coupling based on product release history. In International Conference on Software Maintenance (ICSM '98). IEEE Computer Society Press, November 1998.
Yesterday's Weather: Guiding Early Reverse Engineering.. - Girba, Ducasse, Lanza (2004) (Correct)
No context found.
H. Gall, K. Hajek, and M. Jazayeri. Detection of logical coupling based on product release history. In Proceedings of the International Conference on Software Maintenance 1998.
C-REX: An Evolutionary Code Extractor for C - Hassan, Holt (Correct)
No context found.
H. Gall, K. Hajek, and M. Jazayeri. Detection of logical coupling based on product release history. In IEEE International Conference on Software Maintenance (ICSM98), Bethesda, Washington D.C., Nov. 1998.
C-REX: An Evolutionary Code Extractor for C - Ahmed Hassan And (2004) (Correct)
No context found.
H. Gall, K. Hajek, and M. Jazayeri. Detection of logical coupling based on product release history. In IEEE International Conference on Software Maintenance (ICSM98), Bethesda, Washington D.C., Nov. 1998.
Visualizing and Characterizing the Evolution of Class Hierarchies - Girba, Lanza (2004) (Correct)
No context found.
H. Gall, K. Hajek, and M. Jazayeri. Detection of logical coupling based on product release history. In Proceedings of the International Conference on Software Maintenance 1998.
Visualizing and Characterizing the Evolution of Class Hierarchies - Girba, Lanza (2004) (Correct)
No context found.
H. Gall, K. Hajek, and M. Jazayeri. Detection of logical coupling based on product release history. In Proceedings of the International Conference on Software Maintenance 1998.
Studying the Chaos of Code Development - Ahmed Hassan And (2003) (Correct)
No context found.
H. Gall, K. Hajek, and M. Jazayeri. Detection of logical coupling based on product release history. In IEEE International Conference on Software Maintenance (ICSM98), Bethesda, Washington D.C., Nov. 1998.
Mining Version Histories to Guide Software Changes - Zimmermann, Weißgerber.. (2004) (6 citations) (Correct)
No context found.
H. Gall, K. Hajek, and M. Jazayeri. Detection of logical coupling based on product release history. In Proc. International Conference on Software Maintenance (ICSM '98), pages 190--198, Washington D.C., USA, Nov. 1998. IEEE.
Identification of Software Instabilities - Bevan, Whitehead, Jr. (2003) (2 citations) (Correct)
No context found.
H. Gall, K. Hajek and M. Jazayeri, "Detection of Logical Coupling Based on Product Release History," Proc. International Conference on Software Maintenance, November 16-20, 1998, pp. 190-198.
Mining Software Repositories to Guide Software Development - Hassan (2005) (1 citation) (Correct)
No context found.
H. Gall, K. Hajek, and M. Jazayeri. Detection of logical coupling based on product release history. In IEEE International Conference on Software Maintenance (ICSM98), Bethesda, Washington D.C., Nov. 1998.
Using History Information to Improve Design Flaws Detection - Ratiu, Ducasse, Grba.. (2004) (Correct)
No context found.
H. Gall, K. Hajek, and M. Jazayeri. Detection of logical coupling based on product release history. In Proceedings of the International Conference on Software Maintenance 1998.
Studying the Evolution of Software Systems Using Evolutionary.. - Hassan, Holt (2004) (Correct)
No context found.
H. Gall, K. Hajek, and M. Jazayeri. Detection of logical coupling based on product release history. In IEEE International Conference on Software Maintenance (ICSM98), Bethesda, Washington D.C., Nov. 1998.
Yesterday's Weather: Guiding Early Reverse Engineering.. - Girba, Ducasse, Lanza (2004) (Correct)
No context found.
H. Gall, K. Hajek, and M. Jazayeri. Detection of logical coupling based on product release history. In Proceedings of the International Conference on Software Maintenance 1998.
Predicting Change Propagation in Software Systems - Ahmed Hassan And (2004) (1 citation) (Correct)
No context found.
H. Gall, K. Hajek, and M. Jazayeri. Detection of logical coupling based on product release history. In IEEE International Conference on Software Maintenance (ICSM98), Bethesda, Washington D.C., Nov. 1998.
The Chaos of Software Development - Ahmed Hassan And (2003) (3 citations) (Correct)
No context found.
H. Gall, K. Hajek, and M. Jazayeri. Detection of Logical Coupling Based on Product Release History. In IEEE International Conference on Software Maintenance (ICSM98), Bethesda, Washington D.C., Nov. 1998.
Online articles have much greater impact More about CiteSeer.IST Add search form to your site Submit documents Feedback
CiteSeer.IST - Copyright Penn State and NEC