• Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

Do we have a product to be sold?

 
H. Hafer
Ranch Hand
Posts: 108
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Dears,

I wonder wether itinerary is a kind of "product" which FBN sells or more kind of "shopping cart" in which one may throw segments (or flights if you wish).

The first one seems to be more appealing (at least to me) because one may freely associate itinerary to a pizza with customer-selectable ingedients.

Does this make sense?

Thanks,
Harbo
 
Parag Doshi
Ranch Hand
Posts: 317
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I think that the segments/flight are the "products" in the system. Itinerary is just a grouping or ordering of the segments as the user sees fit to utilize.
This can be taken a step further to say that a segment is a generic product description ,while a flight is the actual product which generates revenue for the system. In other words, for this system a flight is one of the ways a segment is fulfilled, in some other systems, the segment could be fulfilled by either a flight, car rental, cruise or a water-taxi.

This is my understanding of the system.

Parag
 
H. Hafer
Ranch Hand
Posts: 108
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Originally posted by Parag Doshi:
I think that the segments/flight are the "products" in the system. Itinerary is just a grouping or ordering of the segments as the user sees fit to utilize.


The BDM marks a 1-to-many relation between Customer and Itinerary. There's no contradiction to your description, however, it follows that the customer may utilize up to many ordered sequences. Oh, that's probably the same

Thanks,
Harbo
 
Gerald Davis
Ranch Hand
Posts: 872
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I will have to come back to you on this. I have to go to work
 
Jiboo John
Greenhorn
Posts: 4
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
This is how I understand the Itinerary/Segment/Flight entities.

As per BDOM, customer has One to Many relationship with Itinerary... if we consider these two entities as RDBMS tables, every record in Itinerary table will have customer id as a foreign key (customer creates itinerary). Simillarly, itinerary has one to many relationship with segment table. This means that every record in segment will have itinerary id as a foreign key.... based on the above BDOM directions, I think segment is also created while creating the itinerary... by which I mean Segment is not something that is already available for the customer to choose from.... rather flight is something that is already available for the customer to choose and search and segment/itinerary are created as an output of the search....

Segment to flight relationship seems to me like one to many, segment entity has a reference of flight, in other words flight reference will be a foreign key to segments entity.. One flight can be a part of many segments..... woohhhhhh i am tired of typing...

any thoughts???
 
D. Rose
Ranch Hand
Posts: 215
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I think there is little confusion here. Single Itinerary could still be a product consusting of flights ( relate to order-items etc). Shopping cart can have multiple itineraries.
 
Jiboo John
Greenhorn
Posts: 4
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Rose, I agree.... I think I posted my query to a wrong thread....I apologize for the confusion..
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic