Measuring software failure risk: Methodology and an example
References (46)
- et al.
Optimum Release Time for Software Systems Based on Reliability and Cost Criteria
J. Systems Software
(1980) - et al.
Software Reliability Growth Models for Testing-Effort Control
European J. Oper. Res.
(1990) - et al.
The Future Engineering of Software: A Management Perspective
Computer
(1991) A Spiral Model of Software Development and Enhancement
Computer
(1988)- et al.
Understanding and Controlling Software Costs
IEEE Trans. Software Engrg.
(1988) - et al.
Recalibrating Software Reliability Models
IEEE Trans. Software Engrg.
(1990) - et al.
Safety Verification in Murphy Using Fault Tree Analysis
A User-Oriented Software Reliability Model
IEEE Trans. Software Engrg.
(1980)Measuring Software Safety
- et al.
Applying Reliability Measurement: A Case Study
IEEE Software
(1990)
Software Reliability Measurement
IEEE J. Selected Areas Comm.
(1990)
Acceptable Risk
(1981)
An Empirical Stopping Rule for Debugging and Testing Computer Software
J. Am. Statist. Assoc.
(1987)
Risk Assessment of Computer Controlled Systems
IEEE Trans. Software Engrg.
(1985)
Reliability Engineering and Risk Assessment
(1981)
Optimal Release Policies for Software Systems with Testing Effort
Int. J. Systems Sci.
(1991)
Using Neural Networks in Reliability Prediction
IEEE Software
(1992)
Predicting Software Errors, During Development, Using Nonlinear Regression Models: A Comparative Study
IEEE Trans. Reliability
(1992)
Managing Test-Procedures to Achieve Reliable Software
IEEE Trans. Reliability
(1983)
Software Safety: Why, What, and How
Comput. Surveys
(1986)
Analyzing Software Safety
IEEE Trans. Software Engrg.
(1983)
Safety Verification of Ada Programs Using Software Fault Trees
IEEE Software
(1991)
MTBF is Meaningless in Software Reliability
IEEE Trans. Reliability
(1975)
Cited by (8)
IT managers’ vs. IT auditors’ perceptions of risks: An actor–observer asymmetry perspective
2018, Information and ManagementCitation Excerpt :Risk is generally regarded as the combination of the probability of an undesirable event occurring and the magnitude of the loss that is associated with the event [47] and has been treated as such in the IS literature (see, e.g., Barki et al. [13]). Therefore, these two factors have often been used together to define and describe risk [12,48,49]. As both probability of risk and impact of risk can, in theory, influence risk perception, we included both elements in our model.
Investigation of risk perception and risk propensity on the decision to continue a software development project
2000, Journal of Systems and SoftwareCost estimation of software projects: A sub-additive approach
2017, Journal of Modern Project ManagementMeasuring the risk of software projects
2015, International Journal of Software Engineering and its ApplicationsThe reluctance to report bad news on troubled software projects: A theoretical model
2003, Information Systems JournalOn comparisons of random, partition, and proportional partition testing
2001, IEEE Transactions on Software Engineering
Copyright © 1994 Published by Elsevier Inc.