Details

FOREWORD (<i>Linda Rising</i>). <p>INTRODUCTION.</p> <p>I.1 What's the Dark Side?</p> <p>I.1.1 Why the Dark Side?</p> <p>I.1.2 Who Cares About the Dark Side?</p> <p>I.1.3 How Dark is the Dark Side?</p> <p>I.1.4 What Else is on the Dark Side?</p> <p>I.1.5 Ethics and the Dark Side.</p> <p>I.1.6 Personal Anecdotes About the Dark Side.</p> <p>Reference.</p> <p><b>PART 1: DARK SIDE ISSUES.</b></p> <p><b>CHAPTER 1 SUBVERSION.</b></p> <p>1.1 Introductory Case Studies and Anecdotes.</p> <p>1.1.1 A Faculty Feedback System.</p> <p>1.1.2 An Unusual Cooperative Effort.</p> <p>1.1.3 Lack of Cooperation due to Self Interest.</p> <p>1.1.4 An Evil Teammate.</p> <p>1.1.5 Thwarting the Evil Union.</p> <p>1.2 The Survey: Impact of Subversive Stakeholders On Software Projects.</p> <p>1.2.1 Introduction.</p> <p>1.2.2 The Survey.</p> <p>1.2.3 The Survey Findings.</p> <p>1.2.4 Conclusions.</p> <p>1.2.5 Impact on Practice.</p> <p>1.2.6 Impact on Research.</p> <p>1.2.7 Limitations.</p> <p>1.2.8 Challenges.</p> <p>1.2.9 Acknowledgments.</p> <p>1.3 Selected Responses.</p> <p>1.3.1 Sample Answers to the Question: "What Were the Motivations and Goals of the Subversive Stakeholders?"</p> <p>1.3.2 Sample Answers to the Question "How Were the Subversive Attacks Discovered?"</p> <p>1.3.3 Sample Answers to the Question "How Can Projects be Defended Against Subversive Stakeholders?"</p> <p>1.4 A Follow-Up to the Survey: Some Hypotheses and Related Survey Findings.</p> <p>References.</p> <p><b>CHAPTER 2 LYING.</b></p> <p>2.1 Introductory Case Studies and Anecdotes.</p> <p>2.2 Incidents of Lying: The Survey.</p> <p>2.2.1 The Survey Results.</p> <p>2.2.2 General Scope.</p> <p>2.2.3 An Overview of the Problem.</p> <p>2.2.4 Clarifi cation of Terms.</p> <p>2.2.5 Discussion.</p> <p>2.2.6 Conclusions.</p> <p>2.2.7 Limitations.</p> <p>2.3 Qualitative Survey Responses on Lying.</p> <p>2.4 What Can Be Done About Lying?</p> <p>2.5 The Questionnaire Used in the Survey.</p> <p>References.</p> <p><b>CHAPTER 3 HACKING.</b></p> <p>3.1 Case Studies of Attacks and Biographies of Hackers.</p> <p>3.2 Cyber Terrorism and Government-Sponsored Hacking.</p> <p>3.3 The Hacker Subculture.</p> <p>3.3.1 Why They Are Called "Hackers".</p> <p>3.3.2 Motivation of Hackers.</p> <p>3.3.3 Hacker Slang.</p> <p>3.3.4 Hacker Ethics.</p> <p>3.3.5 Public Opinion about Hackers.</p> <p>3.4 How a Hacker Is Identified.</p> <p>3.5 Time Line of a Typical Malware Attack.</p> <p>3.6 Hacker Economy: How Does a Hacker Make Money?</p> <p>3.7 Social Engineering.</p> <p>3.7.1 Social Engineering Examples and Case Studies.</p> <p>3.7.2 Tactics of Social Engineering.</p> <p>3.8 A Lingering Question.</p> <p>3.9 Late-Breaking News.</p> <p><b>CHAPTER 4 THEFT OF INFORMATION.</b></p> <p>4.1 Introduction.</p> <p>4.2 Case Studies.</p> <p>4.2.1 Data Theft.</p> <p>4.2.2 Source Code Theft.</p> <p>4.3 How Do the Victims Find Out That Their Secrets Are Stolen?</p> <p>4.4 Intellectual Property Protection.</p> <p>4.4.1 Trade Secret Protection.</p> <p>4.4.2 Copyright Protection.</p> <p>4.4.3 Patent Protection.</p> <p>4.4.4 Steganography.</p> <p>4.5 Open Versus Closed Source.</p> <p><b>CHAPTER 5 ESPIONAGE.</b></p> <p>5.1 Introduction.</p> <p>5.2 What Is Espionage?</p> <p>5.3 Case Studies.</p> <p>5.3.1 Sweden Versus Russia.</p> <p>5.3.2 Shekhar Verma.</p> <p>5.3.3 Lineage III.</p> <p>5.3.4 GM versus VW: Jose Ignacio Lopez.</p> <p>5.3.5 British Midland Tools.</p> <p>5.3.6 Solid Oak Software.</p> <p>5.3.7 Proctor & Gamble versus Unilever.</p> <p>5.3.8 News Corp Versus Vivendi.</p> <p>5.3.9 Spying: Was A TI Chip Really Stolen by a French Spy?</p> <p>5.3.10 Confi cker.</p> <p>5.4 Cyber Warfare.</p> <p>Reference.</p> <p><b>CHAPTER 6 DISGRUNTLED EMPLOYEES AND SABOTAGE.</b></p> <p>6.1 Introduction and Background.</p> <p>6.2 Disgruntled Employee Data Issues.</p> <p>6.2.1 Data Tampering.</p> <p>6.2.2 Data Destruction.</p> <p>6.2.3 Data Made Public.</p> <p>6.2.4 Theft Via Data.</p> <p>6.3 Disgruntled Employee Software Issues.</p> <p>6.3.1 Software Destruction.</p> <p>6.4 Disgruntled Employee System Issues.</p> <p>6.5 What to Do About Disgruntled Employee Acts.</p> <p>6.6 Sabotage.</p> <p>References.</p> <p><b>CHAPTER 7 WHISTLE-BLOWING.</b></p> <p>7.1 A Hypothetical Scenario.</p> <p>7.2 Whistle-Blowing and Software Engineering.</p> <p>7.3 More Case Studies and Anecdotes.</p> <p>7.3.1 Jeffrey Wigand and Brown and Williamson Tobacco.</p> <p>7.3.2 A Longitudinal Study of Whistle-Blowing.</p> <p>7.3.3 An Even More Pessimistic View.</p> <p>7.3.4 Academic Whistle-Blowing.</p> <p>7.3.5 The Sum Total of Whistle-Blowing.</p> <p>References.</p> <p><b>APPENDIX TO CHAPTER 7 PRACTICAL IMPLICATIONS OF THE RESEARCH INTO WHISTLE-BLOWING.</b></p> <p>References.</p> <p><b>PART 2: VIEWPOINTS ON DARK SIDE ISSUES.</b></p> <p>Introduction.</p> <p><b>CHAPTER 8 OPINIONS, PREDICTIONS, AND BELIEFS.</b></p> <p>8.1 Automated Crime (<i>Donn B. Parker</i>).</p> <p>Information Sources.</p> <p>8.2 Let's Play Make Believe (<i>Karl E. Wiegers</i>).</p> <p>Reference.</p> <p>8.3 Dark, Light, or Just Another Shade of Grey? (<i>Les Hatton</i>).</p> <p>8.4 Rational Software Developers as Pathological Code Hackers (<i>Norman Fenton</i>).</p> <p><b>CHAPTER 9 PERSONAL ANECDOTES.</b></p> <p>9.1 An Offi cer and a Gentleman Confronts the Dark Side (<i>Grady Booch</i>).</p> <p>9.2 Less Carrot and More Stick (<i>June Verner</i>).</p> <p>References.</p> <p>9.3 "Them and Us": Dispatches from the Virtual Software Team Trenches (<i>Valentine Casey</i>).</p> <p>9.4 What is it to Lie on a Software Project? (<i>Robert N. Britcher</i>).</p> <p>9.5 "Merciless Control Instrument" and the Mysterious Missing Fax (<i>A. H. (anonymous)</i>).</p> <p>9.6 Forest of Arden (<i>David Alan Grier</i>).</p> <p>9.7 Hard-Headed Hardware Hit Man (<i>Will Tracz</i>).</p> <p>9.8 A Lighthearted Anecdote (<i>Eugene Farmer</i>).</p> <p>CONCLUSIONS.</p> <p>INDEX.</p>

<b>Johann Rost</b> has worked in the software industry for twenty years. He has taught at the University of Applied Science at Bingen, Germany, and at Politehnica University at Bucharest, Romania. <p><b>Robert L. Glass</b> is the author of twenty-eight books on computing subjects, including the bestselling Facts and Fallacies of Software Engineering. He has written nearly one hundred articles on computing subjects and has served as a columnist for three leading publications—Communications of the ACM ("The Practical Programmer"), IEEE Software ("The Loyal Opposition"), and Information Systems Management ("Through a Glass, Darkly").</p>

<b>Betrayal! Corruption! Software Engineering?</b> <p>This is not a book about software project failure, or about prescriptive thinking about how to build software better. This is a book about the evil things that happen on computing and software projects—what the kinds of evil are, how they manifest themselves, and what the good guys can do about them.</p> <p>In this timely report on vice at every level of software project management, industry experts Johann Rost and Robert Glass explore the seamy underbelly of software engineering. Based on the authors' original research and augmented by frank insights from other well-respected figures, <i>The Dark Side of Software Engineering</i> consists of anecdotes about occurrences of the practices, an analysis of research findings in the context of the anecdotes, and some suggestions on what to do about the dark side. Discussions draw from the software and information technology literature and from the management literature specific to these topics.</p> <p>This is a book full of surprises—to be read by both software and computing practitioners and academics. It addresses seven "dark side matters" of software project work that involve dubious management and technologist practices, including:</p> <ul> <li> <p>Subversion</p> </li> <li> <p>Espionage</p> </li> <li> <p>Lying</p> </li> <li> <p>Disgruntled employees and sabotage</p> </li> <li> <p>Hacking</p> </li> <li> <p>Whistleblowing</p> </li> <li> <p>Theft of information</p> </li> </ul> <p>Written in a quick-reading journalistic style, <i>The Dark Side of Software Engineering</i> goes where other management studies fear to tread—a corporate environment where schedules are fabricated, trust is betrayed, millions of dollars are lost, and there is a serious need for the kind of corrective action that this book ultimately proposes.</p>

SG