Deprecated: The each() function is deprecated. This message will be suppressed on further calls in /home/zhenxiangba/zhenxiangba.com/public_html/phproxy-improved-master/index.php on line 456
Com S 541: Details About Interim Project Report
[go: Go Back, main page]

Department of Computer Science

Com S 541: Programming Languages

Got a question?

Got a question or comment? Contact us at (515) 294-6168 or hridesh@cs.iastate.edu.

Interim Project Report: Due Nov 3, 2008 at 11:59pm CST

Format for Interim Report: Interim report must be prepared using LaTeX. We require you to use LaTeX as the operational semantics, type systems, and meta-theory can be easily typeset using this typesetting system. We provide a template for preparing these deliverables here.

Submission Instructions: Interim project reports must be submitted via e-mail to hridesh@cs.iastate.edu. If you click the link above the subject will be filled automatically, otherwise please ensure that your subject is exactly "[Fall-08-541-Interim-Project-Report]" (without the quotes).

  • For preparing your project proposal you would have already downloaded the template for project report from here. For preparing your interim project report, please extend the LaTeX project that you already have.
  • Modify the relevant tex file to contain the description of your interim report. Please DO NOT FORGET to add relevant citations to the bibliography file refs.bib.
  • Compile the files using the Makefile included in the template distribution and ensure that there are no LaTeX errors in compilation.
  • Before creating an archive remove LaTeX intermediate files using "make clean".
  • Create an archive of your LaTeX project and name it [LastName]-541-interim-report.tar.gz, e.g. rajan-541-interim-report.tar.gz
  • Please attach this archive file with your submission e-mail.

How to write your submission and how it will be graded?

Following are important parts of your interim project report.

  • Abstract syntax, description of abstract syntax, and motivating examples (5%): In this section you should describe the abstract syntax of the language that you are considering, describe your choices about selection (and omission) of features in your language, and present an example that (a) illustrates your language design, and (b) serves to illustrate that your design solves the problem that your project set out to solve. Make sure to cite and briefly discuss the work on which your language design builds upon.
  • Dynamic Semantics (5%): In this section, you should describe the domains in your dynamic semantics, give a full dynamic semantics of your language including definitions of all auxiliary functions used. The rules in the dynamic semantics should be described formally as in the form of an inference rule and informally.
  • Detailed Discussion of Work that Remains to be Done (2.5%): In this section, you should discuss the problems in the project that remain to be solved. An ideal description would contain an itemized list of tasks that will be undertaken between now and the end of the semester to bring your project to a successful conclusions. It would also include a discussion of challenges that you foresee going forward in your project.
  • Addressing Feedback on Project Proposal (varies): You should have received feedback on your project proposals. In some cases, these feedback were suggestions for improvements and no points were deducted. In other cases, points were deducted due to the fact that the project proposal did not meet the requirements. Please feel free to address those issues in the interim report to get some of those points back. However, please be sure to submit the printed version of your project proposal along with the interim report.