http://blogs.msdn.com/cashto/archive/2007/08/21/advice-to-design-document-writers.aspxAfter having reviewed three ... suboptimal ... design documents this week, I feel I should really say something on the topic of writing up a good design. I know most of my coworkers don't bother reading other people's design docs, so maybe you're totallyenCommunityServer 2.1 SP1 (Build: 61025.2)http://blogs.msdn.com/cashto/archive/2007/08/21/advice-to-design-document-writers.aspx#4494784Tue, 21 Aug 2007 17:24:27 GMT91d46819-8472-40ad-a661-2c78acb4018c:4494784Rob Crowther<p>&gt; it's really not that hard to understand </p> <p>&gt; well-written code in the first place, so why</p> <p>&gt; not go to the authoritative source directly</p> <p>There are two reasons I think:</p> <p>1. The reason why someone is having to refer to the design document in the first place is because the code is not, in fact, well written and they have to fix it.</p> <p>2. You're assuming the only people that would ever need to refer to the design document are developers - this isn't true for all scenarios.</p> http://blogs.msdn.com/cashto/archive/2007/08/21/advice-to-design-document-writers.aspx#9918692Fri, 06 Nov 2009 17:31:14 GMT91d46819-8472-40ad-a661-2c78acb4018c:9918692Ketan<p>Hi,</p> <p>I agree with the nearly all the points that are raised in this post. As, recently I gave feedback on our new template, which in my view inhibited writing.</p> <p>My question is how do you approach writing design - do you think, jot down points on paper, write some code, spend time creating UML diagrams and then put all together in design document? or Open document and start writing? </p> <p>My request to you is.. is there any good design document that you are product of it (open source/others/written by you) and can share with us? </p> <p>Reading good document teaches a lot!</p>