1. Welcome to CS102 Algorithms & Programming II
David Davenport
Computer Engineering Dept. Bilkent University
Tel: (290)1248 Room: EA424
Office hours: any time free!
use the course forums on Moodle…
English
Shout if you don’t understand!
Last updated: 2/2/2015
Previous: 4/2/2014
Welcome to back & to CS102.
All being well this should be section X
Feel free to me with questions or for appointment
In general, if you need help please use the moodle forum. Everyone is expected to contribute!

2. Question….
here?
you
are
Why
Why are you here?

3. This course should help you…
improve your programming abilities
Enhanced OOP
GUI & Event-driven programming
Recursion
Data structures
practice core engineering skills
Written & oral communication
Teamwork
Independent learning

4. Course - Organisation CS102 taken by all CS & EE students
(~250) in 6 sections (4 instructors, lots of assistants!)
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
Course schedule
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.

5. Course - Grading Exams & labs are common to all sections
Overall grades course-wide, not section by section!
15%     Lab. Assignments
30%     Midterm Exam
15%     Final Exam
20% *  Reports, Presentations & Participation             {Requirements 7%, User-Interface 8%, Detailed Design 5%}
10% *  Demonstration, Final Code & documentation. (+ wiki & peer grade)
10%     Homeworks & Quizzes
Minimum course requirements to be eligible for final exam…
* everyone in group gets same grade (unless not doing their share!)

6. Minimum course requirements
more than 30% on the midterm exam
more than 50% average on quizzes & homeworks
more than 70% class attendance
more than 70% lab average
personal project logs properly completed each week
reasonable contributions to each project stage.
New regulations came into effect Spring 2012/13.
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!
Failure to meet these minimum course requirements will result in an FZ grade.

7. Grading Scales Labs Projects
(100) Fully complete, correct and understood
(80) Almost fully complete, correct and/or understood
(20) Incomplete/incorrect, poor understanding, little real interest/effort shown
(0) no real attempt!
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!
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 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.,
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!

8. Grading Scales Labs Projects
(100) Fully complete, correct and understood
(90) Almost fully complete, correct and/or understood
(0) no real attempt!
Students must upload whatever done 24 hours before lab. Get feedback and correct during lab. Resubmit without penalty. Demonstrate understanding. The objective is to learn.
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!
Older explanation!
Students will be informed of problems with their lab work and are expected to correct and resubmit it.
Within reason, students may resubmit work several times providing they are making a concerted effort to learn.
In such cases, there will be no loss of grades.
Students must demonstrate that they understand the concepts included in lab assignment.
To receive 90 it must be more than 90% complete and correct, anything less gets zero!
In other words, students are expected to properly complete all assigned work.
To check understanding, TAs and instructors may ask individual students questions related to their solutions.
They may also ask for modifications and/or tasks in addition to the prescribed lab assignments.
Failure to complete these tasks correctly may result in a grade of zero!
In giving a grade of 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 zero. 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.,
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!

9. Course - Misc Lab sessions start week 3 Use Moodle –check frequently!
See also (your section’s webpage)
Textbook
Java Software Solutions, Lewis & Loftus International 8th edition (as for CS101)
You 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.)
Continue using Moodle for assignment submission, etc. (must enroll via SRS).
Hint: subscribe to main forum to get announcements.
Cheating/plagiarism… don’t even think about it!
a number of students had disciplinary proceedings against them last semester!
Cheating/Plagiarism!

10. Good luck ToDo Any questions? Enroll to Moodle
Lab assignment 1 (due in lab week 3)
Find group & project (asap!)
same section only
5 people
Any questions?
Reminder:
Groups from SAME SECTION only.
Normally 5 people. minimum 4, maximum 6 people (if circumstances require)

11. Be aware - Beware ENGLISH only! Learn by doing Design Testing
Team work
Estimation
Record keeping
Usability

13. Course Timetable Out of Date
Monday
Tuesday
Wednesday
Thursday
Friday
8:40
Sec 2
Sec 7
Sec 1
Sec 4
Sec 3
Sec 5
9:40
10:40
11:40
12:40
13:40
lab sec 1
lab sec 6
lab sec 2
lab sec 7
lab sec 3
Sec 6
lab sec 8
 lab sec 4
Sec 8
 lab sec 5
14:40
15:40
16:40
Clipped from webpage!

14. Course Timetable
See SRS
Sections 1, 2 & 3 ( Spring 2010/2011)

15. Why are you here? How did you understand the question?
The universe, the university, the CS dept., CS102?
To Learn… (hopefully!)
How?
by being told (require background, must listen & apply!)
by doing (no alternative, you must do it, no one can do it for you!)
c.f. learning to ride a bike, play a musical instrument or even becoming fluent a foreign language.

16. Why are you here? Can you learn for me? To learn (hopefully!)
Learning is something you have to do for yourself, no one can do it for you
All students are individuals, learners who come with different backgrounds, interests, abilities, goals, etc.
As a “teacher” all I can do is act as guide & support,
& help you get the confidence to continue learning on your own if you wish.
Also, must check whether you meet local, national & international standards.
Provide feedback telling you when & why you are not meeting them.
It is then up to you to resolve any shortcomings.
Note: can also demotivate, drain confidence!

17. Honesty & Trust You expect me to be honest
And I expect you to be honest too!
I do not intend to invest time & resources trying to prove otherwise.
You can only cheat yourself
The course is arranged so there is little or no benefit in terms of grade, all you may gain by copying, is time now. In the long-run you will lose much more, in terms of both trust, learning & so grades!
Violations of trust
That do come to light will be severely punished.
What counts as cheating?
Mostly obvious, I would hope! Acknowledge your sources. Always indicate the extent & source of any help you received or ideas used.
Give credit where credit is due.
Do not claim (or appear to claim) as yours, ideas that have come from someone else.
See university policy on academic honesty.

18. Neat stuff… Sun advert "Java is everywhere!"
World without Java Commercial (comedy?)
"Bumptop Prototype" 3D desktop using "piles" and pen gesture input on Tablet, NEAT.
oh, and don't forget the rap version
Perhaps, if time, equipment & network permit?
DEMOS examples of previous years projects…

19. Schedule - Spring 2009/2010 See moodle Week Beginning... Class Project
Lab 1
1 Feb.
Introduction & review 2
8 Feb.
Review objects, classes & arrays
Groups & Projects (fixed by Fri. 12th)
Lab1 due 3
15 Feb.
Inheritance & polymorphism
Requirements Reports {drafts}
?quiz? 4
22 Feb.
Abstract classes & interfaces [prj]
" {critique & presentations}
[prj] 5
1 Mar.
"
" {presentations & revised reports}
Lab2 due 6
8 Mar.
GUI's
User Interface Reports {drafts}
Lab3 due 7
15 Mar.
"  {critique & presentations}
Lab4 due 8
22 Mar.
"    (Midterm - 10am Sat. 20th March )  [prj]
"  {revised reports} 9
29 Mar.
Detailed Design Reports
Lab5 due 10
5 Apr.
Holiday – Spring recess 11
12 Apr.
Recursion
" {presentations...} 12
19 Apr.
 " {23 April Fri. holiday}
Implementation
Lab6 due 13
26 Apr.
Streams & exceptions {29th Apr - 1st May Spring Festival,  not holiday! } 14
3 May.
Data structures
Lab7 15
10 May.
"   & Concluding Remarks
Demos! {revised DD reports} 16
17 May.
Final Exams {17th - 29th May}

20. Schedule - Spring 2010/2011
See moodle