Bachelor of Science in Computer Science
Course ContentImplementation
Mambo Vipi, Final Year Warrior! Let's Build Your Dream!
You've done the hard yards! You've wrestled with the proposal, battled the literature review, and designed a killer methodology in Chapter 3. Sasa, ni wakati wa mambo halisi! Welcome to the Implementation Phase, or as I like to call it, the "Kuunda" (to create/build) stage. This is where your brilliant ideas jump off the paper and come to life. It's the most challenging, yet most rewarding, part of your entire project. Think of yourself as a fundi, but instead of bricks and mortar, you're using code, data, circuits, or survey questions to build your masterpiece. Let's get our hands dirty!
So, What Exactly is Implementation?
In the simplest terms, Implementation is the process of executing the plan you laid out in your methodology. It's the "doing" part. It’s turning your project's blueprint into a tangible product, system, or result. Whether you're building a mobile app, a solar-powered water pump, or a business plan for a new kibanda, this is where it all happens.
Kenyan Analogy: The Chapati Process
Think about making chapati. Your proposal was deciding, "Leo tunakula chapati." Your literature review was checking different recipes online. Your methodology was listing the ingredients (unga, mafuta, maji, chumvi) and the steps. Implementation is the actual mixing of the dough, rolling it out, and cooking it on the pan until you have a perfect, layered chapati. You can't just wish it into existence; you have to do the work!
Step 1: The Game Plan - Prepare for "Kazi"
Before you jump in, a smart fundi always arranges their tools. You need a solid game plan. Don't just start randomly; that's how projects get stuck like a matatu in Jamhuri Day traffic!
- Revisit Your Methodology (Chapter 3): This is your map. Read it again. What did you promise to do? What are the specific steps, tools, and techniques you said you would use?
- Gather Your Tools (Your "Jembe"):
- Software: VS Code, Android Studio, MATLAB, SPSS, Figma? Install and set them up.
- Hardware: Arduino boards, sensors, Raspberry Pi, multimeter? Get them from Luthuli Avenue if you need to, and test them.
- Data: Do you have your datasets? Your survey questions? Are your interview participants lined up?
- Break It Down: A big project is scary. A series of small tasks is manageable. Break down your implementation into small, weekly goals. This is your work plan.
**ASCII Art: The Implementation Flow**
[Start: Review Plan]
|
V
[Gather Tools & Resources]
|
V
+----[Build Module 1]----+
| | |
| V |
| [Test Module 1] ----> [Find Bug?] --(Yes)--> [Fix Bug]
| | |
| (No) |
| | <------------------------------------------+
| V
+----[Integrate & Repeat for Module 2, 3...]----+
|
V
[Final System Testing]
|
V
[Done! Document Everything]
Step 2: The Core Process - Building Your Masterpiece
This part varies depending on your project. Here are a few examples:
For the Tech Gurus (Software/IT Projects):
You're probably coding. Remember to follow good practices!
- Version Control is Your Best Friend: Use Git and GitHub from DAY ONE. It's like a "Ctrl+Z" for your whole project. It will save you from tears, trust me.
- Write Modular Code: Create small functions or classes that do one thing well. It's easier to test and debug.
- Comment Your Code: Explain what you are doing. The person who will thank you the most is "Future You" trying to remember why you wrote that weird line of code at 2 AM.
<!-- A simple example of an HTML structure for a project -->
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="UTF-8">
<title>My Final Year Project</title>
<link rel="stylesheet" href="css/styles.css">
</head>
<body>
<header>
<h1>Project Title: Smart Poultry Farm Monitor</h1>
</header>
<main>
<!-- Main content like dashboards, forms, etc. will go here -->
<div id="dashboard">
<p>Loading data...</p>
</div>
</main>
<script src="js/main.js"></script>
</body>
</html>
For the Engineers & Builders (Hardware Projects):
You're bringing something physical to life!
- Safety First: Especially when dealing with electricity or machinery. Wear appropriate gear.
- Sourcing Components: You know the places – Luthuli, Kirinyaga Road. Plan your budget carefully. Sometimes components fail, so it's good to have a backup or two.
- Incremental Assembly: Build and test in stages. First, make the LED blink. Then, connect the sensor. Then, make the sensor control the LED. Don't try to assemble the whole thing at once.
Let's do a quick budget calculation for a simple hardware project.
### Sample Project Budget Calculation ###
# Project: Automated Hand Sanitizer Dispenser
# 1. List all components and their costs.
# Item | Unit Cost (KES) | Quantity | Total (KES)
# ---------------------------------------------------------------------
# Arduino Uno | 1200 | 1 | 1200
# Ultrasonic Sensor (HC-SR04) | 250 | 1 | 250
# Micro Servo Motor | 400 | 1 | 400
# 5V Mini Water Pump | 300 | 1 | 300
# Jumper Wires (Set) | 200 | 1 | 200
# Plastic Casing/Box | 500 | 1 | 500
# ---------------------------------------------------------------------
# 2. Calculate the Sub-Total Cost.
# Sub-Total = 1200 + 250 + 400 + 300 + 200 + 500
# Sub-Total = 2850 KES
# 3. Add a Contingency Fund (for unexpected costs, like a blown sensor!).
# A good rule of thumb is 15% of the sub-total.
# Contingency = 0.15 * 2850
# Contingency = 427.50 KES (let's round up to 450)
# 4. Calculate the Final Estimated Total Cost.
# Total Cost = Sub-Total + Contingency
# Total Cost = 2850 + 450
# Total Cost = 3300 KES
For the Researchers & Planners (Social Sciences/Business Projects):
Your "product" might be a report, a business plan, or a new framework, based on the data you gather.
- Execute Your Data Collection: This is your core task. Conduct your interviews, distribute your surveys (using tools like Google Forms), or run your focus groups.
- Be Professional and Ethical: When dealing with people, always be respectful of their time and ensure confidentiality.
- Organize Your Data Immediately: Transcribe your interviews and key in your survey data as soon as you get it. Don't let it pile up!
Real-World Scenario: Maria's Community Health Project
Maria's project was to analyze the effectiveness of community health volunteers (CHVs) in her home village in Vihiga. Her implementation involved:Her implementation wasn't about code, but about systematic, on-the-ground execution of her research plan.
- Week 1-2: Getting permission from the local chief and clinic. She then trained two friends to help her administer surveys.
- Week 3-6: She and her team visited 100 households, conducting surveys using tablets with the KoboToolbox app to collect data offline.
- Week 7-8: She conducted in-depth interviews with 10 CHVs to understand their challenges. She recorded these interviews (with permission) for later transcription.
Step 3: Testing - "Ina-work Kweli?"
Building is one thing, but making sure it works is another! Testing is not an afterthought; it's a continuous process.
- Unit Testing: Testing the smallest individual parts. Does your login function actually log a user in? Does your sensor give a correct reading?
- Integration Testing: Seeing if the different parts work together. When you press the "Submit" button on the website, does the data actually save to the database?
- User Acceptance Testing (UAT): This is the ultimate test. You give your project to a real user (not your classmate who already knows how it works!) and watch them use it. Do they understand it? Can they complete the main task? This is where you get the most valuable feedback!
Step 4: Challenges & Kupambana - When Things Go Wrong
I will not lie to you: something WILL go wrong. Your code will break. A component will refuse to work. A key interviewee will cancel. This is normal! It's part of the learning process. The key is not to panic, but to kupambana (to struggle, to persevere).
- The "Bug" is Your Teacher: Every error message is a clue. Read it carefully. Google it. It's teaching you something new.
- Talk to Your Supervisor: They have seen it all. Don't be afraid to say, "Mwalimu, I'm stuck." They are there to guide you, not to judge you.
- Take a Break: Sometimes, the best way to solve a problem is to walk away from it. Go for a walk, grab a cup of chai, then come back with fresh eyes.
Finally: Document As You Go!
Please, please, please, do not wait until the end to write your Chapter 4 (Implementation and Testing). Keep a work diary or a log. Take screenshots of your progress. Write down the challenges you faced and how you solved them. This documentation is the story of your journey, and it will make writing your final report a thousand times easier.
You are at the peak of your academic journey. This project is your signature, your masterpiece. Pour your passion into it, learn from your mistakes, and be proud of what you create. Now go on, build something amazing!
Pro Tip
Take your own short notes while going through the topics.
