IEEE Software, Volume 15, 1998

Volume 15, Number 1, January/February 1998

• Edward Yourdon: A Tale of Two Futures. 23-29
• Robert L. Glass: In Praise of Practice. 30-31
• Grady Booch: Leaving Kansas. 32-35
• Michael Jackson: Will There Ever Be Software Engineering? 36-39
• M. M. Lehman: Software's Future: Managing Evolution. 40-44
• Stephen J. Andriole: Software: The Good, the Bad, and the Real. 45-47

• Patrick Naughton: Basic to Java: Assembling a Career (Interview). 14-17
• Michael J. Pont: Soapbox: Why Java is Dangerous. 20-22
• Robert L. Glass: Loyal Opposition: Is There Really a Software Crisis? 104-105

• Frank van Latum, Rini van Solingen, Markku Oivo, Barbara Hoisl, H. Dieter Rombach, Günther Ruhe: Adopting GQM-Based Measurement in an Industrial Environment. 78-86

• David N. Card: Learning from Our Mistakes with Defect Causal Analysis. 56-63
• Allan Baktoft Jakobsen: Bottom-up Process Improvement Tricks. 64-68
• Mark-Jason Dominus: Perl: Not Just for Web Programming. 69-74

• Kai Koskimies, Tarja Systä, Jyrki Tuomi, Tatu Männistö: Automated Support for Modeling OO Software. 87-94
• Mike Mannion, Barry Keepence, David Harper: Using Viewpoints to Define Domain Requirements. 95-102

• Al Davis: From The Editor: Recovering from Method Abuse. 4-8
• James Sanders: Software Synergies. 13
• Karen Mackey: Culture At Work: Beyond Dilbert - Creating Cultures that Work. 48-49
• Roger S. Pressman: Manager: Fear of Trying - The Plight of Rookie Project Managers. 50-51 , 54
• Joe Oates: Toolbox: Evaluating Data Warehouse Toolkits. 52-54
• Jarrett Rosenberg: Quality Time: Five Easy Steps to Systematic Data Handling. 75-77
• Steve McConnell: Best Practices: The Art, Science, and Engineering of Software Development. 118-120

Volume 15, Number 2, March/April 1998

• Article Summaries. 4
  

• Alan M. Davis:
  The Harmony in Rechoirments. 6-8
  

• Letters. 10-12, 14
  

• Jeffrey M. Voas:
  COTS Software: The Economical Choice? 16-19
  

• Dehua Ju:
  China's Budding Software Industry. 20-21
  

• Alan Kay: Inventing the Future. 22-24
  

• Daniel M. Berry, Brian Lawrence:
  Guest Editors' Introduction: Requirements Engineering. 26-29
  

• Carl Clavedetscher:
  Point: User Involvement Key to Success. 30, 32
  
• Brian Lawrence:
  Counterpoint: Designers Must Do the Modeling. 31, 33
  

• Klaus Weidenhaupt, Klaus Pohl, Matthias Jarke, Peter Haumer:
  Scenarios in System Development: Current Practice. 34-45
  
• Neil A. M. Maiden, Cornelius Ncube:
  Acquiring COTS Software Selection Requirements. 46-56
  

• Robert L. Glass:
  Reuse: What's Wrong with This Picture? 57-59
  

• Robert S. Clark:
  The Black Death: A Parallel of Perilous Projects. 60-61
  

• James Sanders:
  Opportunities Online: Fact or Fantasy? 62-64, 122
  

• Sarah Kuhn:
  The Software Design Studio: An Exploration. 65-71
  
• Dan O'Day:
  This Old House. 72-75
  

• Søren Lauesen:
  Real-Life Object-Oriented Systems. 76-83
  

• Jeffrey Kotula:
  Using Patterns To Create Component Documentation. 84-92
  

• Nicholas Zvegintzov:
  Frequently Begged Questions and How to Answer Them. 93-96
  

• Jeff Tian, Joe Palma:
  Analyzing and Improving Reliability: A Tree-Based Approach. 97-104
  
• Hee Beng Kuan Tan, Tok Wang Ling:
  Correct Program Slicing of Database Operations. 105-112
  

• Tsuneo Yamaura:
  Why Johnny Can't Test. 113-115
  

• In the News. 116-118
  

• Bookshelf. 120-122
  

• Products for Practitioners. 124-126
  

• Steve McConnell:
  Problem Programmers. 126-128
  

Volume 15, Number 3, May/June 1998

• Article Summaries. 4
  

• Alan M. Davis:
  More Words of Wisdom. 6-9
  

• Letters. 10-14
  

• Ellis Horowitz:
  Guest Editor's Introduction: Migrating Software to the World Wide Web. 18-21
  
• Maria Cobb, Harold Foley III, Ruth Wilson, Miyi Chung, Kevin Shaw:
  An OO Database Migrates to the Web. 22-30
  
• Serena Coetzee, Judith Bishop:
  A New Way to Query GISs on the Web. 31-40
  

• Interview with Ellen Ullman: Of Machines, Methods, and Madness. 42-45
  

• Les Hatton:
  Does OO Sync with How We Think? 46-54
  
• Richard Wiener:
  Watch Your Language! 55-56
  
• Vivekanand P. Kochikar:
  The Object-Powered Web. 57-62
  

• James E. Schultz:
  MANAGING A Y2K PROJECT-STARTING NOW. 63-71
  
• Tim Athey:
  Leadership Challenges for the Future. 72-77
  

• Samuel G. McLellan, Alvin W. Roesler, Joseph T. Tempest, Clay Spinuzzi:
  Building More Usable APIs. 78-86
  

• Shari Lawrence Pfleeger:
  The Nature of System Change. 87-90
  

• Anol Bhattacherjee, James H. Gerlach:
  Understanding and Managing OOT Adoption. 91-96
  

• Jean McLendon:
  Healing the Ailing Workplace. 97-99
  

• James Sanders:
  Y2K: Don't Play It Again, Sam. 100-102
  

• Robert L. Glass:
  Defining Quality Intuitively. 103-104, 107
  

• Tim Lister:
  Hallucinations at 37000 Feet. 105-107
  

• In the News. 108-110
  

• Products for Practitioners. 111-112
  

• Bookshelf. 115-118
  

• Steve McConnell:
  Feasibility Studies. 119-120
  

Volume 15, Number 4, July/August 1998

• Article Summaries. 4
  

• Alan M. Davis:
  Predictions and Farewells. 6-9
  

• Letters. 10-13
  

• Norman F. Schneidewind, Christof Ebert:
  Guest Editors' Introduction: Preserve or Redesign Legacy Systems? 14-17
  

• John C. Munson:
  Point: Software Lives Too Long. 18, 20
  
• Nicholas Zvegintzov:
  Counterpoint: Software Should Live Longer. 19, 21
  

• Jeffrey M. Voas:
  Maintaining Component-Based Systems. 22-27
  
• Spencer Rugaber, Jim White:
  Restoring a Legacy: Lessons Learned. 28-33
  
• Norman F. Schneidewind:
  How To Evaluate Legacy System Maintenance. 34-42
  

• Michele Jackman:
  Homeopathic Remedies for Team Toxicity. 43-45
  

• Barbara Kitchenham, Stephen G. Linkman:
  Validation, Verification, and Testing: Diversity Rules. 46-49
  

• Paolo Nesi:
  Managing OO Projects Better. 50-60
  
• Robin Baines:
  Across Disciplines: Risk, Design, Method, Process, and Tools. 61-64
  

• Roger R. Bate:
  Do Systems Engineering? Who, Me? 65-66
  

• Robert L. Glass:
  Maintenance: Less Is Not More. 67-68
  

• Søren Lauesen, Houman Younessi:
  Is Software Quality Visible in the Code? 69-73
  
• Ho-Won Jung:
  Optimizing Value and Cost in Requirements Analysis. 74-78
  

• In the News. 79-82
  

• Products for Practitioners. 83-85
  

• Bookshelf. 87-90
  

• Rob Thomsett:
  The Year 2000 Bug: A Forgotten Lesson. 91-93, 95
  

• Steve McConnell:
  Why You Should Use Routines...Routinely. 94-96
  

Volume 15, Number 5, September/October 1998

• Article Summaries. 4
  

• Letters. 6-9
  

• Karl E. Wiegers:
  Read My Lips: No New Models! 10-13
  

• Michael Jackson:
  Defining a Discipline of Description. 14-17
  

• Mark Weisz:
  Dilbert University. 18-22
  

• JoAn Ferguson, Sarah A. Sheard:
  Leveraging Your CMM Efforts for IEEE/EIA 12207. 23-28
  

• Bruce H. Barnes:
  Computer Security Research: A British Perspective. 30-33
  

• Wojtek Kozaczynski, Grady Booch:
  Guest Editors' Introduction: Component-Based Software Engineering. 34-36
  
• Alan W. Brown, Kurt C. Wallnau:
  The Current State of CBSE. 37-46
  
• Andrea Chávez, Catherine Tornabene, Gio Wiederhold:
  Software Component Licensing: A Primer. 47-53
  
• Elaine J. Weyuker:
  Testing Component-Based Software: A Cautionary Tale. 54-59
  
• Tom Digre:
  Business Object Component Architecture. 60-69
  
• Pamela Zave, Michael Jackson:
  A Component-Based Approach to Telecommunication Software. 70-78
  
• Israel Ben-Shaul, James W. Gish, William N. Robinson:
  An Integrated Network Component Architecture. 79-87
  

• James Sanders:
  Linux, Open Source, and Software's Future. 88-91
  

• Patricia L. Ferdinandi:
  Facilitating Communication. 92-96
  

• Rini van Solingen, Egon Berghout, Frank van Latum:
  Interrupts: Just a Minute Never Is. 97-103
  

• Roger S. Pressman, Ted G. Lewis, Ben Adida, Ellen Ullman, Tom DeMarco, Thomas Gilb, Brent C. Gorda, Watts S. Humphrey, Ray Johnson:
  Can Internet-Based Applications Be Engineered? 104-110
  

• Focus on Components. 111-112
  

• Bookshelf. 115-118
  

• In the News. 119-125
  

• Steve McConnell:
  Building the Community. 126-128
  

Volume 15, Number 6, November/December 1998

• Article Summaries. 4
  

• Letters. 6, 8-9
  

• Bill Curtis:
  Which Comes First, the Organization or Its Processes? 10-13
  

• Diomidis Spinellis:
  The Computer's New Clothes. 14-17
  

• Alan M. Davis:
  A Golden Thread in Software's Tapestry. 18-21
  

• Carl K. Chang, Maarten Boasson, Tomoo Matsubara:
  Guest Editors' Introduction: Setting the Standard. 22-25
  
• Michael Franz:
  The Java Virtual Machine: A Passing Fad? 26-29
  

• Tsuneo Yamaura:
  How to Design Practical Test Cases. 30-36
  

• James Coplien, Daniel Hoffman, David M. Weiss:
  Commonality and Variability in Software Engineering. 37-45
  

• Robert Oshana:
  Tailoring Cleanroom for Industrial Use. 46-55
  

• Mikio Aoyama:
  Web-Based Agile Software Development. 56-65
  

• Kathryn Bassin, Theresa Kratschmer, Padmanabhan Santhanam:
  Evaluating Software Development Objectively. 66-74
  

• Daniel Le Métayer, Valérie-Anne Nicolas, Olivier Ridoux:
  Exploring the Software Development Trilogy. 75-81
  

• Stephen J. Andriole:
  The Politics of Requirements Management. 82-84
  

• Philip M. Johnson, Anne M. Disney:
  The Personal Software Process: A Cautionary Case Study. 85-88
  

• Fred Hein:
  The Blame Game. 89-91
  

• Steve McConnell:
  Weighing In on Standards. 92-102
  

• Tom DeMarco, Tim Lister:
  Human Capital. 103-105
  

• Thanks to Our 1998 Referees. 105-106
  

• Keri Schreiner:
  In the News. 107-110
  

• Focus on Microsoft. 111-112
  

• Bookshelf. 124-126
  

• Steve McConnell:
  How To Read a Technical Article. 126-128