Sciweavers

47 search results - page 4 / 10
» Summarizing software artifacts: a case study of bug reports
Sort
View
SE
2008
14 years 11 months ago
Static Bug Detection Through Analysis of Inconsistent Clones
Existing software systems contain a significant amount of duplicated code. Such redundancy can negatively impact program correctness, since inconsistent updates to duplicated code ...
Elmar Jürgens, Benjamin Hummel, Florian Deiss...
98
Voted
ERSHOV
2009
Springer
14 years 7 months ago
Applicability of the BLAST Model Checker: An Industrial Case Study
Model checking of software has been a very active research topic recently. As a result, a number of software model checkers have been developed for analysis of software written in ...
Emanuel Kolb, Ondrej Sery, Roland Weiss
MSR
2006
ACM
15 years 3 months ago
Tracking defect warnings across versions
Various static analysis tools will analyze a software artifact in order to identify potential defects, such as misused APIs, race conditions and deadlocks, and security vulnerabil...
Jaime Spacco, David Hovemeyer, William Pugh
99
Voted
EUROSYS
2011
ACM
14 years 1 months ago
Striking a new balance between program instrumentation and debugging time
Although they are helpful in many cases, state-of-the-art bug reporting systems may impose excessive overhead on users, leak private information, or provide little help to the dev...
Olivier Crameri, Ricardo Bianchini, Willy Zwaenepo...
SIGSOFT
2005
ACM
15 years 10 months ago
A case study on value-based requirements tracing
Project managers aim at keeping track of interdependencies between various artifacts of the software development lifecycle, to find out potential requirements conflicts, to better...
Matthias Heindl, Stefan Biffl