• Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

Part II: Questions regarding the component diagram

 
Mark Egloff
Ranch Hand
Posts: 30
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hello there

I have a couple of basic questions how the component diagram should be modeled and what it should contain or not. Let me know your thoughts.

- Which kind of stereotypes should be used? Should I use generic ones as "application", "library" or only J2EE Patterns releated as "Business Delegate"? or both?

- When should I use a stereotype, when a label on a dependency link? Should I prefer therefore labels instead of stereotypes?

- Should I include a component "BDOM" with stereotype <<library>> in my component model, which represents the business domain class model?

- Should I model only one component for the JSP's or each JSP separately?

- What is about the DAO's, should I show DAO separately or only one and add there some note?

- what is about the interfaces, I saw some component diagrams there has been shown interfaces as "HTTP" or "XML". I don't thikn that this should be part in a component diagram, this is more related to a deployment diagram. To list all home and remote interfaces of a bean makes also no sense in my eyes. So what type of interfaces do you suggest to show?

Thank you
regards
Mark

[ January 01, 2005: Message edited by: Mark Egloff ]
[ January 01, 2005: Message edited by: Mark Egloff ]
 
Mark Egloff
Ranch Hand
Posts: 30
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Nobody yet? Please don't let hang me around with this... Thanks....
 
Parag Doshi
Ranch Hand
Posts: 317
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Mark,
Some of my thoughts...

- Which kind of stereotypes should be used? Should I use generic ones as "application", "library" or only J2EE Patterns releated as "Business Delegate"? or both?


Most of the literature will talk about using the "application" , "library" stereotypes. I used stereotypes <<entity bean>>, <<stateful session bean>> etc. I did not use the generic ones. I also didnt use Business Delegate etc as the name of my component had them appended at the end. For eg. LoginServlet, WebAppBusinessDelegate etc

- When should I use a stereotype, when a label on a dependency link? Should I prefer therefore labels instead of stereotypes?


I have used stereotypes for my components and labels for my dependency links.


- Should I include a component "BDOM" with stereotype <<library>> in my component model, which represents the business domain class model?

My BDOM components were either realized as entity beans or as POJOs. I made a note that if its not sterotyped as Entity bean, then its a POJO. I havent used any generic stereotypes, though it can be very well used there.



- Should I model only one component for the JSP's or each JSP separately?

One should be enough. Create a component and stereotype it as <<JSP>> and attach a note suggesting that this represents all JSPs in the system or words to that effect.


- What is about the DAO's, should I show DAO separately or only one and add there some note?

You can take the same approach as JSP, but I showed the DAOs separately.


- what is about the interfaces, I saw some component diagrams there has been shown interfaces as "HTTP" or "XML". I don't thikn that this should be part in a component diagram, this is more related to a deployment diagram. To list all home and remote interfaces of a bean makes also no sense in my eyes. So what type of interfaces do you suggest to show?


You are right. I didnt show any interfaces other than my business interfaces (For eg. I have Adapter interfaces and its realization components). I have avoided showing any other EJB related remote/local interfaces and also the HTTP and XML related once. My focus was mainly on the business interfaces and components.


HTH
Parag
 
Ajith Kallambella
Sheriff
Posts: 5782
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
If you haven't already, checkout http://www.agilemodeling.com/style/componentDiagram.htm
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic