Should we document the code?
What are the standards by which this assignment is checked?
|Assignment 4a will be checked along with 4b (In assignment 4b you will add some functionality to your 4a program). I will check your initial design and the how this design evolved over time. For example, I would like to see if the new requirements resulted in code duplications.|
If a Ticket contains the passenger seat number, shouldn't the Flight have an "Number of Seats in Plane" attribute?
|This was not required by the customer who ordered this software (Obviously, this may change in assignment 4b). You may add it if you'd like|
Why the flights/tickets do not have a unique id?
|The story in the homework document describes the properties of problem-space entities (flights, passengers, tickets). It is very likely that when these entities are "translated" into program-space elemtns (objects, DB tables, etc.) the programmer will add additional properties which are needed by the implementation. |
It is also possible that some of these additional properties will also find their way into the user-interface, depending on how the program lets the user enter data items.
Therefore, the answer is that you may add additional properties as needed by your implementation.
Also, note that the homework does not require you to define a Passenger, a Ticket or a Flight class. You may represent the problem space entities any way you like.
If the data in the view is illegal, should the model contain the illegal information? if yes - in what way?
|This is an implementation issue which is completely up to you|
Should the program allow performing "Save" when the data in the view is illegal?
Can we use libraries other than the standard Java library?
What should "Check data" check in this assignment?
|For this submission the "check data" functionality need not be full. The basic thing is to check that all tickets have a valid passenger and flight fields. You may add more checks if you want.|