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

Departure and Return flight

 
Manny Pacman Pacquiao
Ranch Hand
Posts: 36
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
These are disctinct things but obviously would have the save behaviour and attributes. I've been pondering whether to use Generalization from a Flight object/class or as Aggregate elements object/class Segment. W/c one is the best? The Aggregate idea seems to reflect one-way/round-trip. When one-way there would be one element -- departure flight; otherwise, two elements including the return flight.
 
Cleuton Sampaio
Ranch Hand
Posts: 181
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi, aren�t you complicating things a lot? Why distinguish between a departure and a return flight is important? Aren�t they the same class? You have an itinerary, composed by segments. A segment is a seat booked in an actual flight.
 
Newman Huang
Ranch Hand
Posts: 85
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
hi,Pacquiao
you are on the road. remember not to make thing complicated. pay attention to the differences between architecture and detail design(or implementation).
 
Manny Pacman Pacquiao
Ranch Hand
Posts: 36
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Would you be able to provide me a link that would help me do this class diagram correctly? I really need to establish the proper point of view. Right now i've read on domain model class diagram, that would eventually put me into doing analysis/analytic class diagram(this is where you put the cardinalities, relationships...). I don't need a link that would tell me that a class diagram is a square stuff with attributes and methods... T.Y.
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic