CSCI 439 project

CSCI 439: project resources

Clarification: your proposal can be submitted as a pdf through the VIULearn "project proposal" assignment posted for the course.

The term project for the course is worth 15% of your total course grade, and there are two different forms of project available: a research project+presentation or an applied project+demo.

Students are required to attend all project presentations during the final week of classes.

Option 1: research project+presentation
For this option, the student must:

select an area/aspect of compiler theory/application that they find interesting and submit a one-page proposal by 1pm February 12th. The proposal should clearly outline the area to be studied, the planned scope of the study, and how/why it is directly relevant to the course.
study existing works in that area,
write a 3000-5000 word paper summary of the area, to be submitted as a pdf through the git, as described below, by 5pm April 11th
carry out a short (10 minute) presentation in either the lab or lectures during the final week of lectures [exact presentation schedule to be worked out in March]

For grading, the proposal and presentation are each worth 10% of the overall project grade, and the paper itself is worth 80%.

Option 2: applied project+demo
For this option, the student must: develop and implement a compiler or similar tool (interpretter, translator, etc) based on a chosen pair of source/target languages. Either or both languages may be existing languages, variants of existing languages, or entirely new languages created by the student.

As with the research project listed above, the student must submit a one-page proposal by 1pm February 12th. The proposal should clearly outline (the relevant subsets of) both languages and why they were chosen. If only a subset of a language(s) is to be supported then that subset should be clearly described by the proposal.

The student's completed compiler (or other tool) must run on csci's pups/cubs, and is to be submitted through git, as described below, by 5pm December 9th. The submission must include all source code, makefiles, and clear/detailed instructions on how to build/use the tool.

The student will carry out a short (10 minute) demo of their product during the final week of labs [exact presentation schedule to be worked out in November].

For grading, the proposal and demo are each worth 10% of the overall project grade, and the project code/makefiles/instructions are worth 80%.

VIULearn assignment for submission of proposal

A VIULearn assignment ('Project proposal') has been posted for the course to allow you to submit your written proposal as a pdf. The proposal is due on Feb. 12th, but I've allowed a wider date range on VIULearn just in case things go wrong, folks are late, etc.

Git project distribution/submission for final code

A git repository will be made available for code submissions for the final project, all relevant materials should be submitted by the usual fork/clone/add/commit/push cycle (recap shown below).

Reminder of git fetch/clone/submit cycle:

To obtain the project repo initially
   ssh  csci  fork  csci439/project  csci439/$USER/project
   git clone csci:csci439/$USER/project

To submit, be sure you are inside your cloned repository
and have done a "git add" for each file to be submitted, e.g.
   git add filename

Create a commit for the submission, e.g.
   git commit -m "final project submission"

Push the project
   git push origin --all
(being paranoid here with the --all just in case you've created branches)