Identifying Entity Beans in Enterprise Applications
Generally speaking, entity classes identified during the analysis phase should be used as starting points for determining the entity beans you will require for the system.
Referring back to the HomeDirect online banking case study, you might recall that we identified one or more entity classes as we went through specific use cases. For example, the entity classes involved in the Transfer funds use case included Account and CustomerProfile, among others. Both are good candidates for entity beans because each is fairly granular and stands by itself.
Of course, Profile also contains the user's name and customer identifier. Would it make sense then to create distinct entity beans for each Profile? ...