When Should One Stop Testing Software?
From MaRDI portal
Recommendations
Cited in
(23)- Optimal stopping time in software testing based on failure size approach
- scientific article; zbMATH DE number 18880 (Why is no real title available?)
- Stopping rules and estimation for recapture debugging with unequal failure rates
- Optimal policies for security patch management
- Nash equilibrium strategies revisited in software release games
- SEQUENTIAL CONFIDENCE INTERVALS FOR A POPULATION SIZE WITH FIXED PROPORTIONAL ACCURACY
- A sequential software release policy
- An adaptive rule for stopping a discovery process under time censorship
- Practical stopping criteria for validating safety-critical software by estimating impartial relia\-bil\-ity
- Optimal Maintenance Schedules of Computer Software
- Nonparametric Sequential Bayes Estimation of the Distribution Function
- On optimality of one‐bug‐look‐ahead policies for a software testing model
- Buying with exact confidence
- Optimum release time of a software under periodic debugging schedule
- A Bayesian analysis of beta testing
- A RELIABILITY-CONSTRAINED SOFTWARE RELEASE POLICY USING A NON-GAUSSIAN KALMAN FILTER MODEL
- scientific article; zbMATH DE number 218456 (Why is no real title available?)
- Optimal selection and release problem in software testing process: a continuous time stochastic control approach
- Stackelberg strategy solution for optimal software release policies
- Software release policies on a shot-noise process model
- Optimal stopping in software testing
- A unified approach for optimal release, patching and testing time of a software
- Software release games
This page was built for publication: When Should One Stop Testing Software?
Report a bug (only for logged in users!)Click here to report a bug for this page (MaRDI item Q3811559)