Geeks With Blogs

News Google

Nick Harrison Blog<Nick>.Next()

Recently I was asked what it is that a software architect does.   This is a difficult question to answer.    We do so much.     For the outsider it can difficult to explain.

I started thinking about it in terms of the balls that we juggle.   Here is my initial list.   I am sure that there are more:

  • Performance
  • Maintainability
  • Security
  • Reliability
  • Scalability
  • Look and Feel
  • Flexibility
  • Best Practices
  • Time lines
  • Politics   (Office and Project)
  • Software Version Upgrades
  • Individual egos
  • Scope Creep
  • System Integrity
  • System Integration
  • Budget
  • Deployment
  • System Conversion
  • Training / Mentoring
  • Hardware / Network Constraints
  • Business Requirements

In future posts,  I will ruminate over my personal experience in some of these areas.   I hope to hear what others are or have experienced.

Posted on Wednesday, November 23, 2005 7:01 PM Architecture Balls | Back to top

Related Posts on Geeks With Blogs Matching Categories

Comments on this post: The balls software architects juggle

# re: The balls software architects juggle
Requesting Gravatar...
I basically sum it up by saying that a strong architect should be able to fill anyone's shoes; from the customer to the program/project manager to the developer and even, in extreme cases, the system admin. This, of course, includes side jobs such as CM and QA tasks.
Left by Michael Flanakin on Nov 25, 2005 5:24 AM

comments powered by Disqus

Copyright © Nick Harrison | Powered by: