do i need component diagram here?

[Maulin Vasavada]

Hi all,

I have typical implementation scenario like,

1. I have serveral components like UserProfile, ApplicationManagement etc in my application

2. For each such component I have,
- Servlet e.g. UserProfileManagerServlet, ApplicationManagerServlet etc..

3. For each component I have "Persistence Manager"(PM) interface + implemnetation e.g. UserProfilePM, ApplicationPM etc

4. Factory of those PMs that given a name returns a particular PM

5. Servlets communicate with a particular PM via "Data transfer object" (DTO) and those PMs does the persistence for those DTO (probably similar to JDO architecutre you know)

I want to model it in UML. Do I need to use "Component Diagram"? If not how to model this in UML? I don't think "Use case diagram" would help OR will it?

Regards
Maulin

[Lasse Koskela]

Sounds like a good old class diagram would do.

[Maulin Vasavada]

Hi Lasse

So is good?

Thanks
Maulin

[Maulin Vasavada]

sorry..

doesn't seem like UBB's IMG tag worked

please look at http://www.geocities.com/maulin_v/MVC_ClassDiagram.gif

thanks
Maulin

[Stan James]

Here's a neat, short overview of the UML diagrams: The Diagrams of UML 2.0. I love the title, sounds like "The Girls of the Big 8" in Playboy. Heh heh.

Seriously, look around that site. Scott Ambler has some good introductory info about UML. Can anybody recommend a good first book on UML? Doesn't Craig Larman have one?

[Maulin Vasavada]

I guess that I can create a sequence diagram where I don't put specific method calls but general calls like request,process etc...and cover my all cases of such communication into one...

I looked for UML for MVC on google and found some class diagram and couple of sequence diagrams and I thought sequence diagram can depict it more clearly..

Thanks
maulin

[Stan James]

... and cover my all cases of such communication into one

Whoa! Watch out! You might invent patterns! Seriously, that sounds like a great idea. If you can generalize one ring that binds them all, I mean one diagram that represents all the cases, it will probably communicate very well to your team. Might be the only one you need.

I'm a huge fan of sequence diagrams, but that seems to be a personal thing and I seem to be lonely some times. I even made my own tool to generate ASCII sequence diagrams before I had access to Rose.

[Maulin Vasavada]

Hi Stan

I think I would go that way as I consulted my other friend as well and he seems to agree with the idea.

I will try to draw it and post on the same link and let you know.

Cheers
Maulin

[Stan James]

For grins, here's my text only diagramming tool. It's in REXX just in case you wanted to learn another language this week. oochart.rex

Mark Hessling makes the Regina REXX interpreter available for free. Never use .bat again.

input

object View
object Controller
object Model
 
case simple
 
 View Controller FieldXChanged
 Controller Controller UserChangedInterestRate
 Controller Model CalculateLoan
 Model View LoanDataChanged 

Output

Use case simple
 
     View      Controller     Model
 ------------ ------------ ------------
 
      FieldXChanged
      +------------>
                   UserChangedInterestRate
                   <-+
                   CalculateLoan
                   +------------>
      LoanDataChanged
      <-------------------------+

[Maulin Vasavada]

HI all,

Here is the seq diagram I have tried to draw,

http://www.geocities.com/maulin_v/RequestChain_SequenceDiagram.gif

Please feel free to point out problems and issues..

Thanks
Maulin

[Bruno Collet]

Hi Maulin,
I think you are right to settle for sequence diagram.
I love them too
To depict a scenario at a technical level, UML provides sequence, collaboration, and, with less technical details, activity and state diagrams.
If you want to illustrate method calls, sequence and collaboration are the ones.
Bruno

[Maulin Vasavada]

Hi Bruno

so do you think the diagram I have put up make sense?

I have one comment on it that is- it doesn't really reflect removeDTO() operation as removeDTO request doesn't end up returning DTO so I can't generalize it but in general sense it give the idea about every operation sequence now if the DTO being returned is null (in case of removeDTO()) then be it so ...

Thanks
Maulin