Measuring the Robustness of a Resource Allocation
IEEE Transactions on Parallel and Distributed Systems
Reflections on Industry Trends and Experimental Research in Dependability
IEEE Transactions on Dependable and Secure Computing
A Measure of Robustness Against Multiple Kinds of Perturbations
IPDPS '05 Proceedings of the 19th IEEE International Parallel and Distributed Processing Symposium (IPDPS'05) - Workshop 1 - Volume 02
Interval robust multi-objective evolutionary algorithm
CEC'09 Proceedings of the Eleventh conference on Congress on Evolutionary Computation
On enhancing the robustness of commercial operating systems
ISAS'04 Proceedings of the First international conference on Service Availability
A systematic review of software robustness
Information and Software Technology
| Hi-index | 0.00 |
Software developers identify two main reasons why software systems are not made robust: performance and practicality. This work demonstrates the effectiveness of general techniques to improve robustness that are practical and yield high performance. We present data from treating three systems to improve robustness by a factor of 5 or more, with a measured performance penalty of under 5% in nearly every case, and usually under 2%.We identify a third possible reason why software systems are not made robust: developer awareness. A case study on three professional development groups evaluated their ability to estimate the robustness of their software. Two groups were able to estimate their software's robustness to some extent, while one group had more divergent results. Although we can overcome the technical challenges, it appears that even experienced developers canbenefit from tools to locate robustness failures and training in robustness issues.