logging in or signing up The Killer Robot Lilly Download Post to : URL : Related Presentations : Share Add to Flag Embed Email Send to Blogs and Networks Add to Channel Uploaded from authorPOINTLite Insert YouTube videos in PowerPont slides with aS Desktop Copy embed code: (To copy code, click on the text box) Embed: URL: Thumbnail: WordPress Embed Customize Embed The presentation is successfully added In Your Favorites. Views: 1075 Category: Education License: All Rights Reserved Like it (0) Dislike it (0) Added: January 07, 2008 This Presentation is Public Favorites: 0 Presentation Description No description available. Comments Posting comment... Premium member Presentation Transcript The case of theKiller RobotbyRichard Epstein: The case of the Killer Robot by Richard Epstein As retold by Netiva Caftori NEIU Oct. 2004When software engineering and computer ethics collide: When software engineering and computer ethics collideThe news: The news A robot operator, Bart Matthews, was killed by his robot, Robbie CX30, while at work. A programmer, Randy Samuels, who wrote the faulty code was indicted for manslaughter. Silicon Techchronics is Randy’s employer.What really happened?: What really happened? The robot malfunctioned & crushed its operator to death Blood all over Decapitated head Num-lock key light not on Numeric key pad bloodyWho is at fault?: Who is at fault? The programmer who made a careless mistake? The designer? The robotics division? The company? The operator of the robot? The robot?Robbie CX 10 & 20 were experimental.: Robbie CX 10 & 20 were experimental. The robotics division chief, Johnson, put pressure on the project manager Reynolds to finish the project by January. Johnson hired 20 new programmers in June against Reynolds’ will, by shifting resources. Robbie CX 30 had to succeed. Johnson only knew manufacturing hardware. One cannot speed software coding by adding more programmers. Robbie CX 30 was a step ahead in sophistication. Johnson: Perfect software is an oxymoron. Programmer personality: Programmer personality Randy’s home page: freedom for programmers A hacker type Enormous stress Programmer was a prima donna: could not accept criticism or his own fallibility Helpful but arrogant Under pressure to finish project on timeA good programming team: A good programming team Needs to have a whole array of personalities types including: An interaction-oriented person Someone who keeps the peace and helps move things in a positive direction Task-oriented people, but not all A democratic team Egoless programming Team dynamics: Team dynamics The project was controversial from the beginning Jan Anderson, a programmer, was fired after she attacked project manager Reynolds on his decision to use the waterfall methodology versus the prototype methodology. Reynolds was replacing a dead project manager as a cost saving measure instead of hiring someone from outside the company. He never worked with robotics before.More explanations: More explanations The earlier Robbie models processed transactions. Robbie CX30 was to interact with its operator, therefore the interface cannot be designed as an afterthought. Thus, a prototyping model is preferable where the users can use a prototype robot while in the design stage.Software development life-cycleWater fall methodology: Software development life-cycle Water fall methodology Requirements Analysis Design Coding Testing Implementation Maintenance No standard practices Quality controlor quality assurance: Quality control or quality assurance Dynamic testing Static testing Unit testing: Black and white box testing Integration testing Prof Silber attested that test results were inconsistent with actual killer code test results When is the software good enough?: When is the software good enough? Errors can happen in any stage Design stage: 2 alternatives: Waterfall & prototyping Testing User interface The complexity of the task of building real-world software Enormous stress The company-Sili-Tech Two environments:: The company-Sili-Tech Two environments: Worker-friendly: Chip Creek facility. Prevent repetitive strain injuries. Special training for employees. Well designed workstations. Frequent breaks. Worker-unfriendly: Silicon Valley plant. Workers criticized for novelties. No exercises or training encouraged. RSI frequent More compensation claimsLaw suits: Law suits The wife of the murdered operator. The indicted programmer himself. More possible indictments. Why was Randy Samuels indicted?: Why was Randy Samuels indicted? Sili-Tech promised to deliver robots that would cause no bodily harm. So Randy was not legally responsible for the death of the robot operator. Waterson, the president of Sili-Tech has contributed large sums to the re-election of judge McMurdock, who indicted Randy. Functional requirements specify the behavior of the robot under exceptional conditions. Operator intervention may be needed. Exceptional conditions were not mentioned in training of operators. The characters: The characters Jane Cindy Prof Silber Prof Gritty BartE-mail was not secure at Sili-TechIt was found that:: E-mail was not secure at Sili-Tech It was found that: Cindy Yardley faked the test results of the Killer code Johnson told Cindy that the robot was safe and all will lose their jobs if the robot were not shipped on time Randy stole some of his software, but admitted he had bugs in his Killer codeEthical issues: Ethical issues Email privacy Professional ethics: delivering bug-free software Plagiarism-intellectual property Honor confidentiality ACM code of ethics Five ethical tests:by Kallman & Grillo: Five ethical tests: by Kallman & Grillo The mom test: would you tell your mother? The TV test: would you tell your story on national TV? The smell test: does it smell bad? The other person’s shoes test: would you like it if done to you? The market test: would your action make a good sale pitch? You do not have the permission to view this presentation. In order to view it, please contact the author of the presentation.
The Killer Robot Lilly Download Post to : URL : Related Presentations : Share Add to Flag Embed Email Send to Blogs and Networks Add to Channel Uploaded from authorPOINTLite Insert YouTube videos in PowerPont slides with aS Desktop Copy embed code: (To copy code, click on the text box) Embed: URL: Thumbnail: WordPress Embed Customize Embed The presentation is successfully added In Your Favorites. Views: 1075 Category: Education License: All Rights Reserved Like it (0) Dislike it (0) Added: January 07, 2008 This Presentation is Public Favorites: 0 Presentation Description No description available. Comments Posting comment... Premium member Presentation Transcript The case of theKiller RobotbyRichard Epstein: The case of the Killer Robot by Richard Epstein As retold by Netiva Caftori NEIU Oct. 2004When software engineering and computer ethics collide: When software engineering and computer ethics collideThe news: The news A robot operator, Bart Matthews, was killed by his robot, Robbie CX30, while at work. A programmer, Randy Samuels, who wrote the faulty code was indicted for manslaughter. Silicon Techchronics is Randy’s employer.What really happened?: What really happened? The robot malfunctioned & crushed its operator to death Blood all over Decapitated head Num-lock key light not on Numeric key pad bloodyWho is at fault?: Who is at fault? The programmer who made a careless mistake? The designer? The robotics division? The company? The operator of the robot? The robot?Robbie CX 10 & 20 were experimental.: Robbie CX 10 & 20 were experimental. The robotics division chief, Johnson, put pressure on the project manager Reynolds to finish the project by January. Johnson hired 20 new programmers in June against Reynolds’ will, by shifting resources. Robbie CX 30 had to succeed. Johnson only knew manufacturing hardware. One cannot speed software coding by adding more programmers. Robbie CX 30 was a step ahead in sophistication. Johnson: Perfect software is an oxymoron. Programmer personality: Programmer personality Randy’s home page: freedom for programmers A hacker type Enormous stress Programmer was a prima donna: could not accept criticism or his own fallibility Helpful but arrogant Under pressure to finish project on timeA good programming team: A good programming team Needs to have a whole array of personalities types including: An interaction-oriented person Someone who keeps the peace and helps move things in a positive direction Task-oriented people, but not all A democratic team Egoless programming Team dynamics: Team dynamics The project was controversial from the beginning Jan Anderson, a programmer, was fired after she attacked project manager Reynolds on his decision to use the waterfall methodology versus the prototype methodology. Reynolds was replacing a dead project manager as a cost saving measure instead of hiring someone from outside the company. He never worked with robotics before.More explanations: More explanations The earlier Robbie models processed transactions. Robbie CX30 was to interact with its operator, therefore the interface cannot be designed as an afterthought. Thus, a prototyping model is preferable where the users can use a prototype robot while in the design stage.Software development life-cycleWater fall methodology: Software development life-cycle Water fall methodology Requirements Analysis Design Coding Testing Implementation Maintenance No standard practices Quality controlor quality assurance: Quality control or quality assurance Dynamic testing Static testing Unit testing: Black and white box testing Integration testing Prof Silber attested that test results were inconsistent with actual killer code test results When is the software good enough?: When is the software good enough? Errors can happen in any stage Design stage: 2 alternatives: Waterfall & prototyping Testing User interface The complexity of the task of building real-world software Enormous stress The company-Sili-Tech Two environments:: The company-Sili-Tech Two environments: Worker-friendly: Chip Creek facility. Prevent repetitive strain injuries. Special training for employees. Well designed workstations. Frequent breaks. Worker-unfriendly: Silicon Valley plant. Workers criticized for novelties. No exercises or training encouraged. RSI frequent More compensation claimsLaw suits: Law suits The wife of the murdered operator. The indicted programmer himself. More possible indictments. Why was Randy Samuels indicted?: Why was Randy Samuels indicted? Sili-Tech promised to deliver robots that would cause no bodily harm. So Randy was not legally responsible for the death of the robot operator. Waterson, the president of Sili-Tech has contributed large sums to the re-election of judge McMurdock, who indicted Randy. Functional requirements specify the behavior of the robot under exceptional conditions. Operator intervention may be needed. Exceptional conditions were not mentioned in training of operators. The characters: The characters Jane Cindy Prof Silber Prof Gritty BartE-mail was not secure at Sili-TechIt was found that:: E-mail was not secure at Sili-Tech It was found that: Cindy Yardley faked the test results of the Killer code Johnson told Cindy that the robot was safe and all will lose their jobs if the robot were not shipped on time Randy stole some of his software, but admitted he had bugs in his Killer codeEthical issues: Ethical issues Email privacy Professional ethics: delivering bug-free software Plagiarism-intellectual property Honor confidentiality ACM code of ethics Five ethical tests:by Kallman & Grillo: Five ethical tests: by Kallman & Grillo The mom test: would you tell your mother? The TV test: would you tell your story on national TV? The smell test: does it smell bad? The other person’s shoes test: would you like it if done to you? The market test: would your action make a good sale pitch?