Project Work SS2 Digital Technologies Lesson Note

Download Lesson Note
Lesson Notes

Topic: Project Work

What is a “Project”?

A project isn’t just a long assignment. It is a solution to a problem. Think about your school:

  • Is the library record kept in a dusty book that is hard to search?
  • Do students struggle to know their lesson timetable?
  • Is it hard for the school gatekeeper to know which parent is picking up which child?

As an ICT student, your job is to look at these “real-world” problems and build a digital tool to fix them.

 

Choosing Your Project Path

Depending on what you enjoyed most this term, you can choose one of these three paths for your mini-project:

Path A: The Web Developer (Website)

Build a multi-page website using HTML and CSS.

  • Example: A website for the school’s Sports Inter-house, showing the scores and photos of winners.

Path B: The Programmer (Software/App)

Create a simple program using Python or a mobile app tool.

  • Example: A “CGPA Calculator” where students enter their grades to see their average instantly.

Path C: The Data Analyst (Research)

Collect data, clean it, and present findings.

  • Example: A survey on “Students’ Favorite Subjects” with charts showing why some subjects are more popular than others.

 

The 4 Stages of Your Project (The Roadmap)

To keep your project from becoming a mess, follow these four steps:

Step 1: The “What & Why” (Definition) Define your project in one sentence.

  • Bad: “I want to make a website.”
  • Good: “I want to build a website that helps SS2 students download past computer science questions.”

Step 2: The Design (Wireframing/Algorithm) Draw your plan on paper first!

  • If it’s a website, draw the buttons.
  • If it’s a program, write the algorithm steps.

Step 3: The Build (Coding) This is where you sit at the computer.

  • Tip: Start small. Get one button to work before you try to build ten.

Step 4: The Demo (Presentation) You must be able to explain your work to others.

  • What problem does it solve?
  • What tools did you use?
  • What was the hardest part to fix?

 

Project Management: Using a Gantt Chart

Professional developers don’t just “start.” They use a schedule. A simple version of this is a Gantt Chart. It shows what you will do each week.

Task Week 1 Week 2 Week 3 Week 4
Pick Topic & Plan X
Design & Sketch X
Writing the Code X
Testing & Demo X

 

Troubleshooting: What to do when it “Breaks”

Every project will have a moment where the code doesn’t run or the image doesn’t show. This is normal!

  1. Read the Error Message: The computer usually tells you exactly which line is broken.
  2. Check the “Small Stuff”: Did you miss a semicolon ;? Did you forget to close a tag </div>?
  3. The “Rubber Duck” Method: Explain your code out loud to a friend (or even a toy). Often, just hearing yourself say it helps you find the mistake.

 

Summary Checklist for Students

  • [ ] My project solves a specific problem.
  • [ ] I have a paper sketch/wireframe of my project.
  • [ ] My folders are organized (Images in an images folder!).
  • [ ] I have tested my project on at least two different devices.
  • [ ] I can explain my code to my teacher in 2 minutes.

 

Class Activity: The Pitch Session

Today in class, stand up and give a “1-minute Pitch” of your project idea.

  1. Project Name: (e.g., “The School Fee Reminder App”)
  2. The Problem: (e.g., “Parents forget when the deadline is.”)
  3. The Tool: (e.g., “I will use Python to send a reminder message.”)

Lesson Notes for Other Classes