→ Project proposal due on October 9th Submission.
→ Project proposal meeting on October 10th. Please send me 3 preferred 30 minutes slots for Wednesday or if not possible, next Monday.
The project is the primary artifact of the course; the outcome of all projects will be a research paper (5 to 10 pages). Depending on the class size, the projects may be completed in groups of up to three. The intent of the project is to identify some research question and investigate it.
Project Proposal. A one-page proposal for your project to me. Katja and I will provide you feedback in a one-on-one meeting. The proposal should include a problem statement, the motivation for the project, and set of objectives you aim to accomplish. This is due on October 9th, 2013, at midnight via EasyChair.
Written Report. The report on your experience, including a critiqute of teh technique/tools is due on December 9th, 2013, at midnight via EasyChair. The required length of the written report varies from project to project; all reports must be formatted according to the ACM format and submitted as a PDF in ACM paper format (two-column style).
Four types of possible projects
Build a software tool to solve a problem developers encounter in practice
- Identify a real problem developers face and model a solution
- It can be an implementation of an algorithm proposed in a paper we read, or a visualization of information produced by existing tools, or any new idea you have for a tool
- Preliminary evaluation of the tool required (prof-of-concept to show it works)
- The report includes a description of your tool, sample usage scenario and a comparison to existing tools. (not more than ) 5 pages.
- Gain a more in-depth understanding of a topic you find interesting in class
- Find and read additional research papers on the topic IEEE, ACM. Remember that the synthesis is key: what are relevant papers, how do they contribute to understanding, what shortcomings do they identify, how can future work address these?
- Describe and critique papers to provide a state-of-the-art report on a topic. (not more than) 10 pages.
Evaluate an advanced software development tool
- Gain experience using one or more advanced software development techniques or tools
- Use a software development technique or tool(s) that is relevant to a topic in class and apply it to a problem/system you choose
- Describe your experience, including critique of the technique/tool. (not more than) 5 pages.
Study on existing practice
- Investigate a specific aspect of software development
- Design and conduct interviews or surveys with developers
- Apply open coding to the collected (and transcribed) answers
- Summarize the results of the study, show potential for future research and compare to existing work.
Deliverables: project proposal, written report in ACM paper format Template, presentation (10 minutes)