I had no idea of what is TOGAF, until one day, a friend told me that she is studying for the TOGAF Certification. Now what is that, I asked. She said, it is the most boring topic I have ever studied. The yucky standards are written in a strange language. It has an impossible grammar, and it is very difficult to read. You need to read and memorize the huge documents in order to clear it. But it is a valuable asset on your CV.
In every sense, that was the most demotivating introduction to the subject. I ignored it. Soon after that, few more friends told me that they were working towards it. All that they said did arouse my curiosity. I picked up the TOGAF standard document and scanned through it.
I was expecting some technical content in there. But found something entirely different. But it was interesting. The standard is difficult to read, but the topic is interesting. I have seen the frustration and chaos when we work on a large scale architecture change. If only we had followed a defined framework.. I thought.
My friends then talked me into spending a good amount of money towards the Simplilearn course, and we started working on it. I found the standards document was indeed impossible. So I extracted notes out of it, trying to frame it in a good, readable language. Here are my notes.
The ADM is central to the TOGAF framework. One might say it is the core of TOGAF. Understanding each phase of the ADM is very important for understanding and implementing TOGAF.
TOGAF provides a range of techniques that can be followed as we work towards the architecture development. Along with this, it also defines several deliverables that should be produced at each point in the process. This simplifies the roadmap.