Design Diagram/Document for Seam projects?

[saeediqbal1]

Hey all,

I would like to know your opinion on what do you consider when writing project design documents and making design diagrams for Seam projects please. For example with J2EE 1.4, we usually have design patterns implement in the diagram , have web layer, dao and web services maybe as broad layers and inside each we have several components such as View (facelets, templates, ajax) .. you get the idea.

If you would like to share a sample diagram/document, that'ld be great too.

I think having a well-written design document helps having a well-design software end-product.
Thanks much.

-si

[norman.richards]

I think most Seam users are not only using lighter architectures than what you are used to with J2EE but also a lighter (more agile, though I hate that term) process. So, I doubt you'll get many responses back from people using heavy
design processes with Seam.

If you ask specific architectural questions, I'm quite sure you'll get some interesting responses.

[bsmithjj]

<total-imho>
Most of those diagrams that show lots of little blocks with words like DAO, servlets, etc. say very little to someone outside of your working group because they assume we share a common vocabulary and belief system about the constituents of an application written in Java. Even worse are those humongous class diagrams generated by some UML reverse-engineering tool. I think Fowler's UML As Sketch blog does a good job of stating an excellent way to use UML (http://www.martinfowler.com/bliki/UmlAsSketch.html) - mainly as a sketch tool for discussing specific aspects (e.g. a component) of a system of interest.
</total-imho>