Do’s on writing software design and architecture documents
· If you drone endlessly with details, you don’t see the forest from the trees.
· If you don’t use multiple views, you are likely to miss important aspects of the solution
· If you aren’t focused on quality attributes, then you are most likely documenting design and not architecture
· And if you don’t explain the rationale, then the document doesn’t have a lot of added value beyond the code itself

October 14th, 2008 at 7:28 pm
[...] Do’s on writing software design and architecture documents [...]
October 21st, 2008 at 12:05 am
[...] Do’s on writing software design and architecture documents [...]
October 21st, 2008 at 12:11 am
[...] Do’s on writing software design and architecture documents [...]
October 23rd, 2008 at 2:50 pm
[...] Do’s on writing software design and architecture documents [...]
October 25th, 2008 at 8:54 pm
[...] Do’s on writing software design and architecture documents [...]
October 31st, 2008 at 11:47 pm
[...] Do’s on writing software design and architecture documents [...]
November 3rd, 2008 at 11:50 pm
[...] Do’s on writing software design and architecture documents [...]
November 4th, 2008 at 12:00 am
[...] Do’s on writing software design and architecture documents [...]
May 22nd, 2009 at 5:00 pm
? ?? ?????? ?? ?????????, ? ???????