100 likes | 211 Views
COMS S1007 Object-Oriented Programming and Design in Java. July 31, 2008. This week. Last time: Networking Chapter 21 Today: Exceptions and Multithreading Chapters 11 and 20 Also: Final Project guidelines. Next Two Weeks. Next week Data Structures (Chp 15 & 16)
E N D
COMS S1007Object-Oriented Programming and Design in Java July 31, 2008
This week • Last time: Networking • Chapter 21 • Today: Exceptions and Multithreading • Chapters 11 and 20 • Also: Final Project guidelines
Next Two Weeks • Next week • Data Structures (Chp 15 & 16) • Design Patterns (not in the book) • Advanced Topics (let me know!) • And then • Tue Aug 12: Final Project Due! And exam review • Thu Aug 14: Final Exam!
Roomba Mania • All working submissions were given three rooms to “clean” • Honorable mention: Alex, Josh, Bobby, Rebecca • Finalists: Courtney, Jao-Ke, Koichiro
Final Project • Due at 5:30pm on Tuesday, Aug 12 • NO LATE SUBMISSIONS ACCEPTED! • The final project accounts for 25% of your final grade • The final exam is 40% and is two days later! • Please submit the code electronically and print a copy to bring to class
Final Project Grading • 75% for the program itself • It does what you proposal said it would. • The design of your classes. • The style of your programming, including adherence to coding conventions. • The readability of the code, including meaningful variable names and good use of comments throughout.
Final Project Grading • 10% for documentation • a "README" file which describes all of the classes in your program, what they do, how they relate to each other, and why you made the design decisions that you did • the README file should also contain a UML diagram of your classes and their relationships • a one page user manual for your application that describes how to run your program and how to use it
Final Project Grading • 15% for robustness and testing • The program should not crash when given invalid inputs from the user • Every public method in your program should have an assert statement that checks that all input parameters are within legal bounds • You must write a complete set of unit tests for all non-trivial public methods in every class • The README file must also describe the system testing that you performed
Final Project Presentation • In class on Tuesday, August 12 • 7-8 minutes or so describing what the program does, the classes you created, how they relate to each other, and why you made the design decisions that you did • 2-3 minute demo of your program • Volunteers only! (You may be volunteered)
Important Dates • Aug 12 • Final Project due (no extensions!!) • Final Project presentations in class (optional) • Aug 14 • Final exam (no makeup exam!)