Lesson 172 - TOGAF in 10 Minutes
HTML-код
- Опубликовано: 21 окт 2023
- In lesson 156 I gave a brief introduction to the Zachman Framework for enterprise architecture. In this lesson i do the same thing, only this time with TOGAF-The Open Group Architecture Framework. In this lesson I focus mostly on the Architecture Development Method (ADM) and how the various phases of the ADM work.
Reference Links:
Zachman Framework : www.developertoarchitect.com/...
Software Architecture Monday: bit.ly/3dadEe3
Fundamentals of Software Architecture: amzn.to/3rgFLjY
Software Architecture: The Hard Parts: amzn.to/3BjMMF2
Excellent explanation. Thank you!
Very good intro. Would love to see a real world example of a monolith going through the ADM and number of iterations to get to micro-services level.
beautifully described, keep the content coming
Thanks, very helpful
Hi Mark, I've been studying togaf for a few months. I thoroughly enjoy your description of the togaf framework. It cleared up a lot gaps I had.
Glad you found it useful!
Thank you so much for this informative video.
Very nice overview, in 10 minutes no less, thank you Mark.
Thanks Troy!
Great video! Exactly what I was looking for
Glad you enjoyed it!
Whata greate video, very uselful, thank you very mush.
I really like this simple introduction..thank you Mark.
Glad you found it useful!
Just confirming architecture content framework comes under Architecture Work Product. Very Beneficial Video.
Nice!
Great lecture
Thanks!
Hi Mark, love your videos! Recently I bought both your books. 😉 I have a suggestion for a possible next topic: inbox/outboox pattern. I think you haven't discuss them so far?
I'm always looking for new ideas, so thank you! I'll add that in a future video.
@@markrichards5014 Great, many thanks!
Thanks for a timely video. Which vendors do you feel currently provide good quality TOGAF training, whether self-paced or instructor led?
That depends on whether you are seeking training or certification. Certification is usually through The Open Group, but there are other books and online resources where you can go much deeper into how TOGAF works.
Mark, great tutorial! Where does the buy-in typically come from for what I would call a seismic shift in a company's culture. It was a topic broached in one of our Data Architecture meetings a while back, but it's become more of a buzzword rather than a reality. For example, the company has a vision to move everything (possible)to the cloud and along the way modernise some stuff. As I understand, TOGAF is a 360 degree of your business right down to the bare bones of technology, but where would a cloud vision fit into this, especially of you also have multiple initiatives going on in parallel such as migrations, integrations etc?
Moving to cloud would be a separate initiative, driven by A (arch vision). it is in this phase that buy-in would occur.
Another question, sorry to go on :) As I understand, this is essentially driven by A. - Architecture Vision and from this we elicit changes downstream to Business, Data, Tech. The example you use of a monolithic database, so you've decided a legacy system needs to go. But how then does this drive the C.technology, are they related?
Not all phases are needed, and in most cases they are done in parallel. You can do phases B and C in any order. This flexibility is one of the things I like about TOGAF.
I can see a relationship between Business Architecture and Conway's law but is there one, Mark? Does TOGAF explicitly discuss this?
Not explicitly. Team topologies is a tough one in TOGAF because there's really not a phase to explicity cal that out. That said, TOGAF is incredibly flexible, so you can always add a "Phase B1" to include this concern.
@@markrichards5014 clearly with TOGAF, there can only B1. #Dad-Joke