Sciweavers

47 search results - page 8 / 10
» Summarizing software artifacts: a case study of bug reports
Sort
View
ICSM
2007
IEEE
15 years 3 months ago
Indexing Noncrashing Failures: A Dynamic Program Slicing-Based Approach
Recent software systems usually feature an automated failure reporting component, with which a huge number of failures are collected from software end-users. With a proper support...
Xiangyu Zhang Chao Liu, Yu Zhang, Jiawei Han, Bhar...
VSTTE
2010
Springer
14 years 7 months ago
Towards Scalable Modular Checking of User-Defined Properties
Abstract. Theorem-prover based modular checkers have the potential to perform scalable and precise checking of user-defined properties by combining pathsensitive intraprocedural re...
Thomas Ball, Brian Hackett, Shuvendu K. Lahiri, Sh...
ICSM
2009
IEEE
15 years 4 months ago
Measuring the progress of projects using the time dependence of code changes
Tracking the progress of a project is often done through imprecise manually gathered information, like progress reports, or through automatic metrics such as Lines Of Code (LOC). ...
Omar Alam, Bram Adams, Ahmed E. Hassan
KBSE
2005
IEEE
15 years 3 months ago
Determining the cost-quality trade-off for automated software traceability
Major software development standards mandate the establishment of trace links among software artifacts such as requirements, architectural elements, or source code without explici...
Alexander Egyed, Stefan Biffl, Matthias Heindl, Pa...
65
Voted
ICSM
2009
IEEE
15 years 4 months ago
On the use of relevance feedback in IR-based concept location
Concept location is a critical activity during software evolution as it produces the location where a change is to start in response to a modification request, such as, a bug repo...
Gregory Gay, Sonia Haiduc, Andrian Marcus, Tim Men...