Taking some inspiration from the recently published SOA and FAIL manifestos, I thought I'd have a go at writing my own for software architecture.

1. Some up-front architecture over doing the whole lot or none at all
2. Designing for non-functional requirements over trying to tack them on at the end of the project
3. Evaluating technology over just choosing it because it looks good on your CV/resume
4. Experimentation over hoping your design will work
5. Code over endless discussions, meetings and diagrams
6. Collaboration over ivory tower dictation
7. Involvement over running away and letting the team deal with the "implementation" problems
8. Coaching team members over stroking your own ego
9. Pragmatism over perfection
10. Real problems over intellectual (self) stimulation
11. Simplicity and common sense over complex and convoluted ideas
12. Short and useful architecture documentation that reflects reality over encyclopaedias that nobody reads, understands or cares about

Humour aside, this does reflect my view of the role of a software architect. What else would you include?

Responses[6]

Posted by Simon Brown on 02 November 2009 08:43:36 GMT #