 | 2009 |
|---|
| 34 |       | Martin Fowler:
A Pedagogical Framework for Domain-Specific Languages.
IEEE Software 26(4): 13-14 (2009) |
| 2007 |
|---|
| 33 | | Steven Fraser,
Frederick P. Brooks Jr.,
Martin Fowler,
Ricardo Lopez,
Aki Namioka,
Linda M. Northrop,
David Lorge Parnas,
Dave A. Thomas:
"No silver bullet" reloaded: retrospective on "essence and accidents of software engineering".
OOPSLA Companion 2007: 1026-1030 |
| 2005 |
|---|
| 32 | | Martin Fowler:
Finding good design.
OOPSLA Companion 2005: 4 |
| 31 | | Martin Fowler:
The State of Design.
IEEE Software 22(6): 12-13, 16 (2005) |
| 2004 |
|---|
| 30 | | Jim Haungs,
Martin Fowler,
Ralph E. Johnson,
Steve McConnell,
Richard P. Gabriel:
Software development: arts & crafts or math & science?
OOPSLA Companion 2004: 141-142 |
| 29 | | Martin Fowler,
Don Box,
Anders Hejlsberg,
Alan Knight,
Rob J. High,
John Crupi:
The great J2EE vs. microsoft.NET shootout.
OOPSLA Companion 2004: 143-144 |
| 28 | | Steven Fraser,
Lougie Anderson,
Ron Crocker,
Richard P. Gabriel,
Martin Fowler,
Ricardo Lopez,
Dave A. Thomas:
Challenges in outsourcing and global development: how will your job change?
OOPSLA Companion 2004: 145-147 |
| 27 | | Martin Fowler:
Module Assembly.
IEEE Software 21(2): 65-67 (2004) |
| 2003 |
|---|
| 26 | | Martin Fowler:
What Is the Point of the UML?
UML 2003: 325 |
| 25 | | Martin Fowler:
When to Make a Type.
IEEE Software 20(1): 12-13 (2003) |
| 24 | | Martin Fowler:
Patterns.
IEEE Software 20(2): 56-57 (2003) |
| 23 | | Martin Fowler:
Who Needs an Architect?
IEEE Software 20(5): 11-13 (2003) |
| 22 | | Martin Fowler:
Data Access Routines.
IEEE Software 20(6): 96-98 (2003) |
| 2002 |
|---|
| 21 | | Leon J. Osterweil,
Philippe Kruchten,
Martin Fowler,
Wilhelm Schäfer:
Lightweight vs. heavyweight processes: is this even the right question?
ICSE 2002: 649 |
| 20 | | Martin Fowler:
Refactoring.
ICSE 2002: 701 |
| 19 | | Martin Fowler:
Information systems architecture.
ICSE 2002: 702 |
| 18 | | Martin Fowler:
Refactoring: Improving the Design of Existing Code.
XP/Agile Universe 2002: 256 |
| 17 | | Martin Fowler:
Public versus Published Interfaces.
IEEE Software 19(2): 18-19 (2002) |
| 16 | | Elisabeth Hendrickson,
Martin Fowler:
The Software Engineering of Internet Software: Guest Editors' Introduction.
IEEE Software 19(2): 23-24 (2002) |
| 15 | | Martin Fowler:
Yet Another Optimization Article.
IEEE Software 19(3): 20-21 (2002) |
| 14 | | Martin Fowler:
Using Metadata.
IEEE Software 19(6): 13-17 (2002) |
| 2001 |
|---|
| 13 | | Martin Fowler:
Design - Avoiding Repetition.
IEEE Software 18(1): (2001) |
| 12 | | Martin Fowler:
Design - Separating User Interface Code.
IEEE Software 18(2): (2001) |
| 11 | | Martin Fowler:
Reducing Coupling.
IEEE Software 18(4): 102-104 (2001) |
| 10 | | Martin Fowler:
To Be Explicit.
IEEE Software 18(6): 10-15 (2001) |
| 2000 |
|---|
| 9 | | Martin Fowler:
Refactoring.
TOOLS (34) 2000: 437- |
| 1998 |
|---|
| 8 | | Alistair Cockburn,
Martin Fowler:
Question time! about Use Cases.
OOPSLA 1998: 226-229 |
| 1997 |
|---|
| 7 | | Martin Fowler:
A Survey of Object Oriented Analysis and Design Methods (Tutorial).
ICSE 1997: 653-654 |
| 1996 |
|---|
| 6 |  | Steven Fraser,
Robert C. Martin,
Stephen J. Mellor,
Michael Lee,
Grady Booch,
Stephen Garone,
Martin Fowler,
Douglas C. Schmidt,
Marie Lenzi:
Translation: Myth or Reality? (Panel Session).
OOPSLA 1996: 441-443 |
| 1994 |
|---|
| 5 | | Martin Fowler:
Comparison of Analysis and Design Methods.
TOOLS (13) 1994: 517 |
| 4 | | Martin Fowler:
Application Views: Another Technique in the Analysis and Design Armoury.
JOOP 7(1): 59-66 (1994) |
| 1993 |
|---|
| 3 | | Martin Fowler:
A Comparison of Object-Oriented Analysis and Design Methods.
TOOLS (11) 1993: 527 |
| 2 | | Martin Fowler:
A comparison of object-oriented analysis and design methods (abstract).
OOPS Messenger 4(2): 217 (1993) |
| 1 | | Martin Fowler,
Thomas Cairns:
Martin Flower, Thomas Cairns.
OOPS Messenger 4(2): 222 (1993) |
