Program evolution: processes of software change
Program evolution: processes of software change
Analyzing Regression Test Selection Techniques
IEEE Transactions on Software Engineering
An empirical study of regression test selection techniques
ACM Transactions on Software Engineering and Methodology (TOSEM)
Bridging the requirements/design gap in dynamic systems with use case maps (UCMs)
ICSE '01 Proceedings of the 23rd International Conference on Software Engineering
Formal Concept Analysis: Mathematical Foundations
Formal Concept Analysis: Mathematical Foundations
Whole program Path-Based dynamic impact analysis
Proceedings of the 25th International Conference on Software Engineering
Scenario Evolution: A Closer View on Relationships
ICRE '00 Proceedings of the 4th International Conference on Requirements Engineering (ICRE'00)
Automating Impact Analysis and Regression Test Selection Based on UML Designs
ICSM '02 Proceedings of the International Conference on Software Maintenance (ICSM'02)
An ASM Operational Semantics for Use Case Maps
RE '05 Proceedings of the 13th IEEE International Conference on Requirements Engineering
Change Impact Analysis for Requirement Evolution using Use Case Maps
IWPSE '05 Proceedings of the Eighth International Workshop on Principles of Software Evolution
A concept analysis inspired greedy algorithm for test suite minimization
PASTE '05 Proceedings of the 6th ACM SIGPLAN-SIGSOFT workshop on Program analysis for software tools and engineering
Regression Testing UML Designs
ICSM '06 Proceedings of the 22nd IEEE International Conference on Software Maintenance
| Hi-index | 0.00 |
Modification analysis is part of most maintenance processes and includes among other activities, early prediction of potential change impacts, feasibility studies, cost estimation, etc. Existing impact analysis and regression testing techniques being source code based require at least some understanding of the system implementation. In this research we present a novel approach that combines UCM with FCA to assist decision makers in supporting modification analysis at the requirements level. Our approach provides support for determining the potential modification and re-testing effort associated with a change without the need to analyze or comprehend source code. We demonstrate the applicability of our approach on a telephony system case study.