@conference {12105,
	title = {A case study of measuring process risk for early insights into software safety},
	booktitle = {Software Engineering (ICSE), 2011 33rd International Conference on},
	year = {2011},
	month = {2011/05//},
	pages = {623 - 632},
	abstract = {In this case study, we examine software safety risk in three flight hardware systems in NASA{\textquoteright}s Constellation spaceflight program. We applied our Technical and Process Risk Measurement (TPRM) methodology to the Constellation hazard analysis process to quantify the technical and process risks involving software safety in the early design phase of these projects. We analyzed 154 hazard reports and collected metrics to measure the prevalence of software in hazards and the specificity of descriptions of software causes of hazardous conditions. We found that 49-70\% of 154 hazardous conditions could be caused by software or software was involved in the prevention of the hazardous condition. We also found that 12-17\% of the 2013 hazard causes involved software, and that 23-29\% of all causes had a software control. The application of the TRPM methodology identified process risks in the application of the hazard analysis process itself that may lead to software safety risk.},
	keywords = {analysis;software, and, computing;risk, constellation, control;software, Hardware, maintenance;, measurement;aerospace, measurement;software, NASA, process, program;TPRM;flight, risk, safety;technical, spaceflight, systems;process},
	doi = {10.1145/1985793.1985881},
	author = {Layman,L. and Basili, Victor R. and Zelkowitz, Marvin V and Fisher,K.L.}
}
@article {18362,
	title = {A management tool for evaluation of software design},
	journal = {Software Engineering, IEEE Transactions on},
	volume = {17},
	year = {1991},
	month = {1991/09//},
	pages = {961 - 971},
	abstract = {A model for evaluating software designs based on extending the functional model of program verification with concepts from economic decision theory has been proposed. The authors describe the method, and discuss a prototype implementation of a tool, called Selector, which implements this technique. It is suggested that a system like Selector can be used in two ways: as a decision support system for management to be used in the process of making choices among various alternatives; and as a prototyping investigative system for proposing and answering a series of {\textquoteleft}what if{\textquoteright} scenarios. The proposed model depends on a risk analysis, of each potential solution and aspects of decision theory to modify the evaluation strategy. The model depends on equilibrium probabilities for generating answers},
	keywords = {analysis;software, decision, designs;decision, investigative, model;management, probabilities;evaluation, prototyping;software, Selector;decision, strategy;functional, Support, system;economic, system;risk, systems;program, theory;equilibrium, tool;program, tools;, verification;prototyping, verification;software},
	isbn = {0098-5589},
	doi = {10.1109/32.92916},
	author = {Cardenas-Garcia,S. and Zelkowitz, Marvin V}
}
