Date: Wed, 6 Mar 2013 13:53:41 +0100 From: Tom Verhoeff Subject: 2IP15, participation, upcoming deadline for graded work, groups Message-ID: <20130306125341.GE26921@win.tue.nl> To: Participants of 2IP15 (Programming Methods) with some activity in peach [Email addresses suppressed] This message covers 6 topics (see the numbered headers). Read carefully. 1. Participation If you DO NOT intend to complete this course for credit and have stopped active participation in the meantime, then please let me know about this a.s.a.p. Note that work for at most one homework assignment may be missing. 2. Deadline for Binary Puzzle Assistant Model that will be graded The model (abstract binary puzzle state) part of the large programming assignment will be graded (20% of final grade). The upcoming deadline is Sunday 10 March 2013, 23:00. 3. Deadline extension If you (think you) have a valid reason for an extended deadline, then you should IMMEDIATELY take action. Please consult the FAQ at . Deadline extension requests sent near or after the deadline expires will need extra motivation. 4. Grading criteria In the model part, we will apply the Checklist for Larger OO Programs, with a particular focus on items 2 (coding standard), 3 (naming), 4 (constants), 5 (auxiliary variables), 6 (coding idiom), 7 (functional decomposition), 8 (locality of declarations), 9 (coupling style of methods), 10 (unit tests), 11 (exceptions), 12 (clear use of classes: enumeration, record type, Abstract Data Type), 13 (iterators), 14 (coherence), and 15 (package + package-info.java). Note that items 9 and 10 of the Coding Standard concern comments and javadoc. This documentation is an essential part of the deliverable. This also means that the application of Design Patters in your model is not a primary concern for the intermediate grade. First, focus on the other aspects, and demonstrate that you have undestood the underlying principles. Design patterns can be applied later as part of refactoring your model, when you combine it with one or more views and a controller. 5. Submission format Please, be reminded that you submit your entire (NetBeans) project as ZIP archive (other formats are NOT SUPPORTED). Peach will show you some archive contents in Preprocessing Steps 0 and 1. Note: If you do not use NetBeans, then it is your obligation to deliver your source files in such a way that we can evaluate your work. Evaluation means that we must be able to read, compile, and run your program parts, including all unit test cases with JUnit 4. This obligation can be met by (a) organizing the files clearly and (b) adding a README.txt file that explains the organization and, in particular, how to compile and run test cases. We are NOT interested in receiving precompiled files (*.class or *.jar); we must be able to compile and run them ourselves. Alternatively, you can move your source files into a NetBeans project after development and check that it works as expected. 6. From three to two instruction groups Because of limited participation in the instruction and lab sessions, we have decided to reduce the number of groups from three to two. Group 3 (Instructor: Gerard Zwaan) will be distributed among the other groups to balance their size. Gerard Zwaan will be involved in grading and other aspects of the course. Sincere regards, Tom Verhoeff -- E-MAIL: T.Verhoeff (a) TUE.NL | Dept. of Math. & Comp. Science PHONE: +31 40 247 41 25 | Eindhoven University of Technology FAX: +31 40 247 54 04 | PO Box 513, NL-5600 MB Eindhoven http://www.win.tue.nl/~wstomv/ | The Netherlands