Case analysis module machado, college study notes - Case analysis, Study notes of Computational and Statistical Data Analysis

Study Guide. This module is founded on two insights: the analogy between problem-solving in ethics and design methodology and the eectiveness of case analysis for practicing skills in ethical problem-solving. Stu- dents 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 l

Typology: Study notes

2011/2012

Uploaded on 10/12/2012

hollyb
hollyb 🇺🇸

4.8

(44)

431 documents

1 / 7

Toggle sidebar

This page cannot be seen from the preview

Don't miss anything!

bg1
Connexions module: m13787 1
Case Analysis Module: Machado
William Frey
This work is produced by The Connexions Project and licensed under the
Creative Commons Attribution License
Abstract
This module is founded on two insights: the analogy between problem-solving in ethics and design
methodology and the eectiveness of case analysis for practicing skills in ethical problem-solving. Stu-
dents 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 de-
veloped 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 to network dierent online and oine sources for ethics across the curriculum. It consists of four com-
ponents designed to provide tools for an in-depth analysis of the cases found at www.computingcases.org
1
; it also makes substantial references to the draft manuscript of a textbook in computer ethics entitled
Good Computing: A Virtue Approach to Computer Ethics under contract with Jones and Bartlett Pub-
lishing Company. (This book will consist of the cases displayed at Computing CasesTherac-25, Machado,
and Hughes Aircraftand 7 additional cases all developed through NSF projects DUE-9972280 and DUE
9980768.)
Module Introduction:
This module as displayed in Connexions presents the case abstract and timeline both taken from Com-
puting Cases. 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 will open a short document that discusses the safety implications of the case)
a Socio-Technical Analysis which spells out the dierent components of the cases socio-technical sys-
tem such as hardware, software, physical surroundings, people/groups/roles, procedures, laws, and
data/data structures.
Version 1.2: Mar 2, 2007 8:18 am US/Central
http://creativecommons.org/licenses/by/2.0/
1
http://www.computingcases.org/
http://cnx.org/content/m13787/1.2/
pf3
pf4
pf5

Partial preview of the text

Download Case analysis module machado, college study notes - Case analysis and more Study notes Computational and Statistical Data Analysis in PDF only on Docsity!

Case Analysis Module: Machado

William Frey

This work is produced by The Connexions Project and licensed under the Creative Commons Attribution License †

Abstract This module is founded on two insights: the analogy between problem-solving in ethics and design methodology and the eectiveness of case analysis for practicing skills in ethical problem-solving. Stu- dents 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 de- veloped 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 to network dierent online and oine sources for ethics across the curriculum. It consists of four com- ponents designed to provide tools for an in-depth analysis of the cases found at www.computingcases.org^1 ; it also makes substantial references to the draft manuscript of a textbook in computer ethics entitled Good Computing: A Virtue Approach to Computer Ethics under contract with Jones and Bartlett Pub- lishing Company. (This book will consist of the cases displayed at Computing CasesTherac-25, Machado, and Hughes Aircraftand 7 additional cases all developed through NSF projects DUE-9972280 and DUE 9980768.) Module Introduction: This module as displayed in Connexions presents the case abstract and timeline both taken from Com- puting Cases. 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 will open a short document that discusses the safety implications of the case)
  • a Socio-Technical Analysis which spells out the dierent components of the cases socio-technical sys- tem such as hardware, software, physical surroundings, people/groups/roles, procedures, laws, and data/data structures. ∗Version 1.2: Mar 2, 2007 8:18 am US/Central †http://creativecommons.org/licenses/by/2.0/ (^1) http://www.computingcases.org/
  • supporting documents such as three RFCs (Request for Comments) on the Unix nger command, a prole of students at UCI, and an interview with Allen Schiano from the University of California at Irvine's Oce of Academic Computing.

These materials all posted at www.computingcases.org^2 provide the background information necessary for a detailed and exhaustive case analysis. (A suggestion: since you will be working in groups, divide these readings among your group members and take advantage of class time to report to one another on the contents of the links you have individually explored. Be sure to triangulate by assigning more than 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 the Machado case will provide the focus for an in-depth case analysis. You will respond to the decision-point by working through a four stage decision making procedure inspired by the standard Software Development cycle:

  • problem specication,
  • solution generation,
  • solution testing, and...
  • solution implementation.

Module Activities:

  1. Instructor introduces the case based on the abstract and timeline found at www.computingcases.org^3
  2. Students read case abstract, timeline, case decision point, and case analysis exercises.
  3. Students do further research into the case by consulting ComputingCases materials which include narratives, histories, supporting documents, and ethical analyses.
  4. Students carry out the activities outlined in the accompanying case exercises by (a) specifying the problem raised in the decision point, (b) generating solutions, (c) testing solutions using ethics tests, and (d) developing plans for implementing the solution over situational constraints.
  5. Students prepare their case analyses working in small groups.
  6. These groups present their completed analysis to the class in a case-debrieng session.
  7. The instructor concludes by discussing the problem-solving issues and intermediate moral concepts raised by the case. Machado Abstract: In September of 1996, 19 year-old Richard Machado sent email to 59 Asian students at his public college, threatening them with phrases like I will personally make it my life's career to hunt you down and kill you and signed by Asian Hater. Several of these individuals reported this incident to the Oce of Academic computing (OAC). One of the recipients was a student employee of the OAC. The administrators of the OAC were faced with a decision about how to respond to harassing and threatening email sent over their system to students of their University, using their facilities. Machado Timeline

11/16/95 Machado sends email threat to New University pa- per (UCI) via his roommate's computer.The email is traced to the roommate's computer.Roommate later said Machado had access to the computerMa- chado identied as sender. continued on next page

(^2) http://www.computingcases.org/ (^3) http://www.computingcases.org/

11/14/96 A stolen vehicle report is led for Machado's sec- ond roommate's car.Machado had told one room- mate he was borrowing his other roommate's car.Machado did not have permission to borrow car.

11/18/96 FBI attempts investigation.An agent goes to Machado's residence; Machado is not there and hasn't been seen there since 11/13.Machado al- legedly left with Young's keys on 11/14.Other sus- picions: $80 missing from roommate's coin jar; $ visa charges to roommate's card, $54 of which were unauthorized; calls on 11/10, 11, and 12.

11/21/96 FBI agent phones Machado's roommate for conr- mation of stolen car/info on Machado's disappear- ance.

11/22/96 Roommate interviewed.

11/23/96 Tammy Machado (Machado's sister) interviewed and said Machado had disappeared on the day his brother called him to inquire about Machado's name appearing in newspaper regarding Asian hate mails.Machado denied the reports in the paper to his brother; claimed it to be someone else.Tammy is informed that court date is set for 11/25 and if Richard doesn't show, they would issue a warrant for his arrest.

2/6/97 Machado is arrested when attempting to enter US from Mexicocaught by US Immigration Inspec- tor.Machado is reported as looking homeless, hav- ing no possessions, looking for construction work in Mexico.

9/16/97 Machado is charged with 10 counts of interfering with a federally protected activityin this case, students attending a university.Machado is told he will face up to 10 years if convicted.

11/12/97 Trial takes place and on this date a re- cess is granted when new information is un- covered/presented.Questionnaires were revealed in which 9 of the students who got the messages said they were not overtly bothered by Machado's email. continued on next page

11/18/97 Jury deadlocked 9 to 3 in favor of acquittal.Case said to have national importance by federal prose- cutors, so a second trial was set for 1/27/98. 2/13/98 Richard Machado is found guilty on 2 counts of civil rights violations.Took only 3 weeks of trial to reach verdict.Following conviction, Machado is released on a $10,000 bond from custody but is turned over to Irvine police on impending auto theft charges.Sentencing is postponed until 4/10/98.Pos- sible maximum time Machado could serve would be 1 yr.Machado has already spent 1 yr. in jail await- ing trials, tec.Machado is recommended for anger & racial tolerance counseling, not allowed on UCI campus, and prohibited from having any contact with victims.

Table 1

Scenario #1: You are a systems administrator at the Oce of Academic Computing at the University of California at Irvine and have been asked to modify the Unix system to prevent the reoccurrence of the Machado incident Scenario #2: You are a systems administrator at the Oce of Academic Computing at the University of California at Irvine and have been asked to develop an orientation program for students who will use university computing laboratories and facilities. Special emphasis is put on preventing a reoccurrence of the Machado incident.

  1. Identify key components of the STS

Part/Level of Analy- sis

Hardware Software Physical Surround- ings

People, Groups, & Roles

Procedures Laws & Regula- tions

Data & Data Structures

Table 2

  1. Specify the problem: 2a. Is the problem a disagreement on facts? What are the facts? What are cost and time constraints on uncovering and communicating these facts? 2b. Is the problem a disagreement on a critical concept? What is the concept? Can agreement be reached by consulting legal or regulatory information on the concept? (For example, if the concept in question is safety, can disputants consult engineering codes, legal precedents, or ethical literature that helps provide consensus? Can disputants agree on positive and negative paradigm cases so the concept disagreement can be resolved through line-drawing methods? 2c. Use the table to identify and locate value conicts within the STS. Can the problem be specied as a mismatch between a technology and the existing STS, a mismatch within the STS exacerbated by the introduction of the technology, or by overlooked results?

Time Cost Individual Organization Legal/ So- cial

Available Techno- logy

Manufacturability

Table 6