Tuesday, October 11, 2005

Software Architect: what do I actually do?

This is one of that articles that I always carry on in my backpack:

Rationale:
A key part of the software architect's job is producing an architectural description of the system that defines the architecture's key functions, features, and characteristics for its stakeholders. Where do you start? What do you need to know? Nick Rozanski and Eóin Woods provide detailed answers to these questions, with useful suggestions on how to attack this fundamental document that underpins any development project.

No comments: