18-749 Reading List Spring 2003

Course Home Page


Course Introduction & Example Paper Discussion

Required:

Note: Read Wallace & Kuhn before reading Sullivan & Chillarege.

Supplemental:


Case Studies

Required:

Supplemental:


HW Fault Tolerance & Dependability Modeling

Required:

Supplemental:

Pending:


SW Fault tolerance: rollback/rollforward

Required:

Supplemental


SW Fault Tolerance: other techniques

Required:

Other High-Level Discussions

Supplemental:

See also: Exception handling; Fault Injection


Distributed Time

Required:

Supplemental:


Exception Handling

Required:

Supplemental:

Other sources:


Byzantine Agreement

Required:

Supplemental:


Fault Tolerant Middleware

Required:

Supplemental:


Group Membership

Required:

Supplemental:


Exception Handling Studies

Required:

Supplemental:


Dependable Upgrade

Required:

Supplemental:


Multi-Version Software

Required:

Supplemental:

Other sources:


Fault Injection

Required:

Supplemental:


Boeing 777: Case Study

Required:

Supplemental:


Graceful Degradation

Required:

Supplemental:


Robustness Testing

Required:

Supplemental:

Other sources:


Distributed Real Time Computing & Scheduling

Required:

Other High-Level Summaries:

Supplemental:

Other Sources:


Verification & Validation

Required:

Supplemental:

Supplemental Formal Methods papers:

Other sources:


Case Study: Three Mile Island

Required:


User Interface & Operator Errors

Required:

Supplemental:

Other Reading:


Software Safety

Required:

Other High-Level Summaries:

Supplemental:


Embedded Security

Required:

Supplemental:


Safety cases & risk management

Required:

Supplemental:

Risk Management Tools


Societal Issues

Required:

Supplemental:

Other References:

http://www.badsoftware.com/ has several papers that talk about UCITA, which is an attempt to regulate software that will have an effect on embedded system software.


TTP & Automotive Protocols: Case Study

Required:

Supplemental:


Very Dependable Systems

Required:

Supplemental: