it doesn't depend on struts or not struts, but on what you want to model and how deep you want to go.
I'd say use-cases and activity-diagrams for the first level. class diagrams and collaborations for the seconds level (which can be less or more detailed) sequence if you like sequences. everything else... depending on your goals, which can be moving. For example a deployment diagram could make more sense at the end of the design process and so on. regards Leon On 4/10/07, Asaf Paris Mandoki <[EMAIL PROTECTED]> wrote:
What kind of UML diagrams are necessary to fully model a complete struts application? --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
