Robust Storage Structures for Crash Recovery
IEEE Transactions on Computers - The MIT Press scientific computation series
A Theory of Fault-Based Testing
IEEE Transactions on Software Engineering
The costs and benefits of pair programming
Extreme programming examined
Endo-testing: unit testing with mock objects
Extreme programming examined
Software fault tolerance techniques and implementation
Software fault tolerance techniques and implementation
Formal Methods Application: An Empirical Tale of Software Development
IEEE Transactions on Software Engineering
Computer
IEEE Software
Integrating Formal Methods into the Development Process
IEEE Software
Recovery Oriented Computing (ROC): Motivation, Definition, Techniques,
Recovery Oriented Computing (ROC): Motivation, Definition, Techniques,
COMPSAC '03 Proceedings of the 27th Annual International Conference on Computer Software and Applications
Assertions in Object Oriented Software Maintenance: Analysis and a Case Study
ICSM '04 Proceedings of the 20th IEEE International Conference on Software Maintenance
Basic Concepts and Taxonomy of Dependable and Secure Computing
IEEE Transactions on Dependable and Secure Computing
Combining statistical monitoring and predictable recovery for self-management
WOSS '04 Proceedings of the 1st ACM SIGSOFT workshop on Self-managed systems
Investigations Into Graceful Degradation of Evolutionary Developmental Software
Natural Computing: an international journal
Pragmatic Unit Testing in Java with JUnit
Pragmatic Unit Testing in Java with JUnit
Toward recovery-oriented computing
VLDB '02 Proceedings of the 28th international conference on Very Large Data Bases
| Hi-index | 0.00 |
Recovery-oriented software is built with the perspective that hardware or software failures and operation mistakes are facts to be coped with, as they are problems that cannot be fully solved while developing real complex applications. Consequently, any software will always have a non-zero chance of failure. Some of these failures may be caused by defects that may be removed or encapsulated. From the point of view of removing or encapsulating defects, a failure is considered to be trivial, when (i) the required effort to identify and eliminate or encapsulate the causing defect is small, (ii) the risk of making mistakes in these steps is also small and (iii) the consequences of the failure are tolerable. It is highly important to design systems in such a way that most (ideally all) of the failures are trivial. Such systems are called ‘debuggable systems’. In this study, we present the results of systematic applying techniques that focus on creating debuggable software for real embedded applications. Copyright © 2008 John Wiley & Sons, Ltd.