IT Architecture

I've attempted to answer this question in "Introduction to IT architecture" in the developerWorks Architecture zone.

This involves issues around being an information technology (IT) architect (a.k.a. systems architect) and developing architectures. See the Wikipedia Information Technology Portal.

A very popular type of architecture today is Service-Oriented Architecture (SOA).

Becoming an Architect

Resources:

• IT Architecture: Resource round-up on developerWorks is a collection of materials discussing what architecture is and how to learn more
• IT architecture forum on developerWorks is a place to discuss architectural issues
• Architectural Thinking is a class we offer to train architects
• Sample IT projects help show you how architects approach problems

Articles:

• The Open Group Architecture Framework (TOGAF)
  • "Understand The Open Group Architecture Framework (TOGAF) and IT architecture in today's world" (developerWorks)
  • "Introducing The Open Group Architecture Framework (TOGAF)" (developerWorks)
• "Enterprise IT architect: Meet the new kid on the block" (developerWorks)

Certification:

• Professional Certification Program from IBM – All certifications, not just architects
• IBM Service Oriented Architecture (SOA) Certification has information on becoming a IBM Certified SOA Solution Designer
  • Namely, take Test 667: Architectural Design of SOA Solutions
    • Looks like you can often take the test for free at WebSphere Users' Groups and at WebSphere conferences
  • Training resources for learning about SOA architecture (I also recommend Exploring IBM SOA Technology and Practice)
  • SOA Certification Roadmap shows that passing Test 667 makes you an IBM Certified SOA Solution Designer
• Sun Certified Enterprise Architect for the Java 2 Platform, Enterprise Edition (SCEA for J2EE)
  • The culmination of the Java EE Certification Path
  • Part of the Java EE Learning Path
• IT Architect Certification Program (Open Group)
  • IT Architect Certification (Wikipedia)
• IBM Certified Solution Designer - Rational Software Architect
• BEA Certified Architect
• Microsoft Certified Architect Program
• Infrastructure Systems Architect Certification (IBM)

Why become an architect?

Bill Higgins points out:

That's a dangerous question. I think a big problem with many architects is that they're out of touch with development because they live at too high a level to consistently make optimal technical decisions, but usually don't hesitate to do so.

I actually went from developer to architect back to developer because I found the architecture work too technically unfulfilling. A question I'd ask that developer is "Why do you want to become an architect?"

Finally a couple of resources:

• Jonathan Rothman: Architects Must Code
• Antipattern: Architects Don't Code
• Martin Fowler: Who Needs an Architect?

That's a good point. (And thanks for the resources!) Developers often have too narrow a view and architects too high-level a view. Worse yet, one group often doesn't have much respect for what the other group brings to the table. Ideally, an individual should appreciate the overall architectural issues on the project and the implementation details that affect the architecture; but that's a tall order.

I think people want to be architects for control, because they see things being done badly on their project (fill in your list of favorite rants here), don't see "the architect" doing anything about it, and think "If only I were the architect, I would run things properly." What people may not realize is that the architect doesn't necessarily run things either. That's more the team lead, project lead, project manager, etc.; but they often wonder if they're really running things, since ultimately you can tell the staff what to do but they don't necessarily do it.

I'm not sure architects necessarily have more control than developers or anyone else. In fact, it's ultimately really difficult to get control per se, at best what you can have is influence. And how do you get influence? IMHO: Leadership.