This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
I'm using Business Delegates in my project to talk to session EJBs.
My question is how detailed must be the sequence diagram when representing the business delegate.
I mean it seems to me that the diagram would look really cluthered if I represent the business delegate, service locator, EJBHome and EJBOject with the needed interactions to get the EJBObject.
I was thinking in the lines of creating a generic sequence diagram showing how the Business Delegate would interact with the EJBObject and then use just the business delegate in the diagrams for each use case. (The downside of this is that in the sequence diagram you never _see_ any EJB related component, which perhaps may be a requirement for the assigment??)
i think you can do, as you say, a generic sequence diagram showing how the Business Delegate works and using in your use-case realization (sequence diagram) the EJB and not the business delegate. Ex.: actor -> view/controller -> EJB -> DAO (eventually)
GiUsEpPe (SCJP, SCWCD, SCBCD, IBM OOAD, SCEA/OCMJEA 5)
I’ve looked at a lot of different solutions, and in my humble opinion Aspose is the way to go. Here’s the link: http://aspose.com
subject: sequence diagram using a Business Delegate