"Concept maps have long provided visual languages widely used in many different disciplines and application domains. Abstractly, they are sorted graphs visually represented as nodes having a type, name and content, some of which are linked by arcs. Concretely, they are structured diagrams having discipline- and domain-specific interpretations for their user communities, and, sometimes, formally defining computer data structures. Concept maps have been used for a wide range of purposes and it would be useful to make such usage available over the World Wide Web." (Brian R Gaines, "WebMap: Concept Mapping on the Web", 2001)
"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, [interview] 2003)
"Science does not speak of the world in the language of words alone, and in many cases it simply cannot do so. The natural language of science is a synergistic integration of words, diagrams, pictures, graphs, maps, equations, tables, charts, and other forms of visual and mathematical expression. [… Science thus consists of] the languages of visual representation, the languages of mathematical symbolism, and the languages of experimental operations." (Jay Lemke, "Teaching all the languages of science: Words, symbols, images and actions", 2003)
"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." (Martin Fowler," UML Distilled: A Brief Guide to the Standard Object Modeling", 2004)
"In mathematics a good diagram is an invaluable aid to clear reasoning, whereas a bad one can seriously mislead. But it is not often that a diagram is good enough to suggest fresh avenues of inquiry altogether." (Anthony W F Edwards, "Cogwheels of the mind: The story of Venn diagrams", 2004)
"Good diagrams clarify. Very good diagrams force the ideas upon the viewer. The best diagrams compellingly embody the ideas themselves." (R W Oldford & W H Cherry, "Picturing Probability: the poverty of Venn diagrams, the richness of Eikosograms", 2006)
"A diagram is a graphic shorthand. Though it is an ideogram, it is not necessarily an abstraction. It is a representation of something in that it is not the thing itself. In this sense, it cannot help but be embodied. It can never be free of value or meaning, even when it attempts to express relationships of formation and their processes. At the same time, a diagram is neither a structure nor an abstraction of structure." (Peter Eisenman, "Written Into the Void: Selected Writings", 1990-2004, 2007)
"A modeling language is usually based on some kind of computational model, such as a state machine, data flow, or data structure. The choice of this model, or a combination of many, depends on the modeling target. Most of us make this choice implicitly without further thinking: some systems call for capturing dynamics and thus we apply for example state machines, whereas other systems may be better specified by focusing on their static structures using feature diagrams or component diagrams. For these reasons a variety of modeling languages are available." (Steven Kelly & Juha-Pekka Tolvanen, "Domain-specific Modeling", 2008)
"What was clearly useful was the use of diagrams to prove certain results either in algebraic topology, homological algebra or algebraic geometry. It is clear that doing category theory, or simply applying category theory, implies manipulating diagrams: constructing the relevant diagrams, chasing arrows by going via various paths in diagrams and showing they are equal, etc. This practice suggests that diagram manipulation, or more generally diagrams, constitutes the natural syntax of category theory and the category-theoretic way of thinking. Thus, if one could develop a formal language based on diagrams and diagrams manipulation, one would have a natural syntactical framework for category theory. However, moving from the informal language of categories which includes diagrams and diagrammatic manipulations to a formal language based on diagrams and diagrammatic manipulations is not entirely obvious." (Jean-Pierre Marquis, "From a Geometrical Point of View: A Study of the History and Philosophy of Category Theory", 2009)
"Diagrams are information graphics that are made up primarily of geometric shapes, such as rectangles, circles, diamonds, or triangles, that are typically (but not always) interconnected by lines or arrows. One of the major purposes of a diagram is to show how things, people, ideas, activities, etc. interrelate and interconnect. Unlike quantitative charts and graphs, diagrams are used to show interrelationships in a qualitative way." (Robbie T Nakatsu, "Diagrammatic Reasoning in AI", 2010)
"What advantages do diagrams have over verbal descriptions in promoting system understanding? First, by providing a diagram, massive amounts of information can be presented more efficiently. A diagram can strip down informational complexity to its core - in this sense, it can result in a parsimonious, minimalist description of a system. Second, a diagram can help us see patterns in information and data that may appear disordered otherwise. For example, a diagram can help us see mechanisms of cause and effect or can illustrate sequence and flow in a complex system. Third, a diagram can result in a less ambiguous description than a verbal description because it forces one to come up with a more structured description." (Robbie T Nakatsu, "Diagrammatic Reasoning in AI", 2010)
"[…] a conceptual model is a diagram connecting variables and constructs based on theory and logic that displays the hypotheses to be tested." (Mary Wolfinbarger Celsi et al, "Essentials of Business Research Methods", 2011)
"Diagrams furnish only approximate information. They do not add anything to the meaning of the data and, therefore, are not of much use to a statistician or research worker for further mathematical treatment or statistical analysis. On the other hand, graphs are more obvious, precise and accurate than the diagrams and are quite helpful to the statistician for the study of slopes, rates of change and estimation, (interpolation and extrapolation), wherever possible." (S C Gupta & Indra Gupta, "Business Statistics", 2013)
"Systems archetypes thus provide a good starting theory from which we can develop further insights into the nature of a particular system. The diagram that results from working with an archetype should not be viewed as the 'truth', however, but rather a good working model of what we know at any point in time." (Daniel H Kim, "Systems Archetypes as Dynamic Theories", The Systems Thinker Vol. 24 (1), 2013)
"As mathematics gets more abstract, diagrams become more and more prominent as the ways that things fit together abstractly become both more subtle and more important. Moreover, the diagram often sums up the situation more succinctly than the explanation in words, [..]" (Eugenia Cheng, "Beyond Infinity: An Expedition to the Outer Limits of Mathematics", 2017)
"Models are formal structures represented in mathematics and diagrams that help us to understand the world. Mastery of models improves your ability to reason, explain, design, communicate, act, predict, and explore." (Scott E Page, "The Model Thinker", 2018)
No comments:
Post a Comment