Last updated on
CS-214 fall 2024 final exam (2/2)
- Course
- Software Construction
- Exam duration
- 3 hours
- Total points
- 160 pts
Exam instructions
There are one exercise set and three mini-labs in the exam.
-
Exercise Set (60 points):
-
CSV Parser (20 points)
Topics: Safe Effects, Exception Handling -
Counter styles (40 points)
Topics: Recursion, Laziness, Specifications
-
-
K-Window Minimum (100 points)
Topics: Data Structures, Trees and Recursion, Debugging
Links
Submission
Submit your solutions through Moodle, like you did for labs during the semester.
- Make sure to run tests locally on your machine with
sbt testbefore submitting. - Submit your solutions as soon as possible for each question. Do not wait until the end of the exam to submit everything at once.
- In most cases, only your last submission will count: make sure not to submit broken code.
- You will not be able to submit a new version of a solution until the last submission is graded.
Exam end
At the end of the exam, you will have five minutes to submit your solutions one last time. Note that the automatic grader can take time when everyone submits together, so you may not see its output for that last submission.
After the last five-minutes submission window, stop using the computer and log out to close your session. Make sure to submit your work before that.
- Except for unforeseen circumstances, code not submitted to Moodle will not be graded.
- Make sure to use the log out menu option to close your session.
- Do not leave the room until permitted to do so.
Tips
- Be strategic: Skim through all problems and start with the ones you’re most comfortable with.
- Don’t waste time: Some tests are harder than others (in some case, we have even indicated that in the exam).
- Go deep: Reading and understanding a problem takes time, so doing just the first few questions of each problem may not pay off. It’s often better to invest in a few problems than to do a small bit of every problem.
- Use the tests: We will give you all tests: use them for debugging.
Do not work on multiple exercises at the same time. Do not start multiple copies of VSCode at the same time. If you want to switch exercises, make sure to shut down all running SBT and VSCode instances first.