• Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

Question about interfaces in component diagram

 
Dhiren Joshi
Ranch Hand
Posts: 463
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I am not quite sure when interface should be shown in component diagrams.
I was thinking it need be shown only when a subsystem is used in the component diagram.
EG ServiceLocator definitely doesnt need an interface and same with the WEB framework calls.
Now EJB's have a Facade which represents thier interface so I am kinda of getting confused when one needs to really show them and when they shdnt be .
Some one please help
Also can some one also explain the design concepts which help in identifying a business model as a composite entity and a Business object..
Please see my previous post. Previous Post

Thanks
Dhiren
 
Dhiren Joshi
Ranch Hand
Posts: 463
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
anybody ... PLEASE HELP!!!
 
jawle jaw
Greenhorn
Posts: 3
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I donot understanding why we have to show interface in component diagram when accessing some other system. Rational Rose doesn't even support that, unless we stereotype a component as interface. Unless I'm missing it somewhere in the tool.
 
Dhiren Joshi
Ranch Hand
Posts: 463
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Thanks Jaw,
I agree with you that where is the need to show interface in component diagram but in many POSTs I have seen contrary to this concept.
SCEAs in thier posts have recommended that interfaces be used.
Any suggestions from any one. :confused
Thanks
Dhiren
 
Dhiren Joshi
Ranch Hand
Posts: 463
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Jaw,
I found a way for Rose to add interfaces in component diagram.
Add interface in logical view and drag and drop it on the component diagram.
Also I took a look at the CAdde's diagram on pg 172-173 . That clarifes the doubt of when to use the interface.
Only if calling a subsystem do we need to use an interface.
HTH
Dhiren
 
Ramon Gill
Ranch Hand
Posts: 344
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi Dhiren & Jaw,
IMO interfaces are only needed in component diagrams when you need to access other systems (i.e. a credit card authoriser). I don't regard a Facade as an interface, so I would use the component symbol for this (see Cade's session beans).

A Business Oject is a noun (Customer, adress, etc). This can be implemented as Entity Beans, DAO's, or as POJO's.

A Composite Entity could be an Account which consists of a Customer as a parent with dependants of Address, Contact Info. You could represent this as a single component.

Ray
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic