Introduction to Computer Science I for majors by James Tam | Return to the course web page |
Additional details will be added here as we get closer to the actual exam date.
Many students will find the final exam far more challenging to the midterm.
Similar to how A2 and A3 were much more challenging/harder than A1 final will be harder than midterm (in order to improve your design and problem solving skills you needed to solve more challenging problems).
Also the difference is partly because of the nature of the material (functional decomposition is more complex than looping, looping is more complex than branching etc.) .
How to rise to this challenge:
Going to class and doing assignments will help.
Completing additional practice work can help even more.
Following the 4 tips for success from the start of the term.
It's expected that you are not only familiar with procedural programming concepts but also terminology that you have been taught. Consequently, when terminology is used on the exam I cannot explain the meaning of the terminology. As a purely hypothetical example if you were asked to write proper documentation for a function, I won't be able to explain what 'documentation' means.
Terminology questions have cropped in the past a few times but because Zoom has to be used as the tool for answer questions (and unlike asking your questions in person because you aren't aware of how busy the queue may be in Zoom) I am reminding you all ahead of time so the wait to get questions answered isn't made unnecessarily long and so some of you don't get caught off guard during the final because you don't understand what questions are asking.
Although it has been mentioned in class a few times (and does go without saying) you should go through all the course material and not only become familiar with the programming concepts and practice at improving your hands on skills but you should also study your terminology.
Asking questions during the exam:
Asking questions via email (only send me exam related questions during the day of the exam to allow me to more quickly get through any exam related questions).
The exam can be written within a 24 hour window for the convenience of students. That doesn't mean, of course, that you can ask me questions anytime during that window and expect a timely answer. I will respond to email as best I can during that time, keep in mind however that I am just one person. Unlike a physical exam the drawback is that you cannot see how busy I am with questions. If many of you start sending me questions that I might not be able to get through them all. Keep that in mind, so I don't for instance end up having a single person sending long stream of email questions or send me questions about other things during that time.
Asking questions via Zoom:
- Going into the Zoom link is similar to raising your hand during an exam: you don't raise your hand unless you actually have a question.
- In a similar fashion don't don't go into the Zoom link unless you already have a question otherwise the time wasted letting you into the room and waiting for you to leave will make everyone else's wait longer which is especially detrimental if the queue is long.
One advantage of Zoom is that I can verbally answer questions which is faster than email and I can let all the people waiting in the waiting room know via a single chat message that I am currently busy helping someone. Another advantage is that if needed you can show me the exam question you are asking about via a screen share.
Day/time when I will be available via Zoom: Monday Dec. 19 from 9:30 - 11:30 AM. Since the next set of exams scheduled that day should not commence before noon and the Registrar tries avoid time conflicts when scheduling final exams this should mean that the time when I am available for questions should work for students. To make its accessible for students in all lectures I will use my Zoom link for my office time and not the two different Zoom links for each the lectures: https://ucalgary.zoom.us/j/92187498221?pwd=M0FkK1dwOGxvQ0ZzYXNaaitWNklPdz09
Examination instructions (these are the actual instructions that you should follow when you you start writing so you need to read them beforehand):
For all questions, unless otherwise specified assume that there are no syntax errors in any programs or program fragments.
Open book exam, aids (e.g. course text book, notes) are allowed.
Recording or making captures of the exam in any form is strictly prohibited
The exam must be completed individually, no collaboration is allowed.
The submit feature of D2L:
'Submit' for D2L quizzes is equivalent to you handing in your paper exam in a regular in class exam.
DO NOT submit your quiz until you really are done writing the quiz because, similar to a paper exam, you can't "take back your submission".
DO submit your quiz when you have finished. Similar to a paper exam if you don't hand anything in then you shouldn't expect that it will be marked.
In D2L you will see a submit button twice. When you press one button you will see an option to press the second button. You need to click on both of them to have your exam graded.
The First time you see it is when (I believe) when you get to the last question in your exam you will see the 'Submit Quiz' button outlined (in red in image below).
(The screen capture is from the exam for another lecture so the specific quiz information may not match yours).
Second time after you click on the first button. This time you will see a warning something to the effect that you are now submitting your work for grading and you won't be able go back to your exam if you do so. Click on the second button (again outlined in red) when are really done.
The exam will be cumulative. You are expected to be familiar with material covered before the midterm. But the bulk of the questions will focus heavily on material you saw after the midterm. The exception is functions. Because it's difficult to write useful or even just semi-useful program by applying just one programming concept some exam questions will relate to material from several topics (e.g., you could be required to apply branches, functions, files and lists in just a single question or even in the body of a single function). Consequently it won't be possible to give a topic by topic break-down of the proportion of the exam that relate to a particular topic. However what can be specified is the major topics (worth a greater proportion of the final exam) and the minor topics (still important but will tend to be worth a lesser proportion).
Major topics |
|
Minor topics |
|
|
|
|
|
|
|
||
|
||
|
||
|
||
|
Multiple choice questions ~24 marks |
|
~20 - 30 questions | |
Short answer questions ~24 marksExamples: code writing, code traces/conceptual questions, terminology/conceptual questions. Conceptual questions = relate to a concept, topic or theory computer among the course topics. |
|
~6 questions | |
Cut off scales
Min percent | GPA |
0 | 0 |
10 | 0.1 |
20 | 0.3 |
30 | 0.5 |
35 | 0.7 |
40 | 1 |
41 | 1.1 |
42 | 1.2 |
43 | 1.3 |
44 | 1.4 |
45 | 1.5 |
47 | 1.6 |
50 | 1.7 |
51 | 1.8 |
53 | 1.9 |
55 | 2 |
57 | 2.1 |
58 | 2.2 |
60 | 2.3 |
61 | 2.4 |
62 | 2.5 |
63 | 2.6 |
65 | 2.7 |
67 | 2.8 |
68 | 2.9 |
70 | 3 |
72 | 3.1 |
73 | 3.2 |
75 | 3.3 |
76 | 3.4 |
77 | 3.5 |
78 | 3.6 |
80 | 3.7 |
82 | 3.8 |
84 | 3.9 |
86 | 4 |
90 | 4.1 |
93 | 4.2 |
97 | 4.3 |
1 It's based on a near-final version of the final exam (exact proportions may vary *slightly*)