Facilitating the Spread of Knowledge and Innovation in Professional Software Development

Write for InfoQ


Choose your language

InfoQ Homepage Zachman Framework Content on InfoQ


RSS Feed
  • Zachman's Views On Impact Of Cloud Computing On Enterprise Architecture

    John Zachman, the originator of the Zachman framework, recently wrote an article that addresses the questions regarding the impact of cloud computing on enterprise architecture; especially given how disruptive and popular cloud architectures are becoming an effective technique to cut costs.

  • Latest Release of Zachman Framework Highlights Its Role as an Ontology

    John Zachman, considered one of the fathers of the Enterprise Architecture discipline, recently released the third edition of his popular framework. This version included some minor text updates, improved graphics and a subtle effort to re-classify this artifact as an ontology instead of a framework.

  • EA as a Catalyst for Innovation

    Melvin Greer, a senior fellow at Lockheed Martin, challenged enterprise architects to drive EA as an enabler of innovation at various talks and most notably in his interview with Government Computer News. InfoQ spoke with Melvin Greer to clarify his vision of enterprise architecture and its impact on the relationship between IT and business.

  • Is it Time to Rethink Enterprise Architecture?

    Gabriel Morgan thinks so. As businesses are changing more rapidly every day, and IT is getting slower every day. For him, EA Frameworks are simply not equipped to achieve business-IT alignment. He shares some of his experience after his team started to focus on company transformation and adopted business management concepts instead.

  • Partitioned-Iterative more appropriate for EA than Zachman, TOGAF?

    Roger Sessions claims that the most popular EA frameworks (Zachman, TOGAF, FEA, and Gartner) have failed to evolve to the needs of today's more complex development needs. Instead, Sessions proposes a 'Partitioned-Iterative' Approach that reduces complexity through partitioning an organization in smaller pieces, rather than defining the architecture for the whole company at once.