Win a copy of The Little Book of Impediments (e-book only) this week in the Agile and Other Processes forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

Class Diagram

 
Rishi Krishnan
Greenhorn
Posts: 28
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi,

I am totally confused on this.

From the business stand point Equipment and Seat entities have whole/part relationship. But I am not realizing(using) this relationship in my EJB implementation. DAO takes care of getting seats for a Equipment.

Now do I have to provide a composite relationship between Equipment and Seat?

if I do'nt indicate this relationship in EJB, there is no where in the class diagram that I can show this relationship(between equipment and seats).

Appreciate any thoughts.

Thanks
 
Marc Peabody
pie sneak
Sheriff
Posts: 4727
Mac Ruby VI Editor
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
You've implied that the seat chosen by the user will not need to be persisted.
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic