• Post Reply Bookmark Topic Watch Topic
  • New Topic

class diagram details for part II

 
john tally
Greenhorn
Posts: 16
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi There,
I am not able to decide on Class diagram if I need a separate Reservation Object every time Customer makes a payment or confirms Itinerary- because the details of the Reservation for a given customer are already captured in the Itinerary??
-JT
 
E. Messing
Ranch Hand
Posts: 69
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hey John
I thought that "status" or "payment status" (a member in the �Itinerary� class) is enough for marking the itinerary as paid. Do you think otherwise?
 
john tally
Greenhorn
Posts: 16
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
The sale and reservation are the most common vocabulary in the online systems that involves credit card transactions.
But for this model, I agree with you.....
JT
 
Gravity is a harsh mistress. But this tiny ad is pretty easy to deal with:
the new thread boost feature: great for the advertiser and smooth for the coderanch user
https://coderanch.com/t/674455/Thread-Boost-feature
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!