Win a copy of The Little Book of Impediments (e-book only) this week in the Agile and Other Processes forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

project organization -domain model etc

 
Peter Warde
Ranch Hand
Posts: 71
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi,

I'm doing Part 2 (passed Part 1 83%) and I have 2 questions about it.

Firstly - Cade shows the domain model with only java classes with no <<EJBEntityBean>> stereotype. Why's this and how should the domain model be depicted in UML terms?

Secondly - I have read some where in this forum that it might be good idea to do a "detailed class design separated from the domain model". So is this just a series of fragments - how do you relate it to the domain mdel if it is separate from it?

Any thoughts on these ( I suppose the question is generally about how to organise the project best so any advice on this too would be good).

Thanks

Peter
 
Dan Drillich
Ranch Hand
Posts: 1183
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi Peter,

Firstly - Cade shows the domain model with only java classes with no <<EJBEntityBean>> stereotype. Why's this and how should the domain model be depicted in UML terms?


When you speak about Cade's domain model, do you refer to Cade's Domain Object Model or to his Class Diagram.

The domain model should definitely be technology independent. It's more delicate when speaking about the class diagram. Cade didn't choose it to be so - he showed three classes as stateless session beans. Many people in this forum believe that this diagram should also be technology independent.

Regards,
Dan
 
Peter Warde
Ranch Hand
Posts: 71
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi Dan,

I do mean the class diagram. Cade shows 3 statesless session beans, but the rest are presumably POJOs eg Product, ShoppingCart, ReturnRequest etc. Some of these should be depicted in my opinion as EntityBeans eg Product (but not ShoppingCart - why isn't this shown as a Stateful Session Bean?).

What's your opinion? And why does Cade take this approach to doing his diagram. I'm somewhat confused about to what degree we should show a J2EE technology solution and have stereotypes indicting <<SessionBean>>, <<Filter>> etc in our class diagrams.

Any thoughts would be much appreciated.

Thanks

Peter
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic