Week 03 · lesson

Lesson 5: Package the Week 3 Evidence

You now have three weeks of connected work:

a portfolio structure;
improved navigation and media records;
a presentation draft and revision;
spreadsheet records, formulas, and chart evidence; and
a first relational-data sketch.

Today you package that evidence so it can be reviewed without guessing.

Evidence needs a route

A portfolio is useful when evidence has a route.

That means the reviewer can move from the home page or starting document to the evidence and back again.

A good route might look like this:

Home → Projects → Portfolio Evidence → Week 3 Package

A local classroom package might use folders instead:

computer-systems/
  week-03-evidence/
    portfolio-checklist.md
    presentation-revision-notes.md
    spreadsheet-audit.md
    relational-data-sketch.md

Both can work if your teacher approves the format.

Build the package index

Create a short index for Week 3 evidence.

Use this structure:

Evidence item	Location	What it proves	Next improvement
Portfolio release checklist	portfolio page or file path	navigation and evidence are reviewable	add Week 4 database evidence
Presentation revision notes	slide file or notes	feedback led to a visible repair	improve speaker notes
Spreadsheet audit	spreadsheet or written audit	formulas and chart claim were checked	add more records
Relational-data sketch	document or image	artifacts and categories can be separated	build database tables

The index is not busywork. It is the map that makes your evidence inspectable.

Check for private information

Before submitting, inspect every artifact.

Remove or replace:

private student names;
personal email addresses;
phone numbers;
addresses;
account usernames;
login screens;
unrelated personal photos;
copyrighted media without permission; and
anything your teacher has marked as not for sharing.

If you are unsure, do not publish it. Ask for the approved classroom version.

Write a release note

A release note is a short explanation of what changed.

Example:

Week 3 release note:
This package shows the first reviewable portfolio section, a revised presentation, a spreadsheet audit, and a two-table database sketch. The main repair this week was making chart claims more specific and adding a portfolio release checklist.

The release note should name the evidence, not just say "I did work."

Lab 5: Submit the Week 3 package

Create the Week 3 evidence package in the assigned format.

It must include:

package index;
portfolio release checklist;
presentation revision evidence;
spreadsheet audit evidence;
relational-data sketch;
privacy check statement; and
release note.

Use links or file paths that make sense for your assigned tool.

Final quality check

Before submitting, ask:

Can another person find the evidence?
Can they tell what each artifact proves?
Are unfinished items labeled honestly?
Is private information removed?
Does every claim match the available evidence?

If the answer is no, repair the package before submitting.

Evidence checkpoint

Your Week 3 package is ready when it can stand on its own.

That means a reviewer can open it and understand:

what changed in the portfolio;
how the presentation improved;
what the spreadsheet proves;
what the chart does not prove; and
how the first database model separates related information.

That is the point of the first three weeks: not just files, evidence.