• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Liutauras Vilda
  • Tim Cooke
  • Jeanne Boyarsky
  • Bear Bibeault
Sheriffs:
  • Knute Snortum
  • paul wheaton
  • Devaka Cooray
Saloon Keepers:
  • Tim Moores
  • Stephan van Hulst
  • Ron McLeod
  • Piet Souris
  • Ganesh Patekar
Bartenders:
  • Tim Holloway
  • Carey Brown
  • salvin francis

TOGAF Specification - ADM Phases

 
Ranch Hand
Posts: 10191
3
Mac PPC Eclipse IDE Ubuntu
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
From the TOGAF specification, I could not understand the difference between "Request for Architecture Work" vs the "Statement of Architecture Work"? I see that the Request for Architecture Work starts as an output of the Preliminary phase. What does it contain? Is this some sort of a document? Could somebody throw some light on it?

Also, going through the ADM phases, each one of them in detail, I'm seeing that only some of the outputs of the previous phase becomes the input to the next subsequent phase. Why is this? Is running through each of the phase mandatory? For example., I do not see the Organisational model for Enterprise Architecture as one of the Inputs to the Architecture Vision. So this indicates to me that none of the phases are mandatory. This also coincides with my understanding of a framework, which is to be able to change and adapt to the needs.

I'm seriously not good at memorising and going through the content so far, it seems to me that I have to remember a lot of stuff for me to be able to pass the exam. I'm not sure how healthy this methodology is going to be. What do you guys think?
 
author & internet detective
Posts: 39435
768
Eclipse IDE VI Editor Java
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Joe,
You are correct not every artifact is used in the next phase. Some are used for understanding and communication. TOGAF is a framework and yes, you customize it. I think one of the reasons for all the memorization is so we learn the language of TOGAF and can talk to other TOGAF practitioners. I hate memorizing too though!
 
Joe Harry
Ranch Hand
Posts: 10191
3
Mac PPC Eclipse IDE Ubuntu
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Thanks for the reply Jeanne!

Would just going through the pocket guide be enough or would just going through the unofficial study guide be enough to understand TOGAF?
 
He puts the "turd" in "saturday". Speaking of which, have you smelled this tiny ad?
Java file APIs (DOC, XLS, PDF, and many more)
https://products.aspose.com/total/java
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!