What This Document Is
This is a comprehensive guide outlining the expectations and requirements for the major course project in CSE 567M: Computer Systems Analysis at Washington University in St. Louis. It serves as a central resource for students undertaking an in-depth investigation of a chosen topic within the field, culminating in a formal, publishable-quality report. The guidelines detail the project’s scope, deliverables, and crucial considerations for successful completion.
Why This Document Matters
Students enrolled in CSE 567M who are preparing to begin their course project will find this document essential. It’s particularly valuable during the initial stages of project planning – topic selection, literature review, and outlining – and throughout the writing and revision process. Understanding these guidelines *before* significant work begins can prevent wasted effort and ensure the final submission meets the course’s rigorous standards. It’s also beneficial for students aiming to produce work of a caliber suitable for wider dissemination.
Common Limitations or Challenges
This document provides a framework and set of expectations, but it does *not* offer specific research topics or pre-defined solutions. It doesn’t include example projects or completed reports. It also doesn’t delve into the technical details of specific performance analysis techniques; rather, it assumes prior knowledge gained through coursework. Students will need to independently conduct thorough research and apply their understanding of computer systems analysis principles.
What This Document Provides
* A detailed project schedule with key deadlines for topic selection, reference submission, draft completion, and final report due dates.
* Clarification on the expected depth and breadth of the project, emphasizing a comprehensive survey of relevant literature.
* Important guidelines regarding academic integrity and proper citation practices.
* Recommendations for effective literature searching and information organization.
* Suggestions for writing style and report structure to maximize clarity and impact.
* A recommended organizational structure for the final report, including essential sections like introduction, abstract, and references.
* Technical considerations for file naming and formatting to ensure compatibility.
