CCR - Timeline

Below is an estimated timeline for which I will follow to complete this project. If all things go well, everything should be complete and all documentation should be done for the final presentation. This segment is essential to prevent project creep and keep all requirements in check.

It is important to note that although this is the timeline that is set up in which I will follow, small task lists will be created each week to assist with keeping up.

An overview of the weeks shown below with a task list formed each week to try and accomplish.

Week 1: Jan 25 - Jan 29
    Research track and project ideas
    Get familiar with track again and test old code from previous CS projects

Week 2: Feb 01 – Feb 05
    Continue research and testing track layout with older code
    Implement some ideas for new track and go off of OS class ideas to multi-process

Week 3: Feb 08 – Feb 12
    Continue research and outline for project and interfaces
    Modify or finalize track layout and how program will function

Week 4: Feb 15 – Feb 19
    Continue testing and research of new functions
    Test out communication between multiple computers

Week 5: Feb 22 – Feb 26
    Continuing testing and building interfaces

Week 6: Mar 01 – Mar 05
    Continue coding and potentially bringing in other devices, etc.
    Work on communication with the track
    Figure out AIU and sensor information and begin moving trains

Week 7: Mar 08 – Mar 12
    Continue coding and brining in other devices
    Work on debugging issues and work on Client interface and sending requests

Week 8: Mar 15 – Mar 19
    SPRING BREAK – take week off (going to Vegas)

Week 9: Mar 22 – Mar 26
    Begin prepping walkthrough and components of project
    Finalize a version of the Client interface

Week 10: Mar 29 – Apr 02
    Continue coding and adding changes suggested from walkthroughs
    Keep testing out multiple devices and other additions

Week 11: Apr 05 – Apr 09
    Continue looking at other interfaces and debugging
    See if other devices can be brought in

Week 12: Apr 12 – Apr 16
    Continue coding and adding other functions
    Make sure most of documentation is finalized

Week 13: Apr 19– Apr 23
    Continue coding and adding other functions
    Finalize Powerpoint and presentation

Week 14: Apr 26 – Apr 30
    Open Demos and Presentations

Week 15: May 03 – May 07
    Prep for Project Defense

Week 16: May 10 – May 14
    Finalize website and hand in all work

Remote to manually control trains via NCE technology

A Senior Capstone Project - Brice Hilgemann 2010