Volume 19, Number 1, January/February 2002

• 
  Article Summaries. 2

• 
  Steve McConnell: Closing the Gap. 3-5

• 
  Letters. 6-7

• 
  John Daniels: Modeling with a Sense of Purpose. 8-10

• 
  Andy Hunt, Dave Thomas: Ubiquitous Automation. 11-13

• 
  Anup K. Ghosh, Chuck Howell, James A. Whittaker: Building Software Securely from the Ground Up. 14-16
• 
  Anthony Hall, Roderick Chapman: Correctness by Construction: Developing a Commercial Secure System. 18-25
• 
  Jonathan S. Shapiro, Norman Hardy: EROS: A Principle-Driven Operating System from the Ground Up. 26-33
• 
  Khaled M. Khan, Jun Han: Composing Security-Aware Software. 34-41
• 
  David Evans, David Larochelle: Improving Security Using Extensible Lightweight Static Analysis. 42-51

• 
  Rob Pooley, Dave Senior, Duncan Christie: Collecting and Analyzing Web-Based Project Metrics. 52-58
• 
  Tiffany Winn, Paul R. Calder: Is This a Pattern? 59-66
• 
  Rick Kazman, Leonard J. Bass: Making Architecture Reviews Work in the Real World. 67-73
• 
  Evgeni Dimitrov, Andreas Schmietendorf, Reiner R. Dumke: UML-Based Performance Engineering Possibilities and Techniques. 74-83

• 
  George E. Kalb, Gerald M. Masson: Continuous Process Improvement and the Risk to Information Assurance. 84-86

• 
  Ashton Applewhite: Not Just the Facts: What "Requirements" Mean to a Nonfiction Writer. 87-89

• 
  In the News. 90-94

• 
  Howard A. Rubin, Margaret Johnson, Susan Iventosch: The US Software Industry. 95-97

• 
  Reviewer Thanks. 98-99

• 
  Bookshelf. 100-102

• 
  Robert L. Glass: Failure Is Looking More like Success These Days. 103-104

Volume 19, Number 2, March/April 2002

• 
  Article Summaries. 4

• 
  Steve McConnell: Real Quality for Real Engineers. 5-7

• 
  Letters. 8-10

• 
  Donald J. Reifer: Ten Deadly Risks in Internet and Intranet Software Development. 12-14

• 
  John M. Favaro: Managing Requirements for Business Value. 15-17

• 
  Martin Fowler: Public versus Published Interfaces. 18-19

• 
  Andy Hunt, Dave Thomas: Software Archaeology. 20-22

• 
  Elisabeth Hendrickson, Martin Fowler: The Software Engineering of Internet Software: Guest Editors' Introduction. 23-24
• 
  A. Jefferson Offutt: Quality Attributes of Web Software Applications. 25-32
• 
  Colleen Roe, Sergio Gonik: Server-Side Design Principles for Scalable Internet Systems. 34-41
• 
  Larry L. Constantine, Lucy A. D. Lockwood: Usage-Centered Engineering for Web Applications. 42-50
• 
  Alan Knight, Naci Dai: Objects and the Web. 51-59
• 
  Edward Hieatt, Robert Mee: Going Faster: Testing The Web Application. 60-65
• 
  Scott W. Ambler: Lessons in Agility From Internet-Based Development. 66-73
• 
  Rosann Webb Collins: Software Localization for Internet Software: Issues and Methods. 74-80
• 
  Eric Altendorf, Moses Hohman, Roman Zabicki: Using J2EE on a Large, Web-Based Project. 81-89

• 
  Dragan Milicev: Domain Mapping Using Extended UML Object Diagrams. 90-97

• 
  Greg Goth: Long-Term Data Preservation Efforts Ramping Up. 98-102

• 
  Bookshelf. 104-108

• 
  Melody M. Moore: Reverse Engineering and Reengineering: After Y2K. 109

• 
  Doug Baldwin, Peter B. Henderson: The Importance of Mathematics to the Software Practitioner. 110-112

Volume 19, Number 3, May/June 2002

• 
  Article Summaries. 4

• 
  Steve McConnell: I Know What I Know. 5-7

• 
  Failure or Success? 8-12

• 
  Donald J. Reifer: A Little Bit of Knowledge Is a Dangerous Thing. 14-15

• 
  Chris Rupp: Requirements and Psychology. 16-18

• 
  Martin Fowler: Yet Another Optimization Article. 20-21

• 
  Dave Thomas, Andy Hunt: Mock Objects. 22-24

• 
  Ioana Rus, Mikael Lindvall: Guest Editors' Introduction: Knowledge Management in Software Engineering. 26-38
• 
  Jay Liebowitz: A Look at NASA Goddard Space Flight Center's Knowledge Management Initiatives. 40-42
• 
  Andreas Birk, Torgeir Dingsøyr, Tor Stålhane: Postmortem: Never Leave a Project without It. 43-45
• 
  Kurt Schneider, Jan-Peter von Hunnius, Victor R. Basili: Experience in Implementing a Learning Software Organization. 46-49
• 
  Balasubramaniam Ramesh: Process Knowledge Management with Traceability. 50-52
• 
  Shivram Ramasubramanian, Gokulakrishnan Jagadeesan: Knowledge Management at Infosys. 53-55
• 
  Chih-Ping Wei, Paul Jen-Hwa Hu, Hung-Huang Chen: Design and Evaluation of a Knowledge Management System. 56-59
• 
  Seija Komi-Sirviö, Annukka Mäntyniemi, Veikko Seppänen: Toward a Practical Solution for Capturing Knowledge for Software Projects. 60-62

• 
  Sheila Guilford, Gordon Rugg, Niall Scott: Pleasure and Pain: Perceptual Bias and Its Implications for Software Engineering. 63-69
• 
  Gerald Ebner, Hermann Kaindl: Tracing All Around in Reengineering. 70-77
• 
  Michael Guntersdorfer, David G. Kay: How Software Patents Can Support COTS Component Business. 78-83

• 
  Carlos H. C. Duarte: Brazil: Cooperative Development of a Software Industry. 84-87

• 
  John Steven: Putting Software Terminology to the Test. 88-89

• 
  Carol A. Long: Can Project Management Be Extreme Too? 90-92

• 
  Ware Myers: Ivar Jacobson: Shaping Software Development. 93-95

• 
  Greg Goth: A New Era for Research and Development? 98-100

• 
  Robert L. Glass: The Naturalness of Object Orientation: Beating a Dead Horse? 103-104

Volume 19, Number 4, July/August 2002

• 
  Article Summaries. 4

• 
  The Business of Software Improvement. 5-7

• 
  Software Patents Pro and Con. 8-11

• 
  Greg Goth: Will the Cyber-UL Concept Take Hold? 12-15

• 
  Donald J. Reifer: How Good are Agile Methods? 16-18

• 
  James Robertson: Eureka! Why Analysts Should Invent Requirements. 20-22

• 
  John D. McGregor, Linda M. Northrop, Salah Jarrad, Klaus Pohl: Guest Editors' Introduction: Initiating Software Product Lines. 24-27
• 
  Paul C. Clements, Charles Kreuger: Point - Counterpoint: Being Proactive Pays Off - Eliminating the Adoption. 28-31
• 
  Linda M. Northrop: SEI's Software Product Line Tenets. 32-40
• 
  Frank van der Linden: Software Product Families in Europe: The Esaps & Café Projects. 41-49
• 
  Klaus Schmid, Martin Verlage: The Economic Impact of Product Line Adoption and Evolution. 50-57
• 
  Kyo Chul Kang, Jaejoon Lee, Patrick Donohoe: Feature-Oriented Project Line Engineering. 58-65
• 
  Steffen Thiel, Andreas Hein: Modeling and Using Product Line Variability in Automotive Systems. 66-72
• 
  Ari Jaaksi: Developing Mobile Browsers in a Product Line. 73-80

• 
  Richard Pawson: Naked Objects. 81-83

• 
  Alan C. Tribble: Software Safety. 84-85

• 
  Wolfgang Strigel: The Canadian Software Industry. 86-89

• 
  Terry Bollinger: Guest Editor's Introduction: Breaking Out of the Software Engineering Mind-Mold. 90-91
• 
  Reidar Conradi, Alfonso Fuggetta: Improving Software Process Improvement. 92-99
• 
  José Pablo Zagal, Raúl A. Santelices, Miguel Nussbaum: Maintenance-Oriented Design and Development: A Case Study. 100-106
• 
  James A. Whittaker, Steven Atkin: Software Engineering is Not Enough. 108-115
• 
  Norman E. Fenton, Paul Krause, Martin Neil: Software Measurement: Uncertainty and Causal Modeling. 116-122
• 
  Robert David Cowan, Ali Mili, Hany H. Ammar, Alan McKendall Jr., Lin Yang, Dapeng Chen, Terry Spencer: Software Engineering Technology Watch. 123-129

• 
  Bookshelf. 131-133

• 
  Robert L. Glass: In Search of Meaning (A Tale of Two Words). 134-136

Volume 19, Number 5, September/October 2002

• 
  Article Summaries. 4

• 
  Steve McConnell: How to Write a Good Technical Article. 5-7

• 
  How Good Is Software Construction? 8-11

• 
  Betsy Clark: Eight Secrets of Software Measurement. 12-14

• 
  Dorothy R. Graham: Requirements and Testing: Seven Missing-Link Myths. 15-17

• 
  James Newkirk, Alexei A. Vorontsov: How .NET's Custom Attributes Affect Design. 18-20

• 
  Peter P. Chen: From Goto-less to Structured Programming: The Legacy of Edsger W. Dijkstra. 21

• 
  Thomas B. Hilburn, Watts S. Humphrey: The Impending Changes in Software Education. 22-24
• 
  Richard L. Conn: Developing Software Engineers at the C-130J Software Factory. 25-29
• 
  Jorge L. Díaz-Herrera, Michael G. Murphy, Dawn Ramsey: A Collaborative Program to Retrain Lockheed Martin Aero Engineers. 30-34
• 
  Hossein Saiedian, Donald J. Bagert, Nancy R. Mead: Software Engineering Programs: Dispelling the Myths and Misconceptions. 35-41
• 
  Jürgen Börstler, David A. Carrington, Gregory W. Hislop, Susan K. Lisack, Keith Olson, Laurie A. Williams: Teaching the PSP: Challenges and Lessons Learned. 42-48
• 
  Dale Callahan, Bob Pedigo: Educating Experienced IT Professionals by Addressing Industry's Needs. 57-62
• 
  Grant A. Cheston, J. Paul Tremblay: Integrating Software Engineering in Introductory Computing Courses. 64-71
• 
  Thomas B. Hilburn, Watts S. Humphrey: Teaching Teamwork. 72-77
• 
  David A. Umphress, T. Dean Hendrix, James H. Cross II: Software Process in the Classroom: The Capstone Project Experience. 78-85
• 
  Lisa J. Burnell, John W. Priest, John R. Durrett: Teaching Distributed Multidisciplinary Software Development. 86-93
• 
  Allen B. Tucker, Barry W. Boehm: Point/Counterpoint: On the Balance between Theory and Practice / Software Engineering Is a Value-Based Contact Sport. 94-97

• 
  Natalia Juristo Juzgado, Ana María Moreno: Reliable Knowledge for Software Development. 98-99

• 
  Andy Hunt, Dave Thomas: Zero-Tolerance Construction. 100-102

• 
  Software Engineering Education. 103

• 
  Has Object-Oriented Programming Delivered? / Aviation Software Guidelines. 104-107

• 
  Effective Requirements Practices Managing Software Acquisition: Open Systems and COTS Products / Winning with Software: An Executive Strategy. 108-110

• 
  Robert L. Glass: Project Retrospectives, and Why They Never Happen. 111-112

Volume 19, Number 6, November/December 2002

• 
  Article Summaries. 4

• 
  Steve McConnell: Changing of the Guard. 5-7

• 
  Not Another SPI Framework. 8-9

• 
  Dave Thomas, Andy Hunt: State Machines. 10-12

• 
  Martin Fowler: Using Metadata. 13-17

• 
  Ann Miller, Christof Ebert: Guest Editors' Introduction: Software Engineering as a Business. 18-20
• 
  Steven Mair: A Balanced Scorecard for a Small Software Group. 21-27
• 
  Christina Wallin, Fredrik Ekdahl, Stig Larsson: Integrating Business and Software Development Models. 28-33
• 
  Brian A. Nejmeh, Ian Thomas: Business-Driven Product Planning Using Feature Vectors and Increments. 34-42
• 
  Ram Chillarege: The Marriage of Business Dynamics and Software Engineering. 43-49
• 
  Dorothy McKinney: Six Translations between Software-Speak and Management-Speak. 50-52
• 
  Scott L. Andresen: Don Winter: One CEO's Perspective. 53-55
• 
  Greg Hoglund, Gary McGraw: Point/Counterpoint: Security Band-Aids: More Cost-Effective than "Secure" Coding / Building Secure Software: Better than Protecting Bad Software. 56-59

• 
  Natalia Juristo Juzgado, Ana María Moreno, Andrés Silva: Is the European Industry Moving toward Solving Requirements Engineering Problems? 70-77
• 
  Martín González Rodríguez: Automatic Data-Gathering Agents for Remote Navigability Testing. 78-85
• 
  Frank E. McGarry, Bill Decker: Attaining Level 5 in CMM Process Maturity. 87-96

• 
  Richard E. Fairley: Making Accurate Estimates. 61-63

• 
  Shari Lawrence Pfleeger: What Software Engineering Can Learn from Soccer. 64-65

• 
  Aase Tveito, Per Hasvold: Requirements in the Medical Domain: Experiences and Prescriptions. 66-69

• 
  NIST Report Takes a Step toward Better Testing / National Strategy to Secure Cyberspace Proposed. 97-100

• 
  Bookshelf. 101-104

• 
  Robert L. Glass: Predicting Future Maintenance Cost, and How We're Doing It Wrong. 111-112

last updated on Sat May 18 06:37:46 2013 by the dblp team
data released under the ODC-BY 1.0 license
see also our legal information page