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.
Class diagram in the cade's book shows jsp's and Java EE stereotypes, i was just wondering weather this is the right approach, its kind of coupling technology choice with domain model. What do you guys think?
There are a bunch of posts discussing this issue - I've seen a few without even searching for them. To summarize: most go with Cades' approach though it is not what they would do in real work assignment.