MENTORSHIP PROJECT TITLE

AUTHOR NAME

Version Date, 2003-2004
Second Quarter
(final version due Jan. 28, 2004)


  • 2001-2002 Student Abstracts
  • 2002-2003 Student Portfolios
    1. Project Proposal (first quarter)

    2. Project Description , a one page summary of your project, signed by your mentor

    3. Project Poster - 100 pts
      Outline of elements due Fri. Dec. 19, 2003
      Final 3-panel Poster assembled, due Fri. Jan. 23, 2004

    4. Daily Logs/Weekly Goals/Iteration Reports
      - Daily Logs/Weekly Goals DUE each week
      - Iteration Report 1 DUE Fri. Dec. 12, 2003
      - Iteration Report 2 DUE Fri. Jan. 23, 2004
      - Gantt Chart, Vers. 2 DUE Fri. Jan. 23, 2004

    5. Oral report: Summary notes/presentation "slides" and oral presentation
      DUE Fri. Jan. 23, 2004
      - see Mr. Leaf's tips on oral communication skills

    6. Technical Paper - 12-20 pages, double spaced, 250 words per page,
      in LaTex, HTML ("latex2html"), and PDF ("dvipdf", read pdf files with "gv")
      also see what you need to complete and detailed summary of a research paper
      • Title Page, Abstract, 1/3 - 1/2 page, ~75-150 words
      • Introduction, 2 - 3 pages, 500-750 words DUE Fri. Dec. 19, 2003
        • Purpose, subject of the project, goals of the project, why is the this worth
          doing, who will be interested in the results, how can the results be applied?
        • Scope of your study and project, the overall bounds of the work that
          will be involved, e.g., the research or data that will be required,
          and the relationships and variables that will need to be programmed,
          the expected results. You may have to narrow down your research/project objectives.
        • Be specific about what you want to develop. You may have to select a portion of
          your original project idea
      • Background, 2 - 3 pages, 500-750 words DUE Fri. Dec. 19, 2003
        • Background and review of current literature/research in this area.
        • Demonstrate that you know the background of your topic.
        • What kinds of research have been done before in this area?
        • How have others gone about trying to solve similar problems you are dealing with?
        • Where is the "state of the art" today?
        • In what ways may your approach build on and vary from previous work
          that has been done in your project area?
      • Development sections, theory and procedures you're using, analysis: 7 - 10 pages,
        2000-3000 words
        • Hypothesis, explain how you think your project can demonstrate your purpose.
        • Procedure and methods you're using.
        • Show you followed a time plan
        • Demonstrate your research, design, programming, sub-testing and testing
          phases of your project. Show you identified resources that you needed.
        • Tasks and sub-tasks that accomplished to meet your objectives
        • Materials and programming language(s)/tools that were necessary, graphics tools that
          were needed?
        • Describe your algorithms in detail, where did you learn these algorithms
          (methods, processes)
        • Was any data needed, how was this data collected?
        • Methods or processes will be used to test and analyze the data?
        • What error analyses will be performed on the gathered data?
      • Results, analysis, and conclusions: 3 - 5 pages, 750-1250 words
        • Present your final results and analysis - include visuals such as graphs and charts
        • What contributions can these results give to future researchers?
        • Observations/Data/Results, describe your detailed journal of observations, data, and results
        • Analysis (think about how your testing relates to the goal/direction of your project.
          Explain your observations, data, and results, give a summary of what your data has shown you.
        • Describe the main points that you have learned, how about your original hypotheses?
        • Conclusions? Look at your original problem statement. What does it (your project) all
          add up to? What is the value of your project?
        • What further study do you recommend given the results of your experiment?
          What would be the next question to ask?
        • If you repeated this project, what would you change?
      • References
        you need 10 references
      • Appendix section(s) - commented Code listings so far
        20+ pages code needed for final version
        • Code and Development, Research Elements (include your Scientific Method)
        • Screenshots, Output samples, Analysis
        • What levels did your programming go into?
          Do you have only 1 type of task, or do you
          use multiple levels of programming problems/tasks/algorithms.
        • What sort of algorithms did you need to develop?
          Comment about this in your code.

    7. Code and code development,
      8-10 pages for 2nd quarter DUE Fri. Jan. 23, 2004
      WITH TESTING AND ANALYSIS OF TESTS
      - See the Appendix section above for details

    8. EXTRA CREDIT:
      • Write an description of your project for Technos
      • Submit your project for an article in Technos
      • Enter the Science Fair with your project