IEEE Software, Volume 20, 2003

Volume 20, Number 1, January/February 2003

• Warren Harrison:
  The Software Developer as Movie Icon. 5-7
  

• Asking the Right Questions. 8-9
  

• Andy Hunt, Dave Thomas:
  The Art of Enbugging. 10-11
  

• Martin Fowler:
  When to Make a Type. 12-13
  

• Eric Dubois, Klaus Pohl:
  Guest Editors' Introduction: RE 02--A Major Step toward a Mature Requirements Engineering Community. 14-15
  
• Matthias Weber, Joachim Weisbrod:
  Requirements Engineering in Automotive Development: Experiences and Challenges. 16-24
  
• Stewart A. Higgins, Maurice de Laat, Paul M. C. Gieles, Emilienne M. Geurts:
  Managing Requirements for Medical IT Products. 26-33
  
• Xavier Franch, Juan Pablo Carvallo:
  Using Quality Models in Software Package Selection. 34-41
  

• Alan H. Karp, Rajiv Gupta, Guillermo Juan Rozas, Arindam Banerji:
  Using Split Capabilities for Access Control. 42-49
  
• Bill R. Brykczynski, Robert A. Small:
  Reducing Internet-Based Intrusions: Effective Security Patch Management. 50-57
  
• Ian F. Alexander:
  Misuse Cases: Use Cases with Hostile Intent. 58-66
  

• Michael H. Lutz, Phillip A. Laplante:
  C# and the .NET Framework: Ready for Real Time? 74-80
  
• Colin Atkinson, Thomas Kühne:
  Aspect-Oriented Development with Stratified Frameworks. 81-89
  

• Richard Turner:
  Seven Pitfalls to Avoid in the Hunt for Best Practices. 67-69
  

• Adam Stone, Danna Voth:
  Software Flaws: To Tell or Not to Tell? / Open Source in the US Government. 70-73
  

• Jane Huffman Hayes:
  Do You Like Piña Coladas? How Improved Communication Can Improve Software Quality. 90-92
  

• Robert D. Austin, Lee Devin:
  Beyond Requirements: Software Making as Art. 93-95
  

• Carol A. Long:
  Lost, but Making Good Use of Time? 96-99
  

• Robert L. Glass:
  Error-Free Software Remains Extremely Elusive. 103-104
  

• Article Summaries. 4
  
• Saluting Our 2002 Referees. 100-102
  

Volume 20, Number 2, March/April 2003

• Article Summaries. 4
  

• Warren Harrison:
  The Marriage of Research and Practice. 5-7
  

• Benchmarks Are a Tricky Thing. 8-11
  

• James E. Tomayko:
  Scientific Management Meets the Personal Software Process. 12-14
  

• Steve Berczuk:
  Pragmatic Software Configuration Management. 15-17
  

• Richard E. Fairley, Mary Jane Willshire:
  Why the Vasa Sank: 10 Problems and Some Antidotes for Software Projects. 18-25
  
• Martin E. Nordberg III:
  Managing Code Ownership. 26-33
  
• Ali H. Dogru, Murat M. Tanik:
  A Process Model for Component-Oriented Software Engineering. 34-41
  
• Mala Murugappan, Gargi Keeni:
  Blending CMM and Six Sigma to Meet Business Goals. 42-48
  

• Søren Lauesen:
  Task Descriptions as Functional Requirements. 58-65
  
• Jun Liu, Khiang Wee Lim, Weng Khuen Ho, Kay Chen Tan, Rajagopalan Srinivasan, Arthur Tay:
  The Intelligent Alarm Management System. 66-71
  
• Anna Liu, Ian Gorton:
  Accelerating COTS Middleware Acquisition: The i-Mate Process. 72-79
  

• Nancy S. Eickelmann, Animesh Anant:
  Statistical Process Control: What You Don't Measure Can Hurt You! 49-51
  

• Ellen Gottesdiener:
  Requirements by Collaboration: Getting It Right the First Time. 52-55
  

• Martin Fowler:
  Patterns. 56-57
  

• Terry Bollinger:
  Facts and Fantasies: A Review of Two Books. 80-85
  

• Laurianne McLaughlin:
  After ElcomSoft: DMCA Still Worries Developers, Researchers. 86-91
  

• Diomidis Spinellis:
  On the Declarative Specification of Models. 94-96
  

Volume 20, Number 3, May/June 2003

• Warren Harrison:
  Is Software Engineering as We Know It over the Hill? 5-7
  

• Letters. 8-13
  

• Donald J. Reifer:
  XP and the CMM. 14-15
  

• Laurie A. Williams:
  Guest Editor's Introduction: The XP Programmer--The Few-Minutes Programmer. 16-20
  
• Jonathan Rasmusson:
  Introducing XP into Greenfield Projects: Lessons Learned. 21-28
  
• William A. Wood, William L. Kleb:
  Exploring XP for Scientific Research. 30-36
  
• Orlando Murru, Roberto Deias, Giampiero Mugheddu:
  Assessing XP at a European Internet Company. 37-43
  
• Annie I. Antón, Don Wells:
  Point/Counterpoint: Don't Solve a Problem Before You Get to It / Successful Software Projects Need Requirements Planning. 44-47
  

• Jeffrey M. Voas:
  Guest Editor's Introduction: Assuring Software Quality Assurance. 48-49
  
• Alice Leslie Jacob, S. K. Pillai:
  Statistical Process Control to Improve Coding and Code Review. 50-55
  
• Jorge Rady de Almeida Jr., João Batista Camargo Jr., Bruno Abrantes Basseto, Sérgio Miranda Paz:
  Best Practices in Code Inspection for Safety-Critical Software. 56-63
  
• Vaughn T. Rokosz:
  Long-Term Testing in a Short-Term World. 64-67
  
• Jim Lawler, Barbara Kitchenham:
  Measurement Modeling Technology. 68-75
  
• Sherif M. Yacoub:
  Automated QA for Document Understanding Systems. 76-82
  

• James J. Cusick:
  How the Work of Software Professionals Changes Everything. 92-97
  
• Omar Alonso:
  Generating Text Search Applications for Databases. 98-105
  

• Rebecca Parsons:
  Components and the World of Chaos. 83-85
  

• Richard Salit:
  Requirements Are Corporate Assets. 86-88
  

• John A. Stark, Ron Crocker:
  Trends in Software Process: The PSP and Agile Methods. 89-91
  

• Andy Hunt, Dave Thomas:
  The Trip-Packing Dilemma. 106-107
  

• John Dance:
  Extreme Reading. 108-111
  

• Melody M. Moore:
  A License to Practice Software Engineering. 112-113
  

• Laurianne McLaughlin, Joan Hong, Terry Costlow, Dale Strok:
  An Eye on India: Outsourcing Debate Continues / ISO Approves Cosmic-FFP / Web Developers Continue to Focus on Interoperability / Polish Team Wins ACM Contest. 114-118
  

• Robert L. Glass:
  Questioning the Software Engineering Unquestionables. 119-120
  

• Richard H. Thayer:
  Software Engineering Glossary.
  

• Article Summaries. 4
  

Volume 20, Number 4, July/August 2003

• Article Summaries. 4
  

• Warren Harrison:
  Whose Information Is It Anyway? 5-7
  

• Letters. 8-11
  

• Donald J. Reifer, Frank Maurer, M. Hakan Erdogmus:
  Scaling Agile Methods. 12-14
  

• David Lorge Parnas, Mark Lawford:
  Guest Editors' Introduction: Inspection's Role in Software Quality Assurance. 16-20
  
• Alastair Dunsmore, Marc Roper, Murray Wood:
  Practical Code Inspection Techniques for Object-Oriented Systems: An Experimental Comparison. 21-29
  
• Thomas Thelin, Per Runeson, Claes Wohlin:
  Prioritized Use Cases as a Vehicle for Software Inspections. 30-33
  
• Jia Xu:
  Making Software Timing Properties Easier to Inspect and Verify. 34-41
  
• Paul Anderson, Thomas W. Reps, Tim Teitelbaum, Mark Zarins:
  Tool Support for Fine-Grained Software Inspection. 42-50
  

• Morgan Björkander, Cris Kobryn:
  Architecting Systems with UML 2.0. 57-61
  
• Paulo Pinheiro da Silva, Norman W. Paton:
  User Interface Modeling in UMLi. 62-69
  
• Bo Sanden:
  Entity-Life Modeling: Modeling a Thread Architecture on the Problem Environment. 70-78
  

• Luke Hohmann:
  The Difference between Marketecture and Tarchitecture. 51-53
  

• Alan M. Davis:
  System Phenotypes. 54-56
  

• Nancy S. Eickelmann:
  An Insider's View of CMM Level 5. 79-81
  

• Dave Thomas, Andy Hunt:
  Verbing the Noun. 82-83
  

• Bookshelf. 84-86, 95
  

• Ashton Applewhite, Dale Strok:
  Should Governments Go Open Source? / Face to Face with the Experts. 88-93
  

• Robert L. Glass:
  A Big Problem in Academic Software Engineering and a Potential Outside-the-Box Solution. 94-96
  

• Richard H. Thayer:
  Software Engineering Glossary.
  

Volume 20, Number 5, September/October 2003

• Call for Articles: Return on Investment in the Software Industry. 1
  
• Article Summaries. 4
  

• Warren Harrison:
  How IEEE Software Engineers Its Content. 5-7
  

• Finding a Job. 8-10
  

• Martin Fowler:
  Who Needs an Architect? 11-13
  

• Stephen J. Mellor, Anthony N. Clark, Takao Futagami:
  Guest Editors' Introduction: Model-Driven Development. 14-18
  
• Bran Selic:
  The Pragmatics of Model-Driven Development. 19-25
  
• Ed Seidewitz:
  What Models Mean. 26-32
  
• Conrad Bock:
  UML without Pictures. 33-35
  
• Colin Atkinson, Thomas Kühne:
  Model-Driven Development: A Metamodeling Foundation. 36-41
  
• Shane Sendall, Wojtek Kozaczynski:
  Model Transformation: The Heart and Soul of Model-Driven Software Development. 42-45
  
• Torben Weis, Andreas Ulbrich, Kurt Geihs:
  Model Metamorphosis. 46-51
  
• Robert B. France, Sudipto Ghosh, Eunjee Song, Dae-Kyoo Kim:
  A Metamodeling Approach to Pattern-Based Model Refactoring. 52-58
  
• Peter Denno, Michelle Potts Steves, Don Libes, Edward Barkmeyer:
  Model-Driven Integration Using Existing Models. 59-63
  
• Vinay Kulkarni, Sreedhar Reddy:
  Separation of Concerns in Model-Driven Development. 64-69
  
• Axel Uhl, Scott W. Ambler:
  Point/Counterpoint: Model Driven Architecture Is Ready for Prime Time / Agile Model Driven Development Is Good Enough. 70-73
  

• Gregg Rothermel, Sebastian G. Elbaum:
  Putting Your Best Tests Forward. 74-77
  

• Alan MacCormack, Chris F. Kemerer, Michael A. Cusumano, Bill Crandall:
  Trade-offs between Productivity and Quality in Selecting Software Development Practices. 78-85
  
• Ivan Aaen:
  Software Process Improvement: Blueprints versus Recipes. 86-93
  

• Donald J. Reifer, Victor R. Basili, Barry W. Boehm, Betsy Clark:
  Eight Lessons Learned during COTS-Based Systems Maintenance. 94-96
  

• Andy Hunt, Dave Thomas:
  Preparing the Raw Material. 97-98
  

• Tom DeMarco, Tim Lister:
  Risk Management during Requirements. 99-101
  

• Performance Solutions: A Practical Guide to Creating Responsive, Scalable Software / Quality Software Project Management. 102-103
  

• Laurianne McLaughlin, Terry Costlow:
  Buggy Software: Can New Liability Rules Help Quality? / Government Focuses on Software Integrity. 104-108
  

• Karl Reed:
  Good Enough Is Not Good Enough. 109
  

• Nicholas Zvegintzov:
  Do We Know Enough to Teach Software Engineering? 110-112
  

Volume 20, Number 6, November/December 2003

• Article Summaries. 4
  

• Warren Harrison:
  From the Editor: Our 20th Anniversary. 5-7
  

• Open Source Research Ethics. 8-11
  

• Adam Stone, Terry Costlow:
  In the News. 12-16
  

• Dave Thomas, Andy Hunt:
  Pipelines. 17-19
  

• Robert L. Glass:
  Guest Editor's Introduction: The State of the Practice of Software Engineering. 20-21
  
• Capers Jones:
  Variations in Software Development Practices . 22-27
  
• Michael A. Cusumano, Alan MacCormack, Chris F. Kemerer, Bill Crandall:
  Software Development Worldwide: The State of the Practice. 28-34
  
• Timothy Lethbridge, Janice Singer, Andrew Forward:
  How Software Engineers Use Documentation: The State of the Practice. 35-39
  
• Colin J. Neill, Phillip A. Laplante:
  Requirements Engineering: The State of the Practice. 40-45
  
• Marcus Ciolkowski, Oliver Laitenberger, Stefan Biffl:
  Software Reviews: The State of the Practice. 46-51
  
• Andreas Birk, Gerald Heller, Isabel John, Klaus Schmid, Thomas von der Maßen, Klaus Müller:
  Product Line Engineering: The State of the Practice. 52-60
  
• Bas Graaf, Marco Lormans, Hans Toetenel:
  Embedded Software Engineering: The State of the Practice. 61-69
  
• Richard Baskerville, Balasubramaniam Ramesh, Linda Levine, Jan Pries-Heje, Sandra Slaughter:
  Is Internet-Speed Software Development Different? 70-77
  
• Donald J. Reifer:
  Is the Software Engineering State of the Practice Getting Closer to the State of the Art? 78-83
  

• Mike Andrews:
  Signpost: Matching Program Behavior against Known Faults. 84-89
  

• Ramnivas Laddad, Roger T. Alexander:
  Aspect-Oriented Programming Will Improve Quality / Aspect-Oriented Programming: the Real Costs? 90-93
  

• Mohammad Rob:
  Project Failures in Small Companies. 94-95
  

• Martin Fowler:
  Data Access Routines. 96-98
  

• Ian M. Graham:
  The Compleat Requirements Analyste. 99-101
  

• Pete McBreen, Narain H. Gehani, David J. Agans:
  Software Craftsmanship / Bell Labs: Life in the Crown Jewel / Debugging. 108-111
  

• Elaine J. Weyuker:
  I Have My State, You Have Yours. 112