“Graphical design notations have been with us for a while… their primary value is in communication and understanding. A good diagram can often help communicate ideas about a design, particularly when you want to avoid a lot of details. Diagrams can also help you understand either a software system or a business process. As part of a team trying to figure out something, diagrams both help understanding and communicate that understanding throughout a team. Although they aren't, at least yet, a replacement for textual programming languages, they are a helpful assistant… Of these graphical notations, the UML's importance comes from its wide use and standardization within the OO development community. The UML has become not only the dominant graphical notation within the OO world but also a popular technique in non-OO circles.”

— Martin Fowler

Source: UML Distilled: A Brief Guide to the Standard Object Modeling, 2004, p. xxvi

Adopted from Wikiquote. Last update June 3, 2021. History

Help us to complete the source, original and additional information

Do you have more details about the quote "Graphical design notations have been with us for a while… their primary value is in communication and understanding. A …" by Martin Fowler?

Martin Fowler 18

British programmer 1963

Related quotes

“Steve Mellor and I independently came up with a characterization of the three modes in which people use the UML: sketch, blueprint, and programming language. By far the most common of the three, at least to my biased eye, is UML as sketch. In this usage, developers use the UML to help communicate some aspects of a system. As with blueprints, you can use sketches in a forward-engineering or reverse-engineering direction. Forward engineering draws a UML diagram before you write code, while reverse engineering builds a UML diagram from existing code in order to help understand it.”

Martin Fowler (1963) British programmer

Source: A Brief Guide to the Standard Object Modeling Language, 2004, p. 2

“Design is really an act of communication, which means having a deep understanding of the person with whom the designer is communicating.”

Donald A. Norman book The Design of Everyday Things

Source: The Design of Everyday Things

“Ever wish you could draw a few diagrams, press a button, and have a working software system that meets your needs? Sound like magic? Perhaps, but that’s a major part of the Executable UML vision. The basic idea is that you will use a CASE tool to develop detailed UML diagrams and then supplement them by specifications written in a formal language, presumably the OMG’s Object Constraint Language (OCL). The basic idea behind Executable UML is that systems can be modeled at a higher level of abstraction than source code, simulated to support validation of your efforts, and then translated into efficient code. This higher-level of abstraction should help to avoid premature design, enable you to change your system as your requirements evolve, and to delay implementation decisions until the last minute.”

Scott W. Ambler (1966) Canadian software engineer/consultant/author

Source: Agile Modeling: Effective Practices for eXtreme Programming and the Unified Process (2002), p. 172

“Creating a modeling language that is also an executable language has long been a goal of the software community. Many years ago, in 1968 to be exact, while working with software components to successfully develop a telecommunications system, we created a modeling language that was the forerunner to UML. To model components we used sequence diagrams, collaboration diagrams, and state transition diagrams (a combination of state charts and activity diagrams). Our modeling language then seamlessly translated the component models into code. Each code component was in its turn compiled into an executable component that was deployed in our computer system. The computer system was a component management system—thus we had "components all the way down."”

Stephen J. Mellor (1952) British computer scientist

Source: Executable Uml: A Foundation for Model-Driven Architecture, 2002, p. xxiii: Foreword.

“Data is transformed into graphics to understand. A map, a diagram are documents to be interrogated. But understanding means integrating all of the data. In order to do this it’s necessary to reduce it to a small number of elementary data. This is the objective of the “data treatment” be it graphic or mathematic.”

Jacques Bertin (1918–2010) French geographer and cartographer

About the true value of graphics
Interview with Jacques Bertin (2003)

“It's not about having things figured out, or about communicating with other people, trying to make them understand what you understand. It's about a chicken dinner at a drive-in. A soft pillow. Things that don't need explaining.”

Ann Beattie (1947) Short story writer, novelist, professor

Source: Walks with Men

“A lot of musicians don’t learn the business. You just have to be well-rounded in both areas. You have to understand publishing. You have to understand how you make money, what’s in demand, what helps you make the most out of your talent.”

Bradley Joseph (1965) Composer, pianist, keyboardist, arranger, producer, recording artist

Showcase article: [Polta, Anne, Continuing Journey: Bradley Joseph sustains music career with songwriting, recording, West Central Tribune, 2007-02-08, http://www.newspaperprints.com/index.cfm?page=search_results&paper=West%20Central%20Tribune&selectedDate=2007-02-08&start=16&perpage=5, 2007-02-18]

“A graphic is a diagram when correspondences on the plane can be established among all elements of another component.”

Jacques Bertin (1918–2010) French geographer and cartographer

Source: Semiology of graphics (1967/83), p. 193

“Software has to be designed by hackers who understand design, not designers who know a little about software. If you can't design software as well as implement it, don't start a startup.”

Paul Graham (1964) English programmer, venture capitalist, and essayist

"The Other Road Ahead" http://www.paulgraham.com/road.html, September 2001

“Communication is — start by understanding — your own understanding about people. Even though you want them to understand you, you know, it is — unless you understand people, it is almost impossible.”

Shunryu Suzuki (1904–1971) Japanese Buddhist missionary

Sun-Faced Buddha, Moon-Faced Buddha lecture at the Zen Mountain Center (17 August 1971) http://suzukiroshi.sfzc.org/archives/index.cgi/710817V.html
Context: Communication is — start by understanding — your own understanding about people. Even though you want them to understand you, you know, it is — unless you understand people, it is almost impossible. Don't you think so? Only when you understand people, they may understand you. So even though you do not say anything, if you understand people there is some communication.

Help us to complete the source, original and additional information

Martin Fowler 18

Related quotes

Related topics