ACM Computing Surveys (CSUR)
Computer related risks
Crash failures can drive protocols to arbitrary states
PODC '96 Proceedings of the fifteenth annual ACM symposium on Principles of distributed computing
The complexity of crash failures
PODC '97 Proceedings of the sixteenth annual ACM symposium on Principles of distributed computing
End-to-end arguments in system design
ACM Transactions on Computer Systems (TOCS)
Self-stabilizing systems in spite of distributed control
Communications of the ACM
Coordinated atomic actions: how to remain ACID in the modern world
ACM SIGSOFT Software Engineering Notes
Computer
Point-SE Education: We're on Our Own
IEEE Software
IEEE Software
Software Engineering is Not Enough
IEEE Software
IEEE Transactions on Computers
The Double Life of the Transaction Abstraction: Fundamental Principle and Evolving System Concept
VLDB '95 Proceedings of the 21th International Conference on Very Large Data Bases
Recovery semantics for a DB/DC system
ACM '73 Proceedings of the ACM annual conference
1983 Invited address solved problems, unsolved problems and non-problems in concurrency
PODC '84 Proceedings of the third annual ACM symposium on Principles of distributed computing
The Art Of Creating Reliable Software-Based Systems Using Off-The-Shelf Software Components
SRDS '97 Proceedings of the 16th Symposium on Reliable Distributed Systems
Do We Know Enough to Teach Software Engineering?
IEEE Software
Scalable Self-Stabilization via Composition
ICDCS '04 Proceedings of the 24th International Conference on Distributed Computing Systems (ICDCS'04)
Improving availability with recursive microreboots: a soft-state system case study
Performance Evaluation - Dependable systems and networks-performance and dependability symposium (DSN-PDS) 2002: Selected papers
Systems of systems and coordinated atomic actions
ACM SIGSOFT Software Engineering Notes
ACM SIGSOFT Software Engineering Notes
A rational theory of system-making systems
ACM SIGSOFT Software Engineering Notes
Queue - Component Technologies
A critical programmer searches for professionalism
ACM SIGSOFT Software Engineering Notes
Self-stabilizing byzantine agreement
Proceedings of the twenty-fifth annual ACM symposium on Principles of distributed computing
Communications of the ACM - Spam and the ongoing battle for the inbox
Exploring failure transparency and the limits of generic recovery
OSDI'00 Proceedings of the 4th conference on Symposium on Operating System Design & Implementation - Volume 4
A systems analysis of systems integration
ACM SIGSOFT Software Engineering Notes
Software maturity: design as dark art
ACM SIGSOFT Software Engineering Notes
The limits of systems-making organizations
ACM SIGSOFT Software Engineering Notes
Hi-index | 0.00 |
Systems designers will most often design to the N-1 criterion whether the designers know they are doing so or not. Systems designed to the N-1 criterion detect, isolate and (possibly) recover from at most one fault at a time. In contrast to the N-1 criterion, systems integrators must fault isolate in the presence of multiple simultaneous faults and in the absence of user guides. The purpose of this paper is to debug the debugging process used by systems integrators. To that end this paper describes the systems integration environment, identifies factors that drive the efficiency of that effort and provides a critique of the historical roots of architectural firewalls. (If there were no firewalls everything could theoretically interfere with everything else as only the stricture of time would prevent everything from happening at once. Yet a perfect firewall would be an impossibility; a Maxwell's demon of information.) This paper penultimately provides philosophical musings, a self-reflection on meanings uncovered. As this paper has strong non-linear content an attempt has been made for textual constraint by theme: I. The Systems Integration Environment II. An Efficient Systems Integration Efficiency Metric III. Architectural Investigations IV. the Problem Behind the Problem (tPBtP)