Hi All, We have been following a low level design document format which to me is very ancient and outdated. I would be thankful if somebody could provide some guidelines or provide with a template regarding how to go about a low level design document for a mid size enterprise application to be coded using MVC architecture under STRUTS framework... Even general guidelines are welcome.. Thanks in Advance, Yogesh
Originally posted by Yogesh Mathur: Hi All, We have been following a low level design document format which to me is very ancient and outdated. I would be thankful if somebody could provide some guidelines or provide with a template regarding how to go about a low level design document for a mid size enterprise application to be coded using MVC architecture under STRUTS framework... Even general guidelines are welcome.. Thanks in Advance, Yogesh
You can always add some basic use case and sequence diagrams that will work along with MVC & Struts.
I would suggest using http://www.agilemodeling.com/ as a guideline for your modeling effort. For more specific tips we needed to know what you want to document and for what reasons.
The soul is dyed the color of its thoughts. Think only on those things that are in line with your principles and can bear the light of day. The content of your character is your choice. Day by day, what you do is who you become. Your integrity is your destiny - it is the light that guides your way. - Heraclitus
If you believe you can tell me what to think, I believe I can tell you where to go. Go read this tiny ad!
Free, earth friendly heat - from the CodeRanch trailboss