Draft paper for Topic: [?]

Carnegie Mellon University
18-849b Dependable Embedded Systems
Spring 1998

Authors:

Abstract:

....Your Abstract Goes here...

Related Topics:

• Link to topic 1
• Link to topic 2
• Link to topic 3
• LINK TO CLUSTER 1
• LINK TO CLUSTER 2
• Project Page

Contents:

• Introduction
• Key Concepts
• Available tools, techniques, and metrics
• Relationship to other topics
• Conclusions
• Annotated Reference List
• Loose Ends

Introduction

...Your text goes here...

Key Concepts

...Your text goes here...

Available tools, techniques, and metrics

...Your text goes here...

In particular, make an assessment of the state of the art (mature, moderately OK, neophyte, nobody even worries about this yet, etc. etc.)

Relationship to other topics

...Your text goes here.., with relative pointers to other topic directories such as "../life_cycle"

Conclusions

...Your text goes here...

Annotated Reference List

• [Huang96] Huang, G. W. (ed.), Design for X: concurrent engineering imperatives, London: Chapman & Hall, 1996
  
• This book talks about designing for specific properties, including experiences and tools. The values for "X" specifically discussed in chapters by various authors include: dimensional control, printed circuit board assembly, inspectability, material storage/distribution, reliability, electromagnetic compatibility, serviceability, disassembly/recycling, quality, modularity, environmental impact, life cycle cost, and technical merit. The general approach in this field appears to be more evaluative than synthesis-based as one might find in the VLSI field. The contents are largely useful for mechanical engineering designs rather than embedded systems in particular. Nonetheless, this appears to be the best available discussion of multidisciplinary design research and practice.
• [Neumann86] Neumann, Peter G., "On Hierarchical Design of Computer Systems for Critical Applications." IEEE Transactions on Software Engineering, Sept. 1986, vol.SE-12, no.9, p. 905-20.
  

  Abstract: "We consider here the design of computer systems that must be trusted to satisfy simultaneously a variety of critical requirements such as human safety, fault tolerance, high availability, security, privacy, integrity, and timely responsiveness -- and that must continue to do so throughout maintenance and long-term evolution. Hierarchical abstraction is shown to provide the basis for successive layers of trust with respect to the full set of critical requirements, explicitly reflecting differing degrees of criticality. (47 Refs)"

  This is a broad-sweeping paper that ties together a highly inter-disciplinary view of dependability with respect to security, fault tolerance, and safety. It discusses how layered abstraction can be used to produce systems that might actually work in the real world (which is a very messy place indeed). Perhaps the most important point to take away is in the penultimate paragraph of the paper:

  "Above all, it is vital to recognize that completely guaranteed behavior is impossible and that there are inherent risks in relying on computer systems in critical environments. The unforseen circumstances are often the most disasterous."

Loose Ends

Go To Project Page