@conference {12151,
	title = {Obtaining valid safety data for software safety measurement and process improvement},
	booktitle = {Proceedings of the 2010 ACM-IEEE International Symposium on Empirical Software Engineering and Measurement},
	series = {ESEM {\textquoteright}10},
	year = {2010},
	month = {2010///},
	pages = {46:1{\textendash}46:4 - 46:1{\textendash}46:4},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {We report on a preliminary case study to examine software safety risk in the early design phase of the NASA Constellation spaceflight program. Our goal is to provide NASA quality assurance managers with information regarding the ongoing state of software safety across the program. We examined 154 hazard reports created during the preliminary design phase of three major flight hardware systems within the Constellation program. Our purpose was two-fold: 1) to quantify the relative importance of software with respect to system safety; and 2) to identify potential risks due to incorrect application of the safety process, deficiencies in the safety process, or the lack of a defined process. One early outcome of this work was to show that there are structural deficiencies in collecting valid safety data that make software safety different from hardware safety. In our conclusions we present some of these deficiencies.},
	keywords = {case study, NASA, risk analysis, safety metrics},
	isbn = {978-1-4503-0039-1},
	doi = {10.1145/1852786.1852846},
	url = {http://doi.acm.org/10.1145/1852786.1852846},
	author = {Basili, Victor R. and Zelkowitz, Marvin V and Layman,Lucas and Dangle,Kathleen and Diep,Madeline}
}
