l0 - course admin

8/9/2019 L0 - Course Admin

1/16

CS1010E

Programming Methodology


2/16

Welcome to CS1010E

Cohort is split into three lecture groups

(sectional groups)

1. Monday 4pm to 6pm, LT7

2. Tuesday 2pm to 4pm, LT7A

3. Wednesday 4pm to 6pm, LT2

[ CS1010E AY112S1 Lecture 0 ]2

Gary TanCOM2 03 – 50

6516 [email protected]

[email protected]

Henry ChiaCOM2 02 – 56

6516 [email protected]

[email protected]

mailto:[email protected]:[email protected]:[email protected]:[email protected]


3/16

Module Overview

This introductory level module introduces:

Fundamental concepts of problem solving by

computing

Programming using an imperative programming

language

Objectives:

Learn how to solve simple problem

Learn to write good small programs

3[ CS1010E AY112S1 Lecture 0 ]


4/16

Course Resources

IVLE resources:

Announcement: Please read daily

Lesson plan: Important dates are noted.

Workbin: lecture notes, tutorial questions, labs etc

Solutions will be posted later

Discussion forum

For discussion on things related to the course, Can discuss questions, BUT do not post solutions



5/16

Course Website and Reference Book

Course Website located at:

http://www.comp.nus.edu.sg/~cs1010e

5

[ CS1010E AY112S1 Lecture 0 ]

Reference Book:

Problem Solving and Program

Design in C

by Jeri R.Hanly and

Elliot B.Koffman2010, 6th Edition, Pearson

http://www.comp.nus.edu.sg/~cs1010ehttp://www.comp.nus.edu.sg/~cs1010e


6/16

Grading Final Exam (open book) 40%

Saturday, 19 November 2011, Afternoon Session

CA 60%

Labs and Mini-PEs 36% More on this later

Midterm test (open book) 20%

1st October 2011 12 noon (tentative) Duration: 1 hour 30 min (MPSH)

Tutorials 4%



7/16

Tutorial and Homework

Tutorial Questions Weekly, start from week 3

Students are to present their solutions andparticipate in the discussion

Their performance will be assessed Suggested solutions will be discussed if there is

time and they will be released when the lasttutorial session is over

Homework (Self-Test Exercises) Found at the end of each chapter of the book

Discuss on forum



8/16

Lab Exercises : Types

6 Take home labs

To expand what we learned in lectures To prepare for assessed labs:

2 sit-in labs and

2 mini PEs

NO Weightage Not compulsory

2 Sit-in labs

6% each total 12%

2 mini PEs 12% each total 24%



9/16

Lab Schedules (Tentative)Lab Week starting Type

0 22nd Aug (Week 3) Trial lab

1 29th Aug (Week 4) Take Home (1)

2 5th Sept (Week 5) Sit-in (1)

3 12th Sep (Week 6) Take Home (2)

4 26th Sep (Week 7) Take Home (3)

5 3rd Oct(Week 8) Mini PE (1)

6 10th Oct (Week 9) Take Home (4)

7 17th Oct (Week 10) Sit-in (2)8 24th Oct (Week 11) Take Home (5)

9 31st Oct (Week 12) Take Home (6)

10 7th Nov (Week 13) Mini PE (2)



10/16

Lab Exercises: Attendance Attendance:

NOT compulsory for take home labs Clear doubts and discuss possible approaches

Contact the lab tutor directly if you need extra help

Compulsory for sit-in labs and mini PEs

Absence from sit-in labs and mini PEs: Must have valid reasons (documentary proof)

0 will be awarded without valid reasons

The missing percentage of the session(s) will beaccumulated A makeup session will be organized at the end of semester



11/16

Sit-in Labs: Marking Scheme

Correctness: 70% Able to produce the correct answer

Use reasonable approach

Programming style: 30% More information later in the course



12/16

Challenges Ahead

It is going to be “fun”

[ CS1010E AY112S1 Lecture 0 ]


13/16

Class Size

Some fun facts:

~800 students

Split into 3 sectional groups (2 lecturers)

~30 tutorial classes Need 6-7 Teaching Assistants

~33 lab groups

Blocked out one whole day (Wednesday)

Use all available programming labs in the School of

Computing

~30 Lab Teaching Assistants



14/16

Class Size == Admin Problem

We expect administration problems:

Marking of assessment

Quality of teaching staff

Communication problem between various staff

and students

We will try our best to manage the whole

situation Feedback welcome.….but please be nice



15/16

New System

A new system is deployed:

CodeCrunch

For distributing lab question

For automated feedback on your attempt

Implemented by SoC 3rd year students

Deployed for ~1000 students this semester

Feedback appreciated



16/16

New Approach

In the past…. Over-emphasis on the language syntax

Cover too much detail Information overload

Now, we will: Cover the minimum core syntax

Emphasize more on the problem solving approach

You should: Explore further on the basis we provided

Learn how to learn


l0 - course admin

Documents