|
| This Article | ||
| ||
| Share | ||
| Bibliographic References | ||
| Add to: | ||
 Digg  Furl  Spurl  Blink  Simpy  Google  Del.icio.us  Y!MyWeb | ||
| Search | ||
| ||
Signpost: Matching Program Behavior against Known Faults
November/December 2003 (vol. 20 no. 6)
pp. 84-89
| ASCII Text | x | ||
| Mike Andrews, "Signpost: Matching Program Behavior against Known Faults," IEEE Software, vol. 20, no. 6, pp. 84-89, November/December, 2003. | |||
| BibTex | x | ||
| @article{ 10.1109/MS.2003.1241371, author = {Mike Andrews}, title = {Signpost: Matching Program Behavior against Known Faults}, journal ={IEEE Software}, volume = {20}, number = {6}, issn = {0740-7459}, year = {2003}, pages = {84-89}, doi = {http://doi.ieeecomputersociety.org/10.1109/MS.2003.1241371}, publisher = {IEEE Computer Society}, address = {Los Alamitos, CA, USA}, } | |||
| RefWorks Procite/RefMan/Endnote | x | ||
| TY - MGZN JO - IEEE Software TI - Signpost: Matching Program Behavior against Known Faults IS - 6 SN - 0740-7459 SP84 EP89 EPD - 84-89 A1 - Mike Andrews, PY - 2003 VL - 20 JA - IEEE Software ER - | |||
Modern computer programs are often composite systems, relying on numerous commercial component libraries. When a program fails, the causes of that failure will often be a complex mix of interactions between developer-written code and library code. Debugging programs of this type can be difficult as the programmer is forced to try and isolate the source of faulty behavior in multiple components from multiple sources?some of which they know well and others in which they may have no experience. Often there are large areas of code to examine and it is not always clear if the problem is due to a bug in the programmer?s code or in a dependant library.
Citation:
Mike Andrews, "Signpost: Matching Program Behavior against Known Faults," IEEE Software, vol. 20, no. 6, pp. 84-89, Nov.-Dec. 2003, doi:10.1109/MS.2003.1241371
Usage of this product signifies your acceptance of the Terms of Use.