<< Chapter < Page Chapter >> Page >
This module is founded on two insights: the analogy between problem-solving in ethics and design methodology and the effectiveness of case analysis for practicing skills in ethical problem-solving. Students will learn socio-technical system analysis and how to use this analysis to predict the problems likely to accompany the implementation of a new technology or computing system. This module has been developed to test networking potentialities of the EAC Toolkit and Connexions by linking to the materials posted at the Computing Cases website. This module is being developed as a part of an NSF-funded project, "Collaborative Development of Ethics Across the Curriculum Resources and Sharing of Best Practices," NSF SES 0551779.

Computer Ethics

Case Module Template: Machado Case

By William J. Frey

Module Abstract:

This module, designed for the EAC Toolkit (NSF SES 0551779), will test the Toolkit and Connexion’s ability tonetwork different online and offline sources for ethics across the curriculum. It consists of four components designed to providetools for an in-depth analysis of the cases found at www.computingcases.org ; it also makes substantial references to the draft manuscript of a textbook in computer ethics entitledGood Computing: A Virtue Approach to Computer Ethics under contract with Jones and Bartlett Publishing Company. (This book will consistof the cases displayed at Computing Cases—Therac-25, Machado, and Hughes Aircraft—and 7 additional cases all developed through NSFprojects DUE-9972280 and DUE 9980768.)

Module Introduction:

This module as displayed in Connexions presents the case abstract and timeline both taken from ComputingCases. It then refers to the website where the following can be found by browsing:

  • case narrative,
  • case history,
  • a teaching introduction which also provides a useful overview,
  • an ethical analysis that can be accessed by clicking on the appropriate concept in the table displayed (clicking on safety willopen a short document that discusses the safety implications of the case)
  • a Socio-Technical Analysis which spells out the different components of the cases socio-technical system such as hardware,software, physical surroundings, people/groups/roles, procedures, laws, and data/data structures.
  • supporting documents such as three RFCs (Request for Comments) on the Unix finger command, a profile of students at UCI,and an interview with Allen Schiano from the University of California at Irvine’s Office of Academic Computing.

These materials all posted at www.computingcases.org provide the background information necessary for a detailed and exhaustive case analysis. (Asuggestion: since you will be working in groups, divide these readings among your group members and take advantage of class timeto report to one another on the contents of the links you have individually explored. Be sure to triangulate by assigning morethan one member to each link. This will help to identify and solve problems in interpretation.)

The case abstract and timeline in this module outline the case. The following decision point taken from theMachado case will provide the focus for an in-depth case analysis. You will respond to the decision-point by working through a fourstage decision making procedure inspired by the standard Software Development cycle:

Get Jobilize Job Search Mobile App in your pocket Now!

Get it on Google Play Download on the App Store Now




Source:  OpenStax, Modules linking to computing cases. OpenStax CNX. Jul 26, 2007 Download for free at http://legacy.cnx.org/content/col10423/1.2
Google Play and the Google Play logo are trademarks of Google Inc.

Notification Switch

Would you like to follow the 'Modules linking to computing cases' conversation and receive update notifications?

Ask