1. Welcome to CS102 Algorithms & Programming II
Spring 2017/18
David Davenport
Aynur Dayanık
Last updated: 08/02/2018
Pre-requisite: CS101 – students expected to have basic programming skills

2. This course should help students…
improve their programming abilities
Enhanced OOP
GUI & Event-driven programming
Recursion
Data structures
practice core engineering skills
Written & oral communication
Teamwork
Independent learning
Students must have passed CS101 and so have a basic understanding of structured-programming and simple OOP.
TAs duty is to support & evaluate student learning.

3. see weekly schedule on moodle
Course - Organisation
CS102 taken by all CS & EE students
(~250) in 5 sections
2 instructors, ~20 TAs, 5 Graders
4 credits – 3hr lecture & 4hr lab every week
Two tracks…
Lectures & Labs (as per CS101)
Design project
Group & project selection
Requirements, UI design, Detailed Design
Implementation & Demo
Students must attend labs every week even though there may not always be assignments.
At these times they will meet with their group (and their TA) and work on the project.
see weekly schedule on moodle
Use Moodle for…
assignment submission & grading
communication

4. Course - Grading Exams & labs are common to all sections
Overall grades course-wide, not section by section!
15%     Lab. Assignments
25%     Midterm Exam
25%     Final Exam
25% *  Reports, Presentations & Participation             {Requirements 6%, User-Interface 7%, Detailed Design 3%} Demonstration, Final Code & documentation 9% (inc. wiki, weekly personal logs & peer grade)
10%     Homeworks & Quizzes
Minimum course requirements to be eligible for final exam…
Must also do well on final exam to pass!
In addition to minimum course requirements to enter final exam
Students who fail to achieve a reasonable mark on the Final exam will fail the course, irrespective of their other grades!
Note: numbers don’t add up!
* everyone in group gets same project grade (unless not doing their share!)

5. Minimum course requirements
more than 30% on the midterm exam
more than 80% lab average
personal project logs properly completed each week
reasonable contributions to each project stage.
Failure to meet these minimum course requirements will result in an FZ grade.
New regulations came into effect Spring 2012/13
(and revised 2016/17 ~ now no Retake exams!).
Students failing to met the minimum course requirements will receive an FZ grade and be ineligible for the final exam and retake exams.
All this course info is now on moodle & STARS!
Note: Exams are closed book & closed notes; no computers, phones, etc. allowed!
But don’t panic... providing you are working this shouldn’t be a problem!

6. Evaluating Lab work… Labs
(100) Proficient Assignment completed, though a few minor errors may remain. Student is clearly interested in learning, understands concepts, responds quickly, requires few if any revisions.
(80) Acceptable at least 80% of all parts of the assignment completed, most corrections/additional work done, relevant concepts/skills mostly understood though some difficulties remain. Student is interested and working, but still requires guidance and/or considerable revisions.
(20) Weak Less than 80% of work completed and/or revisions not done. Student displays poor understanding, and/or has put little real interest/effort into improving. Fails to revise sufficiently to get 80!
(0) no real attempt!
Students must upload whatever done 24 hours before lab. Get feedback, correct & resubmit during lab without penalty. Demonstrate understanding. The objective is to learn.
Assignments will be given about a week before the lab sessions.
Students are expected to work on them individually & in their own time.
Students must upload whatever work they have done 24 hours before the lab
(even if incomplete; the idea is to demonstrate you really are trying to learn!)
TAs will look at each student’s work with them individually during the lab.
TAs are trying to decide whether the student has understood the relevant concepts and acquired the necessary skills.
To this end, student’s are expected to demonstrate their solution to the TA
+ TAs will check that the solution is logically and stylistically correct,
informing the student of anything which is inappropriate, and
+ to ensure understanding, TAs will, as needed,
+ ask a number of questions about the solution
+ ask for changes/extensions to the solution
+ give additional related programming problems
Students are expected to complete their work correctly,
including any additional programming tasks assigned by the TA,
and show the TA again, during the lab session
(this submission, checking, and resubmission cycle
may be repeated as necessary, within reason, without loss of grades).
Note: repetition of the same mistake after having already being warned
on more than two occasions, will result in a fixed grade of 20 for that lab!
Once the TA is satisfied that the student really has completed the work,
understood the concepts, and acquired the requisite skills, they will assign an appropriate grade
(100 for fully complete and understood, 80 for almost complete and/or understood, i.e. ~80% ok!)
Note: TAs are expected to verbally inform students of the reason for the lower grade.
- this reason should also be recorded along with the grade in the feedback section on moodle.
Until such time, a grade of zero will be given. It is the student’s responsibility to demonstrate work to the TA.
Students who fail to demonstrate any real interest in learning, i.e. are unable to answer questions about the code,
or fail to do the changes/additional code they are asked for, will receive a grade of 20.
Should the student be unable to demonstrate sufficient understanding during the lab session,
TAs may, in exceptional circumstances, give a 24 hour extension.
*****************
Note: In giving a grade of 80 or 100, the TA is saying that the student has demonstrated that they understand the relevant concepts.
Note: Code that fails to meet proper stylistic standards will get 0/20 unless and until it is corrected This includes, but is not limited to:
Incorrect indentation,
poor use of whitespace (including irrelevant multiple blank lines, no blank line between logical sections, especially methods, etc.),
lack of header comments, lack of other comments,
meaningless names (for packages, programs, methods, variables, constants, etc.,)
failure to follow Java naming conventions, etc.
Students will be informed of such problems and given the opportunity to resolve and resubmit the work the first two times.
On subsequent occasions, the grade will be (permanently) zero or 20 as appropriate!
Note: these relate to the student's understanding, not just the specific assignment.

7. Evaluating Project work...
Projects
(10) excellent (almost impossible!)
(8) good
(6) ok but could be better
(4) weak definitely not up to scratch, more effort needed.
(0) no real attempt!
Notes:
Be realistic… (nothing is excellent the first -or second- time!)
Grades are in absolute terms (everyone can get F or A!)
+/- grades & report criteria?
May have different TA evaluate project reports?
Give +/- on each grade, i.e. good+ is 9, good- is 8.
Do not give 10 to everyone (anyone?)
Be critical, point out mistakes, inconsistencies, etc.
But positive, suggests alternatives, give them confidence & support.
Each stage has some
common criteria (presentation, style, spelling, grammar, etc.)
distinct criteria (creativity, etc.)
(see Moodle for further details).

8. Good luck ToDo Any questions? Enroll to CS102 Moodle (via AIRS)
Subscribe to private forum
Add students to CS102-SS groups
Check out course details
Look at Lab01
Any questions?
Reminder:
Groups from SAME SECTION only.
Normally 5 people. maximum 6 people (if circumstances require)
Everyone must attend lab sessions EVERY WEEK
(even if there is no programming assignment due; you must meet your TA & group.)
Continue using same textbook (Lewis & Loftus, 8th edition --though earlier editions are ok too.)
See webpage ~david/cs102/assistants/