John Zachman (1934) American computer scientist
Source: A Framework for Information Systems Architecture, 1987, p. 281 as cited in: San Murugesan, Yogesh Deshpande (2001) Web Engineering: Managing Diversity and Complexity of Web. p, 126
Source: A Framework for Information Systems Architecture, 1987, p. 283. cited in: Stephen L. Montgomery (1994) Object-oriented information engineering: : analysis, design, and implementation. p. 279
John Zachman (1934) American computer scientist
Source: A Framework for Information Systems Architecture, 1987, p. 281 as cited in: San Murugesan, Yogesh Deshpande (2001) Web Engineering: Managing Diversity and Complexity of Web. p, 126
John Zachman (1934) American computer scientist
Zachman (1986) as cited in: Peter Bernus, Kai Mertins, Günter Schmidt (2005) Handbook on Architectures of Information Systems. p. 544
Mark S. Fox (1952) Canadian computer scientist and Professor of Industrial Engineering
Michael Grüninger and Mark S. Fox (1995) " The role of competency questions in enterprise engineering http://www.eil.utoronto.ca/enterprise-modelling/papers/benchIFIP94.pdf." Benchmarking—Theory and Practice. Springer US, 1995. 22-31.
Dana Arnold (1961) Middlessex uni prof
Source: Reading Architectural History (2002), Ch. 1 : Reading the past : What is architectural history?
John Zachman (1934) American computer scientist
Zachman (1987) cited in: Antonio Laganà, Marina L. Gavrilova, Vipin Kumar (2004) Computational Science and Its Applications -- ICCSA 2004. p. 604
James Martin (author) (1933–2013) British information technology consultant and writer
Source: The great transition (1995), p. 58; As cited in: Jan Hoogervorst (2009, p. 9)
Marvin Minsky (1927–2016) American cognitive scientist
Music, Mind, and Meaning (1981)
Context: What is the difference between merely knowing (or remembering, or memorizing) and understanding?... A thing or idea seems meaningful only when we have several different ways to represent it — different perspectives and different associations.... Then we can turn it around in our minds, so to speak: however it seems at the moment, we can see it another way and we never come to a full stop. In other words, we can 'think' about it. If there were only one way to represent this thing or idea, we would not call this representation thinking.
Donald H. Liles (1947) American engineer
Source: Enterprise modeling within an enterprise engineering framework (1996), p. 993
Robert Venturi book Complexity and Contradiction in Architecture
2. Complexity and Contradiction vs. Simplification or Picturesqueness
Complexity and Contradiction in Architecture (1966)
Derek Hitchins (1935) British systems engineer
Source: Advanced Systems Thinking, Engineering and Management (2003), p. 309; partly cited in: Kurt A. Richardson, Wendy J. Gregory, Gerald Midgley (2006) Systems Thinking and Complexity Science. p. 39