SessId013

What the Heck is "Software Architecture"?

Where does architecture end and design begin? In most organizations, the boundary is fuzzy -- the architect's job varies from project to project. Outcomes are variable. But an organization that has a shared, clear understanding of the meaning and value of software architecture can do a better job of design. Its projects are more successful, more predictable. It can more easily transfer technologies from one project to the next. It learns. In this session, we'll use a clever simulation to offer an experiential understanding of the power and limitations of architecture. The experience provides a shared metaphor that teams can use when they apply their learnings to software projects.

The practice of "software architecture" may be viewed as constraint satisfaction. These constraints may be:

so numerous as to be uncountable
so soft as to be unquantifiable or even emotional
so arcane as to be really understood by very few.

So, satisfying these constraints becomes a very difficult problem.

What are the skills that someone who wishes to practice "software architecture must possess?

Obviously, a sense of humor is the first one. Working in an environment like that. Anyone who takes themself too seriously will crack. - JerryWeinberg

A sense of the absurd. Creating something truly wacky might shake out a few unstated preferences.
A love for adventure. No matter where you go you'll work hard to get there.
The ability to say NO. If something formed is desired you'll need to make some decisions to move away from formlessness.

- BeckyWinant

The Architect on our project, Mike Kalan, was recently in a meeting across divisions where he had to introduce himself and what he does. His answer:

"I do almost nothing on almost everything."

I think there are some real fundamental concepts to architecture in this statement:

The work is in the difference between "almost nothing" and "nothing."
The scope of the work is "almost everything" in a system, to the right level of detail.

- JimJarrett

SteveSmith: Jim, wow, Mike does have a way with words. His words describe my job very well. I suspect that if my manger's manager's manager heard me describe my job that way, he would fire me. I'll bet Mike is very respected and people therefore interpret his comments positively. --Steve

Steve, Mike does have a huge amount of credibility in the organization. He's been involved with the most complex successful products at the company for 20 years, and has allies and friends across the company. Those who dislike him don't know him. - Jim

Mike Kalan's words are another variation on the definition of generalist. The specialist being one who "does almost everything on almost nothing". As I am also a generalist, though not an architect, I find them very recognizable.

Jim, I don't find you on the Guest Book or in the AYE 2001 attendee list. Would you please identify yourself? -- MikeMelendez

Updated: Monday, December 10, 2001