IEEE Software, Volume 18, 2001

Volume 18, Number 1, January/February 2001

Usability Engineering

• 
  Natalia Juristo Juzgado, Helmut Windl, Larry L. Constantine:
  Guest Editors' Introduction: Introducing Usability. 20-21
• 
  Xavier Ferré, Natalia Juristo Juzgado, Helmut Windl, Larry L. Constantine:
  Usability Basics for Software Developers. 22-29
• 
  George M. Donahue:
  Usability and the Bottom Line. 31-37
• 
  Karla Radle, Sarah Young:
  Partnering with Development: How Three Organizations Succeeded. 38-45
• 
  Jean Anderson, Francie Fleek, Kathi Garrity, Fred Drake:
  Integrating Usability Techniques into Software Development. 46-53
• 
  Shirley A. Becker, Florence E. Mottay:
  A Global Perspective on Web Site Usability. 54-61
• 
  Molly Hammar Cloyd:
  Designing User-Centered Web Applications in Web Time. 62-69
• 
  Marc Hassenzahl, Andreas Beu, Michael Burmester:
  Engineering Joy. 70-76

Features

• 
  Yuri Chernak:
  Validating and Improving Test-Case Effectiveness. 81-86
• 
  Eduardo Miranda:
  Improving Subjective Estimates Using Paired Comparisons. 87-91
• 
  John Mylopoulos, Lawrence Chung, Stephen Shaoyi Liao, Huaiqing Wang, Eric S. K. Yu:
  Exploring Alternatives during Requirements Analysis. 92-96

Departments

• 
  Steve McConnell:
  From the Editor - Roundtable: Who Needs Software Engineering? 5-8
• 
  Introducing the Boards - IEEE Software Editorial Board and Industry Advisory Board Members. 9-12
• 
  Letters. 13-15
• 
  Emanuel R. Baker:
  Manager - Which Way, SQA? 16-18
• 
  Deependra Moitra:
  Country Report - India's Software Industry. 77-80
• 
  Martin Fowler:
  Design - Avoiding Repetition. 97-99
• 
  Kalpana Mohan:
  In the News - The International Software Connection, Peer-to-Peer Computing. 100-103
• 
  Melody M. Moore:
  From Your Technical Council - TCSE: Incubator of Software Engineering Programs. 104
• 
  Christof Ebert:
  Bookshelf - Software Product-Line Engineering, Design Patterns for the Enterprise. 105-107
• 
  Reviewer Thanks. 108-110
• 
  Hugh Robinson:
  Loyal Opposition - Reflecting on Research and Practice. 112-111

Volume 18, Number 2, March/April 2001

Global Software Development

• 
  James D. Herbsleb, Deependra Moitra:
  Guest Editors' Introduction: Global Software Development. 16-20
• 
  Erran Carmel, Ritu Agarwal:
  Tactical Approaches for Alleviating Distance in Global Software Development. 22-29
• 
  Audris Mockus, David M. Weiss:
  Globalization by Chunking: A Quantitative Approach. 30-37
• 
  Alexander Repenning, Andri Ioannidou, Michele Payton, Wenming Ye, Jeremy Roschelle:
  Using Components for Rapid Distributed Software Development. 38-45
• 
  Jesús Favela, Feniosky Peña-Mora:
  An Experience in Collaborative Software Engineering Education. 47-53
• 
  Richard Heeks, Srinivas Krishna, Brian Nicholson, Sundeep Sahay:
  Synching or Sinking: Global Software Outsourcing Relationships. 54-60
• 
  Christof Ebert, Philip De Neve:
  Surviving Global Software Development. 62-69
• 
  Robert D. Battin, Ron Crocker, Joe Kreidler, K. Subramanian:
  Leveraging Resources in Global Software Development. 70-77
• 
  Werner Kobitzsch, H. Dieter Rombach, Raimund L. Feldmann:
  Outsourcing in India. 78-86

Feature

• 
  Huaiqing Wang, Chen Wang:
  Open Source Software Adoption: A Status Report. 90-95

Departments

• 
  Letters. 6-8
• 
  Steve McConnell:
  From the Editor - Art, Science, and Engineering. 9-11
• 
  Donald J. Reifer:
  Manager - Software Management's Seven Deadly Sins. 12-15
• 
  Robert Cochran:
  Country Report - Ireland: A Software Success Story. 87-89
• 
  Martin Fowler:
  Design - Separating User Interface Code. 96-97
• 
  Keith W. Miller:
  Quality Time - A Modest Proposal for Software Testing. 100-101
• 
  Bookshelf - The Limits of Software: People, Projects, and Perspectives. 102
• 
  Greg Goth:
  In the News - The Open Market Woos Open Source. 104-109
• 
  Tex Curtis:
  Loyal Opposition - So You Wanna Be a Cowboy. 0-3

Volume 18, Number 3, May/June 2001

Organizational Change

• 
  Ann Miller:
  Guest Editor's Introduction: Organizational Change. 18-20
• 
  Michael Deck:
  Managing Process Diversity While Improving Your Practices. 21-27
• 
  Marina Blanco, Pedro Gutiérrez, Giuseppe Satriani:
  SPI Patterns: Learning from Experience. 28-35
• 
  Ramkumar Ramaswamy:
  Mentoring Object-Oriented Projects. 36-40
• 
  Stan Rifkin:
  What Makes Measuring Software So Hard? 41-45
• 
  Barry W. Boehm, Paul Grünbacher, Robert O. Briggs:
  Developing Groupware for Requirements Negotiation: Lessons Learned. 46-55
• 
  Ann Miller, Eric Schmidt, Mary E. Boone:
  Two Interviews, Two Perspectives. 56-59

Features

• 
  Michiel van Genuchten, Cor van Dijk, Henk Scholten, Douglas R. Vogel:
  Using Group Support Systems for Software Inspections. 60-65
• 
  Drasko M. Sotirovski:
  Heuristics for Iterative Software Development. 66-73
• 
  Csaba J. Egyhazy, Scott Eyestone, Janet Martino:
  Defining Team Processes Using OO Metaphors. 74-83
• 
  James A. Whittaker:
  Software's Invisible Users. 84-88

Departments

• 
  Steve McConnell:
  From the Editor - An Ounce of Prevention.
• 
  Letters. 8-13
• 
  John Cosgrove:
  Manager - Software Engineering and the Law. 14-16
• 
  Craig Larman:
  Design - Protected Variation: The Importance of Being Closed. 89-91
• 
  Dehua Ju:
  Country Report - China's Budding Software Industry. 92-95
• 
  Jeffrey M. Voas:
  Quality Time - Faster, Better, and Cheaper. 96-97
• 
  Melody M. Moore:
  From Your Technical Council - Focus on Software Reliability Engineering. 98
• 
  In the News - New Center Will Help Software Development "Grow Up". 99-103
• 
  Bookshelf - Testing Computer Software, Second Edition, CORBA 3 Fundamentals and Programming, Second Edition. 104-106
• 
  Robert L. Glass:
  Loyal Opposition - Frequently Forgotten Fundamental Facts about Software Engineering. 112-111

Volume 18, Number 4, July/August 2001

Article Summaries

• 
  Article Summaries. 4

From the Editor

• 
  Steve McConnell:
  Common Sense. 5-7

Letters

• 
  Letters. 8-11

Requirements

• 
  Suzanne Robertson:
  Are We Afraid of the Dark? 12-15

Quality Time

• 
  Jeffrey M. Voas:
  Composing Software Component "ilities". 16-17

Fault Tolerance

• 
  Jeffrey M. Voas:
  Guest Editor's Introduction: Software Fault Tolerance-Making Software Behave. 18-19
• 
  Lui Sha:
  Using Simplicity to Control Complexity. 20-28
• 
  Karama Kanoun:
  Real-World Design Diversity: A Case Study on Cost. 29-33
• 
  Les Hatton:
  Exploring the Role of Diagnosis in Software Engineering. 34-39
• 
  Michel Raynal, Mukesh Singhal:
  Mastering Agreement Problems in Distributed Systems. 40-47
• 
  William Yurcik, David Doss:
  Achieving Fault-Tolerant Software with Rejuvenation and Reconfiguration. 48-52

Round Table

• 
  Jeffrey M. Voas:
  Fault Tolerance. 54-57

Feature

• 
  Hubert F. Hofmann, Franz Lehner:
  Requirements Engineering as a Success Factor in Software Projects. 58-66
• 
  Søren Lauesen, Morten Borup Harning:
  Virtual Windows: Linking User Tasks, Data Models, and Interface Design. 67-75
• 
  Jean-Marc Jézéquel, Daniel Deveaux, Yves Le Traon:
  Reliable Objects: Lightweight Testing for OO Languages. 76-83
• 
  Linda Upchurch, Gordon Rugg, Barbara A. Kitchenham:
  Using Card Sorts to Elicit Web Page Quality Attributes. 84-89

Interview

• 
  Ware Myers:
  Developers Need Some Slack. 90-92

Country Report

• 
  Manfred Broy, Susanne Hartkopf, Kirstin Kohler, H. Dieter Rombach:
  Germany: Combining Software and Application Competencies. 93-95

In the News

• 
  In the News. 96-99

Design

• 
  Martin Fowler:
  Reducing Coupling. 102-104

Manager

• 
  Jack Ferguson:
  Crouching Dragon, Hidden Software: Software in DOD Weapon Systems. 105-107

Bookshelf

• 
  Bookshelf. 108-109

Loyal Opposition

• 
  Stan Rifkin:
  Why Software Process Innovations Are Not Adopted. 110-112

Volume 18, Number 5, September/October 2001

Article Summaries

• 
  Article Summaries. 4

From the Editor

• 
  Steve McConnell:
  The Nine Deadly sins of Project Planning. 5-7

Letters

• 
  Letters. 8-9

Requirements

• 
  Neil A. M. Maiden, Alexis Gizikis:
  Where Do Requirements Come From? 10-12

Manager

• 
  Watts S. Humphrey:
  Engineers Will Tolerate a Lot of Abuse. 13-15

Benchmarking

• 
  David N. Card, David Zubrow:
  Benchmarking Software Organizations. 16-17
• 
  Charles R. Symons, John McGarry:
  Point/Counterpoint: Software Benchmarking: Serious Management Tool or a Joke? / When It Comes to Measuring Software, Every Project Is Unique. 18-21
• 
  Katrina Maxwell:
  Collecting Data for Comparability: Benchmarking Software Development Productivity. 22-25
• 
  Christopher J. Lokan, Terry Wright, Peter R. Hill, Michael Stringer:
  Organizational Benchmarking Using the ISBSG Data Repository. 26-32
• 
  James T. Heires:
  What I Did Last Summer: A Software Development Benchmarking Case Study. 33-39
• 
  Sam Fogle, Carol Loulis, Bill Neuendorf:
  The Benchmarking Process: One Team's Experience. 40-47
• 
  Gareth C. Thomas, Howard R. Smith:
  Using Structured Benchmarking to Fast-Track CMM Process Improvement. 48-52
• 
  Greg Goth:
  NSDIR: A Legacy beyond Failure-Early Benchmarking Effort Was Ahead of Its Time. 53-56

Feature

• 
  Brian Witten, Carl E. Landwehr, Michael A. Caloyannides:
  Does Open Source Improve System Security? 57-61
• 
  Adam L. Buchsbaum, Yih-Farn Chen, Huale Huang, Eleftherios Koutsofios, John M. Mocenigo, Anne Rogers, Michael Jankowsky, Spiros Mancoridis:
  Visualizing and Analyzing Software Infrastructures. 62-70
• 
  Peter W. Fach:
  Design Reuse through Frameworks and Patterns. 71-76

Country Report

• 
  Tomoo Matsubara:
  Japan: A Huge IT Consumption Market. 77-80

In the News

• 
  In the News. 81-85

From Your Technical Council

• 
  Melody M. Moore:
  Software Reuse: Silver Bullet? 86

Design

• 
  Kent L. Beck:
  Aim, Fire. 87-89

Quality Time

• 
  Roger T. Alexander:
  Improving the Quality of Object-Oriented Programs. 90-91

Bookshelf

• 
  Bookshelf. 92-95

Loyal Opposition

• 
  Robert L. Glass:
  A Story about the Creativity Involved in Software Work. 96-97

Volume 18, Number 6, November/December 2001

Article Summaries

• 
  Article Summaries. 4

Letters

• 
  Letters. 6

From the Editor

• 
  Steve McConnell:
  Raising Your Software Consciousness. 7-9

Design

• 
  Martin Fowler:
  To Be Explicit. 10-15

Reports from the Field

• 
  Wolfgang Strigel:
  Guest Editor's Introduction: Reports from the Field-Using Extreme Programming and Other Experiences. 17-18
• 
  Mark C. Paulk:
  Extreme Programming from a CMM Perspective. 19-26
• 
  James Grenning:
  Launching Extreme Programming at a Process-Intensive Company. 27-33
• 
  Peter Schuh:
  Recovery, Redemption, and Extreme Programming. 34-41
• 
  Charles J. Poole, Jan Willem Huisman:
  Using Extreme Programming in a Maintenance Environment. 42-50
• 
  Lena Holmberg, Lars Mathiassen:
  Survival Patterns in Fast-Moving Software Organizations. 51-55
• 
  Lutz Prechelt:
  Accelerating Learning from Experience: Avoiding Defects Faster. 56-61

Requirements

• 
  Brian Lawrence, Karl E. Wiegers, Christof Ebert:
  The Top Risks of Requirements Engineering. 62-63

Quality Time

• 
  K. Suzanne Barber, Jim Holt:
  Software Architecture Correctness. 64-65

Manager

• 
  Linda Larson Kemp, Kenneth E. Nidiffer, Louis C. Rose, Robert Small, Michael Stankosky:
  Knowledge Management: Insights from the Trenches. 66-68

Features

• 
  Uttara Nerurkar:
  Web User Interface Design: Forgotten Lessons. 69-71
• 
  Tapani Kilpi:
  Implementing a Software Metrics Program at Nokia. 72-77
• 
  Ralf Lämmel, Chris Verhoef:
  Cracking the 500-Language Problem. 78-88
• 
  Girish Keshav Palshikar:
  Applying Formal Specifications to Real-World Software Development. 89-97

Country Report

• 
  The Russian Software Industry. 98-101

In the News

• 
  Andrey A. Terekhov:
  In the News. 102-105

Loyal Opposition

• 
  Robert L. Glass:
  Extreme Programming: The Good, the Bad, and the Bottom Line. 111-112