Opening screen: Title, Abstract and Author (YOU!), School year

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

1. Help with LaTeX

2. Project Proposal (from first quarter) - Have posted by Friday, April 30

3. Project Description due Fri. Apr. 30, 2004 (draft 1, at least)
   ALSO make a 2-column version: Sample Project Description (tex) and (PDF) in two column form

4. Display your project poster (DUE May 27)
   Hang your poster on the WALL

5. Explanation, elucidation of the Research area for your project

6. Reading Technical Research Papers
   - Read and report on at least 1 technical paper this quarter,
   Identify a new research paper by Thurs/Fri May 13/14

7. Your project's technical Research Paper
   - First Check of All Sections for the Paper - Thurs/Fri May 13/14
   • 15-20 pages, double spaced + 10 references + Appendices (your Code goes here)
   • in LaTex, PDF ("dvipdf", read pdf files with "gv") and HTML ("latex2html"), and
     - 1st Quarter, you have finished
   • Title Page
   • Abstract, 1/3 - 1/2 page, ~75-150 words
   • Introduction, 2 - 3 pages, 500-750 words
     • 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
     • 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
     Theory, Procedure, and Workplan Discussion
     • 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
     Results , Conclusion, Recommendations
     • 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, 10 references
   • Appendix section(s) - commented Code listings
     20+ pages total of code
   • Code and Development, Research Elements (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.

8. Code and code development, first check of the RUNNING VERSION
   of you project Thurs/Fri May 13/14
   20+ pages total DUE Fri. June 4, 2004
   - First Check of Code/Prototype Status - Friday, April 30
   WITH TESTING AND ANALYSIS OF TESTS
   - See the Appendix section above for details
   
   
9. Daily Logs/Weekly Goals/Iteration Reports
   - First Check Logs - Friday, April 30, Second Check - Thurs/Fri May 13/14
   - Daily Logs/Weekly Goals, Iteration Reports throughout the year
   - Other methods: Gantt Chart/Time charts
   - Do you have a scientific method you utilized?

10. Summary notes/presentation "slides" about your current status and oral presentation

11. Tutorial(s) for future students

12. Suggested Web Portfolio Final Format

13. Permanent Archive of your portfolio (use "tar")
    • Create an Archive of all the important elements of your project to save
    • Use "tar"
    • See Ten USEFUL UNIX Commands (scroll down)
    • Create a "username04" directory
    • Put all your important work to save in here:
      Research paper (all formats), Screenshots, Code, Tutorials, etc. that you want to save
    • "tar -cf username04.tar username04" - This "archives" everything in the folder
    • This archived folder can be saved in a permanent location

14. Where will you be next year?
    What college do expect to attend, what program?
    Can you find any coursework that could apply to your project?

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