Win a copy of Cross-Platform Desktop Applications: Using Node, Electron, and NW.js this week in the JavaScript forum!
  • Post Reply Bookmark Topic Watch Topic
  • New Topic

architecture design example  RSS feed

 
yamini nadella
Ranch Hand
Posts: 257
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Design an airline reservation system. For the purposes of this question, we will simplify the system requirements.

Assuming the simple airline reservation system consists of Passenger, Ticket Agent and Flight Attendant. It is common practice in the airline system that they shift the staff around. For example Flight Attendant is sometimes not only is a flight attendant, but also a Ticket Agent(either doing the ticket check-in at the counter or collecting boarding passes at the boarding gate). In others cases, a Flight attendant is also a passenger.

Based on this simple scenario, how do you go about designing a object-oriented system that represents these relationships or hierarchy?

Expect the system to grow and extend. For example adding ground crew(like technician, laggauge personel, etc), pilot, etc. Will your design accomodate the addition of the objects and the new relationships easily? If so, how? Please outline your class hierarchy.
 
Geoffrey Chu
Ranch Hand
Posts: 70
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Is this from your College?

Originally posted by yamini nadella:
Design an airline reservation system. For the purposes of this question, we will simplify the system requirements.

Assuming the simple airline reservation system consists of Passenger, Ticket Agent and Flight Attendant. It is common practice in the airline system that they shift the staff around. For example Flight Attendant is sometimes not only is a flight attendant, but also a Ticket Agent(either doing the ticket check-in at the counter or collecting boarding passes at the boarding gate). In others cases, a Flight attendant is also a passenger.

Based on this simple scenario, how do you go about designing a object-oriented system that represents these relationships or hierarchy?

Expect the system to grow and extend. For example adding ground crew(like technician, laggauge personel, etc), pilot, etc. Will your design accomodate the addition of the objects and the new relationships easily? If so, how? Please outline your class hierarchy.
 
Ajith Kallambella
Sheriff
Posts: 5782
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Since this is a general architecture and design question, you may get a better response in EJB/J2EE forum. I will be transferring the thread over there.
 
Luis Zhang
Greenhorn
Posts: 1
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Could anybody tell me the solution of this example?
thanks so much.
 
Don Morgan
Ranch Hand
Posts: 84
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
The initial posting here is very old, but I see renewed interest....

I would say to start thinking along the lines of "roles" and how role(s) can be an attribute of an employee. Which role(s) are active can then vary as the employee's situation changes.
 
Don Morgan
Ranch Hand
Posts: 84
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
By the way, this does sound (and is stated) much more like an o-o question than an EJB/J2EE question. It should be moved to the "OO, Patterns, UML and Refactoring" forum.
 
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!