I have been looking at Roberto's Data class locking program and notice it includes tests of create and delete as well as update and read when checking for deadlock etc.
In my assigment URLyBIRD and most peoples it seems we are only required to supply find and booking functionality to the user. Although I did include an implemenetaion for create and delete it is not actuallly used by the GUI at all.
So I am wondering would the assignment assessors test our create and delete implementation when assessing out locking.
I think they will do a full test of the interface they provided (and you must implement). Of course this is just speculation, because I don't really know. I used JUnit test to have a full coverage test of all my methods. So i was pretty sure they would work as expected.
Champion... even though we are not required to provide the functionalities of creating and deleting records, I'd say we must provide valid implementations for these methods. I know that we can't really confirm that, but thinking of reuse, let's say that there's a method somewhere in a class that expects the same interface that we are required to implement... and in this method, records are created and deleted, and they want to use our implementation... if we do not provide valid implementations, this wouldn't be possible... and of course, this would be just a scenario where the assessors could verify if you thought about reuse when developing your assignment.
I agree with Roberto that you should provide update for all fields. It may not mention it directly but i think that it is better to implement it, at least i did in my approach. Since you are able to create a new record I don't see why the user will not be able to update that record. Regarding the implementation its faire simple, since the mechanisme is the same, the only difference would be to change the location of the file you are updating instead of create where appends data on the end of the file