Sciweavers

712 search results - page 44 / 143
» Software debugging, testing, and verification
Sort
View
SIGSOFT
2002
ACM
14 years 9 months ago
Isolating cause-effect chains from computer programs
Consider the execution of a failing program as a sequence of program states. Each state induces the following state, up to the failure. Which variables and values of a program sta...
Andreas Zeller
SIGSOFT
2006
ACM
14 years 9 months ago
Finding failure-inducing changes in java programs using change classification
Testing and code editing are interleaved activities during program development. When tests fail unexpectedly, the changes that caused the failure(s) are not always easy to find. W...
Barbara G. Ryder, Frank Tip, Maximilian Störz...
REFSQ
2010
Springer
13 years 7 months ago
Challenges in Aligning Requirements Engineering and Verification in a Large-Scale Industrial Context
[Context and motivation] When developing software, coordination between different organizational units is essential in order to develop a good quality product, on time and within b...
Giedre Sabaliauskaite, Annabella Loconsole, Emelie...
ICRA
2007
IEEE
157views Robotics» more  ICRA 2007»
14 years 3 months ago
Distributed Watchpoints: Debugging Large Multi-Robot Systems
Abstract— Tightly-coupled multi-agent systems such as modular robots frequently exhibit properties of interest that span multiple modules. These properties cannot easily be detec...
Michael DeRosa, Jason Campbell, Padmanabhan Pillai...
KBSE
2007
IEEE
14 years 3 months ago
Testing concurrent programs using value schedules
Concurrent programs are difficult to debug and verify because of the nondeterministic nature of concurrent executions. A particular concurrency-related bug may only show up under ...
Jun Chen, Steve MacDonald