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
Famous John Zachman Quotes
Source: Concepts of the Framework for Enterprise Architecture, 1993, p. 1
“Decentralization without structure is chaos.”
Source: A Framework for Information Systems Architecture, 1987, p. 276 cited in: Robert Mylls (1994) Information engineering: CASE, practices and techniques. p. 8
                                        
                                        Zachman cited in: Egon Berghout and Dan Remenyi, Egon Berghout (2003) Proceedings of the 10th European Conference on Information Technology Evaluation - 2003. p. 503 
In this quote the "framework" refers to the Zachman Framework
                                    
Source: Business Systems Planning and Business Information Control Study: A comparison, 1982, p. 31
Source: Extending and Formalizing the Framework for Information Systems Architecture, 1992, p. 613, cited in: Nik Bessis, Fatos Xhafa (2011) Next Generation Data Technologies for Collective Computational Intelligence. p. 84
John Zachman Quotes
Source: Concepts of the Framework for Enterprise Architecture, 1993, p. 3
Source: Extending and Formalizing the Framework for Information Systems Architecture, 1992, p. 615
Zachman (1987) cited in: Antonio Laganà, Marina L. Gavrilova, Vipin Kumar (2004) Computational Science and Its Applications -- ICCSA 2004. p. 604
Source: Enterprise Architecture: The Issue of The Century, 1997, p. 1
Zachman (1994) cited in: Ronald G. Ross (2003) Principles of the Business Rule Approach. p. 35
Source: Business Systems Planning and Business Information Control Study: A comparison, 1982, p. 31
Zachman (1986) as cited in: Peter Bernus, Kai Mertins, Günter Schmidt (2005) Handbook on Architectures of Information Systems. p. 544
Source: Business Systems Planning and Business Information Control Study: A comparison, 1982, p. 34
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
                                        
                                        In the 1987 article Zachman states: The architect’s drawings are a transcription of the owner’s perceptual requirements. 
Source: A Framework for Information Systems Architecture, 1987, p. 278 cited in: David C. Hay (2003) Requirements Analysis: From Business Views to Architecture. p. 5
                                    
Source: A Framework for Information Systems Architecture, 1987, p. 276, cited in: Jaap Schekkerman (2003) How to Survive in the Jungle of Enterprise Architecture. p. 131
Zachman cited in: Carol O'Rourke, Neal Fishman, Warren Selkow (2003) Enterprise architecture using the Zachman Framework. p. 538
                                        
                                        Top down implies scope - that is, looking at the business as a whole as opposed to looking at pieces or subparts of it. 
Business Systems Planning and Business Information Control Study: A comparison, 1982
                                    
                                        
                                        Planning Methodologies: Stage Assessment, Critical Success Factors, Strategy Set Transformation, etc. 
Design Approaches: Structured Analysis, Entity-Relationship Approaches, etc. 
Tools and Techniques"Problem Statement Language/Problem Statement Analyzer (PSL/PSA), Prototype Development Methodology, Structured Analyses and Design Techniques, etc.
From an historical perspective, BSP and BICS likely will be looked back on as primitive attempts to take an explicit, enterprise-level architectural approach to information systems. 
Source: Business Systems Planning and Business Information Control Study: A comparison, 1982, p. 32
                                    
Source: Extending and Formalizing the Framework for Information Systems Architecture, 1992, p. 590
Source: Enterprise Architecture: The Issue of The Century, 1997, p. 1-2
Source: A Framework for Information Systems Architecture, 1987, p. 276, cited in: CM Pereira (2004), "A method to define an Enterprise Architecture using the Zachman Framework". in: SAC '04 Proceedings of the 2004 ACM symposium on Applied computing. pp. 1366-1371