Thursday, October 9, 2008

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


  1. ? ?? ?????? ?? ?????????, ? ???????

  2. I think this is an informative post and it is very useful and knowledgeable. therefore, I would like to thank you for the efforts you have made in writing this article. Open Source Crowdfunding Software