This article needs additional citations for verification. Please help improve this article by adding citations to reliable sources. Unsourced material may be challenged and removed. (August 2010)

talk was a program originally used for live text communication between different users of a single multi-user computer running the Unix operating system. In 1983, a new version of talk was introduced as a Unix command with BSD v4.2, and would also accommodate electronic conversations between users on different machines. Follow-ons to talk included ntalk and ytalk. ytalk was the first to allow conversations between more than two users, and was written in part to allow communication between users on computers with different endianess. All of these programs split the interface into different sections for each participant. The interfaces did not convey the order in which statements typed by different participants would be reassembled into a log of the conversation. Also, all three programs are real-time text, where they transmit each character as it was typed. This leads to a more immediate feel to the discussion than recent instant messaging clients or IRC. Users more familiar with other forms of instant text communication would sometimes find themselves in embarrassing situations by typing something and deciding to withdraw the statement, unaware that other participants of the conversation had seen it all happen in real time.

talk was previously available on the DEC PDP-11 computer system in the 1970s. In that earlier form, talk did not separate text from each user. Thus, if each user were to type simultaneously, characters from each user were intermingled. Since slow teleprinter keyboards were used at the time (11 characters per second maximum), users often could not wait for each other to finish. It was common etiquette for a long typing user to stop when intermingling occurs to see the listener's interrupting response. This is much the same as interrupting a long monologue when speaking in person.

The more modern Unix version of talk uses curses to break the terminal into multiple zones for each user, thus avoiding intermingling text.

A popular program called "flash", which sent malformed information via the talk protocol, was frequently used by pranksters to corrupt the terminal output of the unlucky target in the early 1990s. It did this by including terminal commands in the field normally designated for providing the name of the person making the request. When the victim would receive the talk request, the name of the person sending the request would be displayed on their screen. This would cause the terminal commands to execute, rendering the person's display unreadable until they reset it. Later versions of talk blocked flash attempts and alerted the user that one had taken place. Later it became clear that, by sending different terminal commands, it is even possible to have the user execute commands. As it has proven impossible to fix all programs that output untrusted data to the terminal, modern terminal emulators have been rewritten to block this attack, though some may still be vulnerable.^[1][2]

See also[link]

• List of Unix programs
• Write (Unix) – program for sending messages for unix (since 1975)

Notes[link]

For information about Wikipedia talk pages, see Wikipedia:Talk page

Look up talk in Wiktionary, the free dictionary.

Talk may refer to:

• Conversation, interactive communication between two or more people
• Speech, the production of a spoken language
• Interaction, face to face conversations

Software[link]

• Google Talk, a Windows- and web-based instant messaging program
• talk (software), a Unix messaging program
• AppleTalk, an early networking protocol designed by Apple for their Macintosh computers

Music[link]

• Talk (Yes album)
• Talk (Paul Kelly album)
• "Talk" (song), by Coldplay
• "Talk", a song by Tracy Bonham on the album Liverpool Sessions
• Talk Talk, a popular British rock group active from 1981 to 1991
• "Talking", a song by British rock band The Rifles
• "Talk", a song by Redgum from their 1986 album Midnight Sun

Other meanings[link]

• Talk (film)
• Talk (magazine)
• Talk show, a broadcast program format
• Talk radio, a radio format
• Talk (play)

This disambiguation page lists articles associated with the same title. If an internal link led you here, you may wish to change the link to point directly to the intended article.

Computer software, or just software, is a collection of computer programs and related data that provides the instructions for telling a computer what to do and how to do it. Software refers to one or more computer programs and data held in the storage of the computer for some purposes. In other words, software is a set of programs, procedures, algorithms and its documentation concerned with the operation of a data processing system. Program software performs the function of the program it implements, either by directly providing instructions to the computer hardware or by serving as input to another piece of software. The term was coined to contrast to the old term hardware (meaning physical devices). In contrast to hardware, software "cannot be touched".^[1] Software is also sometimes used in a more narrow sense, meaning application software only. Sometimes the term includes data that has not traditionally been associated with computers, such as film, tapes, and records.^[2]

Computer software is so called to distinguish it from computer hardware, which encompasses the physical interconnections and devices required to store and execute (or run) the software. At the lowest level, executable code consists of machine language instructions specific to an individual processor. A machine language consists of groups of binary values signifying processor instructions that change the state of the computer from its preceding state. Programs are an ordered sequence of instructions for changing the state of the computer in a particular sequence. It is usually written in high-level programming languages that are easier and more efficient for humans to use (closer to natural language) than machine language. High-level languages are compiled or interpreted into machine language object code. Software may also be written in an assembly language, essentially, a mnemonic representation of a machine language using a natural language alphabet. Assembly language must be assembled into object code via an assembler.

History[link]

This section may need to be rewritten entirely to comply with Wikipedia's quality standards. You can help. The discussion page may contain suggestions. (January 2012)

The first theory about software was proposed by Alan Turing in his 1935 essay Computable numbers with an application to the Entscheidungsproblem (Decision problem).^[3] The term "software" was first used in print by John W. Tukey in 1958.^[4] Colloquially, the term is often used to mean application software. In computer science and software engineering, software is all information processed by computer system, programs and data.^[4] The academic fields studying software are computer science and software engineering.

The history of computer software is most often traced back to the first software bug in 1946^{[citation needed]}. As more and more programs enter the realm of firmware, and the hardware itself becomes smaller, cheaper and faster as predicted by Moore's law, elements of computing first considered to be software, join the ranks of hardware. Most hardware companies today have more software programmers on the payroll than hardware designers^{[citation needed]}, since software tools have automated many tasks of Printed circuit board engineers. Just like the Auto industry, the Software industry has grown from a few visionaries operating out of their garage with prototypes. Steve Jobs and Bill Gates were the Henry Ford and Louis Chevrolet of their times^{[citation needed]}, who capitalized on ideas already commonly known before they started in the business. In the case of Software development, this moment is generally agreed to be the publication in the 1980s of the specifications for the IBM Personal Computer published by IBM employee Philip Don Estridge. Today his move would be seen as a type of crowd-sourcing.

Until that time, software was bundled with the hardware by Original equipment manufacturers (OEMs) such as Data General, Digital Equipment and IBM^{[citation needed]}. When a customer bought a minicomputer, at that time the smallest computer on the market, the computer did not come with Pre-installed software, but needed to be installed by engineers employed by the OEM. Computer hardware companies not only bundled their software, they also placed demands on the location of the hardware in a refrigerated space called a computer room. Most companies had their software on the books for 0 dollars, unable to claim it as an asset (this is similar to financing of popular music in those days). When Data General introduced the Data General Nova, a company called Digidyne wanted to use its RDOS operating system on its own hardware clone. Data General refused to license their software (which was hard to do, since it was on the books as a free asset), and claimed their "bundling rights". The Supreme Court set a precedent called Digidyne v. Data General in 1985. The Supreme Court let a 9th circuit decision stand, and Data General was eventually forced into licensing the Operating System software because it was ruled that restricting the license to only DG hardware was an illegal tying arrangement.^[5] Soon after, IBM 'published' its DOS source for free,^{[citation needed]} and Microsoft was born. Unable to sustain the loss from lawyer's fees, Data General ended up being taken over by EMC Corporation. The Supreme Court decision made it possible to value software, and also purchase Software patents. The move by IBM was almost a protest at the time. Few in the industry believed that anyone would profit from it other than IBM (through free publicity). Microsoft and Apple were able to thus cash in on 'soft' products. It is hard to imagine today that people once felt that software was worthless without a machine. There are many successful companies today that sell only software products, though there are still many common software licensing problems due to the complexity of designs and poor documentation, leading to patent trolls.

With open software specifications and the possibility of software licensing, new opportunities arose for software tools that then became the de facto standard, such as DOS for operating systems, but also various proprietary word processing and spreadsheet programs. In a similar growth pattern, proprietary development methods became standard Software development methodology.

Types of software[link]

A layer structure showing where the operating system software and application software are situated while running on a typical desktop computer

Software includes all the various forms and roles that digitally stored data may have and play in a computer (or similar system), regardless of whether the data is used as code for a CPU, or other interpreter, or whether it represents other kinds of information. Software thus encompasses a wide array of products that may be developed using different techniques such as ordinary programming languages, scripting languages, microcode, or an FPGA configuration.

The types of software include web pages developed in languages and frameworks like HTML, PHP, Perl, JSP, ASP.NET, XML, and desktop applications like OpenOffice.org, Microsoft Word developed in languages like C, C++, Objective-C, Java, C#, or Smalltalk. Application software usually runs on an underlying software operating systems such as Linux or Microsoft Windows. Software (or firmware) is also used in video games and for the configurable parts of the logic systems of automobiles, televisions, and other consumer electronics.

Practical computer systems divide software systems into three major classes^{[citation needed]}: system software, programming software and application software, although the distinction is arbitrary, and often blurred.

System software[link]

System software is computer software designed to operate the computer hardware to provide basic functionality and to provide a platform for running application software.^[6][7] System software includes device drivers, operating systems, servers, utilities, and window systems.

System software is responsible for managing a variety of independent hardware components, so that they can work together harmoniously. Its purpose is to unburden the application software programmer from the often complex details of the particular computer being used, including such accessories as communications devices, printers, device readers, displays and keyboards, and also to partition the computer's resources such as memory and processor time in a safe and stable manner.

Programming software[link]

Programming software include tools in the form of programs or applications that software developers use to create, debug, maintain, or otherwise support other programs and applications. The term usually refers to relatively simple programs such as compilers, debuggers, interpreters, linkers, and text editors, that can be combined together to accomplish a task, much as one might use multiple hand tools to fix a physical object. Programming tools are intended to assist a programmer in writing computer programs, and they may be combined in an integrated development environment (IDE) to more easily manage all of these functions.

Application software[link]

Application software is developed to perform in any task that benefits from computation. It is a set of programs that allows the computer to perform a specific data processing job for the user. It is a broad category, and encompasses software of many kinds, including the internet browser being used to display this page. This category includes:

• Business software
• Computer-aided design
• Databases
• Decision-making software
• Educational software
• Image editing
• Industrial automation
• Mathematical software
• Medical software
• Molecular modeling software
• Quantum chemistry and solid state physics software
• Simulation software
• Spreadsheets
• Telecommunications (i.e., the Internet and everything that flows on it)
• Video editing software
• Video games
• Word processing

Software topics[link]

Architecture[link]

Users often see things differently than programmers. People who use modern general purpose computers (as opposed to embedded systems, analog computers and supercomputers) usually see three layers of software performing a variety of tasks: platform, application, and user software.

• Platform software: Platform includes the firmware, device drivers, an operating system, and typically a graphical user interface which, in total, allow a user to interact with the computer and its peripherals (associated equipment). Platform software often comes bundled with the computer. On a PC you will usually have the ability to change the platform software.
• Application software: Application software or Applications are what most people think of when they think of software. Typical examples include office suites and video games. Application software is often purchased separately from computer hardware. Sometimes applications are bundled with the computer, but that does not change the fact that they run as independent applications. Applications are usually independent programs from the operating system, though they are often tailored for specific platforms. Most users think of compilers, databases, and other "system software" as applications.
• User-written software: End-user development tailors systems to meet users' specific needs. User software include spreadsheet templates and word processor templates. Even email filters are a kind of user software. Users create this software themselves and often overlook how important it is. Depending on how competently the user-written software has been integrated into default application packages, many users may not be aware of the distinction between the original packages, and what has been added by co-workers.

Documentation[link]

Most software has software documentation so that the end user can understand the program, what it does, and how to use it. Without clear documentation, software can be hard to use—especially if it is very specialized and relatively complex like Photoshop or AutoCAD.

Developer documentation may also exist, either with the code as comments and/or as separate files, detailing how the programs works and can be modified.

Library[link]

An executable is almost always not sufficiently complete for direct execution. Software libraries include collections of functions and functionality that may be embedded in other applications. Operating systems include many standard Software libraries, and applications are often distributed with their own libraries.

Standard[link]

Since software can be designed using many different programming languages and in many different operating systems and operating environments, software standard is needed so that different software can understand and exchange information between each other. For instance, an email sent from a Microsoft Outlook should be readable from Yahoo! Mail and vice versa.

Execution[link]

Computer software has to be "loaded" into the computer's storage (such as the hard drive or memory). Once the software has loaded, the computer is able to execute the software. This involves passing instructions from the application software, through the system software, to the hardware which ultimately receives the instruction as machine code. Each instruction causes the computer to carry out an operation – moving data, carrying out a computation, or altering the control flow of instructions.

Data movement is typically from one place in memory to another. Sometimes it involves moving data between memory and registers which enable high-speed data access in the CPU. Moving data, especially large amounts of it, can be costly. So, this is sometimes avoided by using "pointers" to data instead. Computations include simple operations such as incrementing the value of a variable data element. More complex computations may involve many operations and data elements together.

Quality and reliability[link]

Software quality is very important, especially for commercial and system software like Microsoft Office, Microsoft Windows and Linux. If software is faulty (buggy), it can delete a person's work, crash the computer and do other unexpected things. Faults and errors are called "bugs." Many bugs are discovered and eliminated (debugged) through software testing. However, software testing rarely – if ever – eliminates every bug; some programmers say that "every program has at least one more bug" (Lubarsky's Law). All major software companies, such as Microsoft, Novell and Sun Microsystems, have their own software testing departments with the specific goal of just testing. Software can be tested through unit testing, regression testing and other methods, which are done manually, or most commonly, automatically, since the amount of code to be tested can be quite large. For instance, NASA has extremely rigorous software testing procedures for many operating systems and communication functions. Many NASA based operations interact and identify each other through command programs called software. This enables many people who work at NASA to check and evaluate functional systems overall. Programs containing command software enable hardware engineering and system operations to function much easier together.

License[link]

The software's license gives the user the right to use the software in the licensed environment. Some software comes with the license when purchased off the shelf, or an OEM license when bundled with hardware. Other software comes with a free software license, granting the recipient the rights to modify and redistribute the software. Software can also be in the form of freeware or shareware.

Patents[link]

Software can be patented in some but not all countries; however, software patents can be controversial in the software industry with many people holding different views about it. The controversy over software patents is about specific algorithms or techniques that the software contains, which may not be duplicated by others and considered intellectual property and copyright infringement depending on the severity.

Design and implementation[link]

Design and implementation of software varies depending on the complexity of the software. For instance, design and creation of Microsoft Word software will take much more time than designing and developing Microsoft Notepad because of the difference in functionalities in each one.

Software is usually designed and created (coded/written/programmed) in integrated development environments (IDE) like Eclipse, Emacs and Microsoft Visual Studio that can simplify the process and compile the program. As noted in different section, software is usually created on top of existing software and the application programming interface (API) that the underlying software provides like GTK+, JavaBeans or Swing. Libraries (APIs) are categorized for different purposes. For instance, JavaBeans library is used for designing enterprise applications, Windows Forms library is used for designing graphical user interface (GUI) applications like Microsoft Word, and Windows Communication Foundation is used for designing web services. Underlying computer programming concepts like quicksort, hashtable, array, and binary tree can be useful to creating software. When a program is designed, it relies on the API. For instance, if a user is designing a Microsoft Windows desktop application, he/she might use the .NET Windows Forms library to design the desktop application and call its APIs like Form1.Close() and Form1.Show()^[8] to close or open the application and write the additional operations him/herself that it need to have. Without these APIs, the programmer needs to write these APIs him/herself. Companies like Sun Microsystems, Novell, and Microsoft provide their own APIs so that many applications are written using their software libraries that usually have numerous APIs in them.

Computer software has special economic characteristics that make its design, creation, and distribution different from most other economic goods.^{[specify][9][10]}

A person who creates software is called a programmer, software engineer, software developer, or code monkey, terms that all have a similar meaning.

Industry and organizations[link]

A great variety of software companies and programmers in the world comprise a software industry. Software can be quite a profitable industry: Bill Gates, the founder of Microsoft was the richest person in the world in 2009 largely by selling the Microsoft Windows and Microsoft Office software products. The same goes for Larry Ellison, largely through his Oracle database software. Through time the software industry has become increasingly specialized.

Non-profit software organizations include the Free Software Foundation, GNU Project and Mozilla Foundation. Software standard organizations like the W3C, IETF develop software standards so that most software can interoperate through standards such as XML, HTML, HTTP or FTP.

Other well-known large software companies include Novell, SAP, Symantec, Adobe Systems, and Corel, while small companies often provide innovation.

See also[link]

	Software portal
	Free software portal

• List of software
• Personal computer hardware

References[link]

External links[link]

Wikimedia Commons has media related to: Software

Look up software in Wiktionary, the free dictionary.

• Software Wikia

Eben Moglen
Born	(1959-07-13) July 13, 1959 (age 52)
Occupation	Professor of Law and Legal history at Columbia University, Director-Counsel and Chairman, Software Freedom Law Center
Website
http://emoglen.law.columbia.edu

Eben Moglen is a professor of law and legal history at Columbia University, and is the founder, Director-Counsel and Chairman of Software Freedom Law Center, whose client list includes numerous pro bono clients, such as the Free Software Foundation.

Professional biography[link]

Moglen started out as a computer programming language designer^[1] and then received his bachelor's degree from Swarthmore College in 1980, where he won the Hicks Prize for Literary Criticism. In 1985, he received a Master of Philosophy in history and a JD from Yale University. He has held visiting appointments at Harvard University, Tel Aviv University and the University of Virginia since 1987.

He was a law clerk to Justice Thurgood Marshall (1986–87 term). He joined the faculty of Columbia Law School in 1987, and was admitted to the New York bar in 1988.^[2] He received a Ph.D. in history from Yale University in 1993. Moglen serves as a director of the Public Patent Foundation.

Moglen was part of Philip Zimmermann's defense team, when Zimmermann was being investigated over the export of Pretty Good Privacy, a public key encryption system, under US export laws.^[3]

In 2003 he received the EFF Pioneer Award. In February 2005, he founded the Software Freedom Law Center.

Moglen is closely involved with the Free Software Foundation, serving as general counsel since 1994 and board member from 2000 to 2007. As counsel, Moglen was charged with enforcing the GNU General Public License (GPL) on behalf of the FSF,^[4] and later became heavily involved with drafting version 3 of the GPL. On April 23, 2007 he announced in a blog post that he would be stepping down from the board of directors of the Free Software Foundation. Moglen stated that after the GPLv3 Discussion Draft 3 had been released, he wanted to devote more time to writing, teaching, and the Software Freedom Law Center.^[5]

Freedom Box Foundation[link]

In February 2011, Moglen created the Freedom Box Foundation to design software for a very small server called the FreedomBox. The FreedomBox is an affordable personal server which runs only free software, with a focus on anonymous and secure communication.^[6] The foundation's purpose is to raise funds for the creation and expansion of software for the FreedomBox. Moglen hopes for upwards of $500,000 to be able to launch FreedomBox officially within a year.^[7]

Stances on free software[link]

Moglen says that free software is a fundamental requirement for a democratic and free society in which we are surrounded by and dependent upon technical devices. Only if controlling these devices is open to all via free software, can we balance power equally.^[8]

Moglen's Metaphorical Corollary to Faraday's Law is the idea that the information appearance and flow between the human minds connected via the Internet works like induction. Hence Moglen's phrase "Resist the resistance!" (i.e. remove anything that inhibits the flow of information).^[9]

Statements and perspectives[link]

This section of a biographical article needs additional citations for verification. Please help by adding reliable sources. Contentious material about living persons that is unsourced or poorly sourced must be removed immediately, especially if potentially libelous or harmful. (May 2007)

Moglen at GPL V3 conference in Bangalore, 2006

While speaking in New Delhi, India, in 2006, he remarked: "Anything that is worth copying is worth sharing." His other quotes: "The more we give away, the richer we become." And: "Note how even the smallest encounter with Free Software can make a man cheerful about the future of our judge" (said after hearing a judge of the Allahabad high court, India speak on the subject).^{[citation needed]}

Moglen believes the idea of proprietary software is as ludicrous as having "proprietary mathematics" or "proprietary geometry". This would convert the subjects from "something you can learn" into "something you must buy", he has argued. He points out that software is among the "things which can be copied infinitely over and over again, without any further costs".

Moglen has criticized what he calls the "reification of selfishness". He has said, "A world full of computers which you can't understand, can't fix and can't use (because it is controlled by inaccessible proprietary software) is a world controlled by machines."

He has called on lawyers to help the Free Software movement, saying: "Those who want to share their code can make products and share their work without additional legal risks." He urged his legal colleagues, "It's worth giving up a little in order to produce a sounder ecology for all. Think kindly about the idea of sharing."

Moglen sketches the history of copyright law as a form of industrial regulation, and analyses how the changes in technology have thrown the roles created by those laws into crisis. As part of an interview for Steal This Film in April 2007

Moglen has criticized trends which result in "excluding people from knowledge". On the issue of Free Software versus proprietary software, he has argued that "much has been said by the few who stand to lose". Moglen calls for a "sensible respect for both the creators and users" of software code. In general, this concept is a part of what Moglen has termed a "revolution" against the privileged owners of media, distribution channels, and software. On March 13, 2009, in a speech given at Seattle University, Moglen said of the free software movement that, "'When everybody owns the press, then freedom of the press belongs to everybody' seems to be the inevitable inference, and that’s where we are moving, and when the publishers get used to that, they’ll become us, and we’ll become them, and the first amendment will mean: 'Congress shall make no law […] abridging freedom of speech, or of the press […].', not – as they have tended to argue in the course of the 20th century – 'Congress shall make no law infringing the sacred right of the Sulzbergers to be different.'.".^[10]

On the subject of Digital Rights Management, Moglen once said, "We also live in a world in which the right to tinker is under some very substantial threat. This is said to be because movie and record companies must eat. I will concede that they must eat. Though, like me, they should eat less."^[11]

References[link]

External links[link]

more links can be found on wikisource

Wikiquote has a collection of quotations related to: Eben Moglen

Wikisource has original works written by or about: Eben Moglen

Wikimedia Commons has media related to: Eben Moglen

Wikinews has related news: France : Open World Forum 2010

Free software portal

• Eben Moglen's webpage at Columbia University
• ‘A lawyer who is also idealist - how refreshing’, March 30, 2006 interview in The Guardian.

Lectures / papers[link]

• Why Political Liberty Depends on Software Freedom More Than Ever, transcript of keynote speech at the 2011 FOSDEM conference in Brussels on February 5, 2011
• Freedom in the cloud: Software Freedom, Privacy, and Security for Web 2.0 and Cloud Computing, transcript of speech given to the Internet Society's New York branch on February 5, 2010
• Anarchism Triumphant: Free Software and the Death of Copyright - August 1999 PDF
• The dotCommunist Manifesto: Video of talk at UNC-Chapel Hill, Howard W. Odum Institute, 51 min, November 1, 2001
  • Transcript
• The Future of the Net ISOC-NY talk (May 2002) (audio)
• The dotCommunist Manifesto - January 2003 PDF
• Opening keynote at Wizards of OS3, Berlin, June 10, 2004, 57 min
  • Video, 20 MiB and 131 MiB MPEG videos
  • Audio, 64 kbit/s 26 MiB, 96 kbit/s 39 MiB MP3, and 88 kbit/s 36 MiB Ogg Vorbis formats
  • Text version, 42 KiB HTML, also available in PDF and PostScript formats
• Free Software and Free Media ISOC-NY talk (May 2006) (video / audio)
• Framing the Debate: Free Expression versus Intellectual Property, the Next Fifty Years paper (February 2007)
• Patent Law at a Crossroads: Bilski and Beyond Cardozo School of Law, NYC (November 2, 2009) (video/audio)
• Freedom in the Cloud: Software Freedom, Privacy and Security for Web 2.0 and Cloud Computing ISOC-NY Talk (February 5, 2010) (video/audio)
• Making History: Israeli Law and Historical Reconstruction, (2000)
• Freeing the Mind: Free Software and the Death of Proprietary Culture (2003)
• So Much for Savages:Navajo 1, Government 0 in Final Moments of Play (1999)

v t e GNU Project History GNU Manifesto Free Software Foundation Europe India Latin America History of free software Licenses GNU General Public License GNU Lesser General Public License Affero General Public License GNU Free Documentation License GPL linking exception Software GNU (variants) Hurd GNOME Bash GCC GNU Emacs glibc Coreutils Build system GNUnet Gnuzilla (IceCat) Gnash more... Public speakers Alexandre Oliva Benjamin Mako Hill Bradley M. Kuhn Eben Moglen Federico Heinz Georg C. F. Greve Loïc Dachary Ricardo Galli Richard Stallman Robert J. Chassell John Sullivan Other topics GNU/Linux naming controversy Revolution OS BadVista Defective by Design

This article relies largely or entirely upon a single source. Please help improve this article by introducing citations to additional sources. Discussion about the problems with the sole source used may be found on the talk page. (October 2007)

Martin Fowler is an author and international speaker on software development, specializing in object-oriented analysis and design, UML, patterns, and agile software development methodologies, including extreme programming.

Fowler started working with software in the early 1980s^[1] and has written six books on the topic of software development (see Publications). In March 2000, he became Chief Scientist at ThoughtWorks, a systems integration and consulting company.^[1]

Fowler is a member of the Agile Alliance and helped create the Manifesto for Agile Software Development in 2001, along with more than 15 co-authors. He maintains a bliki, a mix of blog and wiki. He popularized the term Dependency Injection^[2] as a form of Inversion of Control.

Fowler was born in Walsall, England, and lived in London a decade before moving to United States in 1994. He lives near Boston, Massachusetts in the suburb of Melrose.^[1]

He went to Queen Mary's Grammar School for his secondary education.

Publications[link]

• Fowler, Martin. Analysis Patterns: Reusable Object Models. Addison-Wesley. ISBN 0-201-89542-0. 
• Fowler, Martin; Kent Beck. Planning Extreme Programming. Addison-Wesley. ISBN 0-201-71091-9. 
• Fowler, Martin (September 2003). UML Distilled: A Brief Guide to the Standard Object Modeling Language (3rd ed. ed.). Addison-Wesley. ISBN 0-321-19368-7. 
• Fowler, Martin; Kent Beck, John Brant, William Opdyke, and Don Roberts (June 1999). Refactoring: Improving the Design of Existing Code. Addison-Wesley. ISBN 0-201-48567-2. 
• Fowler, Martin; David Rice, Matthew Foemmel, Edward Hieatt, Robert Mee, and Randy Stafford (November 2002). Patterns of Enterprise Application Architecture. Addison-Wesley. ISBN 0-321-12742-0.  (Jolt productivity award 2003 ^[3])
• Fowler, Martin (September 2010). Domain-Specific Languages. Addison-Wesley. ISBN 978-0-321-71294-3. 

Online presentations[link]

• List of talks on Martin's website
• Keynote at RailsConf 2006
• An Introduction to Language Oriented Programming at JAOO 2006
• The Yawning Crevasse of Doom at QCon London 2007 (with Dan North)
• Does My Bus Look Big In This? at QCon London 2008 (with Jim Webber)
• Forging a New Alliance at ThoughtWorks Quarterly Technology Briefing, October 2008 (with Scott Shaw)
• Agilists and Architects: Allies not Adversaries at QCon San Francisco 2008 (with Rebecca Parsons)
• Technology in the Obama Campaign at QCon London 2009 (with Zack Exley)
• Three Years of Real-World Ruby at QCon London 2009
• The Evolving Panorama of Data at QCon London 2012 (with Rebecca Parsons)

References[link]

External links[link]

• Home Page of Martin Fowler
• A Conversation with Martin Fowler
• The New Methodology, a paper on lightweight software development methodology
• Dependency Injection