Friday, June 29, 2012

Software Zen and the Art of Versatilism

In my other blog which I run jointly with David Evans of Koan Solutions we explore what it is to be a versatilist and some of the attributes such people need to have or acquire. Following on from a previous post on the Top 10 Success Secrets of Software Architects here are five more "softer" attributes that software architects might find useful, all link to our versatilist blog.
  1. Software architecture is not so much about what you create as what you want to change. See What do we do for a living?
  2. In creating solutions, of any kind, making the right connections is all important. See Making the right connections.
  3. Innovation comes when there's an intersection between the arts and the sciences. See And one more thing...
  4. Whatever you are working on right now…choose at least three other ways to perceive it. See Perceptual positions.
  5. Sometimes a reference point just encourages us to keep our worldview, our biases, our grudges and our affections. try losing your reference point. See Losing your reference points.

Thursday, June 28, 2012

Top 10 Success Secrets for Software Architects

Peter Eeles, my co-author of The Process of Software Architecting, has a great presentation called  Top 10 Success Secrets for Software Architects which summarises nicely the attributes a successful architect needs to have and also covers the key points from our book. Briefly these are:


Successful Architects...For example they...
1Understand end-to-end development.Follow a repeatable process.
2Understand their role.Understand what an architecture is. Understand what an architect does. Understand the benefits of architecting.
3Manage risk and manage change.Derive their architectures iteratively.
4Communicate with stakeholders.Document their architectures.
5Reuse assets.Embrace different types of assets.
6Right-size their involvement.Select relevant viewpoints.
7Influence the requirements.Ensure tradeoffs are negotiated.
8Derive solutions from business needs.Produce business-driven architectures.
9Refine solutions based on technology.Realize architectures in available technology.
10Appreciate the broader context.Align their work with the “bigger picture”.


Peter presented this, with more detail around the attributes and examples, on a public call today. For a replay of the presentation go here. The slides are on slideshare here.