Skip to main content

Timeline for Predicting software errors

Current License: CC BY-SA 3.0

12 events
when toggle format what by license comment
Mar 1, 2016 at 13:21 answer added Danny Schoemann timeline score: 2
Sep 29, 2014 at 22:47 comment added yegor256 This article may help you: technoparkcorp.com/innovations/test-planning
Sep 26, 2014 at 13:33 comment added Thomas Owens You may be interested in reading Stephen Kan's Metrics and Models in Software Quality Engineering. There are various models for software quality and reliability, along with techniques to manage and improve them that are discussed in several chapters of the book. However, I'm not sure that your ideas relating people leaving to quality is appropriate. Also, 2 projects is not likely to yield sufficient data points for any kind of meaningful analysis.
Sep 26, 2014 at 9:46 comment added user5529 Are there rules that define when the developers should leave or not? Can they leave the file when there are open bugs?or, when they are leaving file, are they removing the bygs? This can help to investigate further the reasons
Sep 24, 2014 at 19:46 comment added David Espina You cannot conclude anything from this. Results are random and a range. You cannot uncover the natural range of bugs from studying only two projects. This is like trying to understand car accidents in your country using two trips with two drivers along a ten mile strip on route 27.
Sep 24, 2014 at 18:13 answer added Philip Kolocotronis timeline score: 2
Sep 24, 2014 at 15:37 answer added Todd A. Jacobs timeline score: 4
Sep 24, 2014 at 15:27 comment added Dora Maris @MarkC.Wallace Thanks for your comment. Actually, we counted the number of leavers developers who worked in a particular file. This implies that the leaver person had knowledge about that file and know-how is lost. We are not worried about the reason a developer left the project.
Sep 24, 2014 at 14:49 comment added MCW Perhaps you don't have the right indicators? Developers leave for many reasons, and many of those reasons are not related to code quality.
Sep 24, 2014 at 14:48 history edited MCW CC BY-SA 3.0
spelling, minor formatting issues.
Sep 24, 2014 at 13:54 review First posts
Sep 24, 2014 at 14:49
Sep 24, 2014 at 13:50 history asked Dora Maris CC BY-SA 3.0