If you are a Software Architect, Application Architect, or an Enterprise Architect, you should be familiar to these three major enterprise architect (EA) frameworks.
1. “The Zachman Framework is an enterprise architecture framework which provides a formal and highly structured way of viewing and defining an enterprise. It consists of a two dimensional classification matrix based on the intersection of six communication questions (What, Where, When, Why, Who and How) with five levels of reification, successively transforming the most abstract ideas (on the Scope level) into more concrete ideas (at the Operations level)” (from wikipedia)
Other architecture frameworks have been introduced based on this Zachman Framework.
2. TOGAF (The Open Group Architecture Framework)
TOGAF is a framework – a detailed method and a set of supporting tools – for developing an enterprise architecture. It may be used freely by any organization wishing to develop an enterprise architecture for use within that organization (see 4.5.1 Conditions of Use).
TOGAF is developed and maintained by members of The Open Group, working within the Architecture Forum (refer to www.opengroup.org/architecture). The original development of TOGAF Version 1 in 1995 was based on the Technical Architecture Framework for Information Management (TAFIM), developed by the US Department of Defense (DoD). The DoD gave The Open Group explicit permission and encouragement to create TOGAF by building on the TAFIM, which itself was the result of many years of development effort and many millions of dollars of US Government investment.
3. DoDAF (Department of Defense Architecture Framework)
“The Department of Defense Architecture Framework (DoDAF) is an architecture framework for the United States Department of Defense (DoD) that provides structure for a specific stakeholder concern through viewpoints organized by various views. These views that act as mechanisms for visualizing, understanding, and assimilating the broad scope and complexities of an architecture description through tabular, structural, behavioral, ontological,pictorial, temporal or graphical means.
It is especially suited to large systems with complex integration and interoperability challenges, and is apparently unique in its use of “operational views” detailing the external customer’s operating domain in which the developing system will operate.”
Hope this helps.