Re: OFFICIAL BRAINSTORM TEAM FOR THESIS MAKING (IT thesis projects,proposals,ideas et
ok ang prof mo ah
so kakausapin mo yung mga reservation API ng mga airlines via wire or web.
yung coding madali pero yung connection mo sa airline reservation/ticketing system ang medyo mahirap unless isa kang software provider company
this is not a thesis material dahil sa haba ng development at testing time
kung gusto mo gawa ka nalang ng sarili mong reservation API at yun ang kausapin mo, parang proof of concept nalang at hindi connected sa airline
Indeed, what he really
possibly do si to create his own
mock airline API reservation, then create a a system that will connect to that mock airline.
But if you had already documented that it would connect to multiple airlines, then you would have to connect to multiple mock APIs that you are gonna have to build. And those APIs must not be just a clone of the first mock API that you will build.
For example, you have three different mock airline APIs, let's name it:
• LIPAD Airlines
• iFly Airlines
• AGILA Airlines
Then here's how it could go, LIPAD Airlines will require your system to throw necessary authentication and information details that their API needs to make a response which are the flight schedules, cost of flight, number of vacancy, etc.. Then LIPAD Airlines will make a response of those information in .TXT format that your system would have to process and make it appear in your front-end.
And that data flow was just the one of the many possible transactions that could happen in a booking system, like cancelling their flight, changing their schedules, payment, etc.
And for the sake of example, let me continue to iFly Airlines. Example is that their API requires you to throw data to them in XML format and they would throw back data in XML format too. See the difference?
And for AGILA Airlines, for example is that you are a close partner of that airline or let it be that you are a sister company of them and for that reason, they gave you full access to their databases. Then you would only have to throw authentication data to them before you could actually access their databases.
As Eric said, this is not a thesis material. It requires a lot of time in build phase and much more in testing phase. In my honest opinion, if you can still back out, then back out. Or if you cannot back out, then you would have to be very careful with your SCOPE and LIMITATIONS.
Kudos to all system analysts! (: