Volume 25, Number 1, January - February 2008
- Hakan Erdogmus:
So Many Languages, So Little Time.
4-6

- Grady Booch:
Morality and the Software Architect.
8-9

- Konstantin Beznosov, Brian Chess:
Security for the Rest of Us: An Industry Perspective on the Secure-Software Challenge.
10-12

- Charlie Lai:
Java Insecurity: Accounting for Subtleties That Can Compromise Code.
13-19

- Inger Anne Tøndel, Martin Gilje Jaatun, Per Håkon Meland:
Security Requirements for the Rest of Us: A Survey.
20-27

- Jeffrey A. Ingalsbe, Louis Kunimatsu, Tim Baeten, Nancy R. Mead:
Threat Modeling: Diving into the Deep End.
28-34

- Shari Lawrence Pfleeger, Rachel Rue:
Cybersecurity Economic Issues: Clearing the Path to Good Practice.
35-42

- David Callele, Eric Neufeld, Kevin Schneider:
Emotional Requirements.
43-45

- Axel Uhl:
Model-Driven Development in the Enterprise.
46-49

- Jeff Patton:
Ambiguous Business Value Harms Software Products.
50-51

- J. B. Rainsberger, Johanna Rothman:
Are You Done Yet?
52-53

- Robert C. Martin, Grigori Melnik:
Tests and Requirements, Requirements and Tests: A Möbius Strip.
54-59

- Lan Cao, Balasubramaniam Ramesh:
Agile Requirements Engineering Practices: An Empirical Study.
60-67

- Rick Mugridge:
Managing Agile Project Requirements with Storytest-Driven Development.
68-75

- Rebecca Wirfs-Brock:
Valuing Design Repair.
76-77

- Diomidis Spinellis:
Rational Metaprogramming.
78-79

- Sangsoo Kim, Hoh Peter In, Jongmoon Baik, Rick Kazman, Kwangsin Han:
VIRE: Sailing a Blue Ocean with Value-Innovative Requirements.
80-87

- Forrest Shull, Carolyn B. Seaman:
Inspecting the History of Inspections: An Example of Evidence-Based Technology Diffusion.
88-90

- Steven Fraser, Dennis Mancl:
No Silver Bullet: Software Engineering Reloaded.
91-94

- Robert L. Glass:
Intuition's Role in Decision Making.
96

Volume 25, Number 2, March - April 2008
- Hakan Erdogmus:
Measurement Acquiescence.
4-6

- Óscar Dieste Tubío, Natalia Juristo Juzgado, Forrest Shull:
Understanding the Customer: What Do We Know about Requirements Elicitation?
11-13

- Alain Désilets:
Tell Me a Story.
14-15

- Grady Booch:
Tribal Memory.
16-17

- Daniel M. Berry:
The Software Engineering Silver Bullet Conundrum.
18-19

- Rebecca Wirfs-Brock:
Connecting Design with Code.
20-21

- J. David Blaine, Jane Cleland-Huang:
Software Quality Requirements: How to Balance Competing Priorities.
22-24

- Ipek Ozkaya, Len Bass, Robert L. Nord, Raghvinder S. Sangwan:
Making Practical Use of Quality Attribute Information.
25-33

- Martin Glinz:
A Risk-Based, Value-Oriented Approach to Quality Requirements.
34-41

- Björn Regnell, Richard Berntsson-Svensson, Thomas Olsson:
Supporting Roadmapping of Quality Requirements.
42-47

- Martin S. Feather, Steven L. Cornford, Kenneth A. Hicks, James D. Kiper, Tim Menzies:
A Broad, Quantitative Model for Making Early Requirements Decisions.
49-56

- Jørgen Bøegh:
A New Standard for Quality Requirements.
57-63

- Tom Gilb, Alistair Cockburn:
Point/Counterpoint.
64-67

- José Luis Sierra, Alfredo Fernández-Valmayor, Baltasar Fernández-Manjón:
From Documents to Applications Using Markup Languages.
68-76

- David S. Janzen, Hossein Saiedian:
Does Test-Driven Development Really Improve Software Design Quality?
77-84

- Panagiotis Louridas:
Orchestrating Web Services with BPEL.
85-87

- Diomidis Spinellis:
Using and Abusing XML.
88-89

- Neil A. M. Maiden:
User Requirements and System Requirements.
90-91

- Greg Goth:
"Googling" Test Practices? Web Giant's Culture Encourages Process Improvement.
92-94

- Robert L. Glass:
On the Impurity of the English Language.
96

Volume 25, Number 3, May - June 2008
- Hakan Erdogmus:
The Infamous Ratio Measure.
4-7

- Arilo Claudio Dias Neto, Rajesh Subramanyan, Marlon Vieira, Guilherme Horta Travassos, Forrest Shull:
Improving Evidence about Software Technologies: A Look at Model-Based Testing.
10-13

- Rebecca Wirfs-Brock:
Design Strategy.
14-15

- Helena Sustar, Ulrike Pfeil, Panayiotis Zaphiris:
Requirements Elicitation with and for Older Adults.
16-17

- Grady Booch:
Architectural Organizational Patterns.
18-19

- Jeff Patton:
Getting Software RITE.
20-21

- Diomidis Spinellis:
Software Builders.
22-23

- Bill Curtis, Girish Seshagiri, Donald J. Reifer, Iraj Hirmanpour, Gargi Keeni:
The Case for Quantitative Process Management.
24-28

- Uma Sudhakar Rao, Srikanth Kestur, Chinmay Pradhan:
Stochastic Optimization Modeling and Quantitative Project Management.
29-36

- David N. Card, Kevin Domzalski, Glyn Davies:
Making Statistics Part of Decision Making in an Engineering Organization.
37-47

- Edward F. Weller, David Card, Bill Curtis, Bob Raczynski:
Point/Counterpoint.
48-51

- Christof Ebert:
Open Source Software in Industry.
52-53

- Kris Ven, Jan Verelst, Herwig Mannaert:
Should You Adopt Open Source Software?
54-59

- Jacco H. Wesselius:
The Bazaar inside the Cathedral: Business Models for Internal Markets.
60-66

- Christian Floerkemeier, Elgar Fleisch:
RFID Applications: Interfacing with Readers.
67-70

- Jörg Dörr, Sebastian Adam, Michael Eisenbarth, Michael Ehresmann:
Implementing Requirements Engineering Processes: Using Cooperative Self-Assessment and Improvement.
71-77

- Magne Jørgensen, Stein Grimstad:
Avoiding Irrelevant and Misleading Information When Estimating Development Effort.
78-83

- Edward Curry, Paul Grace:
Flexible Self-Management Using the Model-View-Controller Pattern.
84-90

- Greg Goth:
Ultralarge Systems: Redefining Software Engineering?
91-94

- Robert L. Glass:
Software: Hero or Zero?
96

Volume 25, Number 4, July - August 2008
- Hakan Erdogmus:
Essentials of Software Process.
4-7

- Sebastian Schaffert, François Bry, Joachim Baumeister, Malte Kiesel:
Semantic Wikis.
8-11

- Rebecca Wirfs-Brock:
Up-front Design.
12-13

- Grady Booch:
Measuring Architectural Complexity.
14-15

- Barbara Paech:
What Is a Requirements Engineer?
16-17

- Judith Segal, Chris Morris:
Developing Scientific Software.
18-20

- Rebecca Sanders, Diane Kelly:
Dealing with Risk in Scientific Software Development.
21-28

- Victor R. Basili, Jeffrey C. Carver, Daniela Cruzes, Lorin Hochstein, Jeffrey K. Hollingsworth, Forrest Shull, Marvin V. Zelkowitz:
Understanding the High-Performance-Computing Community: A Software Engineer's Perspective.
29-36

- David Woollard, Nenad Medvidovic, Yolanda Gil, Chris Mattmann:
Scientific Software as Workflows: From Discovery to Distribution.
37-43

- Karen S. Ackroyd, Steve H. Kinder, Geoff R. Mant, Mike C. Miller, Christine A. Ramsdale, Paul C. Stephenson:
Scientific Software Development at a Research Facility.
44-51

- Mark R. Vigder, Norman G. Vinson, Janice Singer, Darlene A. Stewart, Keith Mews:
Supporting Scientists' Everyday Work: Automating Scientific Workflows.
52-58

- Richard P. Kendall, Jeffrey C. Carver, David Fisher, Dale Henderson, Andrew Mark, Douglass E. Post, Clifford E. Rhoades Jr., Susan E. Squires:
Development of a Weather Forecasting Code: A Case Study.
59-65

- Raghvinder S. Sangwan, Pamela Vercellone-Smith, Phillip A. Laplante:
Structural Epochs in the Complexity of Software over Time.
66-73

- Tony Savor:
Testing Feature-Rich Reactive Systems.
74-81

- Les Hatton:
Testing the Value of Checklists in Code Inspections.
82-88

- Diomidis Spinellis:
The Way We Program.
89-91

- Tracy Hall, Helen Sharp, Sarah Beecham, Nathan Baddoo, Hugh Robinson:
What Do We Know about Developer Motivation?
92-94

- Robert L. Glass:
Two Mistakes and Error-Free Software: A Confession.
96

Volume 25, Number 5, September - October 2008
- Hakan Erdogmus:
Must Software Research Stand Divided?
4-6

- Ejike Ofuonye, Patricia Beatty, Ian Reay, Scott Dick, James Miller:
How Do We Build Trust into E-commerce Web Sites?
7-9

- Philippe Kruchten:
The Biological Half-Life of Software Engineering Ideas.
10-11

- Hisham Mubarak:
Developing Flexible Software Using Agent-Oriented Software Engineering.
12-15

- J. B. Rainsberger:
In or Out?
16-17

- Simon Helsen, Arthur G. Ryman, Diomidis Spinellis:
Where's My Jetpack?
18-21

- Nathaniel Ayewah, David Hovemeyer, J. David Morgenthaler, John Penix, William Pugh:
Using Static Analysis to Find Bugs.
22-29

- Patrice Godefroid, Jonathan de Halleux, Aditya V. Nori, Sriram K. Rajamani, Wolfram Schulte, Nikolai Tillmann, Michael Y. Levin:
Automating Software Testing Using Program Analysis.
30-37

- Emerson R. Murphy-Hill, Andrew P. Black:
Refactoring Tools: Fitness for Purpose.
38-44

- Oliver Hummel, Werner Janjic, Colin Atkinson:
Code Conjurer: Pulling Reusable Software out of Thin Air.
45-52

- Dragos Manolescu, Brian Beckman, V. Benjamin Livshits:
Volta: Developing Distributed Applications by Recompiling.
53-59

- Florian Deissenboeck, Elmar Jürgens, Benjamin Hummel, Stefan Wagner, Benedikt Mas y Parareda, Markus Pizka:
Tool Support for Continuous Quality Control.
60-67

- Martin Mahaux, Neil A. M. Maiden:
Theater Improvisers Know the Requirements Game.
68-69

- Rebecca Wirfs-Brock:
Enabling Change.
70-71

- Jeff Patton:
Consider Multiple Solutions.
72-73

- Barry W. Boehm, Ricardo Valerdi:
Achievements and Challenges in Cocomo-Based Software Resource Estimation.
74-83

- Khaled El Emam, Akif Günes Koru:
A Replicated Survey of IT Software Project Failures.
84-90

- Sukanya Ratanotayanon, Susan Elliott Sim:
Inventive Tool Use to Comprehend Big Code.
91-92

- Grady Booch:
Nine Things You Can Do with Old Software.
93-94

- Robert L. Glass:
Negative Productivity and What to Do about It.
96

Volume 25, Number 6, November - December 2008
- Hakan Erdogmus:
25 Years of Software.
2-5

- Jeff Patton:
A Conversation with Alan Cooper: The Origin of Interaction Design.
15-17

- Brian W. Kernighan:
Sometimes the Old Ways Are Best.
18-19

- Grady Booch:
Back to the Future.
20-21

- Christof Ebert:
A Brief History of Software Technology.
22-25

- Neil A. M. Maiden:
Requirements 25 Years On.
26-28

- Rebecca Wirfs-Brock:
Designing Then and Now.
29-31

- Shari Lawrence Pfleeger:
Software Metrics: Progress after 25 Years?
32-34

- Philippe Kruchten:
Licensing Software Engineers?
35-37

- Cornelius Ncube, Patricia A. Oberndorf, Anatol W. Kark:
Opportunistic Software Systems Development: Making Systems from What's Available.
38-41

- Slinger Jansen, Sjaak Brinkkemper, Ivo Hunink, Cetin Demir:
Pragmatic and Opportunistic Reuse in Innovative Start-up Companies.
42-49

- Sriram Balasubramaniam, Grace A. Lewis, Soumya Simanta, Dennis B. Smith:
Situated Software: Concepts, Motivation, Technology, and the Future.
50-55

- Barry W. Boehm, Jesal Bhuta:
Balancing Opportunities and Risks in Component-Based Software Development.
56-63

- Zeljko Obrenovic, Dragan Gasevic, Anton Eliëns:
Stimulating Creativity through Opportunistic Software Development.
64-70

- M. Todd Gamble, Rose F. Gamble:
Monoliths to Mashups: Increasing Opportunistic Assets.
71-79

- Michiel van Genuchten, Robert Baillargeon:
Point/Counterpoint.
80-83

- Anna Börjesson Sandberg, Lars Mathiassen:
Managing Slowdown in Improvement Projects.
84-89

- Robert L. Glass, Johann Rost, Matthias S. Matook:
Lying on Software Projects.
90-95

- Carlos Santos Jr.:
Understanding Partnerships between Corporations and the Open Source Community: A Research Gap.
96-97

- Viswa Viswanathan:
Rapid Web Application Development: A Ruby on Rails Tutorial.
98-106

- Mark Ingebretsen:
Unconferences Catch On with Developers.
108-110

Last update Tue May 21 19:37:45 2013
CET by the DBLP Team —
Data released under the ODC-BY 1.0 license — See also our legal information page