Do I need to to follow formal methods to be a "real" Software Architect?
I'm a programmer who has become a software architect through experience of what works in various situations, combined with an understanding of business.  I suppose you could say I follow the [Good enough architecture methodology][1].

Larger corporations have a very different view of what a software architect should be (I generally don't fit their definition!).  The words *IT Governance* and [TOGAF][2] / [Zachman][3] usually crop up.

Do I need formal training on IT Governance? Do I really need to know specific architecture frameworks to be a software architect?


  [1]: http://en.wikipedia.org/wiki/Good_enough_architecture_methodology
  [2]: http://en.wikipedia.org/wiki/TOGAF
  [3]: http://en.wikipedia.org/wiki/Zachman_Framework
Do I need to to follow formal methods to be a "real" Software Architect?
===

I'm a programmer who has become a software architect through experience of what works in various situations, combined with an understanding of business.  I suppose you could say I follow the [Good enough architecture methodology][1].

Larger corporations have a very different view of what a software architect should be (I generally don't fit their definition!).  The words *IT Governance* and [TOGAF][2] / [Zachman][3] usually crop up.

Do I need formal training on IT Governance? Do I really need to know specific architecture frameworks to be a software architect?


  [1]: http://en.wikipedia.org/wiki/Good_enough_architecture_methodology
  [2]: http://en.wikipedia.org/wiki/TOGAF
  [3]: http://en.wikipedia.org/wiki/Zachman_Framework