I am trying to do the class diagram for my assignment.
The elements in my class diagram are modeled as entities or sessions(@entity and @session). Based on the requirements in my assignment I would like to have a number of "helper" type classes for the sessions. I understand the application service pattern to be "helpers" to sessions. Hence, was wondering if I could stereotype these classes with @application service. Hence I would end up with @entity, @session, @application service?
Instead of using @Session I would rather use the more specific @Stateful and @Stateless, you could lose marks by not being specific enough.
As for the @application I would not personaly use it, I would stick to the default stereotypes @Entity, @Stateful, @Stateless, @MDB and the one for the JSF managed bean (@Managed ?) for the real component classes managed by the container. Any other other class that is not a component managed by the container is a regular class even if it comes from a JEE pattern.
Hi, I completely second Ntumba's suggestions. Be specific about statefull(@Statefull) or stateless(@Stateless) for session beans and also specify @Entity for entities.
Check thisthread for more details on stereotypes.
Sorry - had 1 more question on this general theme.
In Cade's example, everywhere he has a dependency he includes the text "uses" on the dependency line. I find this makes my diagram very cluttered looking. Just wondering if people typically follow that approach