; Hand this in to: ece849-staff+hw@ece.cmu.edu ;Required Reading @article{schinzinger86_hazards, author = "Roland Schinzinger", title = "Technology hazards and the engineer", journal = "IEEE Technology and Society Magazine", year = "1986", pages = "12--16", abstract = "The nature and variety of technology hazards; how engineers and society assess the hazards and react to avoid harm; the need for a new style of engineering.", url = "http://www.ece.cmu.edu/~ece849/papers/schinzinger86_technology_hazards.pdf", studentname = "", summary = "", contribution1 ="", contribution2 ="", contribution3 ="", contribution4 ="", contribution5 ="", weakness1 = "", weakness2 = "", weakness3 = "", weakness4 = "", weakness5 = "", interesting = "high/med/low", opinions = "", } @article{redmill02, author = "Redmill, F.", title = "Some dimensions of risk not often considered by engineers", journal = "Computing & Control Engineering Journal", year = "2002", volume = "13", number = "6", abstract = "For many years risk analysis has informed the design and operatoin of technologically risky systesm, and many engineers and scientists consider risk to be objectively measurable. But a great deal of research into the subject by social scientists, including psychological studies into risk perception and decision-making, should interest engineers and could inform improvements to the process of risk analysis.", url = "http://ieeexplore.ieee.org/iel5/2218/26014/01161460.pdf", studentname = "", summary = "", contribution1 ="", contribution2 ="", contribution3 ="", contribution4 ="", contribution5 ="", weakness1 = "", weakness2 = "", weakness3 = "", weakness4 = "", weakness5 = "", interesting = "high/med/low", opinions = "", } @article{davis94_liabilities, author = "Dai Davis", title = "Safety critical systems - legal liabilities", journal = "Computing & control", year = "1994", volume = "5", number = "1", pages = "13 -17", abstract = "Where does the responsibility 'buck' stop if a piece of software in a critical application fails? This article examines the range of liabilities placed on manufacturers and suppliers of safety-critical computer systems.", url = "http://ieeexplore.ieee.org/iel1/2218/6747/00272963.pdf", studentname = "", summary = "", contribution1 ="", contribution2 ="", contribution3 ="", contribution4 ="", contribution5 ="", weakness1 = "", weakness2 = "", weakness3 = "", weakness4 = "", weakness5 = "", interesting = "high/med/low", opinions = "", } @article{knight02_license, author = "John C. Knight and Nancy G. Leveson", title = "Licensing software engineers: Should software engineers be licensed?", journal = "Communications of the ACM", volume = "45", number = "11", year = "2002", pages = "87--90", url = "http://doi.acm.org/10.1145/581571.581601", studentname = "", summary = "", contribution1 ="", contribution2 ="", contribution3 ="", contribution4 ="", contribution5 ="", weakness1 = "", weakness2 = "", weakness3 = "", weakness4 = "", weakness5 = "", interesting = "high/med/low", opinions = "", } ;Supplemental Readings @article{Bowen00, author = "Bowen, J.", title = "The ethics of safety-critical systems", journal = "Communications of the ACM 43,", year = "2000", pages = "91-7", number = "4", abstract = "The use of safety-critical software is rapidly increasing. Computers are used in safety-critical applications at least an order of magnitude more often compared to a decade ago. It is important to note, however, that software decisions are often based on economic rather than safety considerations. Safety implications are more difficult to assess. Some industry professionals claim that increased use of software increases the safety of the system. However, since it is so difficult to measure software reliability, this is difficult to justify in practice. There are many practices that should be avoided in order to enhance the safety features of software systems", url = "http://doi.acm.org/10.1145/332051.332078", studentname = "", summary = "", contribution1 = "", contribution2 = "", contribution3 = "", contribution4 = "", contribution5 = "", weakness1 = "", weakness2 = "", weakness3 = "", weakness4 = "", weakness5 = "", interesting = "high/med/low", opinions = "", } @article{Gotterbarn99, author = "Gotterbarn, D.", title = "How the new Software Engineering Code of Ethics affects you", journal = "IEEE Software 16,", year = "1999", pages = "58-64", number = "6", abstract = "The Software Engineering Code of Ethics and Professional Practice has recently been approved. This article looks at the immediate and long-term implications: Why does a profession need a code of ethics? How will this code function in an emerging profession like software engineering? What impact will it have on software practitioners?", url = "http://", studentname = "", summary = "", contribution1 = "", contribution2 = "", contribution3 = "", contribution4 = "", contribution5 = "", weakness1 = "", weakness2 = "", weakness3 = "", weakness4 = "", weakness5 = "", interesting = "high/med/low", opinions = "", } @article{Gibbs94, author = "Wayt Gibbs, W.", title = "Software's chronic crisis", journal = "Scientific American (International Edition) 271,", year = "1994", pages = "72-81", number = "3", abstract = "Despite 50 years of progress, the software industry remains years, perhaps decades, short of the mature engineering discipline needed to meet the demands of an information age society. Software engineering remains a term of aspiration. The vast majority of computer code is still handcrafted from raw programming languages by artisans using techniques they neither measure nor are able to repeat consistently. The picture is not entirely bleak. Intuition is slowly yielding to analysis as programmers begin using quantitative measurements of the quality of the software they produce to improve the way they produce it. The mathematical foundations of programming are solidifying as researchers work on ways of expressing program designs in algebraic forms that make it easier to avoid serious mistakes. Academic computer scientists are starting to address their failure to produce a solid corps of software professionals. Perhaps most important, many in the industry are turning their attention toward inventing the technology and market structures needed to support interchangeable, reusable software parts", url = "http://www.ece.cmu.edu/~ece749/papers/gibbs94_sw_chronic_crisis.pdf", studentname = "", summary = "", contribution1 = "", contribution2 = "", contribution3 = "", contribution4 = "", contribution5 = "", weakness1 = "", weakness2 = "", weakness3 = "", weakness4 = "", weakness5 = "", interesting = "high/med/low", opinions = "", } @article{Herkert94, author = "Herkert, J.R.", title = "Ethical risk assessment: valuing public perceptions", journal = "IEEE Technology and Society Magazine 13,", year = "1994", pages = "4-10", number = "1", abstract = "Engineers are confronted with an array of moral issues and dilemmas as the complexity modern technology results in equally complex efforts to assess the accompanying environmental and safety risks. The author examines the connections between engineering ethics, risk communication, and the engineering culture. First moral issues in risk assessment are reviewed and the ethical responsibilities of engineers with respect to risk assessment and risk communication are discussed. The conventional model of risk communication, which holds that only experts possess relevant risk information, is then critiqued, and the findings of social scientists and humanists with respect to the dual importance of expert and public risk information are reviewed. Following a discussion of the prevailing engineering culture, particularly as it relates to the problems involved in risk communication, some suggestions are made for transforming the engineering culture in a manner conducive to more meaningful discussion of risk", url = "http://ieeexplore.ieee.org/iel1/44/6777/00273764.pdf", studentname = "", summary = "", contribution1 = "", contribution2 = "", contribution3 = "", contribution4 = "", contribution5 = "", weakness1 = "", weakness2 = "", weakness3 = "", weakness4 = "", weakness5 = "", interesting = "high/med/low", opinions = "", } @article{Kahn86, author = "Kahn, S.", title = "Economic estimates of the value of life", journal = "IEEE Technology and Society Magazine 5,", year = "1986", pages = "24-31", number = "2", abstract = "Reviews the economic literature that, for policy evaluation purposes, assigns a value to risking human lives. The ethical justification for evaluating risk is argued by observing how much people are willing to pay personally to avoid risks. Most willingness-to-pay figures are based on observations of how much compensation workers must be paid to work at a risky job. The conceptual and practical problems and biases in these figures are explained. The main studies of financial value of life calculation are reviewed in light of this discussion. It is concluded that a conservative estimate for the value of risking a life is $8 million (1984 dollars), a figure far greater than is typically used in policy analysis", url = "http://www.ece.cmu.edu/~ece749/papers/kahn86_value_life.pdf", studentname = "", summary = "", contribution1 = "", contribution2 = "", contribution3 = "", contribution4 = "", contribution5 = "", weakness1 = "", weakness2 = "", weakness3 = "", weakness4 = "", weakness5 = "", interesting = "high/med/low", opinions = "", }