Hi Akash,
You could think about what changes might occur in the future, and see if they can be handled by your current design with little or no disruption to the user.
So if a column was added to the database, would your program handle it?
If the user wanted to search on an additional column, could that be added to your GUI easily?
If the user needed to enter an additional piece of information to do a booking (say an owner name) would you have to make major changes to your user interface (requiring retraining / disruption)?
If the FBNS decided to swap to the other network protocol (the one you have not implemented), could it be added without too much work?
If FBNS decided to do a web interface, could they reuse some / most of your code?
As far as the 'control scheme' to handle this: if you use some design
patterns, this all falls into place. At least that is how I choose to read it. So by using MVC, I have a scheme for future web connectivity. And so on.
Regards, Andrew