Not all frameworks that are often assofiated with EA are meant to address all levels of architecture. This table shows which frameworks may be applied to which level.
Notes: --TOGAF is mainly commercial, and focuses on an architecture process or cycle. Recently is added verbiage about EA, but still does not contain a "current" or "as-is" architecture in the cycle, or enterprise level abstractions. --DODAF is mainly military. It incorporated IDEF years ago. It recently incorporated UML. --FEAF is derivative of EAP. It was created to implement FEA in the federal governemnt. --EAP is derivative of Zachman. --Zachman is the grandady of EA frameworks. Martin preceeds it, but was not thought of as EA, perhaps partially because Zachman invented this term. --IDEF was never completed in its total vision, and contains only activity modeling (BPR/segment level), logical data modeling (segment level) and physical modeling (solutions level). --Segment level architecture is equivalent to BPR or "transformation of government". --UML, despite vast hype, was created as a software engineering framework and not an EA framework and is not all things to all people for all purposes.
"If you do anything long enough, you eventually get good at it." MK
