Software Engineering of Fault Tolerant Systems (Software Engineering and Knowledge Engineering) (Software Engineering and Knowledge Engineering) (Series ... Engineering and Knowledge Engineering)

CONTENTS......Page 10
Preface......Page 6
1. Motivations for the Book......Page 12
2. Dependability and Fault Tolerance......Page 14
3. Defining Software Engineering......Page 17
3.2. How to Make Good Software......Page 18
4. Fault Tolerance Engineering: from Requirements to Code......Page 19
4.2. Software Architecture and Fault Tolerance......Page 20
4.3. Low-level Design and Fault Tolerance......Page 22
5. Verification and Validation of Fault Tolerant Systems......Page 23
5.3. Constraint Solvers......Page 24
5.5. UML-based approaches to modelling and validating dependable systems......Page 25
6.1. Programming Languages Perspectives......Page 26
6.1.1. Exception Handling......Page 27
6.1.3. Reflection and Aspect-Orientation......Page 28
6.2. Frameworks for Fault Tolerance......Page 29
6.3. Advanced Frameworks for Fault Tolerance......Page 31
7. Contribution of this Book to the Topic......Page 32
References......Page 35
Part A. Fault Tolerance Engineering: From Requirements to Code......Page 42
Exploiting Reflection to Enable Scalable and Performant Database Replication at the Middleware Level J . Salas, R. Jimenez-Peris, M. Patino-Martinez and B. Kemme......Page 44
1. Introduction......Page 45
2. Two Basic Database Replication Protocols......Page 47
3.1. Reflective database connection......Page 49
3.1.1. Basic algorithm......Page 50
3.2. Reflective requests......Page 51
3.3. Reflective transactions......Page 52
3.3.2. Readsets......Page 53
3.5. Reflective concurrency control......Page 54
3.5.2. Indirect abort......Page 55
4. Evaluation......Page 56
4.1. Experiment setup......Page 57
4.2. The cost of reflective writeset retrieval......Page 58
4.3. The gain of reflective writeset application......Page 60
4.4. The impact of reflective requests......Page 62
4.5. The cost of reflective concurrency control......Page 65
4.6. Analytical scalability......Page 66
5. Related Work......Page 69
References......Page 70
Adding Fault-Tolerance to State Machine-Based Designs S. S. Kulkarni, A. Arora and A . Ebnenasir......Page 73
1. Introduction......Page 74
2. Preliminaries......Page 76
2.2. Specifications and Correctness Criteria for Functional Designs......Page 77
2.3. Faults......Page 78
2.4. Fault-Tolerance......Page 79
3. Problem Statement......Page 80
4. Adding Failsafe Fault-Tolerance......Page 82
4.1. Case Study: Parking Lot Problem......Page 84
5. Adding Nonmasking Fault-Tolerance......Page 87
6. Adding Masking Fault-Tolerance......Page 89
6.1. Parking Lot Problem: Adding Masking Fault- Tolerance......Page 92
7. Related Work......Page 93
8. Impact of Proposed Algorithms and Open Problems......Page 94
9. Conclusions and Future Work......Page 98
References......Page 99
1.1. Motivation......Page 102
1.2.1. Stateful us. stateless services......Page 104
1.2 2. Business services vs. infrastructure services......Page 105
1.3. Model of a service-oriented system......Page 106
2.1.1. State synchronization via the data store......Page 107
2.1.3. Fundamental replication methods for service-oriented systems......Page 108
2.2.1. No replication at all......Page 112
2.2.2. No replication on the lower layer......Page 113
2.2.3. No replication on the upper layer......Page 114
2.2.4. Replication on both layers......Page 115
3.1. Primary-backup replication middleware......Page 117
3.3. Replication system architecture pattern......Page 119
3.3.2. Monitoring service......Page 120
3.3.4. Replication protocol......Page 121
3.3.6. Transaction service......Page 122
4. Related Work......Page 123
5. Conclusions and Future Work......Page 124
References......Page 125
Part B. Verification and Validation of Fault Tolerant Systems......Page 130
1. Introduction......Page 132
2.1. Related Work......Page 135
2.2. Nexus Interface......Page 137
2.3. Software Residual Faults and SoCs......Page 138
3. OCD-based Software Fault Emulation......Page 139
3.1.2. CaIlee Address......Page 141
3.1.3. Caller and Target Addresses......Page 142
3.2. Step 2: Fault Location Choice and Emulation......Page 143
3.3. Step 3: Target Component Value Monitoring......Page 144
3.5. Step 5: Result Analysis......Page 145
4. A Nexus-based Approach for Monitoring and Time Measurement......Page 146
4.2. Component Error Detection Latencies......Page 147
5. Case Study......Page 149
5.2. Experimental Results......Page 152
5.3. 0S Error Detection Latency Time......Page 153
5.4. Real-Time Tasks Execution Times......Page 155
6. Conclusions......Page 158
References......Page 159
1. Introduction......Page 161
2. A Formal Semantics for UML 2.0 Statecharts......Page 163
3. A Temporal Logic Language for UML 2.0 Statecharts......Page 168
4. Efficient Evaluation of Temporal Logic Formulae......Page 172
5. A Watchdog Architecture for UML 2.0 Statecharts......Page 174
6. Experimental Evaluation of Error Detection Capabilities......Page 179
7. Conclusions and Future Work......Page 184
References......Page 185
1. Introduction......Page 186
1.2. OSEKtime FTCom......Page 189
2. FOCUS......Page 190
3.1. Fault-Tolerant Embedded System......Page 194
3.2. FTCom......Page 196
3.3.1. Abstractions......Page 199
3.3.2. FlexRay Requirements and Architecture......Page 200
3.3.3. FlexRay Controller......Page 202
3.3.4. Cable......Page 203
4.2. FlexRay Frames......Page 205
5. Verification of the Properties: FlexRay......Page 206
6. Related Work......Page 207
References......Page 208
Part C. Languages and Tools for Engineering Fault Tolerant Systems......Page 210
1.1. Fault Tolerance and Exception Management......Page 212
1.2. Model Driven Development......Page 213
1.3. Horizontal and Vertical Domains......Page 214
1.4. Model Driven Exception Management......Page 215
2.1. Overview......Page 216
2.2. Concurrent Systems......Page 217
3. Model Driven Exception Management Framework......Page 218
3.1. Exception Management Modeling Language......Page 221
3.2. Model Transformation......Page 225
3.3. Exception Management Library......Page 227
3.4. Domain Specific Modeling Tools......Page 229
4. Project Tracker Case Study......Page 230
5. Related Work......Page 234
6. Conclusion and Future Work......Page 235
References......Page 237
1. Introduction......Page 241
2. The System Setup......Page 242
3. Model-based Failure Detection......Page 247
4.1. Reliability Measure......Page 250
4.2. Optimal Repair and Adaptation......Page 254
5. Example......Page 259
6. Conclusions......Page 264
References......Page 265
Extending the Applicability of the Neko Framework for the Validation and Verification of Distributed Algorithms L. Falai and A . Bondaualli......Page 267
1. Introduction......Page 268
2.1. The Neko framework......Page 269
2.1.1. Approaches for the Integration of C/C++ Code in a Java Framework......Page 271
2.1.2. Approaches to make a tool usable in a larger class of systems......Page 272
3. How to directly include C/C++ code as components of a Neko application......Page 274
3.2. Component Adaptation......Page 276
3.3. Communication between C/C++ code and Java......Page 277
3.4. Quantitative Evaluation of C/C++ code with NekoStat......Page 278
3.5.1. Quantitative Analysis of ASFDA......Page 279
3.5.2. Qualitative analysis of ASFDA......Page 281
4.1. Server Factory......Page 284
4.1.1. Utilities for campaign definition and execution......Page 286
4.2. Compatibility of the new Java utilities......Page 287
5. Concluding Remarks and Future Works......Page 288
References......Page 291