Regarding the new save/load facility, should it replace the existing save/load implementation ?
|No. The new save/load format should come in addition to the existing format.|
Some of the features are actually already implemented in my submission for assignment 4a. Does it count?
|Yes, but you should explicitly mention these features in the list of features (in the "Help->About" dialog box) so I would not miss them.|
The textual file format you presented does not conform with my implementation, so i need to change it. Am I allowed to do so? (The problems: I have an unique Id for each object, the price we use is a double, The passanger type is a String...)
|No, you are not allowed to change the format. I am sure you can find a creative solution for the problems you mention.|
Can we assume that in the textual file we open, the rows are sorted so that passengers and flights come first and only then the tickets?
|No, you cannot assume that.|
Should the buttons in the toolbar show icons, or can they show text instead?
|They can show text. But such toolbars make the program a little less user-friendly (compared to tool-bars with icons), so you may loose points in the "usability" grade.|
Should the toolbar contain all the actions available in the menus, or should it contain only the frequently used ones (such as add/remove rows, undo/redo, check data)?
|As in most GUI applications, the tool-bar should offers only the frequently used actions.|
What happens if a passenger has two (or more) flights from an airport to two different destinations? How do we compute the "remaining" value in such circumstances?
|The remaining value should contain the maximum length of a sequence computed over all possible sequences leaving the target airport. For example, if we have these tickets (assuming all departures take place less than X hours from the previous arrival):|
Ticket 1: Tel-aviv -> NY
Ticket 2: NY -> Chicago
Ticket 3: NY -> Toronto
Ticket 4: Toronto -> Moscow
Then we have that:
remaining(Ticket 1) = 2
remaining(Ticket 2) = 0
remaining(Ticket 3) = 1
remaining(Ticket 4) = 0
You said that the features in the excercise are worth 50 points overall. There are 10 features, are we to understand that each feature is worth 5 points?
|The features have different weights based on their difficulty. On average each feature is 5 points.|
When calculating the remaining value my algorithm goes into an infinite loop if a flight duration is zero. Can we avoid that?
|In such cases you may display a special symbol (such as: "???") indicating that you could not compue this value|
What file-name suffix should the program use for the textual format?
|Use the ".csv" suffix|