Richard G. Epstein, Westchester University of Pennsylvania
Mike Melamed, CWRU 2000
The Case of the Killer Robot is a detailed scenario that combines elements of software engineering and computer ethics.
The scenario consists of fictitious articles that touch on specific issues in software engineering and computer ethics. The articles discuss programs such as programmer psychology, team dynamics, user interfaces, software process models, software testing, the nature of requirements, software theft, and privacy. A major consideration is "when is the software good enough?"
The articles in the scenario begin with the indictment for manslaughter of a programmer who wrote faulty code that caused the death of a robot operator. Slowly, over the course of many articles, students are introduced to factors within the software company that also contributed to the accident. They are shown software development as a social process. It is hoped that students will begin to realize the complexity of the task of building real-world software and to see some of the ethical issues intertwined in that complexity.
This scenario is about 70 pages long and includes some tongue-in-cheek humor.
For permission see author information.
The Sentinel-Observer learned today that Randy Samuels and others who worked on the "killer robot" project at Silicon Techtronics Inc. were under tremendous pressure to finish the robot software by January 1 of this year. According to an informed source, top level management warned killer robot project staff that "heads would roll" if the January 1 deadline was not met.
Randy Samuels, a Silicon Techtronics programmer, was indicted last week on charges of manslaughter in the now famous killer robot case. Samuels wrote the flawed software that caused a Silicon Techtronics Robbie CX30 industrial robot to crush and fatally injure its operator, Bart Matthews. Matthews was a robot operator at Cybernetics Inc. According to Silicon Valley Prosecuting Attorney Jane McMurdock, Samuels misinterpreted a mathematical formula, "turning harmless Robbie into a savage killer."
Our informed source, who wishes to remain anonymous, called "Martha" for the rest of this article, has intimate knowledge of all aspects of the Robbie CX30 project. In an exclusive interview, Martha told the Sentinel-Observer that there was an enormous amount of friction between robotics division chief Ray Johnson and the Robbie CX30 project manager Sam Reynolds.
"They hated each other's guts," Martha said. "By June of last year the robot project had fallen six months behind schedule, and Johnson went through the roof. There were rumors that the entire robotics division, which he headed, would be terminated if Robbie (the CX30 robot) didn't prove a commercial success. He called Sam (Reynolds) into his office, and he really chewed Sam out. I mean, you could hear the yelling all the way down the hall. Johnson told Sam to finish Robbie by the first of January or heads would roll."
"I'm not saying that Johnson was ordering Sam to cut corners," Martha added. "I think the idea of cutting corners was implicit. The message was, cut corners if you want to keep your job."
According to documents provided by Martha, twenty new programmers were added to the Robbie CX30 project on June 12 of last year. This was just several days after the stormy meeting between Johnson and Reynolds.
Martha reported the new hires were a disaster: "Johnson unilaterally arranged for these new hires, presumably by shifting resources from other aspects of the Robbie project. Reynolds was vehemently opposed to this. Johnson only knew about manufacturing hardware. That was his background. He couldn't understand the difficulties that we were having with the robotics software. You can't speed up a software project by adding more people. It's not like an assembly line."
According to Martha and other sources inside the project, the hiring of the twenty new programmers led to a staff meeting attended by Johnson, Reynolds, and all members of the Robbie CX30 software project. At this meeting, it was Reynolds who was upset. He complained that the project did not need more people, and he argued that the main problem was that Johnson and others in Silicon Techtronics management did not understand that the Robbie CX30 was fundamentally different from earlier versions of the robot. These sources told the Sentinel-Observer that the new programmers were not fully integrated into the project even six months later, when ten Robbie CX30 robots, including the robot that killed Bart Matthews, were shipped out.
Martha explained, "Sam just wanted to keep things as simple as possible. He didn't want the new people to complicate matters. They spent six months reading manuals. Most of the new hirees didn't know diddly about robots and Sam wasn't about to waste his time trying to teach them."
Martha said the June 12 meeting has become famous in Silicon Techtronics corporate lore because it was at that meeting that Ray Johnson announced his "Ivory Snow Theory" of software design and development. She recounted, "Ray gave us a big multimedia presentation, with slides and everything. The gist of his Ivory Snow Theory is simply that Ivory Snow is 99 and 44/100 percent pure and there was no reason why robotics software had to be any purer than that. He stated repeatedly that 'Perfect software is an oxymoron.'"
Martha and the other insiders who came forward with information consistently portrayed Johnson as a manager in desperate need of a successful project. Earlier versions of Robbie, the CX10 and the CX20, were experimental in nature, and no one had expected them to be commercial successes. In fact, the robotics division of Silicon Techtronics has operated heavily in the red since its inception six years ago. If the CX30 did not succeed, Silicon Techtronics was going to drop out of the industrial robotics business altogether.
"The earlier Robbie robots got a lot of press, especially here in Silicon Valley," said another source, who also wishes to remain anonymous. "Robbie CX30 was going to capitalize on the good publicity generated by the earlier projects. The only thing was that Robbie CX30 was more revolutionary than Johnson wanted to admit. CX30 represented a gigantic step forward in terms of sophistication. There were a lot of questions about the industrial settings that the CX30 would be working in. Much of what we had to do was entirely new, but Johnson couldn't bring himself to understand that. He just saw us as unyielding perfectionists. One of his favorite quotes was 'Perfection is the enemy of the good.'"
The site is updating and expanding and is currently in beta form. We encourage you to browse and see all that the Online Ethics Center has to offer. We are actively working to improve your experience on the site and hope you find what you are looking for.
We would be delighted to hear your thoughts on the site reorganization, and if you need help finding a specific resource, please contact us via email at firstname.lastname@example.org.