ECE 1747H Parallel Programming Project 

Fall 2016


The goal of the project is to do a miniature version of a research project. You will first pick a topic, and argue in a proposal that this is a topic worth exploring, and that you are capable and prepared to do so. You will design and implement a solution to the problem you have chosen, and measure the performance of your solution. You will finally present the results of your project in a final report and in a classroom presentation.

Please keep in mind that this is a research project, and not a programming project. Although the implementation of your solution is an essential component, it is only one aspect of the project, next to other equally important components, such as the evaluation and the presentation of your results. Typical research topics include parallelization and analysis of a sequential code or improvement or adaptation of a pre-existing parallel code.

Projects should be done individually or in small groups (ideally of two students, but three students are also acceptable). All reports and presentations should be done in a group basis. The most interesting projects usually result from groups.



Your proposal should be submitted in PDF format to the professor by email ( Your proposal should cover the following topics:


Your presentations of both your proposal and project should be well-prepared. You should be ready to handle questions from the professor and your classmates. Time limits will be strictly enforced. Please use PowerPoint to produce your slides. A projector will be provided. 

Please refer to Professor Mark Hill's advice on oral presentations when preparing your talks.

Final Report

Your final report should be submitted in PDF format to the professor by email ( Your final report will typically contain the following content:

The most important parts of establishing your contribution are an appropriately detailed description of the solution and a thorough analysis of the quantitative data. The abstract is incredibly important for setting the overall tone for the reader.

If you have never written a technical document before, you should seriously consider reading one of the standard references on the subject. One of the best reference texts is The Elements of Style by Strunk and White.


Common pitfalls include the following:

Back to ECE 1747H