The goal of this project is to build a single system that uses multiple languages to do its work. It is very difficult to quantify the “size” of a project, but it should be enough to justify marks for 26% of a 3rd year CMPT course. In particular for this project, you should have: • several pieces of interacting functionality (which give us the excuse to use multiple languages); • overall complexity that leads to a thousand to several thousand lines of code (while also noting that lines of code is a horrible way to measure complexity of software); • complexity added by the technical challenge of getting multiple languages to work together; • a system that can be easily deployed and actually works. A couple of possible topics for the project can be found on the project ideas page. You do not have to choose from those ideas and are free to choose any topic if it meets the requirements specified below.

In this examination, candidates are allowed to have three sheets of A4 paper with whatever notes they desire written or printed on one or both sides of the paper. Magnifying devices to enlarge the contents of the sheets for viewing are not permitted. No further notes, printed matter or books are allowed in this exam.

This assignment has just one exercise. It is designed to help you get familiar with hashing and Java’s HashMap.

The course-work constitutes a total of 30% of the final course grade (∼ 30 hours per student in total). The course-work deals with a single problem but is split between two distinct pieces of work: • Component A: Group-based exercise worth 25% (∼25h per student) of the final course grade. Marked by the lecturer or a qualified marking assistant. Written feedback will be provided to the group and potentially to the individual student in case individual grades deviate from the group’s grade. Submission: Friday 4th December 4:30pm via Moodle. • Component B: Individual video presentation worth 5% (∼ 5h per student) of the final course grade. Marked by the lecturer or a qualified marking assistant. Individual, written feedback based on the marking scheme. Submission: Friday 4th December 4:30pm via Moodle.

This is an open-ended assignment in which you are expected to write a detailed report documenting your results. Please submit your solution electronically via gradescope, on or before Dec 7 (Monday week 10). Submissions should be in the form of a written report, which is expected to be at least four pages (double column, 11pt), or roughly 2.5-3 thousand words, plus figures, tables, and equations. See an example template in the lecture slides to get an idea of the length expected. Examples of datasets and projects that may be of interest in this assignment will be discussed in the lectures, though you may use any dataset you wish (including the ones we used for Assignment 1). For a selection of datasets that I frequently use, see https://cseweb.ucsd.edu/~jmcauley/datasets.html

1. This project is to be completed independently, with no outside help except for a named teammate, if you have been assigned one. You may use whatever class materials you wish in completing this assignment. BUT DO NOT DISCUSS QUESTIONS OR RESULTS WITH ANYONE ELSE, WITHIN OR OUTSIDE OF THE CLASS. Failure to follow this directive will result in a failing grade. 2. Late projects will be accepted at a penalty of 2 points/hour (it’s a 100 point project), strictly enforced.

Write or print your solutions in A4-size paper, convert to one pdf file and submit on blackboard. The test is between 7:30pm-9:30pm, and you have 30 minutes (due 10:00pm) to upload your solutions.

Your answers to the problems in this section should be proofs, unless otherwise stated. F is a field, V and W are vector spaces over F.

Objectives: - Assembly language programs in x86-64 - Using assembler directives in x86-64 - Writing code for functions in x86-64; passing parameters in accordance with System V ABI conventions - Working with values smaller than 8 bytes - integrating C and assembler functions - working with structures in assembly language

Throughout this course you will be designing and implementing a Data Science Toolbox using Python. There will be 5 major deliverables and required, supporting discussion posts. The first deliverable will be focused on designing the class hierarchy, building the basic coding infrastructure, and beginning the documentation process.