Sciweavers

47 search results - page 3 / 10
» Summarizing software artifacts: a case study of bug reports
Sort
View
CSCW
2004
ACM
15 years 2 months ago
Learning from project history: a case study for software development
The lack of lightweight communication channels and other technical and sociological difficulties make it hard for new members of a non-collocated software development team to lea...
Davor Cubranic, Gail C. Murphy, Janice Singer, Kel...
WCRE
2010
IEEE
14 years 7 months ago
Software Process Recovery: Recovering Process from Artifacts
—Often stakeholders, such as developers, managers, or buyers, want to find out what software development processes are being followed within a software project. Their reasons in...
Abram Hindle
66
Voted
COMPSAC
2009
IEEE
15 years 4 months ago
Integrating System Modeling with Project Management - A Case Study
In software engineering projects, there are two different types of modeling tools. On the one hand, there are tools to model the system under construction, i.e. tools for requirem...
Jonas Helming, Jörn David, Maximilian Koegel,...
81
Voted
ICSM
2007
IEEE
15 years 3 months ago
Release Pattern Discovery: A Case Study of Database Systems
Studying the release-time activities of a software project — that is, activities that occur around the time of a major or minor release — can provide insights into both the de...
Abram Hindle, Michael W. Godfrey, Richard C. Holt
CSMR
2007
IEEE
15 years 3 months ago
How Clones are Maintained: An Empirical Study
Despite the conventional wisdom concerning the risks related to the use of source code cloning as a software development strategy, several studies appeared in literature indicated...
Lerina Aversano, Luigi Cerulo, Massimiliano Di Pen...