· 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
Thursday, October 9, 2008
Do’s on writing software design and architecture documents
Subscribe to:
Post Comments (Atom)
? ?? ?????? ?? ?????????, ? ???????
ReplyDeleteI 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
ReplyDeleteHi! This is my first comment here so I just wanted to give a quick shout out and say I genuinely enjoy reading your blog posts. Can you recommend any other Beauty Write For Us blogs that go over the same topics? Thanks a ton!
ReplyDeleteYour blog provided us with valuable information to work with. Each & every tips of your post are awesome. Thanks a lot for sharing. Keep blogging.. www.bookmetoday.com
ReplyDeleteI just found this blog and have high hopes for it to continue. Keep up the great work, its hard to find good ones. I have added to my favorites. Thank You.
ReplyDeleteThe website is looking bit flashy and it catches the visitors eyes. Design is pretty simple and a good user friendly interface. bookmetoday.com
ReplyDelete