AI Summary
[DOCUMENT_TYPE: user_assignment]
**What This Document Is**
This document provides comprehensive guidelines for the major class project in CSE 571S: Network Security at Washington University in St. Louis. It’s designed to help students successfully navigate the project requirements, from initial topic selection and research to final report submission. It outlines expectations for both comprehensive survey-style projects and more hands-on, implementation-focused work. This isn’t a tutorial *on* network security concepts, but rather a guide to *demonstrating* your understanding of them through a substantial project.
**Why This Document Matters**
This guide is essential for any student undertaking the course project. It clarifies the instructor’s expectations regarding project scope, depth, and presentation. Understanding these guidelines *before* you begin will save significant time and effort, ensuring your work aligns with the grading criteria and project goals. It’s particularly useful for students who are unsure about the appropriate level of technical detail, research requirements, or formatting standards. Refer to this guide throughout the project lifecycle – from initial planning to final submission – to stay on track.
**Common Limitations or Challenges**
This document focuses on *how* to approach and structure the project, not *what* specific network security topic to choose. It doesn’t offer detailed technical solutions or code examples. It also doesn’t provide a pre-defined list of approved project topics; students are responsible for identifying and proposing their own. While it references previous successful projects, it doesn’t guarantee approval for replicating those exact ideas. It also doesn’t cover specific tools or technologies – the choice of these is left to the student, based on the project’s requirements.
**What This Document Provides**
* Detailed expectations for project types (surveys vs. hands-on)
* Guidelines on conducting thorough literature reviews and utilizing search resources.
* Recommendations for effective writing style and organization, including structuring sections and subsections.
* Specific formatting requirements for the final report, including file naming conventions and the inclusion of essential elements like abstracts and acronym lists.
* Clear stipulations regarding academic integrity and avoiding copyright infringement.
* Information on potential publication opportunities for high-quality projects.