In today's competing environment, government agencies, as well as private companies, are in great need to learn how to balance their priorities, adjust existing investments and use their resources to accomplish their business strategy.
This was and still is the main goal for establishing of an Enterprise Architecture capability. Some organizations position EA as the Enterprise Decision Support capability - which provides a fact-based and architecture-grounded approach to making IT and business decisions.
Numerous government departments and agencies have been using enterprise architecture for some time - usually with regards to mandatory compliance with enterprise architecture frameworks, per example - the Department of Defense Architecture Framework (DoDAF) and the Federal Enterprise Architecture (FEA). This was before TOGAF was even created.
These frameworks typically focus on reference models and taxonomies that companies are required to utilize when describing their current state and their plans for the future state. But there is a new breed of companies which are looking past compliance requirement and want to use the business transformation dimension of enterprise architecture.
In the Department of Defense (DoD) environment, this can be realized with the "capability-driven" aspects inside DoDAF, in which the company aligns its architecture to a set of capabilities that are important for its mission.
Additionally, the Capability Viewpoint in DoDAF allows companies to describe their capability requirements and how their company supports and delivers those capabilities. The Capability Viewpoint likewise provides models needed to fill capability gaps and how certain capabilities are going to be implemented over time and managed with regards to an overall capability portfolio. For people familiar with TOGAF this must sound very familiar.
An important change in DoDAF 2 is the "fit-for-purpose" principle, which enables companies to choose which architecture models and viewpoints to develop based on program/mission requirements.
A fundamental consequence of this lies in the fact that the company is no longer needed to create all the models for every DoDAF viewpoint. They only need to choose the models and viewpoints that are relevant to development and deployment of their new, improved capabilities.
While DoDAF provides some concise guidance on the best way to build architecture descriptions and later using them for capability deployment as well as capability management, many companies are looking for a set of methods and techniques that are more well-defined as well as based on the best practices and industry standards.
This is where The Open Group Architecture Framework (TOGAF) steps in. DoDAF can be significantly improved by integrating with TOGAF. TOGAF 9.1 version should be used, especially the Architecture Development Method (ADM) from the TOGAF. The ADM is not only able to describe how to create descriptions of the target architectures, but also provides extensive guidance on how to set up an Enterprise Architecture capability and proper roadmapping as well as migration planning.
What won't be easy s finding enterprise architecture tools that will fully support using multiple frameworks like DoDAF and TOGAf together. Most enterprise architecture tools will require you to choose one or the other framework but not both. Final Thoughts
Most important, the TOGAF ADM describes how to actually realize the target architecture through integration with solution delivery lifecycles and system engineering. Finally, TOGAF depicts how to maintain an EA capability
in order to manage the evolution of the enterprise architecture. Basically, DoDAF provides a common vocabulary for enterprise architecture content, while TOGAF provides a common vocabulary for development and utilization of that content.
keywords: TOGAF, DoDAD, TOGAF software, enterprise architecture tools