TOGAF emphasizes the need to tailor its documentation to meet the individual needs of each enterprise architecture project. Every enterprise and every project is unique, so it is impossible to provide a generic enterprise architecture framework that would work for everyone.
In part 3 of this 4-part article Good e-Learning’s enterprise architecture expert Roger Evernden takes a look at the reference frameworks, models and patterns.
Some companies adopting TOGAF see it largely as a methodology; often they are ones that are just starting out with enterprise architecture, and so they see the Architecture Development Method (ADM) as a good outline of the process they should follow. Customizing TOGAF for these companies is a simple matter of carrying out the tasks described in the Phases of the ADM, and integrating the various inputs and outputs with others that are involved in changes within the enterprise.