Problems of Togaf9 Part 2


I have received lots of criticism being critical about TOGAF.  Great!  Major comment has been that one needs not to use it as such but take the best or suitable parts for whatever is the need.  Let us think about that for a moment!

TOGAF9 Introduction states:

TOGAF Says: TOGAF is a framework - a detailed method and a set of supporting tools - for developing an enterprise architecture. It may be used freely by any organization wishing to develop an enterprise architecture for use within that organization.

Mirafor wonders: Detailed method for developing enterprise architecture!  I assume that detailed method means that it is supposed to be also logical.  Or is it so that method is always logical by nature.  Hmm…based on what proven theory?

TOGAF Says: The purpose of enterprise architecture is to optimize across the enterprise the often fragmented legacy of processes (both manual and automated) into an integrated environment that is responsive to change and supportive of the delivery of the business strategy

Mirafor wonders: This means that it is process development only!  Or have I missed something?  Which comes first process or information?  Or is it so that strategy is information developed by strategy process.  Is then strategy process improvement responsibility of enterprise architecture?  Did I say enterprise architecture process…?  We are confused what is process and what is information.

OK…let us move to Part IV of the TOGAF to get clarification….

…And Togaf9 Part IV states in overview:

“The TOGAF Architecture Development Method (ADM) provides a process lifecycle to create and manage architectures within an enterprise. At each phase within the ADM, a discussion of inputs, outputs, and steps describes a number of architectural work products or artifacts, such as process and application. The content metamodel provided here defines a formal structure for these terms to ensure consistency within the ADM and also to provide guidance for organizations that wish to implement their architecture within an architecture tool.”

TOGAF Says: At each phase within the ADM, a discussion of inputs, outputs, and steps describes a number of architectural work products or artifacts, such as process and application”

Mirafor wonders: Are “inputs and outputs” information?  Do “steps” mean process “tasks”? Do “architectural work products or artifacts” mean information about them since we are not developing the actual “physical products” at this point?  Ooh…sorry…I stopped reading too early…it continues “such as process and application”. 

Mirafor conclusion: So it seems that TOGAF is a process for developing processes. Moreover, its process for describing processes.  I think there is quite many of those already. 

I am just still wondering if an enterprise is nothing but a process?

Even if enterprise is nothing but a process then should it not be information model about enterprise process?

Information model about the “universal artifacts” or just a “class model?”

I admit that I am confused trying to understand!  My feeling is that so are many others.





1 Comment

  • Mohan said

    Interesting argument: It is like arguing there are mousetrap's and better mousetraps out there. I think of the Open Group as a community trying to enhance the overall process around Architecture. So would I rather build a new mousetrap myself or go with one that has worked for my neighbor/cousin?

Add a Comment