• Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

How complex should be the part-2 design

 
Kiran S Govindaiah
Greenhorn
Posts: 5
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hello all,

I am wondering how complex the design must be for the PART-2 assignment. For example:
1. Should my system handle hike in price after a particular date.
2. Should my system allow reserving a seat of a particular seat to 2 different people? Say the plane goes from A->B->C should I allow B->C reserved by another person if A->B is already booked.
Etc.

Any inputs regarding this matter is highly appreciated. Thanks in advance.

Regards,
Kiran S G
 
Ajith Kallambella
Sheriff
Posts: 5782
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator

1. Should my system handle hike in price after a particular date.


It would be nice to have such a feature, but it is not required. The necessary and sufficient condition to pass the test is to fulfil the requirements ie., all the use cases. Anything extra would be nice, but does not entitle you for more points. I recall that *nothing* about pricing policy is mentioned in the assignment and therefore, you can either ignore the fact that prices can change or implement some strategy that accomodates pricing variations.


2. Should my system allow reserving a seat of a particular seat to 2 different people? Say the plane goes from A->B->C should I allow B->C reserved by another person if A->B is already booked.
Etc.

Again, this would be a nice feature and I'm sure real flight reservation systems incorporates such a thing. However, from the assignment point of view, you are only required to fulfil the "Create and change itinerary" scenario.

In summary, I am not discouraging you from implementing a complex and sophisticated system with plenty of value added feature. However, such complexity is not expected by evaluators at Sun.

Cheers,
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic