|Course Title||Programming Fundamentals|
|Units of Credit||6|
|Lecturer In Charge/Course Convener||Andrew Taylor |
|Lecturers||Andrew Taylor |
|Admin||Mei Cheng Whale |
Stream A: Central Lecture Block 7
Stream B: Mathews Theatre A
Stream A: Central Lecture Block 7
Stream B: Mathews Theatre A
|Tut-lab||3 hour slot selected when you enrol (weeks 1-10)|
All lectures will be recorded. Unfortunately UNSW's lecture recording system can only be accessed via Moodle Moodle will not be used for any other course activities.
Sometimes urgent information may be sent to you by email. Make sure you pay careful attention to any email you receive.
All official email will be sent to your UNSW email address. It's essential you read this email address regularly. If you forward your email, please be careful to do so correctly and test the forwarding.
Additional information will be provided in the Course Forum. You should check the course forum regularly. It is the best place to ask questions about the course.
Consultations times vary through session and are listed on the course home page.
COMP1511 has no prerequisites, and assumes no background knowledge.
This course introduces students to the basics of programming. Topics covered include:
The course aims for students to become proficient in programming using a high level language, C. By the end of the course, students should be able to construct C programs to solve problems.
COMP1511 is designed for computer science majors, and for any student with a keen interest in computing, regardless of their degree program.
COMP1911 is for students who are not computer science majors. COMP1911 covers a subset of the material in COMP1511 and moves at a more gentle pace.
If you are a computer science major, you must take COMP1511
If you are not a computer science major, but have an interest in computer science and think you may take further COMP courses, you also should enrol in COMP1511
And if you have previous programming experience - and enjoyed it - choose COMP1511
Course Introduction, Introduction to Linux & Shell, Compiling and
Running C Programs,
Data Types, Variables, Simple I/O with print and scanf, Arithmetic expressions,
|Week 2||Nested-If statements, Boolean Expressions,|
|Week 5||Characters and Strings, Command Line Arguments, Multi-file Programs|
|Week 6||Functions, Variable Scope and lifetime|
Dynamic memory allocation (malloc)
Assignment 1 due
|Week 8||Introduction to version control, Structs, Linked Lists|
|Week 9||Stacks and Queues, Abstract data types & Interfaces,|
Assignment 2 due|
C implementation memory models, Invalid C and Security (buffer overflow and other issues), Professionalism, Codes of Conduct, Ethics for Programmers Revision, Exam preparation
|Exam Period||Final Exam|
Topics including development approaches, programming style, testing, debugging strategies and ethics will be discussed though the course as they arise.
This course has a heavy practical orientation. Lectures will revolve around live demonstrations of programming and use of tools. Labs and assignments form a key part.
Lectures will be used to present the theory and practice of the techniques and tools in this course. There will be extensive use of practical demonstrations during lectures. Lecture notes will be available on the course web pages before each lecture.
From week 1 you will also be expected to attend a one-hour tutorial session to clarify ideas from lectures and work through exercises based on the lecture material. You should make sure that you use them effectively by examining in advance the material to be covered in each week's tutorial, by asking questions, by offering suggestions and by generally participating. The tutorial questions will be posted on the Web in the week before each tutorial. There are no marks for tutorial attendance.
Following the tutorial class each week, there will be a two-hour laboratory class, during which you will work on a variety of small practical problems involving the tools introduced in lectures. Because this course is practical in nature, laboratory classes are a very important component. If you do not put a great deal of effort into the lab classes you risk failing the final exam.
Each week, there will be several exercises to work on. These exercises will be released in the week preceding the lab class.
Most lab exercises will be done in pairs, and you and you partner should discuss the exercises before the lab to maximise the usefulness of the class.
Tutors will facilitate you forming pairs in your week 1 lab (which is not assessed). The pairs will change twice during session.
Starting week 3, pairs will also be asked to do code reviews in the tutorials, to explain how they tackled a particular problem and describe interesting features of their solution.
Lab exercises will be automarked (marked automatically by a computer), so that tutors can spend lab time assisting students rather than marking labs.
For each of the lab exercises, both members of each lab pair need
to submit the exercise separately using
You cannot obtain marks by e-mailing lab work to tutors or lecturers.
If you cannot complete the exercise by the end of the lab
you may complete it in your own time and submit it using the
before midnight Sunday (Sunday 11:59:59pm).
Challenge exercises may be specified for some labs.
Some challenge lab exercises typically will specify that they are individual exercises (not to be done with your partner).
Challenge exercises may be silly, confusing or unreasonably difficult.
Do not worry if you can not complete challenge exercises.
Lab exercises will be automarked, using test cases that you haven't seen:
different to the test cases
autotest runs for
(Hint: do your own testing as well as running
There will be partial marks for attempts which fail some of these automated tests.
Automarking will be run several days after the submission deadline for the lab. When it is complete you should be able to view it here or by running this command on a CSE machine:
1511 classrun -collect exercise_name
When all components of a lab are automarked you should be able to view the the marks via give's web interface or by running this command on a CSE machine:
1511 classrun -sturec
There will be more lab marks available than necessary to obtain full marks for the 13% lab component. In other words: total lab marks will be capped.
The lab exercises for week are worth in total 2 marks.
Except there are no marks for the week 1 lab.
Usually each lab exercise will be worth the same - for example if there are 5 lab exercises each will be worth 0.4 marks.
Except challenge exercises (see below) will never total more than 20% of each week's lab mark.
The best 8 of your 9 lab marks for weeks 2-10, will be summed to give you a mark out of 13.
If their sum exceeds 13 - your total mark will be capped at 13.
There will be 8 weekly coding tests from weeks 3-10 designed to give you timely & realistic feedback of your understanding of the course material.
These will be conducted in your own time under self-enforced exam-like conditions.
Each tests will specify the conditions but typically these will include
Each coding test will be automatically marked. There will be partial marks for attempts which do not pass automatic tests. Here is an indicative guide:
|Passes all automatic tests.||1/1|
|Fails several automatic tests.||0.75/1|
Your mark for the coding test component will be the sum of your best 7 of 8 test marks.
Any deliberate violation of the test conditions will result in a mark of zero for the entire programming test component.
The weekly programming test must be completed by Sunday Midnight.
There are two assessable programming assignments. Assignments give you the chance to practice what you have learned on relatively large problems (compared to the small exercises in the labs). Assignments are a very important part of this course, therefore it is essential that you attempt them yourself.
The assignment weighting and deadlines may change a little when the assignment designs are complete.
Late assignments submissions will be penalized. The exact penalty will be specified in the assignment specification - typically it is 2% reduction in maximum mark for every hour late.
There will be a three-hour primarily practical exam, to be held in the CSE labs during the exam period. This will be centrally timetabled and appear in your UNSW exam timetable.
It will contain implementation tasks which will require you to write C programs. It will also contain sections which require you to read code or answer questions.
During this exam you will be able to execute, debug and test your answers. The implementation tasks will be similar to those encountered in lab exercises
COMP1511 has two hurdle requirements on the final exam.
Hurdle Requirement #1: on the final exam you must solve a task by writing a program that uses an array. The final exam will contain multiple questions (clearly marked) which if answered successfully will meet this hurdle requirement. Answering any one of these questions will meet this hurdle requirements.
Hurdle Requirement #2: on the final exam you must solve a task by writing a program that uses a linked list. The final exam will contain multiple questions (clearly marked) which if answered successfully meet this hurdle requirement. Answering any one of these questions will meet this hurdle requirements.
You can not pass COMP1511 unless you achieve both the above hurdles. However you will be offered an additional chance to pass the hurdles in the supplementary exam, if you achieve a mark of 50+ but do not pass both hurdles.
|Final Exam (exam period)||54%|
Students will be offered a supplementary exam if they miss the original exam due to (documented) illness or misadventure.
Students who will be automatically offered supplementary assessment if they achieve a final mark of 50+ but fail to meet the hurdle requirement, if they have attended 9+ tut-labs, 8+ programming tests and have made reasonable attempts on all assignments (achieving > 45%)
Students with final marks in the range 40-49 (whether they have met the hurdle requirement or not) will also be offered supplementary assessment if they have attended 9+ labs, 8+ programming tests and have made reasonable attempts on all assignments (achieving > 45%)
The supplementary exam is I scheduled for the week 27/05-01/06. It is your responsibility to be in Sydney and available for the supplementary exam. No alternative will be offered.
The Student Code of Conduct (Information, Policy) sets out what the University expects from students as members of the UNSW community. As well as the learning, teaching and research environment, the University aims to provide an environment that enables students to achieve their full potential and to provide an experience consistent with the University's values and guiding principles. A condition of enrolment is that students inform themselves of the University's rules and policies affecting them, and conduct themselves accordingly.
In particular, students have the responsibility to observe standards of equity and respect in dealing with every member of the University community. This applies to all activities on UNSW premises and all external activities related to study and research. This includes behaviour in person as well as behaviour on social media, for example Facebook groups set up for the purpose of discussing UNSW courses or course work. Behaviour that is considered in breach of the Student Code Policy as discriminatory, sexually inappropriate, bullying, harassing, invading another's privacy or causing any person to fear for their personal safety is serious misconduct and can lead to severe penalties, including suspension or exclusion from UNSW.
If you have any concerns, you may raise them with your lecturer, or approach the School Ethics Officer, Grievance Officer, or one of the student representatives.
All work submitted for assessment must be your own work.
Lab exercises must be completed by you and your partner.
Assignments must be completed individually.
Submission of other people's work as your own (plagiarism) has a major impact on learning so we use plagiarism detection software to search for multiply-submitted work.
Make sure you read:
This feedback is used to improve the course materials and their delivery.
In the most recent session feedback was very favourable probably as a result of changes based on the previous session's feedback. Feedback from surveys for COMP1511's previous offerings has resulted in changes to COMP1511 delivery, including introduction of weekly programming tests. Some lab exercises and lecture topics will be updated to better reflect current practice.
Students are also encouraged to provide informal feedback during the session, and to let the lecturer in charge know of any problems, as soon as they arise. Suggestions will be listened to very openly, positively, constructively, and thankfully, and every reasonable effort will be made to address them.