; Hand this in to:   ece849+hw@ece.cmu.edu


; Required Readings

@Conference{avizienis00_fundamental_concepts_dependability,
  author =       "Avizienis, A. ; Laprie, J. ; Randell, B.",
  affiliation =  "California Univ., Los Angeles, CA, USA",
  title =        "Fundamental concepts of dependability",
  booktitle =    "Proceedings of ISW 2000. 34th Information Survivability Workshop",
  location =      "Cambridge, MA, USA",
  organization = "IEEE",
  year =         "2000",
  pages =        "7--12",
  abstract =     "Computing systems are characterized by four
                  fundamental properties: functionality, performance, cost and
                  dependability. Dependability of a computing system is the ability to
                  deliver service that can justifiably be trusted. The paper presents the
                  fundamental concepts of dependability, including the threats,
                  attributes and the means by which dependability is obtained.",
  url = "http://citeseer.nj.nec.com/avizienis01fundamental.html",
  studentname =   "",
  summary =       "",
  contribution1 = "",
  contribution2 = "",
  contribution3 = "",
  contribution4 = "",
  contribution5 = "",
  weakness1 =     "",
  weakness2 =     "",
  weakness3 =     "",
  weakness4 =     "",
  weakness5 =     "",
  interesting =   "high/med/low",
  opinions =      "",
}

@Conference{wallace99_medical_device_failures,
  author =       "Wallace, D.R.; Kuhn, D.R.",
  affiliation =  "Nat. Inst. of Stand. & Technol."
  title =        "Failure modes in medical device software: an analysis of 15 years of recall data",
  journal =      "International Journal of Reliability, Quality and Safety Engineering (IJRQSE)",
  year =         "2001",
  volume = 	 "8",
  number = 	 "4",
  pages =        "351-371",
  abstract =     "Most complex systems today contain software, and systems failures activated by software faults can provide lessons for software development practices and software quality assurance. This paper presents an analysis of softwarerelated failures of medical devices that caused no death or injury but led to recalls by the manufacturers. The analysis categorizes the failures by their symptoms and faults, and discusses methods of preventing and detecting faults in each category. The nature of the faults provides lessons about the value of generally accepted quality practices for prevention and detection methods applied prior to system release. It also provides some insight into the need for formal requirements specification and for improved testing of complex hardware-software systems.",
  url = "http://citeseerx.ist.psu.edu/viewdoc/summary?doi=10.1.1.39.6608",
  studentname =   "",
  summary =       "",
  contribution1 = "",
  contribution2 = "",
  contribution3 = "",
  contribution4 = "",
  contribution5 = "",
  weakness1 =     "",
  weakness2 =     "",
  weakness3 =     "",
  weakness4 =     "",
  weakness5 =     "",
  interesting =   "high/med/low",
  opinions =      "",
}


@Conference{sullivan91_odc,
  author =       "Sullivan, M. ; Chillarege, R.",
  affiliation =  "IBM Thomas J. Watson Res. Center"
  title =        "Software defects and their impact on system availability-a study of field failures in operating systems",
  booktitle =    "Fault-Tolerant Computing: Twenty-First International Symposium",
  location =      "Montreal, Que., Canada",
  organization = "IEEE",
  year =         "1991",
  pages =        "2--9",
  ISBN =         "0818621508",
  abstract =     "Defects reported between 1986 and 1989 in the MVS
                    operating system are studied in order to gain the insight needed to
                    provide a clear strategy for avoiding or tolerating them. Typical
                    defects (regular) are compared to those that corrupt a program's memory
                    (overlay), given that overlays are considered by field services to be
                    particularly hard to find and fix. It is shown that the impact of an
                    overlay defect is, on average, much higher than that of a regular
                    defect, that boundary conditions and allocation management are the major
                    causes of overlay defects, not timing, and that most overlays are small
                    and corrupt data near the data that the programmer meant to update.
                    Further analysis is provided on defects in fixes to other defects,
                    failure symptoms, and the impact of defects on customers",
  url = "http://citeseer.nj.nec.com/sullivan91software.html",
  studentname =   "",
  summary =       "",
  contribution1 = "",
  contribution2 = "",
  contribution3 = "",
  contribution4 = "",
  contribution5 = "",
  weakness1 =     "",
  weakness2 =     "",
  weakness3 =     "",
  weakness4 =     "",
  weakness5 =     "",
  interesting =   "high/med/low",
  opinions =      "",
}



; Supplimental Reading

@Conference{chillarege94,
  author =       "R. Chillarege",
  title =        "ODC for process measurement, analysis, and control,",
  booktitle =    "Fourth International Conference on Software Quality, ASQC Software Division",
  year =         "1994",
  abstract =     "This paper provides the motivation and overview of Orthogonal Defect Classification (ODC), a new technology for software process measurement and analysis. ODC provides a significant step forward in being able to understand the dynamics of software development by using classification of defects, so that they provide measurements. This breakthrough is being used at several IBM labs and is now supported by several processes, analyses and tools from the Thomas J. Watson Research Center. ",
  url = "http://www.chillarege.com/odc/articles/asqc/asqc.html";
  studentname =   "",
  summary =       "",
  contribution1 = "",
  contribution2 = "",
  contribution3 = "",
  contribution4 = "",
  contribution5 = "",
  weakness1 =     "",
  weakness2 =     "",
  weakness3 =     "",
  weakness4 =     "",
  weakness5 =     "",
  interesting =   "high/med/low",
  opinions =      "",
}