You are here: Home Undergraduate Senior Project
Navigation
Log in


 
Document Actions

Senior Project Guidelines

CSCI 4390 Senior Project Guidelines

CSCI 4390 Senior Project

Goals and Guidelines 

CSCI 4390 Goals

Students in CSCI 4390 will complete a semester long project within the domain of computer science.  The project should:

    1. require expertise in the field of computer science to complete.
    2. address a real world problem. 
    3. require the student to expand her/his domain of knowledge during the course of the project.
    4. be the topic of a public presentation.
 

To measure the extent to which these goals are achieved, the following specific items are required for CSCI 4390. 

Choosing an Advisor

Prior to enrolling in CSCI 4390, a student must select a faculty advisor and begin work on a project proposal. 

Project Proposal

The student must submit a 2-3 page project proposal.  This proposal must include a summary of the planned project and a discussion of how the proposed project addresses the goals of CSCI 4390 listed above.  A timeline for the proposed project must also be included.  The proposal must be approved and signed by the student’s advisor and the project coordinator within the first week of the enrolled semester. 

Midterm Report

By the end of the eighth week of the enrolled semester the student must submit a midterm report detailing the current status of the project.  In particular, the student should address what aspects of the project are complete, and which aspects still need to be completed.  Further, any divergence from the original project proposal should be detailed.  An updated project timeline must also be included. 

Final Report

The student must submit a final report.  The final report must be approved and signed by the student’s advisor and the project coordinator by the end of the semester.  The report must include the project’s implementation code and a written report: 

  • Implementation code.  Any implementation software, along with proper documentation, must be included on a CD as a part of the final report.
  • Written report. The written report will describe the project, detail what goals were accomplished and how,  and what goals were not accomplished and why they were not accomplished.  The report will also provide a review of related literature, citing relevant books and journal articles.  A copy of the final report shall be signed by both the advisor and the coordinator. 
  • High Quality Writing.  In addition to the content requirements, the written report must also be well written and proofread.  To achieve this goal a first draft of the written report must be provided to the student’s advisor at least one week prior to the final day of classes. If the draft requires substantial revision and rewriting, the student must visit the University writing center to attain help in improving the quality of the report.  The student’s advisor will decide if this is necessary.
 

Final Presentations

The student will give one presentation of their project to the department faculty and a second presentation at a University wide or community wide event.  The faculty presentation will consist of a 30 minute presentation followed by a demonstration of any implemented software.  The second presentation can be fulfilled by participating in the HESTEC poster competition, or speaking at the ACM student research day, or by participating in some other appropriate venue that is feasible for the given semester.


This site conforms to the following standards: