Project Planning – SS3 Computer Hardware & GSM Repair Lesson Note (Second Term)

A final year project is a piece of work in which an SS3 student takes a problem, plans a solution and builds it, such as a custom computer, a repaired smartphone or a school network. It needs a realistic topic, a timeline, a budget, a written report and a presentation to a panel.

Behavioural objectives

By the end of the lesson, students should be able to:

• choose a project topic that solves a real problem and fits the available time, money and tools;
• draw up a week-by-week timeline for a project;
• prepare a budget that includes parts, consumables and a contingency;
• list the parts of a project report;
• prepare to present and defend a project in front of a panel.

What is a final year project?

Congratulations! Reaching SS3 means you are now a senior technician in training. To graduate, you must complete a Final Year Project.

A project is more than another assignment. It is your chance to show your teachers and others that you can take a problem, think of a solution, and build it with your own hands. Whether you are building a custom computer, fixing a “dead” high-end smartphone, or setting up a school network, a project is your “masterpiece.”

How do you choose a project topic?

The biggest mistake students make is choosing a project that is too big or too expensive. You have limited time and a limited budget. To pick a good topic:

• Solve a real problem: Don’t just say “I want to fix a phone.” Instead, say “I want to recover data from a water-damaged Android phone.”
• Check your resources: Do you have the tools? If your project requires an oscilloscope and your lab doesn’t have one, you might need to change your plan.
• Choose what you enjoy: Pick something you actually like. If you love networking, don’t choose a micro-soldering project just because your friend did.

How do you plan the project timeline?

A project takes weeks, so start early. If you wait until the last minute, you will make mistakes and fail. You need a timeline (the “game plan”). Break it down like this:

1. Weeks 1 to 2 (Research): Read books, watch professional repair videos, and talk to your teacher about your idea.
2. Week 3 (Sourcing): Buy the “scrap” boards, the cables, or the software licences you need.
3. Weeks 4 to 6 (Execution): This is the “doing” part. Start the repair or the installation. Take photos of every step.
4. Week 7 (Testing): Does it work? If it fails, you still have time to troubleshoot.
5. Week 8 (Documentation): Write your report.

How do you budget for a project?

Your project shouldn’t make you go broke. Before you start, create a “Bill of Quantities”, which is a list of everything you need to buy and what it costs. Include:

• Parts cost: The price of the motherboard, screen, or router.
• Consumables: Remember the small things: solder wire, flux, IPA (alcohol) and jumper wire.
• Contingency: Always add 10% extra money. In repairs, a tiny component can break unexpectedly, and you will need to buy a replacement.

What should a project report contain?

A project is 50% working and 50% writing. If you build the best machine in the world but don’t write a report, no one will know how you did it. Your project report should include:

1. Introduction: Why did you choose this project?
2. Tools used: List your hardware (soldering iron, multimeter) and software (schematic viewers).
3. The process: Explain step by step what you did. Use the photos you took during the “Execution” stage.
4. Challenges: Be honest. If you burnt a track and had to use a jumper wire to fix it, write it down. Teachers like to see how you solved problems.
5. Conclusion: What did you learn?

How do you present and defend your project?

At the end, you will stand in front of a panel to defend your work.

• Be prepared: Test your project one last time before the presentation.
• Be confident: You are the expert on your project. No one knows it better than you.
• Dress professionally: Wear your lab coat or a neat school uniform. First impressions matter.
• Focus on the “why”: Don’t just show that the phone turns on. Explain how you used the schematic to find the fault.

Evaluation

1. Why is it important to take photos during the repair instead of just at the end?
2. What is a “contingency” in a budget, and why is it useful?
3. If your project fails to work on the day of the presentation, how should you handle the situation with the examiners?

Assignment

Write down one ICT or GSM problem you see in your neighbourhood right now. Explain how it could become a project.