Linked by Eugenia Loli-Queru on Mon 10th Oct 2005 01:08 UTC
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.
Thread beginning with comment 42388
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
Member since:
RE[2]: You annoy programmers
by QuantumG on Mon 10th Oct 2005 03:31
in reply to "RE: You annoy programmers"
Member since:2005-07-06
Member since:
2005-07-06
your job is now to dictate how a system should work even though you don't have the responsiblity of coding it. This gives you the freedom to put any sort of shit together on a page, be it implementable or not, and programmers have to struggle to make your ambiguious crap into a working program. When you then complain that the programmers went "off course" and demand that they follow your "achitecture" don't be surprised if you find a little surprise on the hood of your car at the end of the day.