PROJECT TITLE

AUTHOR NAME

Version Date, 2003-2004
First Quarter
(final version due June 2, 2004)

1st quarter grading requirements Updated Assignments Sept. 11, 2003
  1. Webpage portfolio, initial version. (Due 9/11/03) See: Starting a web page
  2. Link1 - Project proposal (patterned after your project brief)
    - link to preliminary version Due 9/11/03>
    LaTeX, HTML, PDF versions (also Postscript if you want)
    HAND IN A HARD COPY by 9/11/03
  3. Daily logs/Weekly goals for 1st Quarter - Started by 9/11/03
  4. Project Code, tests, analysis create the link(s) even if there is
    nothing at this point. Link due 9/11/03
  5. Coding Practice problems - usaco.org
    - go to "Training" and create a username and password
    "Your Ride is Here", "Greedy Gift Givers", "Broken Necklace",
    "Prime Palindrome"
    Begin these by week of 9/15/03

  • Making a Techlab webpage
  • 2001-2002 Student Abstracts
  • 2002-2003 Student Portfolios, Abstracts and categories
  • Past Project Ideas, 2000-2003

  • Mr. Leaf's How to Run an Open-Ended Problem Solving Project and tips on oral communication skills,
    Gantt charts

    Have the following links on the main title page of your portfolio:

    1. Table of your Interests Due Fri. Sept 19, 2003
      List:
      • Interests not necessarily computer science related
      • Skills and interests that you currently have in computer science
      • Skills and subjects that you'd like to learn about in computer science
      • College(s) you may attend, which department(s) and subject area(s)
        do you think you may study
      • WWW links to university departments/courses that may interest you
      • List one or more possible area for your research this year

    2. Brainstorming:
    3. Identify a Research area for your project DUE by Fri. Oct. 3, 2003
      - a Course or Project Website/Description/Outline that fits your project research topic area
      Samples from 2002-2003 school year:
    4. Reading Technical Research Papers
      - Read and report on 2 technical papers this quarter
      - First paper due by Fri. Oct. 3, 2003
      - Second paper due by Fri. Oct. 31, 2003

    5. Project Proposal - draft version completed by Fri. Oct. 3, 2003,
      final version due Fri. Oct. 31, 2003
      Title, Problem, Purpose, Scope, Background,
      Procedure/Methodology, Expected Results

    6. Title and Abstract - "draft version" completed by Fri. Oct. 3, 2003,
      final version due Fri. Oct. 31, 2003 (1/3 - 1/2 page)
      • Here's a sample definition for an abstract
      • Also see many examples of abstracts -
        "the good, the bad, the ugly" from last year's projects
        Also the 2001-2002 student abstracts above

    7. Use of a Scientific method/process in your project -
      outline completed by Fri. Oct. 31, 2003
      Your Scientific Method will parallel your Project Proposal
      and your Iteration Reports
      • Problem/Purpose - What is your goal, what idea(s) are you testing?
      • Hypothesis (adapt this to your own project characteristics)
        How does your project demonstrate your purpose.
        How will you measure your success?
      • Procedure - how will you build and test your project
      • Materials - these are probably software
      • Observations/Data/Results -
        These relate to the various levels of testing of your project
        throughout the year
        Keep a detailed journal of observations, data, and results!
      • Analysis - THIS IS AN IMPORTANT PART OF YOUR PROJECT
        - How your testing relates to the goal of your project.
        - Are you reaching a realization of your project,
        or are things "stalling"/losing direction/focus?
        - What are you learning throughout the year?
      • Conclusion - Answer your problem/purpose statement.
        What does it all add up to? What is the value of your project?

    8. Technical Paper
      - your Final version will be approx. 15-20 pages, double spaced, 250 words per page,
      in LaTex, HTML ("latex2html"), and PDF ("dvipdf", read pdf files with "gv")
      - For 1st Quarter, you'll need to write draft versions of:
      • Title Page and author (YOU!) DUE Fri. Oct. 3, 2003
      • Abstract, 1/3 - 1/2 page, ~75-150 words DUE Fri. Oct. 3, 2003
      • Introduction, Draft version, 1 - 2 pages, 250-500 words DUE Fri. Oct. 31, 2003
        (Final version 2 - 3 pages, 500-750 words due 2nd quarter)
        • 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, Draft version, 1 - 2 pages, 250-500 words DUE Fri. Oct. 31, 2003
        (Final version 2 - 3 pages, 500-750 words due 2nd quarter)
        • 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?
      • References, so far (10 or more required)
        you need at least 3 references DUE Fri. Oct. 31, 2003
      • Appendix section(s) - commented Code listings so far
        4-5pages 1st quarter DUE Fri. Oct. 31, 2003
        (20+ pages 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.

    9. Code and code development,
      2-3+ pages DUE Fri. Oct. 3, 2003
      4-5 pages for 1st quarter DUE Fri. Oct. 31, 2003
      WITH TESTING AND ANALYSIS OF TESTS
      - See the Appendix section above for details

    10. Daily Logs/Weekly Goals/Iteration Reports
      - Daily Logs/Weekly Goals DUE each week
      - Iteration Report 1 DUE Fri. Oct. 3, 2003
      - Iteration Report 2 DUE Fri. Oct. 31, 2003
      - Gantt Chart 1 DUE Fri. Oct. 31, 2003

    11. Summary notes/presentation "slides" about your current status andoral presentation
      DUE Fri. Oct. 24, 2003
      - see Mr. Leaf's tips on oral communication skills

    12. User(s)/Mentor(s): Has anyone else tested, commented on, given you advice with your project?

    13. EXTRA CREDIT OPPORTUNITY: Supercomputer or Internet2 Application Area
      • Supercomputer Links
      • Internet2 Links
      • Make a new link on your webpage: "Supercomputer Applications" or "Internet2 Applications"
      • Provide a description(s) of applications that are interesting to you.
      • Learn about Parallel Programming:
        Read and study the slides to Chapter 1, Introduction to Parallel Computing
        (see How to register)

    14. MORE 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
    More to look forward to (coming in 2nd and 3rd quarters):
    1. Project Poster (DUE 2nd Quarter)
    2. Project Description , a one page summary of your project - (NOT DUE UNTIL 3rd Quarter)

    3. Have you made a tutorial for other students on an area of your expertise? (NOT DUE UNTIL 3rd Quarter)

    4. Next year: If you have an idea of where you'll be next year - what college
      do expect to attend, what program?
      Can you find any coursework that could apply to your project?

    5. Permanent Archive of your portfolio (use "tar")