Course Requirements

This page describes the course requirements for students enrolled in CISC 4900/4905. All students enrolled in these courses are responsible for the contents of this document. Each individual must submit their copy of documents listed.

These are the documents to be handed in throughout the semester to both your instructor and supervisor.
↓ 1st Week Week ↓

Project Acquisition

At the beginning of the semester, you are to identify a project and a supervisor.

Once you've solidified your plans for your semester and have it documented in your project proposal, submit it by the deadline.

↓ Approx. Add Deadline ↓

Project Reports

The project report is documentation of the activities that go into planning and completing the project. This document should start with a description of objectives along with contact information of stakeholders, a tentative schedule, data source(s), and sample use cases. The first draft of this document should focus on where you convey what will be done this semester and why, when, how, and by whom.   This report should be updated throughout the semester to reflect progress made along the way. By the end of the semester this report should cover descriptions on the progress made, and challenges encountered along the way.


 

Project Logs

Students enrolled in this course are expected to undertake and complete a significant computer-related project. Expect to spend at least 15 hours per week on project related activities.

The log contains a record of all project-related activities; it should indicate both the time spent and the nature of the activity. You are to update your project logs throughout the semester and submitted with reports.

Date Activity Next Steps / Challenges
8/27 1 hr Attended Orientation Session [ ] find a supervisor
1 hr Draft email to supervisor
8/29 2 hr Started outline for project report
8/30 3 hr Write and edit project description
... ... ... ...

 

↓ Approx. 10th Week ↓

 

Project Update

A second draft of the report in the middle of the semester serves as a project update tha reports on progrress since the first version. It should describe the work complete thus far and outline remaining work. In general, it should be a substantial update since the initial first version. There should also include a statement of specific progress already made, and a sharper definition and outline of the project.

 

↓ End of the Semester ↓

 

Project Final Version

This final version of the the report contains a collection of documents that describe the resulting project in a production ready form, including but not limited to: source code and documentation, and project logs.

 

Final Report

The final report should be the final version of the project report.

AND

Final Project Logs

The log contains a record of all project-related activities; it should indicate both the time spent and the nature of the activity. The final logs should contain the activities from the beginning of the semester to the end that show approximately 15 hours per week of time spend towards the project.

AND

Presentation Recording

Demonstrate the work you've completed and explain how you've constructed the project.

Presentation materials can include slides, source code, example use cases, and so forth to demonstrate the work that you have completed.
The suggested timeframe is 10-15 minutes in length.

Course Timeline

This course has one required orientation meeting during the first week, then 15 hours per week required project time.

Students are responsible for managing their projects and turning in reports by deadlines stated on the course calendar

Start

First Week

Orientation Meeting

3rd Week

Project Report, 1st Draft

Continue on your project

Maintain Weekly Logs

Meet with your supervisor

10th Week

Project Report, 2nd Draft Due

Continue on your project

Maintain Weekly Logs

Meet with your supervisor

15th Week

Final Report Due

Final Presentation Due

End

© Designed by Katherine Chuang. This page is still a work in progress, contents may shift around.