Culminating Project Journal & Dev Log

The "Living Document" of Your Project

For your Final ISP, the process is just as important as the product. In the real world, developers keep detailed logs of their work. For this course, this log is how you prove that the code you submit is your own authentic work.

Step 1: Create Your Document

1. Create a new Google Doc or MS Word Doc Online.
2. Name it: Culminating Journal - [Your Name].
3. Click Share and ensure I have permission to editit (e.g., "Anyone with the link can Edit" or share directly to holmjohn@alcdsb.on.ca).
4. Submit a pdf or the document to this dropbbox and paste the link to this document in the comment box to this "ISP Project Journal" Assignment Folder in D2L immediately.

Step 2: The Daily Entry Template

Copy and paste the template below into your document for each day you work on the project. The newest entry should always be at the top.

---------------------------------------------------------
**DATE:** [Insert Date]
**TIME SPENT:** [e.g., 45 mins]

**GOAL FOR TODAY:**
[What did you plan to build or fix today?]

**WHAT I ACCOMPLISHED:**
[Briefly describe what you actually got done. e.g., "Wrote the main menu loop," or "Fixed the bug in the scoring function."]

**CODE SNIPPET / SCREENSHOT:**
[Paste a small screenshot of the code you wrote today, or the program running. Show your progress!]

**AI USAGE LOG (Mandatory):**
[Did you use AI today? If NO, write "None".]
[If YES, copy/paste your prompt here: e.g., "How do I clear the screen in Python?"]
[Briefly explain how you used the AI's answer.]

**ROADBLOCKS / QUESTIONS:**
[Are you stuck on anything? Do you need to ask me a question tomorrow?]
---------------------------------------------------------

How This Helps You

• It prevents panic: By breaking the project into daily chunks, you avoid the last-minute cram session.
• It protects your mark: It provides undeniable proof of your hard work and learning journey.