How to Use The Open Group Architecture Framework (TOGAF)
Understand that all TOGAF work follows through the ADM Cycle., Learn the outside of the ADM Cycle., Learn the Inside of the ADM Cycle, “Requirements Management”., Understand how to read the seven (7) past to the TOGAF Framework., Feel comfortable...
Step-by-Step Guide
-
Step 1: Understand that all TOGAF work follows through the ADM Cycle.
The ADM Cycle is hidden deep inside the framework but is how work progresses in TOGAF and an explanation of everything that is done throughout the TOGAF process. Essentially this is a product development cycle. ADM stands for Architecture Development Method and is one of the 7 parts to a full TOGAF solution but is the part focused on how work is completed. -
Step 2: Learn the outside of the ADM Cycle.
The middle of the ADM Cycle will be ignored in this step for simplicity.
TOGAF starts at “Phase A:
Architecture Vision” and ends at “Phase H:
Architecture Change Management.” Like all good IT management cycles, it repeats forever to make sure the solution stays current.
Phase A is more business level and each Phase moves towards implementation.
The product implementation maxes out around Phase E and then the rest of the phases turn the product into a full solution that can be used by customers in a reliable manner (change management, governance etc) , TOGAF is all about governance.
Every action needs to be approved and evaluated by peers.
This middle circle is stating that the governance board monitors every action in the cycle and all required actions are taking place, The “ADM Cycle” described above is the main cycle of activity within TOGAF. It does not describe the different attributes of these solutions and the unique features of TOGAF.
Those are described in the Framework.
TOGAF is a library of information and tools to use through the ADM Cycle.
Even though there are 7 “Parts” that does not mean they are synchronized.
Instead, they are components to the end solution that are all needed at once to do TOGAF correctly.
Note the Frameworks “Parts” are different than the ADM Cycle’s “Phases.” The ADM’s Phases are part of the components described in “Part II.” , This is TOGAF”, This is where the previously mentioned Architecture Development Method (ADM) Cycle is defined., In other words, Part III is really a component to Part II.
Part III contains several strategies to help make the Part II Architecture in different environments., How to create and use these outputs is defined in Part IV,, Technical Reference Model (TRM):
The best way to describe the TRM is the below diagram.
It is a collection of artifacts and activities to complete all necessary components to a solution to meet the topics addressed in this diagram.
The TDM is one of the two models discussed in Part VI.
The other is the IIIRM, or the Integrated Information Infrastructure Reference Model (IIIRM).
With the emergence of Internet-based technologies in recent years, for many organizations the main focus of attention, and the main return on investment in architecture effort, has shifted from the Application Platform space to the Application Software space. (Indeed, this has been one of the drivers behind the migration of TOGAF itself from a framework and method for Technology Architecture to one for overall enterprise architecture.) This section describes a reference model that focuses on the Application Software space, and "Common Systems Architecture" in Enterprise Continuum terms.
This is the Integrated Information Infrastructure Reference Model (III-RM). , In order to successfully operate an architecture function within an enterprise, it is necessary to put in place appropriate organization structures, processes, roles, responsibilities, and skills to realize the Architecture Capability.
Part VII:
Architecture Capability Framework provides a set of reference materials for how to establish such an architecture function.
Readers should note that although this part contains a number of guidelines to support key activities, in its current form, the Architecture Capability Framework is not intended to be a comprehensive template for operating an enterprise Architecture Capability. -
Step 3: Learn the Inside of the ADM Cycle
-
Step 4: “Requirements Management”.
-
Step 5: Understand how to read the seven (7) past to the TOGAF Framework.
-
Step 6: Feel comfortable with Part I of the seven parts of TOGAF "Introduction": Essentially
-
Step 7: the Part is used to say “Hey!
-
Step 8: Feel comfortable with Part II of the seven parts of TOGAF "Architecture Development Method": The core of activities in TOGAF is “Architecture Development Method Part II.” All other Parts are needed to complete Part II’s activities.
-
Step 9: Feel comfortable with Part III of the seven parts of TOGAF "ADM Guidelines and Techniques": ADM stands for Architecture Development Method or the name of Part II.
-
Step 10: Feel comfortable with Part IV of the seven parts of TOGAF "Architecture Content Framework": Architects will produce a number of outputs as a result of their efforts such as process flows
-
Step 11: architectural requirements
-
Step 12: project plans
-
Step 13: project compliance assessments
-
Step 14: Feel comfortable with Part V of the seven parts of TOGAF "Enterprise Continuum and Tools": Essentially “Enterprise Continuum” means ‘whatever is done
-
Step 15: try to generalize it so that it can be reused for a different project.’ Thus there is no 'recreating the wheel': TOGAF has several great guidelines in reusing as many things as possible.
-
Step 16: Feel comfortable with Part VI of the seven parts of TOGAF "TOGAF Reference Models": Two specific models are outlined in this Part.
-
Step 17: Feel comfortable with Part VII of the seven parts of TOGAF "Architecture Capability Framework": Part VII is all about the below diagram.
Detailed Guide
The ADM Cycle is hidden deep inside the framework but is how work progresses in TOGAF and an explanation of everything that is done throughout the TOGAF process. Essentially this is a product development cycle. ADM stands for Architecture Development Method and is one of the 7 parts to a full TOGAF solution but is the part focused on how work is completed.
The middle of the ADM Cycle will be ignored in this step for simplicity.
TOGAF starts at “Phase A:
Architecture Vision” and ends at “Phase H:
Architecture Change Management.” Like all good IT management cycles, it repeats forever to make sure the solution stays current.
Phase A is more business level and each Phase moves towards implementation.
The product implementation maxes out around Phase E and then the rest of the phases turn the product into a full solution that can be used by customers in a reliable manner (change management, governance etc) , TOGAF is all about governance.
Every action needs to be approved and evaluated by peers.
This middle circle is stating that the governance board monitors every action in the cycle and all required actions are taking place, The “ADM Cycle” described above is the main cycle of activity within TOGAF. It does not describe the different attributes of these solutions and the unique features of TOGAF.
Those are described in the Framework.
TOGAF is a library of information and tools to use through the ADM Cycle.
Even though there are 7 “Parts” that does not mean they are synchronized.
Instead, they are components to the end solution that are all needed at once to do TOGAF correctly.
Note the Frameworks “Parts” are different than the ADM Cycle’s “Phases.” The ADM’s Phases are part of the components described in “Part II.” , This is TOGAF”, This is where the previously mentioned Architecture Development Method (ADM) Cycle is defined., In other words, Part III is really a component to Part II.
Part III contains several strategies to help make the Part II Architecture in different environments., How to create and use these outputs is defined in Part IV,, Technical Reference Model (TRM):
The best way to describe the TRM is the below diagram.
It is a collection of artifacts and activities to complete all necessary components to a solution to meet the topics addressed in this diagram.
The TDM is one of the two models discussed in Part VI.
The other is the IIIRM, or the Integrated Information Infrastructure Reference Model (IIIRM).
With the emergence of Internet-based technologies in recent years, for many organizations the main focus of attention, and the main return on investment in architecture effort, has shifted from the Application Platform space to the Application Software space. (Indeed, this has been one of the drivers behind the migration of TOGAF itself from a framework and method for Technology Architecture to one for overall enterprise architecture.) This section describes a reference model that focuses on the Application Software space, and "Common Systems Architecture" in Enterprise Continuum terms.
This is the Integrated Information Infrastructure Reference Model (III-RM). , In order to successfully operate an architecture function within an enterprise, it is necessary to put in place appropriate organization structures, processes, roles, responsibilities, and skills to realize the Architecture Capability.
Part VII:
Architecture Capability Framework provides a set of reference materials for how to establish such an architecture function.
Readers should note that although this part contains a number of guidelines to support key activities, in its current form, the Architecture Capability Framework is not intended to be a comprehensive template for operating an enterprise Architecture Capability.
About the Author
Paul Ramos
A passionate writer with expertise in cooking topics. Loves sharing practical knowledge.
Rate This Guide
How helpful was this guide? Click to rate: