- Final Submission Checklist Student Name Date Overview Of The Purpose For The Project Functionality Abstract And Modu 1 (150.74 KiB) Viewed 30 times
Final Submission Checklist Student Name: Date: Overview of the purpose for the project, functionality, abstract and modules of the project: UML class diagram to visually model classes of the project including all member variables and methods: Testing Instructions (How does someone run the program?) Describe how tested Feature/Concept Provide Details/Proof Self-Score Demonstrated Where is it located? You may self-score yourself on the following parts. Points are listed to the left. If you have completely fulfilled the project requirement, you may copy the points to the self-score column. 100% Complete: Copy value to self-score Partial Score: If the concept/construct is partially implemented then assess yourself as to what percentage it is complete. Example: 5 pts but concept 80% complete = (5 *0.80) = 4 0% Complete or no details: Enter O into self-score. If no details as to "where it is located?", then score = 0. (5 pts) Main/Start Java (java) file (10) File Input & output(Reading data from a file Writing data to a file (10 pts) Use of 2 cases of abstraction (10 pts) Use of 2 cases of encapsulation (5 pts) Use of 1 case of inheritance (5 pts) Use of 1 case of Polymorphism (10 pts) Use of 2 abstract classes (10 pts) Use of 2 Interfaces (20 pts) GUI (5 different widgets/graphical elements such a label, menu, frame, button, dialog, etc.) (10 pts) Event-driven- programming • 1 case of keyboard input handling • 1 case of mouse (move or button click) handling (10 pts) Handling bad data • One example of testing for bad data entry • One example of using try-except-finally • One example of handling bad data file handling