Volume 21, Number 1, January/February 2004

• 
  Article Summaries. 4-

• 
  Letters. 5-7

• 
  Warren Harrison: From the Editor: Best Practices--Who Says? 8-11

• 
  Victor R. Basili, Barry W. Boehm, Al Davis, Watts S. Humphrey, Nancy G. Leveson, Nancy R. Mead, John D. Musa, David Lorge Parnas, Shari Lawrence Pfleeger, Elaine J. Weyuker: New Year's Resolutions for Software Quality. 12-13

• 
  Donald J. Reifer: Seven Hot Outsourcing Practices. 14-16

• 
  Andy Hunt, Dave Thomas: Three Legs, No Wobble. 18-19

• 
  Jim Shore: Continuous Design. 20-22

• 
  Ian F. Alexander, Suzanne Robertson: Understanding Project Sociology by Modeling Stakeholders. 23-27

• 
  Diomidis Spinellis, Clemens A. Szyperski: Guest Editors' Introduction: How Is Open Source Affecting Software Development? 28-33
• 
  Cristina Gacek, Budi Arief: The Many Meanings of Open Source. 34-40
• 
  Jeffrey S. Norris, Poul-Henning Kamp: Mission-Critical Development with Open Source Software: Lessons Learned. 42-49
• 
  Brian Fitzgerald, Tony Kenny: Developing an Information Systems Infrastructure with Open Source Software. 50-55
• 
  Nicolás Serrano, Sonia Calzada, Jose Maria Sarriegi, Ismael Ciordia: From Proprietary to Open Source Tools in Information Systems Development. 56-58
• 
  Walt Scacchi: Free and Open Source Development Practices in the Game Community. 59-66
• 
  Stephane Lussier: New Tricks: How Open Source Changed the Way My Team Works. 68-72
• 
  Nir Kshetri: Economics of Linux Adoption in Developing Countries. 74-81
• 
  Michel Ruffin, Christof Ebert: Using Open Source Software in Product Development: A Primer. 82-86
• 
  Eric S. Raymond, David G. Messerschmitt: Point/Counterpoint. 88-91

• 
  Andreas Holzinger: Rapid Prototyping for a Virtual Medical Campus Interface. 92-99

• 
  Laurianne McLaughlin, Terry Costlow: In the News. 100-103

• 
  Philipp K. Janert, Shantha Mohan, Robert C. Larrabee, Stephen P. Berczuk, Brad Appleton, Fergus O'Connell, Luke Hohmann: Bookshelf. 104-106

• 
  2003 Reviewers. 107-110

• 
  Robert L. Glass: Sources for Software Development: A Mugwumpish View. 111-112

Volume 21, Number 2, March/April 2004

• 
  Article Summaries. 4-

• 
  Warren Harrison: Learning Organizations and the Software Developer. 5-7

• 
  Letters. 8-12

• 
  Dave Thomas, Andy Hunt: Nurturing Requirements. 13-15

• 
  Roel Wieringa, Christof Ebert: Guest Editors' Introduction: RE'03--Practical Requirements Engineering Solutions. 16-18
• 
  Robyn R. Lutz, Ines Carmen Mikulski: Ongoing Requirements Discovery in High-Integrity Systems. 19-25
• 
  Maya Daneva: ERP Requirements Engineering Practice: Lessons Learned. 26-33
• 
  Jens Bæk Jørgensen, Claus Bossen: Executable Use Cases: Requirements for a Pervasive Health Care System. 34-41

• 
  Michael Schrage: Never Go to a Client Meeting without a Prototype. 42-45

• 
  Diane Kelly, Terry Shepard: A Little Knowledge about Software. 46-48

• 
  Kam Hay Fung, Graham Cedric Low, Pradeep Kumar Ray: Embracing Dynamic Evolution in Distributed Systems. 49-55
• 
  Patrick Th. Eugster, Rachid Guerraoui: Distributed Programming with Typed Events. 56-64

• 
  Martin Fowler: Module Assembly. 65-67

• 
  Richard E. Biehl: Six Sigma for Software. 68-70

• 
  Nicolas Gold, Claire Knight, Andrew Mohan, Malcolm Munro: Understanding Service-Oriented Software. 71-77
• 
  Yasushi Kambayashi, Henry F. Ledgard: The Separation Principle: A Programming Paradigm. 78-87
• 
  Marco Torchiano, Maurizio Morisio: Overlooked Aspects of COTS-Based Development. 88-93

• 
  Ashton Applewhite, Alan Davis: In the News. 94-99

• 
  Deependra Moitra, Martin Fogarty: Bookshelf. 100-101

• 
  Robert L. Glass: On Modeling and Discomfort. 102-104

Volume 21, Number 3, May/June 2004

• 
  Article Summaries. 4-

• 
  Warren Harrison: From the Editor: Clueless--and Oblivious. 5-7

• 
  Letters. 8-10

• 
  Donald J. Reifer: Catching the Brass Ring. 12-14

• 
  Dave A. Thomas: MDA: Revenge of the Modelers or UML Utopia? 15-17

• 
  Hakan Erdogmus, John M. Favaro, Wolfgang Strigel: Guest Editors' Introduction: Return on Investment. 18-22
• 
  Günter Böckle, Paul C. Clements, John D. McGregor, Dirk Muthig, Klaus Schmid: Calculating ROI for Software Product Lines. 23-31
• 
  Rini van Solingen: Measuring the ROI of Software Process Improvement. 32-38
• 
  Mark Denne, Jane Cleland-Huang: The Incremental Funding Method: Data-Driven Software Development. 39-47
• 
  Todd Little: Value Creation and Capture: A Model of the Software Development Process. 48-53
• 
  Barry W. Boehm, LiGuo Huang, Apurva Jain, Raymond J. Madachy: The ROI of Software Dependability: The iDAVE Model. 54-61
• 
  David G. Messerschmitt, Clemens A. Szyperski: Marketplace Issues in Software Planning and Design. 62-70

• 
  Jim Duggan, Jason Byrne, Gerard Lyons: A Task Allocation Optimizer for Software Construction. 76-82
• 
  Jeff Tian: Quality-Evaluation Models and Measurements. 84-91
• 
  James R. Larus, Thomas Ball, Manuvir Das, Robert DeLine, Manuel Fähndrich, Jonathan D. Pincus, Sriram K. Rajamani, Ramanathan Venkatapathy: Righting Software. 92-100

• 
  Ken Orr: Agile Requirements: Opportunity or Oxymoron? 71-73

• 
  Jane Huffman Hayes: On the Virtues of Not Knowing. 74-75

• 
  Andy Hunt, Dave Thomas: OO in One Sentence: Keep It DRY, Shy, and Tell the Other Guy. 101-103

• 
  Fernando Berzal Galiano, Diomidis Spinellis: Bookshelf. 104-105

• 
  Danna Voth, David Nicholls, Dale Strok: In the News. 107-110

• 
  Robert L. Glass: Learning to Distinguish a Solution from a Problem. 111-112

Volume 21, Number 4, July/August 2004

• 
  Article Summaries. 4-

• 
  Warren Harrison: From the Editor: The Dangers of End-User Programming. 5-7

• 
  Letters. 8-10

• 
  Nancy S. Eickelmann: Measuring Maturity Goes beyond Process . 12-13

• 
  Scott Meyers: The Most Important Design Guideline? 14-16

• 
  Arno Puder: MICO: An Open Source CORBA Implementation. 17-19

• 
  David Dorenbos, Annie Combelles: Introduction: Lessons Learned around the World: Key Success Factors to Enable Process Change. 20-21
• 
  Hee-Woong Kim: A Process Model for Successful CRM System Development. 22-28
• 
  Felipe Guerrero, Yadran Eterovic: Adopting the SW-CMM in a Small IT Organization. 29-35
• 
  Anna Börjesson, Lars Mathiassen: Successful Process Implementation. 36-44
• 
  Spencer Rugaber, Kurt Stirewalt: Model-Driven Reverse Engineering. 45-53

• 
  Akif Günes Koru, Jeff Tian: Defect Handling in Medium and Large Open Source Projects. 54-61
• 
  Václav Rajlich, Prashant Gosavi: Incremental Change in Object-Oriented Programming. 62-69
• 
  Viswanathan Kodaganallur: Incorporating Language Processing into Java Applications: A JavaCC Tutorial. 70-77
• 
  Óscar Dieste Tubío, Natalia Juristo Juzgado, Ana María Moreno: How Higher-Education Systems Influence Software Engineering Degree Programs. 78-85

• 
  Erik Simmons: Requirements Triage: What Can We Learn from a "Medical" Approach? 86-88

• 
  Dave Thomas, Andy Hunt: Open Source Ecosystems. 89-91

• 
  Christof Ebert, Stephen J. Mellor: Bookshelf. 92-94

• 
  Robert L. Glass: Some Heresy Regarding Software Engineering. 102-104

Volume 21, Number 5, September/October 2004

• 
  Article Summaries. 4-

• 
  Warren Harrison: From the Editor: Propaganda and Software Development. 5-7

• 
  Letters. 8-16

• 
  Armand Marchesin: Using Linux for Real-Time Applications. 18-20

• 
  Jim Shore: Fail Fast. 21-25

• 
  Jeffrey M. Voas: Software Engineering's Role in Business. 26-27
• 
  Peter Middleton, Ho Woo Lee, Shahrukh A. Irani: Why Culling Software Colleagues Is Popular. 28-32
• 
  Mordechai Ben-Menachem, Garry S. Marliss: Inventorying Information Technology Systems: Supporting the "Paradigm of Change". 34-43
• 
  Glenn J. Browne, Nirup M. Menon: Network Effects and Social Dilemmas in Technology Industries. 44-50
• 
  Amrit Tiwana: Beyond the Black Box: Knowledge Overlaps in Software Outsourcing. 51-58

• 
  William N. Robinson, Han G. Woo: Finding Reusable UML Sequence Diagrams Automatically. 60-67
• 
  Neil A. M. Maiden, Alexis Gizikis, Suzanne Robertson: Provoking Creativity: Imagine What Your Requirements Could Be Like. 68-75
• 
  Allen S. Parrish, Randy K. Smith, David P. Hale, Joanne E. Hale: A Field Study of Developer Pairs: Productivity Impacts and Implications. 76-79
• 
  Yuefeng Zhang: Test-Driven Modeling for Model-Driven Development. 80-86
• 
  Ho-Won Jung, Seung-Gweon Kim, Chang-Shin Chung: Measuring Software Product Quality: A Survey of ISO/IEC 9126. 88-92

• 
  Suzanne Robertson: Requirements and the Business Case. 93-95

• 
  Andy Hunt, Dave Thomas: Imaginate. 96-97

• 
  Jean-Jacques Gras: End-to-End Defect Modeling. 98-100

• 
  Laurianne McLaughlin, Benjamin Alfonsi: In the News. 101-105

• 
  Terry Bollinger, Mike Barker, Philipp K. Janert: Bookshelf. 106-109

• 
  Software Engineering Glossary: Software Design, Part I. 110-

• 
  Robert L. Glass: Anarchy and the Effects of Schedule Pressure. 111-112

Volume 21, Number 6, November-December 2004

• 
  Article Summaries. 4

• 
  User Confidence--and the Software Developer. 5-8

• 
  Letters. 9-11

• 
  Dave Thomas, Andy Hunt: Practice. 12-13

• 
  Jeffrey M. Voas: Software's Secret Sauce: The "-ilities". 14-15

• 
  Terry Bollinger, Jeffrey M. Voas, Maarten Boasson: Persistent Software Attributes. 16-18
• 
  Victor R. Basili, Paolo Donzelli, Sima Asgari: A Unified Model of Dependability: Capturing Dependability in Context. 19-25
• 
  Nicolás Serrano, Ismael Ciordia, Sonia Calzada, Fernando Alonso: Automated Management of Multicustomer Code Bases. 26-31
• 
  Arvind S. Krishna, Cemal Yilmaz, Atif M. Memon, Adam A. Porter, Douglas C. Schmidt, Aniruddha S. Gokhale, Balachandran Natarajan: Preserving Distributed Systems' Critical Properties: A Model-Driven Approach. 32-40
• 
  Francisco Ortin, Benjamín López, J. Baltasar García Perez-Schofield: Separating Adaptable Persistence Attributes through Computational Reflection. 41-49
• 
  Alexander Egyed, Paul Grünbacher: Identifying Requirements Conflicts and Cooperation: How Quality Attributes and Automated Traceability Can Help. 50-58
• 
  Terry Bollinger: Conference Report: The Future of Software Infrastructure Protection. 59-61

• 
  T. R. Madanmohan, Rahul De': Open Source Reuse in Commercial Firms. 62-69
• 
  Jerry Drobka, David Noftz, Rekha Raghu: Piloting XP on Four Mission-Critical Projects. 70-75
• 
  Pauliina Ulkuniemi, Veikko Seppänen: COTS Component Acquisition in an Emerging Market. 76-82

• 
  Michael Jackson: Seeing More of the World. 83-85

• 
  Michael C. Feathers: Before Clarity. 86-88

• 
  Nicolás Serrano, Ismael Ciordia: Ant: Automating the Process of Building Applications. 89-91

• 
  Robert Groth: Is the Software Industry's Productivity Declining? 92-94

• 
  Annual Index. 95-99

• 
  Philipp K. Janert: Introducing Test-Driven Software Development. 100-101

• 
  Johann Rost: Political Reasons for Failed Software Projects. 102-104

• 
  Software Design, Part 2.

last updated on Thu May 23 04:40:49 2013 by the dblp team
data released under the ODC-BY 1.0 license
see also our legal information page