CS357S: Project Details
Project Proposal
Your project proposal should be 2-3 pages, 10pt font, single-spaced, single column, and include the following:
- Names and Stanford email addresses for all team members
- Research problem you will study
- Background on the problem, including why it is important, what others have done about it, and a few key references
- Specific goals of your project
- Proposed approach and required resources (e.g., software tools, hardware infrastructure)
- Relevance to “formal methods for computer systems”
- A timeline for completing the proposed work within the quarter, including midterm review, final presentation, final report, and artifact milestones.
Midterm Review
Your midterm review will consist of a meeting with the course staff to review progress and any issues with your project. You will prepare a midterm review presentation consisting of 3-5 slides that include the following:- Names and Stanford email addresses for all team members
- Overview of the specific research problem you are studying (more detailed than the proposal)
- Technical approach
- Evaluation methodology and preliminary results
- Updated timeline for the rest of the quarter
- (Potential) roadblocks, concerns, unresolved issues, and a plan for resolving or navigating around them
Final Presentation
Give a 10-15 min talk (depending on the class size) to the class on your research project. We suggest the following format:- What is the problem? Why is it important?
- What have others done about it?
- What are you doing about it? That is, describe your technical approach, highlighting the connection to “formal methods for computer systems” (1-2 slides)
- Report on the current status. What works? What is left to do?
- What is the evaluation methodology and a key result?
Final Report
Write a 5-6 page, 10pt font, single-spaced, two-column, project report, using the ACM SIGPLAN template, and include approximately the following:- Introduction - 1 page
- Motivation/Background/Related Work - 1 page
- Approach/Implementation - 1.5-2 pages
- Methodology/Results - 1-1.5 pages
- Discussion/Limitations/Next Steps - 0.5 pages
Artifact
Provide code or a proof artifact, so that the course staff can reproduce your experimental results and understand your methods in detail.Adapted from a template by Andreas Viklund.