To answer the basic question - Sun's exams are based on job-role. In theory, you don't have to know how to program to do software architecture - you simply have to understand how the various technologies work together and which one fits which problem. (In my last job before the firm I work for, our architect had, in fact, never written a line of Java and was a certified software architect, simply from going through the theory classes in his comp-sci curriculum.)
Originally posted by Patrick Williams:
Theodore, How good was this architect? Just curious.
I'm very good.
All jokes aside... I found that Part II and III were more valuable to me than Part I, if only because Part I requires going back to learn the old specs. Since you can use any general-release Java EE technology for the practical exercise, I think it works out well as proof of whether or not you can plan out a solution using something that would have value in the workplace.
Just my $0.02 though.
Originally posted by Theodore Casser:
(In my last job before the firm I work for, our architect had, in fact, never written a line of Java and was a certified software architect, simply from going through the theory classes in his comp-sci curriculum.)
Either you did not understand my question about the Architect above or you are being coy (maybe they read this board). I understand how the SCEA works, but I was just wondering how good an Architect was that never coded, that's all. I'll consider the question dead.
Edit: I just went back and reread this and it came across as rude. I apologize if that's the way that it sounds, but it was not meant that way.
[ July 06, 2007: Message edited by: Patrick Williams ]