default search action
Martin Fowler
Person information
- affiliation: ThoughtWorks, Chicago, Illinois, USA
Refine list
refinements active!
zoomed in on ?? of ?? records
view refined list in
export refined list as
2010 – 2019
- 2011
- [b6]Martin Fowler:
Domain-Specific Languages. The Addison-Wesley signature series, Addison-Wesley 2011, ISBN 978-0-321-71294-3, pp. I-XXVIII, 1-597
2000 – 2009
- 2009
- [j16]Martin Fowler:
A Pedagogical Framework for Domain-Specific Languages. IEEE Softw. 26(4): 13-14 (2009) - 2007
- [c20]Steven Fraser, Frederick P. Brooks Jr., Martin Fowler, Ricardo López, 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
- [j15]Martin Fowler:
The State of Design. IEEE Softw. 22(6): 12-13, 16 (2005) - [c19]Martin Fowler:
Finding good design. OOPSLA Companion 2005: 4 - 2004
- [j14]Martin Fowler:
Module Assembly. IEEE Softw. 21(2): 65-67 (2004) - [c18]Jim Haungs, Martin Fowler, Ralph E. Johnson, Steve McConnell, Richard P. Gabriel:
Software development: arts & crafts or math & science? OOPSLA Companion 2004: 141-142 - [c17]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 - [c16]Steven Fraser, Lougie Anderson, Ron Crocker, Richard P. Gabriel, Martin Fowler, Ricardo López, Dave A. Thomas:
Challenges in outsourcing and global development: how will your job change? OOPSLA Companion 2004: 145-147 - 2003
- [j13]Martin Fowler:
When to Make a Type. IEEE Softw. 20(1): 12-13 (2003) - [j12]Martin Fowler:
Patterns. IEEE Softw. 20(2): 56-57 (2003) - [j11]Martin Fowler:
Who Needs an Architect? IEEE Softw. 20(5): 11-13 (2003) - [j10]Martin Fowler:
Data Access Routines. IEEE Softw. 20(6): 96-98 (2003) - [c15]Martin Fowler:
What Is the Point of the UML? UML 2003: 325 - 2002
- [j9]Martin Fowler:
Public versus Published Interfaces. IEEE Softw. 19(2): 18-19 (2002) - [j8]Elisabeth Hendrickson, Martin Fowler:
The Software Engineering of Internet Software: Guest Editors' Introduction. IEEE Softw. 19(2): 23-24 (2002) - [j7]Martin Fowler:
Yet Another Optimization Article. IEEE Softw. 19(3): 20-21 (2002) - [j6]Martin Fowler:
Using Metadata. IEEE Softw. 19(6): 13-17 (2002) - [c14]Leon J. Osterweil, Philippe Kruchten, Martin Fowler, Wilhelm Schäfer:
Lightweight vs. heavyweight processes: is this even the right question? ICSE 2002: 649 - [c13]Martin Fowler:
Refactoring. ICSE 2002: 701 - [c12]Martin Fowler:
Information systems architecture. ICSE 2002: 702 - [c11]Martin Fowler:
Refactoring: Improving the Design of Existing Code. XP/Agile Universe 2002: 256 - 2001
- [j5]Martin Fowler:
Design - Avoiding Repetition. IEEE Softw. 18(1): 97-99 (2001) - [j4]Martin Fowler:
Design - Separating User Interface Code. IEEE Softw. 18(2): 96-97 (2001) - [j3]Martin Fowler:
Reducing Coupling. IEEE Softw. 18(4): 102-104 (2001) - [j2]Martin Fowler:
To Be Explicit. IEEE Softw. 18(6): 10-15 (2001) - 2000
- [b5]Martin Fowler, Kendall Scott:
UML distilled - a brief guide to the Standard Object Modeling Language (2. ed.). notThenot Addison-Wesley object technology series, Addison-Wesley-Longman 2000, ISBN 978-0-201-65783-8, pp. I-XIX, 1-186 - [c10]Steven Fraser, Kent L. Beck, Ward Cunningham, Ron Crocker, Martin Fowler, Linda Rising, Laurie A. Williams:
Hacker or hero? - extreme programming today (panel session). OOPSLA Addendum 2000: 5-7 - [c9]Martin Fowler:
Refactoring. TOOLS (34) 2000: 437-
1990 – 1999
- 1999
- [b4]Martin Fowler:
Refactoring - Improving the Design of Existing Code. Addison Wesley object technology series, Addison-Wesley 1999, ISBN 978-0-201-48567-7, pp. I-XXI, 1-431 - 1998
- [b3]Martin Fowler, Kendall Scott:
UML konzentriert - die Standardobjektmodellierungssprache anwenden: mit neuester Version UML 1.1. Addison-Wesley-Longman 1998, ISBN 978-3-8273-1329-4, pp. 1-188 - [c8]Alistair Cockburn, Martin Fowler:
Question time! about Use Cases. OOPSLA 1998: 226-229 - 1997
- [b2]Martin Fowler, Kendall Scott:
UML distilled - applying the standard object modeling language. Addison-Wesley-Longman 1997, ISBN 978-0-201-32563-8, pp. I-XVIII, 1-179 - [b1]Martin Fowler:
Analysis patterns - reusable object models. Addison-Wesley series in object-oriented software engineering, Addison-Wesley-Longman 1997, ISBN 978-0-201-89542-1, pp. I-XXI, 1-357 - [c7]Martin Fowler:
A Survey of Object Oriented Analysis and Design Methods (Tutorial). ICSE 1997: 653-654 - 1996
- [c6]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
- [j1]Martin Fowler:
Application Views: Another Technique in the Analysis and Design Armoury. J. Object Oriented Program. 7(1): 59-66 (1994) - [c5]Martin Fowler:
Comparison of Analysis and Design Methods. TOOLS (13) 1994: 517 - 1993
- [c4]Mark Thursz, Martin Fowler, Thomas Cairns, Michael Thick, Gerry Gold:
Clinical systems design. CBMS 1993: 134-139 - [c3]Martin Fowler:
A Comparison of Object-Oriented Analysis and Design Methods. TOOLS (11) 1993: 527 - 1992
- [c2]Martin Fowler:
A comparison of object-oriented analysis and design methods (abstract). OOPSLA Addendum 1992: 217 - [c1]Martin Fowler, Thomas Cairns:
Martin Flower, Thomas Cairns. OOPSLA Addendum 1992: 222
Coauthor Index
manage site settings
To protect your privacy, all features that rely on external API calls from your browser are turned off by default. You need to opt-in for them to become active. All settings here will be stored as cookies with your web browser. For more information see our F.A.Q.
Unpaywalled article links
Add open access links from to the list of external document links (if available).
Privacy notice: By enabling the option above, your browser will contact the API of unpaywall.org to load hyperlinks to open access articles. Although we do not have any reason to believe that your call will be tracked, we do not have any control over how the remote server uses your data. So please proceed with care and consider checking the Unpaywall privacy policy.
Archived links via Wayback Machine
For web page which are no longer available, try to retrieve content from the of the Internet Archive (if available).
Privacy notice: By enabling the option above, your browser will contact the API of archive.org to check for archived content of web pages that are no longer available. Although we do not have any reason to believe that your call will be tracked, we do not have any control over how the remote server uses your data. So please proceed with care and consider checking the Internet Archive privacy policy.
Reference lists
Add a list of references from , , and to record detail pages.
load references from crossref.org and opencitations.net
Privacy notice: By enabling the option above, your browser will contact the APIs of crossref.org, opencitations.net, and semanticscholar.org to load article reference information. Although we do not have any reason to believe that your call will be tracked, we do not have any control over how the remote server uses your data. So please proceed with care and consider checking the Crossref privacy policy and the OpenCitations privacy policy, as well as the AI2 Privacy Policy covering Semantic Scholar.
Citation data
Add a list of citing articles from and to record detail pages.
load citations from opencitations.net
Privacy notice: By enabling the option above, your browser will contact the API of opencitations.net and semanticscholar.org to load citation information. Although we do not have any reason to believe that your call will be tracked, we do not have any control over how the remote server uses your data. So please proceed with care and consider checking the OpenCitations privacy policy as well as the AI2 Privacy Policy covering Semantic Scholar.
OpenAlex data
Load additional information about publications from .
Privacy notice: By enabling the option above, your browser will contact the API of openalex.org to load additional information. Although we do not have any reason to believe that your call will be tracked, we do not have any control over how the remote server uses your data. So please proceed with care and consider checking the information given by OpenAlex.
last updated on 2024-04-25 05:49 CEST by the dblp team
all metadata released as open data under CC0 1.0 license
see also: Terms of Use | Privacy Policy | Imprint