Add a comment


Re: Software Architecture Document Guidelines

If you have identifiable NFRs then the justification section is more a foreign key relationship than a denormalised view ;)

As for their juxtaposition, I have wondered about that in the past. Sometimes it's easier to reference the design decisions after they've been presented, sometimes it's not... The SAD is often better as a hyper-linked tree of information than as a linear Word document in either case. The subtree of interest (and reading order) should be dependent on the viewer's need, not the author.

There are other similar synergies a lite version could appeal to: logical and interface views can often be superimposed, the design view might be driven by the functional view, the deployment view is often implicit in the infrastructure view. That said, most of this could simply be covered by the removal of a section from the existing SAD guidelines.

Re: Software Architecture Document Guidelines

HTML : b, strong, i, em, blockquote, br, p, pre, a href="", ul, ol, li, sub, sup
E-mail address
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).