In the intro to TOGAF it is mentioned that the TOGAF framework enables organizations to effectively address critical business needs by avoiding lock-in to proprietary solutions by standardizing on open methods for Enterprise Architecture.
Is there any more information in the documentation that expands on this point?
Can anyone provide an example of standardising on 'open methods'?
I have found little nuggets around the implementation governance, and opportunities and solutions, but was looking for a fuller explanation on this.
I hope the following points help you understand this better. You will anyway discover the answer yourself when you study the ADM phases in detail.
1. As you might know, TOGAF is a process methodology framework. It is not concerned about the solutions - either proprietary or open. It means, TOGAF mentions the mechanism in which you identify a solution, such as what steps to follow, what points to ponder about when finalizing a solution. The solution could be anything.
2. I believe the 'open method' mentioned in your question is the TOGAF ADM methodology itself. It is a standard and open method created by the Open Group.
3. The ADM procedure needs to be customized at the beginning. While customizing, the EA team can include any organization specific procedures to identify and develop the solutions. EA team can also add any new procedures to ADM. These would be called as 'extensions/ plug-ins'.
4. You can plugin any third party process framework as well if it suits the needs.
5. In every ADM cycle or iteration, there will be a phase-E where the corresponding team will decide which solution building blocks to use. This happens every time. So this provides an opportunity to re-evaluate the existing solutions and find out something new. That way, any lock-in is avoided.
Thanks & regards,
Mithun M S
OCMJEA 6 | TOGAF 9 | SOACP
What's brown and sticky? ... a stick. Or a tiny ad.