posted 14 years ago
Togaf has more to do with enterprise architecture so you need to address a lot of other things then only it-architecture.
I have read some things over Togaf but for me the framework is too complicated. I see a lot of companies with a design of the enterprise architecture, reality one and the way they really work, reality two. So you can write a nice architecture and everyone behaves has own way. Also it's my experience just write the way they work in the way they talk, see, feel and express themselves in their work this gives a better communication and a change to improve and learn. This is normally different from the way Togaf want you to describe the working of a company.
The nice thing with SCEA with is more to do with the it-architecture and more in common the J2EE-architecture, but if you have the abilities you can easily use them in an another context, is that you receive feedback over your architecture. If it's wrong it's working well, people are complaining, projects will last longer, you need to buy a lot of unnecessary hardware of getting the non-functional requirements, etc. Also you need to describe your architecture in a certain standard way so your technical peers will understand your architecture.
Off course you can do both. There is nothing wrong with that.
Remko (My website)
SCJP 1.5, SCWCD 1.4, SCDJWS 1.4, SCBCD 1.5, ITIL(Manager), Prince2(Practitioner), Reading/ gaining experience for SCEA,