Originally Posted by
vibguy
The problem is that this happens much more frequently than before.
Of course, the BAEC terms, the booking terms and the possible options (now additionally price differentiation between buying a regular seat and an exit seat reservation) have become so complex that the IT team might have difficulties to catch up and might release too early under pressure from the revenue team.
In addition, the underlying architecture of the system is archaic and is spaghetti code. Try modifying spaghetti code with new lines of code - combine this with poor systems testing - et voila the results we see all the time with BA IT.