design, implement, test and provide suitable documentation documentation for OldTime Rail to allow bookings for the weekend ahead.

The trains consist of 1 engine, 2 compartment cars, and 2 standard cars, plus a baggage car for passengers' luggage. Each compartment car can take 32 passengers in four compartments of 8 seats each. When booking a party into one of these cars, the party should be kept together in a single compartment. Individual seats are identified by a letter (indicating the carriage) and a two digit number (indicating the particular seat). Allow a passenger to choose their departure time (and therefore direction) • Allow a passenger to choose first class or third class • Store all booking details in a text file • Be easy to use • Be robust against errors and invalid input • Provide clear feedback to the user Refuse a booking if there is insufficient space for the passenger(s) or their luggage • Allow a passenger to book just for one or for a party • Allow a passenger to book a suitcase in to the luggage car • Allow bookings for partial journeys, e.g. Suddean Halt to Endline Station, including allowing the same seat to be booked twice on a journey if there is no overlap • Allow the operator to create a report as a text file (for printing) showing the bookings for a given train • Automatically assign seats to a booking (Based on the rules above) Be object oriented, with a minimum of 5 classes 8 • Be easily maintainable, and extendable to more frequent or longer trains. • Clearly separate UI functionality objects from the data manipulation objects • Name classes, variables, methods etc. with meaningful, clear names using consistent, appropriate capitalisation • Be well documented with both normal // comments within functions and detailed /// comments on methods, classes and other definitions • Have a consistent, appropriate layout including good use of indentation, white-space and individual files for each class