• Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

Cade Class Diagram - Payment and ReturnRequest

 
Peter Bergoff
Ranch Hand
Posts: 103
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hey everyone,

While reviewing Cade's SCEA Study Guide in the case study (pg. 169):

What do you think the Payment and ReturnRequest objects are? I would assume they are Application Services(in J2EE speak). If they are can it be assumed they are StatelessSessionBeans? And if they are StatelessSessionBeans why don't they have the stereotype used with similar objects in the class diagram? All other objects which appear to hold business logic or workflow are StatelessSessionBeans.

Thanks in advance,

Peter
[ June 29, 2004: Message edited by: PETER BERGOFF ]
 
Ramon Gill
Ranch Hand
Posts: 344
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Peter,
A couple of 'implementation' possibilities for the 2 objects you mention are entity beans, or session beans (using DAO's).

However, in my view, class diagrams at a conceptual level should not interested in implementation details (i.e. the type of bean).

Ray
 
Peter Bergoff
Ranch Hand
Posts: 103
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi Ray,

Many thanks for responding.

Cade does specify statelessSessionBean for some of the objects. But these two, which appear to be of the type which need business logic, are very vague.

Any anyone else have thoughts??
 
Peter Bergoff
Ranch Hand
Posts: 103
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I'm really confused by the use of these classes in the Cade class diagram. Are there any design experts or current SCEA people who would be willing to give a guy some help?
 
Peter Bergoff
Ranch Hand
Posts: 103
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Keeping this post alive . . .
 
Ramon Gill
Ranch Hand
Posts: 344
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Peter,
I don't see Payment and ReturnRequest as Application Services. I don't see them as having business logic. To me they are either POJO's or Entity Beans, as they represent entities that are persisted. In this respect, they are the same as Customer and Product, for example.

Ray
 
Peter Bergoff
Ranch Hand
Posts: 103
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
If payment and returnrequest are just for holding data then what class is responsible for doing the business logic for a return or payment?
 
Ramon Gill
Ranch Hand
Posts: 344
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Peter,
look at the Order component diagram on page 172. This shows that the ReturnRequestForm (and ReturnItemForm) details will be passed to the OrderProcessor stateless session bean. I think this stateless session bean will handle the business logic for ReturnRequest.
On the same diagram, OrderProcessor passes details to the Payment subsystem, so again, the OrderProcessor performs the business logic.

Ray
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic