Dear Kent,
Does it mean that I should just model Entity Bean as a single attraction instead of having local interface, remote interface, home and local home?
But how about packaging, as I am using Rational Rose, all my classes are seperated by the package,
so if I model with Rose, I will have package within package and finally reaching the leaf package with a single attraction of entity bean inside?
How about the Value Object that I use in the model? As the entity bean has dependency on such value object as parameter or return value. Should I model them too?