Sciweavers

87 search results - page 3 / 18
» A Software Defect Report and Tracking System in an Intranet
Sort
View
RE
2008
Springer
13 years 5 months ago
Examining the Relationships between Performance Requirements and "Not a Problem" Defect Reports
Missing or imprecise requirements can lead stakeholders to make incorrect assumptions. A "Not a Problem" defect report (NaP) describes a software behavior that a stakeho...
Chih-Wei Ho, Laurie Williams, Brian Robinson
ICSE
2004
IEEE-ACM
14 years 6 months ago
An Empirical Study of Software Reuse vs. Defect-Density and Stability
The paper describes results of an empirical study, where some hypotheses about the impact of reuse on defect-density and stability, and about the impact of component size on defec...
Parastoo Mohagheghi, Reidar Conradi, Ole M. Killi,...
CSCW
2010
ACM
14 years 3 months ago
Communication, collaboration, and bugs: the social nature of issue tracking in small, collocated teams
Issue tracking systems help organizations manage issue reporting, assignment, tracking, resolution, and archiving. Traditionally, it is the Software Engineering community that res...
Dane Bertram, Amy Voida, Saul Greenberg, Robert Wa...
ICSE
2004
IEEE-ACM
14 years 6 months ago
MSR 2004: International Workshop on Mining Software Repositories
A one-day workshop was held on the topic of mining software repositories at ICSE 2004 in Edinburgh, Scotland. The workshop brought together researchers and practitioners in order ...
Ahmed E. Hassan, Richard C. Holt, Audris Mockus
MSR
2006
ACM
14 years 6 days 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