IEEE Software, Volume 13, 1996

Volume 13, Number 1, January 1996

• Ted J. Biggerstaff:
  Moore's Law: Change or Die. 4-6
  

• Gregor Kiczales:
  Beyond the Black Box: Open Implementation. 8-11
  

• Barbara Kitchenham, Shari Lawrence Pfleeger:
  Software Quality: The Elusive Target. 12-21
  

• Norman F. Schneidewind, Norman E. Fenton:
  Point-Counterpoint: Do Standards Improve Quality? 22, 24
  
• Pamela Simmons:
  Quality Outcomes: Determining Business Value. 25-32
  
• R. Geoff Dromey:
  Cornering the Chimera. 33-43
  
• Ilkka Tervonen:
  Support for Quality-Based Design and Inspection. 44-54
  
• Jan Rooijmans, Hans Aerts, Michiel van Genuchten:
  Software Quality in Consumer Electronics Products. 55-64
  
• Taghi M. Khoshgoftaar, Edward B. Allen, Kalai Kalaichelvan, Nishith Goel:
  Early Quality Prediction: A Case Study in Telecommunications. 65-71
  

• Jacqueline M. Antis, Stephen G. Eick, John D. Pyrce:
  Visualizing the Structure of Large Relational Databases. 72-80
  
• David E. Ruddock, Balakrishnan Dasarathy:
  Multithreading Programs: Guidelines for DCE Applications. 80-90
  

• Jakob Nielsen:
  The Importance of Being Beautiful. 92-94
  

• Thomas Gilb:
  Level 6: Why We Can't Get There from Here. 97-98, 103
  

• Karl Dakin:
  Keys to Engineering a Workable Contract. 99-100
  

• Lorenzo Strigini:
  Limiting the Dangers of Intuitive Decision Making. 101-103
  

• Stephen Barlas, Michael J. Lutz, Shari Lawrence Pfleeger:
  In the News. 104-106, 108-112
  

• IEEE Software 1995 Referees. 113-115
  

• Bookshelf. 116-119
  

• David Sharon:
  Meeting the Challenge of Software Maintenance. 122-126
  

• Steve McConnell:
  Who Cares About Software Construction? 128-129
  

Volume 13, Number 2, March 1996

• Alan M. Davis:
  Eras of Software Technology Transfer. 4-7
  

• Praful V. Bhansali:
  Universal Safety Standard is Infeasible-for Now. 8-10
  

• Mark J. Christensen, Carl K. Chang:
  Blueprint for the Ideal Requirements Engineer. 12
  

• Jawed I. A. Siddiqi, M. Chandra Shekaran:
  Requirements Engineering: The Emerging Wisdom. 15-19
  

• Brian Lawrence, Daniel Jackson:
  Do You Really Need Formal Requirements/Requirements Need Form, Maybe Formality (Point-Counterpoint). 20, 22
  
• Barry W. Boehm, Hoh In:
  Identifying Quality-Requirement Conflicts. 25-35
  
• Hans W. Nissen, Manfred A. Jeusfeld, Matthias Jarke, Georg V. Zemanek, Harald Huber:
  Managing Multiple Requirements Perspectives with Metamodels. 37-48
  
• Francisco A. C. Pinheiro, Joseph A. Goguen:
  An Object-Oriented Tool for Tracing Requirements. 52-64
  

• Anthony Hall:
  Using Formal Methods to Develop an ATC Information System. 66-76
  
• Robert Tausworthe, Michael R. Lyu:
  A Generalized Technique for Simulating Software Reliability. 77-88
  
• Steve Jennhwa Yang:
  Debugging for Timing-Constraint Violations. 89-99
  

• Jakob Nielsen:
  The Impending Demise of the File System. 100-101
  

• Capers Jones:
  Our Worst Current Development Practices. 102-104
  

• Karl Dakin:
  Warranties: Promising the Improbable. 105-106
  

• Lawrence Bernstein:
  Better Software Through Operational Dynamics. 107-109
  

• Stephen Barlas, Robert N. Britcher, Maureen McSharry:
  In the News. 110-112, 114-115, 121
  

• Sorel Reisman:
  MacWorld: Lots of Light, Sound, and Audio-Little Strategy. 113-114
  

• Bookshelf. 116-119, 122-123
  

• Rick Shetterly, Alan Chmura:
  Creating the Paperless Office. 124-126
  

• Steve McConnell:
  Missing in Action: Information Hiding. 127-128
  

Volume 13, Number 3, May 1996

• Alan M. Davis:
  Practitioner, Heal Thyself. 4-5
  

• Defining Design Terminology. 8, 10, 12, 14, 16, 20
  

• John Palmer:
  Beware the Lure of Software Slogans. 18-20
  

• Annie Kuntzmann-Combelles:
  Can We Learn Lessons Better? 21
  

• Pei Hsia:
  Making Software Development Visible. 23-26
  

• Karen Mackey:
  Why Bad Things Happen to Good Projects. 27-32
  
• Blayne Maring:
  Object-Oriented Development of Large Applications. 33-40
  
• W. Stephen Adolph:
  Cash Cow in the Tar Pit: Reengineering a Legacy System. 41-47
  
• Peter Gorm Larsen, John S. Fitzgerald, T. M. Brookes:
  Applying Formal Specification in Industry. 48-56
  
• Randall R. Macala, Lynn D. Stuckey Jr., David C. Gross:
  Managing Domain-Specific, Product-Line Development. 57-67
  
• S. Wayne Sherer, Ara Kouchakdjian, Paul Arnold:
  Experience Using Cleanroom Software Engineering. 69-76
  

• Watts S. Humphrey:
  Using A Defined and Measured Personal Software Process. 77-88
  

• Jakob Nielsen:
  Putting the User in User-Interface Testing. 89-90
  

• Edward V. Berard:
  Bringing Testing Into the Fold. 91-92, 95
  

• John M. Favaro:
  When the Pursuit of Quality Destroys Value. 93-95
  

• Karl Dakin:
  The Transaction-Based Pricing Trend. 96-97
  

• In the News. 98-102, 105-106
  

• Sorel Reisman:
  Old-Timers and Upstarts Chime in with New Telephony Products. 103-104
  

• Bookshelf. 107-111
  

• Thomas J. McCabe:
  Cyclomatic Complexity and the Year 2000. 115-117
  

• Steve McConnell:
  How to Defend an Unpopular Schedule. 118, 120
  

Volume 13, Number 4, July 1996

• Alan M. Davis:
  It Feels Like Deja Vu All Over Again. 4
  

• Letters. 6-14
  

• Dwayne Phillips:
  Project Management: Filling in the Gaps. 17-18
  

• Karl Dakin:
  Are Developers Morally Challenged? 20-22
  

• Tom DeMarco, Ann Miller:
  Managing Large Software Projects. 24-27
  
• Walt Gillette:
  Managing Megaprojects: A Focused Approach. 28, 30
  
• Kouichi Kishida:
  Managing Megaprojects: A Free-Form Approach. 29-30
  
• Jean McLendon, Gerald M. Weinberg:
  Beyond Blaming: Congruence in Large Systems Development Projects. 33-42
  
• Tarek K. Abdel-Hamid:
  The Slippery Path to Productivity Improvement. 43-52
  
• Peter Conklin:
  Enrollment Management: Managing the Alpha AXP Program. 53-64
  
• Bonnie Collier, Tom DeMarco, Peter Fearey:
  A Defined Process For Project Postmortem Review. 65-72
  
• Barry W. Boehm:
  Anchoring the Software Process. 73-82
  
• Kathy V. C. Parris:
  Implementing Accountability. 83-93
  
• Norm Brown:
  Industrial-Strength Management Strategies. 94-103
  
• Jim Nielsen, Ann Miller:
  Selecting Software Subcontractors. 104-109
  
• Robert N. Charette:
  Large-Scale Project Management Is Risk Management. 110-117
  

• Shari Lawrence Pfleeger:
  Measuring Reuse: A Cautionary Tale. 118-127
  

• Jakob Nielsen:
  Going Global With User Testing. 129-130
  

• Filippo Lanubile:
  Why Software Reliability Predictions Fail. 131-132, 137
  

• Bookshelf. 133-137
  

• Karen Whitehouse:
  Naming Each Needle in the Haystack. 138
  
• Decision Making: The Key To Successful Project Managment. 139-140
  
• Sorel Reisman:
  Too Small, Too Hot-And Still Too Cool. 141-142
  

• Steve McConnell:
  Daily Build and Smoke Test. 143-144
  

Volume 13, Number 5, September 1996

• Alan M. Davis:
  What's Practical. 4-5
  

• Letters. 6-14
  

• Roger S. Pressman:
  Software Process Impediment. 16-17
  

• Jakob Nielsen:
  Designing to Seduce the User. 18-20
  

• Krishna M. Kavi, Ez Nahouraii:
  Guest Editors' Introduction: Software Tools Assessment. 23-26
  
• Tilmann F. W. Bruckhaus, Nazim H. Madhavji, Ingrid Janssen, John Henshaw:
  The Impact of Tools on Software Productivity. 29-38
  
• Alan W. Brown, Kurt C. Wallnau:
  A Framework for Evaluating Software Technology. 39-49
  
• David A. Grossman, M. Catherine McCabe, Christopher Staton, Bret Bailey, Ophir Frieder, David C. Roberts:
  Performance Testing a Large Finance Application. 50-54
  
• John P. Hudepohl, Stephen J. Aud, Taghi M. Khoshgoftaar, Edward B. Allen, Jean Mayrand:
  Emerald: Software Metrics and Models on the Desktop. 56-60
  
• Alan Chmura, David Sharon:
  Tools Fair: Untangling the Web with Web and Client/Server. 61-72
  

• Alberto Avritzer, Johannes P. Ros, Elaine J. Weyuker:
  Reliability Testing of Rule-Based Systems. 76-82
  
• David M. Cohen, Siddhartha R. Dalal, Jesse Parelius, Gardner C. Patton:
  The Combinatorial Design Approach to Automatic Test Generation. 83-88
  
• Joseph Fong:
  Adding a Relational Interface to a Nonrelational Database. 89-97
  

• Tom Adams:
  Bookshelf. 98-100, 102
  

• Karl Dakin:
  Legal Implications of Blown Schedules. 101-102
  

• In the News. 104-108
  

• Khaled El Emam, Nazim H. Madhavji:
  Does Organizational Maturity Improve Quality? 109-110
  

• Steve McConnell:
  Avoiding Classic Mistakes. 111-112
  

Volume 13, Number 6, November 1996

• Alan M. Davis:
  Art or Engineering, One More Time. 4-5
  

• Daily Build: Solution or Coping Mechanism? 6-10
  

• Jakob Nielsen:
  Usability Metrics: Tracking Interface Improvements. 12-13
  

• Roger S. Pressman:
  Software Process Perceptions. 16-18
  

• Anthony Finkelstein:
  Improving Public Understanding. 20-21
  

• Anthony I. Wasserman:
  Toward a Discipline of Software Engineering. 23-31
  
• Thomas J. Haley:
  Software Process Improvement At Raytheon. 33-41
  
• Kumiyo Nakakoji:
  Beyond Language Translation: Crossing the Cultural Divide. 42-46
  
• Rick Kazman, Gregory D. Abowd, Leonard J. Bass, Paul C. Clements:
  Scenario-Based Analysis of Software Architecture. 47-55
  
• Shawn A. Butler, David Diskin, Norman R. Howes, Kathleen Jordan:
  Architectural Design of a Common Operating Environment. 57-65
  
• Hans Albrecht Schmid:
  Creating Applications From Components: A Manufacturing Framework Design. 67-75
  
• Colin J. Fidge:
  Fundamentals of Distributed System Observation. 77-83
  

• Karl Dakin:
  Do We Need an Implied Warranty of Competence? 97-98
  

• Donna L. Johnson, Judith G. Brodman:
  Realities and Rewards of Software Process Improvement. 99-101
  

• In the News. 102-108
  

• Noah S. Prywes:
  Recovering Design and Specifications from Source Code. 109-111, 114-115
  

• Bookshelf. 116-123
  

• Thanks to Our 1996 Referees. 124-126
  

• Steve McConnell:
  Keep It Simple. 127-128