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