Publication | Closed Access
What we have learned about fighting defects
243
Citations
5
References
2002
Year
Unknown Venue
Software MaintenanceSoftware Development PracticeEngineeringProject ManagementSoftware EngineeringDefectsSoftware AnalysisAutomated Software EngineeringEmpirical Software Engineering ResearchFailure AnalysisSystems EngineeringSoftware AspectSoftware PracticeReliabilityDesignComputer ScienceHuman ErrorAutomated RepairSoftware DesignSoftware DevelopmentExpert OpinionProgram AnalysisSoftware TestingBusinessMedicine
The Center for Empirically Based Software Engineering improves software development by providing guidelines for selecting techniques, recommending research areas, and supporting education. This paper discusses the results to date of a series of e‑Workshops on software defect reduction. The authors run e‑Workshops that capture expert knowledge with minimal overhead to formulate heuristics, presenting discussion items and an encapsulated summary of the expert discussion. The resulting heuristics summarize current expert knowledge and can guide researchers to identify gaps while helping practitioners benchmark or set expectations for development practices.
The Center for Empirically Based Software Engineering helps improve software development by providing guidelines for selecting development techniques, recommending areas for further research, and supporting software engineering education. A central activity toward achieving this goal has been the running of "e- Workshops" that capture expert knowledge with a minimum of overhead effort to formulate heuristics on a particular topic. The resulting heuristics are a useful summary of the current state of knowledge in an area based on expert opinion. This paper discusses the results to date of a series of e-Workshops on software defect reduction. The original discussion items are presented along with an encapsulated summary of the expert discussion. The reformulated heuristics can be useful both to researchers (for pointing out gaps in the current state of the knowledge requiring further investigation) and to practitioners (for benchmarking or setting expectations about development practices).
| Year | Citations | |
|---|---|---|
Page 1
Page 1