Hi Mark,
Thank you for clearing that up. I don't want to be too persistant in my questions, but i thought it may help others to see the distinction you found. Thanks, I appreciate your find.
Here is how it may help:
Although a design should be implementation nonspecific, I have found with EJB that an exception must be made. If I am using EJB 2.0, I will use more data objects as cmp entity beans instead of DAO. If I'm using EJB1.*, then I may not have any entity beans. This change would show up in the class diagram and sequence diagram.
Also, I have read the discussions about whether to indicate EJB classes in the class diagram. Since this project is a mandatory J2EE project, then I think it is ok and appropriate to mention indicate the presence of EJB classes in the class diagram.
Thanks again, Mark for pointing out the EJB version.
-Ravi