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.
If we use JSF as the Web framework for the SuD, from Cade's example, it seems we can include the JSP's in the Class Diagram. However, how do we approach the managed beans that will act as the model as well as the action class for the JSP pages? Should we include them in the class diagram? Seems that we need to, but that would increase the non-business functionality clutter in the CD. On the other hand if we dont, the Controller will direct the request to the EJB session bean, which will be obviously incorrect since that will never happen in a JSP application (i.e. bypassing the Managed bean layer). Please comment.
You could divide your class diagram into several separate class diagrams. All having a different viewpoint on the functionality implemented.
Two potential viewpoints are business and application. One focused on the functionality implemented to support the business as stated in the use cases.
And one focused on the technologies used to make it happen.