At times big upfront architecture document say about more than 50 pages document may not grab the attention of developers/other concerned parties. So we architects should be aware of creating architecture documents which are short and to the point. There is no point in creating big documents which no body interested in to know/refer. In my opinion, the architecture document shall be
1) Shall be simple and shall contain key architecture decisions. In my opinion with few UML diagrams and brief description should solve the purpose.
2) Update the document only if deemed to be necessary/otherwise don't update
Subscribe to:
Post Comments (Atom)
One new learning / day - however small it is
Read a blog / or article Watch TED talk Read a small self-help book (many free eBooks available with less than 100 pages/can be completed i...
-
I underwent TOGAF 8.1.1/9 training and certification program in last week of sept'09. It was good experience and lot of knowledge gained...
-
Few things about the possible differences between these concepts 1) A user story is the title of one scenario, whereas a use case is the con...
-
Read a blog / or article Watch TED talk Read a small self-help book (many free eBooks available with less than 100 pages/can be completed i...
No comments:
Post a Comment