DROPS

Document

Using Program Slicing to Identify Faults in Software

Authors: Sue Black, Steve Counsell, Tracy Hall, and Paul Wernick

Published in: Dagstuhl Seminar Proceedings, Volume 5451, Beyond Program Slicing (2006)

Abstract

This study explores the relationship between program slices and faults. The aim is to investigate whether the characteristics of program slices can be used to identify fault-prone software components. Slicing metrics and dependence clusters are used to characterise the slicing profile of a software component, then the relationship between the slicing profile of the component and the faults in that component are then analysed. Faults can increase the likelihood of a system becoming unstable causing problems for the development and evolution of the system. Identifying faultprone components is difficult and reliable predictors of faultproneness not easily identifiable. Program slicing is an established software engineering technique for the detection and correction of specific faults. An investigation is carried out into whether the use of program slicing can be extended as a reliable tool to predict fault-prone software components. Preliminary results are promising suggesting that slicing may offer valuable insights into fault-proneness.

Cite as

Sue Black, Steve Counsell, Tracy Hall, and Paul Wernick. Using Program Slicing to Identify Faults in Software. In Beyond Program Slicing. Dagstuhl Seminar Proceedings, Volume 5451, Schloss Dagstuhl – Leibniz-Zentrum für Informatik (2006)

Copy BibTex To Clipboard

@InProceedings{black_et_al:DagSemProc.05451.11,
  author =	{Black, Sue and Counsell, Steve and Hall, Tracy and Wernick, Paul},
  title =	{{Using Program Slicing to Identify Faults in Software}},
  booktitle =	{Beyond Program Slicing},
  series =	{Dagstuhl Seminar Proceedings (DagSemProc)},
  ISSN =	{1862-4405},
  year =	{2006},
  volume =	{5451},
  editor =	{David W. Binkley and Mark Harman and Jens Krinke},
  publisher =	{Schloss Dagstuhl -- Leibniz-Zentrum f{\"u}r Informatik},
  address =	{Dagstuhl, Germany},
  URL =		{https://drops.dagstuhl.de/entities/document/10.4230/DagSemProc.05451.11},
  URN =		{urn:nbn:de:0030-drops-5873},
  doi =		{10.4230/DagSemProc.05451.11},
  annote =	{Keywords: Program slicing, slicing metrics, fault proneness, software quality}
}

Document

DOI: 10.4230/DagSemProc.05451.4

And Now For Something Completely Different...

Authors: Sue Black and Philipp Bouillon

Published in: Dagstuhl Seminar Proceedings, Volume 5451, Beyond Program Slicing (2006)

Abstract

A pilot experiment was conducted at Dagstuhl using the 'Beyond program slicing' seminar attendees. Attendees were split into three groups: all were given the same program to understand and a list of program comprehension related questions to answer. Group one had only the source code, group two had the source code and the dynamic trace of the program, group three had the source and a control-flow graph of the program.

Cite as

Sue Black and Philipp Bouillon. And Now For Something Completely Different.... In Beyond Program Slicing. Dagstuhl Seminar Proceedings, Volume 5451, Schloss Dagstuhl – Leibniz-Zentrum für Informatik (2006)

Copy BibTex To Clipboard

@InProceedings{black_et_al:DagSemProc.05451.4,
  author =	{Black, Sue and Bouillon, Philipp},
  title =	{{And Now For Something Completely Different...}},
  booktitle =	{Beyond Program Slicing},
  series =	{Dagstuhl Seminar Proceedings (DagSemProc)},
  ISSN =	{1862-4405},
  year =	{2006},
  volume =	{5451},
  editor =	{David W. Binkley and Mark Harman and Jens Krinke},
  publisher =	{Schloss Dagstuhl -- Leibniz-Zentrum f{\"u}r Informatik},
  address =	{Dagstuhl, Germany},
  URL =		{https://drops.dagstuhl.de/entities/document/10.4230/DagSemProc.05451.4},
  URN =		{urn:nbn:de:0030-drops-5833},
  doi =		{10.4230/DagSemProc.05451.4},
  annote =	{Keywords: Group experiment, program comprehension, source code, dynamic trace, control flow graph}
}

Search Results

Documents authored by Black, Sue

Using Program Slicing to Identify Faults in Software

Abstract

Cite as

And Now For Something Completely Different...

Abstract

Cite as

Thanks for your feedback!

Could not send message