Individual Study & Senior Project Requirements

(version w/ out background for printing)

 

 

If you are enrolled in senior project, you must always meet the requirements given by the current semester’s senior project coordinator.

 

 

We will meet once a week for the whole semester, approximately 14 meetings.  The meeting time will be based upon our mutual schedules.  You must spend at a minimum the hour following our meeting working on this project.  You will be able to work most productively if you leave our discussion and immediately follow up on current action items.  This applies to individual and group projects.

 

 

Here is an outline of items for which you are responsible, as well as projected activities for certain meetings.  Assuming our first meeting is in week one of the semester, each meeting number following will correspond to a week number during the semester.

 

Meeting 2:  Project website presented.  Along with other project specific elements, your site will include a weekly record of every item discussed in our meetings, sort of a weekly *todo* schedule. 

 

Meeting 3:  Version one of project goals, background research, milestone timeline, and analysis presented.

 

Meeting 4:  Final version of project goals and background research presented.  Version two of analysis and milestones presented, including documents such as database schema, flow charts, class and UML diagrams.  Begin system prototype implementation.

 

Meeting 5:  Final version of analysis and milestones presented, including documents such as database schema, flow charts, class and UML diagrams.  Continue system prototype implementation.

 

Meeting 6:  Present system prototype, including end to end system communication.  Begin formal system implementation, focusing on core aspects.

 

Meeeting 7:  Discuss solution progress and future direction.

 

Meeting 8:  Present core functions of system.  Discuss user interface and the next set of core functionality.  Begin formalizing system documentation and your final project report.

 

Meeting 9:  Present next iteration integrated with previous system functionality.

 

Meeeting 10:  Present system documentation and final report version one.

 

Meeeting 11:  Feedback on system documentation and final project report.

 

Meeeting 12:  Discussion of final system modifications.

 

Meeeting 13:  Present system documentation and final project report version two.  Tweak system implementation.

 

Meeeting 14:  Present final system and all documents.

 

 

Items to include within your final system and documents:

  • Final Project Report
  • Analysis documents (diagrams, flow charts, and milestone timeline)
  • Weekly *todo* list.
  • Readme of system installation and operation.
  • Soft copy of all materials on CD or diskette in MS Windows readable format.
  • Soft copy of all materials via email if requested.

 

 

Guidelines for the creation of your system documentation and final project report.