The maximum possible score is 400; the minimum to pass is 320. General Considerations (maximum = 100): 90 Documentation (maximum = 70): 69 O-O Design (maximum = 30): 30 GUI (maximum = 40): 31 Locking (maximum = 80): 80 Data store (maximum = 40): 40 Network server (maximum = 40): 40
I thought I would lose lots marks on documentation. But my documentation is good. I included all the choices I had in doing the assignment and tried a lot to make it clear. Seems the markers like it.
I read a lot on the posts from many of your. It helped me a lot. Thank you very much.
Not sure why I lost the points on GUI. Here is the description:
The GUI consists of three major panes: the search pane, the table pane, and the record pane. The search-pane provides the functions for searching. It collects the user's inputs of the search criteria and sends the criteria to the controller to search the database. The table pane displays the returned records of a search. The record pane displays a selected record and allows the user to modify it. For this project, users are able to enter or change the Owner field. Users are not able to modify the records in the table pane directly. The table is non-editable. Record can only be modified in the record pane as mentioned above.
I also included a menu set for config/help/close and the buttons for previous/next page. I think my GUI design and the layout are good.
The reason I lost points on GUI might be of the Swing programming which may not be good enough. I learned the Swing programming only for the assignment.
Hi Joe, Many many congratulations. Could you tell something about documentation, particularly choice and javadoc. Since I am not native speaker, this task really makes me some frustrated.Thanks, and I really admire you.
I do have lots Java and OO development experiences. But I only did the Swing for the assignment.
I did spent the time on the assignment: About 3 weeks on learning Swing, 1 week on prototype on the data file, 2 weeks on the prototype on locking, 2 weeks on prototype on Socket, 4 weeks on putting all the components together, 2 weeks on testing, and 3 weeks on documentation.
I solve the problems when I do the prototypes.
I watch closely on this forum trying to include it to my implementation when I find anything good.
For the documentation, I write down the choices when I code and test. I do documentation, including javadoc, only after I believe I my assignment is in a good shap. My javadoc is much more detailed than my choices. I include all my observations to the javadoc. But I do try a lot to keep everything "briefly but clearly". I think all we need to do is making sure the evaluator can quickly understand the classes and the choices.
I use simple words and simple sentences. But I do spend lots time on spelling and grammar.