loading...
 This Article 
   
 Share 
   
 Bibliographic References 
   
 Add to: 
 
Digg
Furl
Spurl
Blink
Simpy
Google
Del.icio.us
Y!MyWeb
 
 Search 
   
10th IEEE High Assurance Systems Engineering Symposium (HASE'07)
One in a Baker?s Dozen: Debugging Debugging
Dallas, Texas, USA
November 14-November 16
ISBN: 0-7695-3043-5
ASCII Text
x 
 
Jeffrey Voas, Keith Miller, "One in a Baker?s Dozen: Debugging Debugging," High-Assurance Systems Engineering, IEEE International Symposium on, pp. 75-81, 10th IEEE High Assurance Systems Engineering Symposium (HASE'07), 2007.
 
 
BibTex
x
 
@article{ 10.1109/HASE.2007.80,
author = {Jeffrey Voas and Keith Miller},
title = {One in a Baker?s Dozen: Debugging Debugging},
journal ={High-Assurance Systems Engineering, IEEE International Symposium on},
volume = {0},
year = {2007},
issn = {1530-2059},
pages = {75-81},
doi = {http://doi.ieeecomputersociety.org/10.1109/HASE.2007.80},
publisher = {IEEE Computer Society},
address = {Los Alamitos, CA, USA},
}
 
 
RefWorks Procite/RefMan/Endnote
x 
 
TY - CONF
JO - High-Assurance Systems Engineering, IEEE International Symposium on
TI - One in a Baker?s Dozen: Debugging Debugging
SN - 1530-2059
SP75
EP81
A1 - Jeffrey Voas,
A1 - Keith Miller,
PY - 2007
KW - null
VL - 0
JA - High-Assurance Systems Engineering, IEEE International Symposium on
ER -
 

In [14], Voas outlined 13 major software engineering issues needing further research: (1) what is software quality? (2) what are the economic benefits behind existing software engineering techniques?, (3) does process improvement matter?, (4) can you trust software metrics and measurement?, (5) why are software engineering standards confusing and hard to comply with, (6) are standards interoperable, (7) how to decommission software?, (8) where are reasonable testing and debugging stoppage criteria?, (9) why are COTS components so difficult to compose?, (10) why are reliability measurement and operational profile elicitation viewed suspiciously, (11) can we design in the "ilities" both technically and economically, (12) how do we handle the liability issues surrounding certification, and (13) is intelligence and autonomic computing feasible?

This paper focuses on a simple and easy to understand metric that addresses the eighth issue, a testing and debugging testing stoppage criteria based on expected probability of failure graphs.

Citation:
Jeffrey Voas, Keith Miller, "One in a Baker?s Dozen: Debugging Debugging," hase, pp.75-81, 10th IEEE High Assurance Systems Engineering Symposium (HASE'07), 2007
Usage of this product signifies your acceptance of the Terms of Use.