• Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

Part II questions

 
Richard Duglora�
Greenhorn
Posts: 14
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi

I'm working on the SCEA assignment (FBN) and I'd greatly appreciate some advice from you guys:

1- It seems to me that an Itinerary doesn't need to be persisted as an EntityBean until (and unless) it is paid, since it is kept only for the duration of the customer's session. Am I wrong ?

2- I assume that only ONE component diagram is allowed (right?). In your opinion, is it better to explicitely draw every BusinessDelegate, Controller, JSP form... at the risk of cluttering the diagram, or is it better to show generically the patterns employed and add a note listing the objects to which they apply ?

Thanx

Richard
 
Eduardo Rodrigues
Ranch Hand
Posts: 199
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hello Richard

My thoughts:

1) I agree with you
2) I split my component diagrams in two, according with the tiers..

See you..

Bye
 
H. Hafer
Ranch Hand
Posts: 108
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Originally posted by Richard Duglora�:

2- I assume that only ONE component diagram is allowed (right?).


That's not the wording of the assignment. It says "one component diagram", not "only one". Anyway, I couldn't come up with a the reason to restrict you to only one diagram. So provide as many component diagrams as you might need to carry the message. Don't forget that the message should be simple, act as an architect, not as developer!

HTH,
Harbo
 
D. Rose
Ranch Hand
Posts: 215
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
1- It seems to me that an Itinerary doesn't need to be persisted as an EntityBean until (and unless) it is paid, since it is kept only for the duration of the customer's session. Am I wrong ?


Go through all of your usecases again before making this assumption. Assignment wording may vary and depending on your specific scenario,you would make assumptions.
In my opinoin we need to store unpaid itineraries as well.
 
H. Hafer
Ranch Hand
Posts: 108
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Originally posted by D. Rose:

Go through all of your usecases again before making this assumption. Assignment wording may vary and depending on your specific scenario,you would make assumptions.
In my opinoin we need to store unpaid itineraries as well.

Huh? Where did you get this from in the assignment?

Regards,
Harbo
 
D. Rose
Ranch Hand
Posts: 215
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
We are not supposed to discuss assignment details here!
 
Richard Duglora�
Greenhorn
Posts: 14
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
There are places in the use(less) cases suggesting that the list of itineraries should be "saved", in order to be presented to the customer later.
If "later" means beyond the current session then yes, the itinerary list should be persisted. Otherwise I see no need.

It's also hard to determine whether the itinerary list should be attached to the customer account or to the session because most use cases require the customer to be logged in (including the ones where the list is accessed), which may suggest that the 2 are linked. But it is not explicitely stated, so I'd lazily go for no link (ie list is just attached to the session). Besides, it doesn't make much sense IMHO to keep a selection of flights forever.

These use cases are incredibly ambiguous and twisted (I don't think I'd hire the business analyst . In real life, we could talk to the client to clarify these points. But for this exam we are on our own

Richard
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic