Add a comment

 

Re: Software Architecture Document Guidelines

This document is a masterpiece even though it is V0.1 I can't believe the clarity with which the requirements of what such a doc should cover are conveyed. I've been looking for something to convey to a team and we are not using any bloated methodologies at this time. I find that the trick is first to convey what is required and tools are just there to help, but the requirement of what goes into such a doc is not first understood then tools are a waste of time (i.e. garbage in, garbage out). I find that a lot of sites and companies punting methodologies leave this out and one simply gets lost/bogged down in a quagmire of technobabble that is meaningless. This document at least sets an expectation (or objectives) against which you can measure any document that is produced. In closing, do you have anything against someone like myself utilising sections of this almost verbatim? Once again thanks for a very imformative document!

Re: Software Architecture Document Guidelines


Title
Body
HTML : b, strong, i, em, blockquote, br, p, pre, a href="", ul, ol, li, sub, sup
Name
E-mail address
Website
Remember me Yes  No 

E-mail addresses are not publicly displayed, so please only leave your e-mail address if you would like to be notified when new comments are added to this blog entry (you can opt-out later).