This week's book giveaway is in the OCAJP forum. We're giving away four copies of OCA Java SE 8 Programmer I Study Guide 1Z0-808 and have Jeanne Boyarsky & Scott Selikoff on-line! See this thread for details.
Let's imagine: IF you were to upload your assignment, book exam and all that today. Then, after looking at some other people's solutions, you start to question parts of your own. In fact, you are quite conviced about some of the weaknesses of your application, you can even pinpoint them rather directly. Let's then make a little time travel into the examining room, where there are some (horrible) questions about your design popping up... Would you... a) Defend your decisions, even though you know you could have made it different and even better? Or... b) Describe your design's weaknesses and how they could have been done better? ...of course this has nothing to do with yours truly having uploaded the assignment today...
Well you need to defend your decisions. You can always point out weaknesses as this shows in the general considerations score, meaning you know the weaknesses, but went ahead anyway. Mark p.s. I know where I should have done things differently now, but oh well.
I agree with Mark, you can point out that you are aware of the short comings of your design and implementation. However I would not advise arguing against the decisions you made, stay positive and point out the reasoning behind your decisions. If you argue "I used JComboBoxes because I felt that the user may not know all airports off by heart and therefore believed that with the limited number of airports in the data schema the overhead of dynamically loading the JComboBoxes during initialization was acceptable." I think you show the examiner that you have thought about your choice and made a decision which you feel is valid. If however you argue "I used JComboBoxes to display desination and origin airports, but if the schema was larger I would have used JTextFields with a look up table of the available airports." It shows the examiner that you were in two minds about your decision and are not 100% happy with your decision because there is mention of a rewrite of the GUI as soon as the database grows.