NAME: CHRIS MUSAU
INDEX NUMBER: 12301722
PROJECT TITLE: AZANI INTERNET SERVICE PROVIDER SYSTEM
YEAR: 2026
SCHOOL: MUINDI MBINGU BOYS HIGH SCHOOL
SCHOOL CODE: 12301722
DECLARATION
Chris Musau , solemnly declares that the documentation here in titled
“Computerized Database System for Azani Internet Service Provider “ is my
original work.
I affirm that:
1. All the content included is the result of my work .
2. Any sources used in this documentation have been referenced
with academic standards.
3. Any academics award or qualification in any other institution.
I understand the plagiarism is a serious academic offense and I affirm that this
work is my effort and creativity
NAME:
SIGNATURE:
DATE:
DEDICATION
I dedicate this work to:
1:My parents who have unwavering support my work and
encourage me giving me strength to continue with this project.
2:My friends and relatives who have supported me and shared
experiences that have made this academic memorable.
3:My teacher , whose guidance have shaped my academic and
personal growth in school.
Your support and encouragement have been instrumental in
the completion of this project. Thank you for your support.
TABLE OF CONTENTS
NAME
SCHOOL CODE:
INDEX NUMBER
PROJECT TITLE
YEAR OF EXAMINATION
SCHOOL
DECLARATION
STUDENT’S DECLARATION
DEDICATION
ACKNOWLEDGMENT
TABLE OF CONTENTS
LIST OF TABLES AND FIGURES
CHAPTER 1:INTRODUCTION
1.1 BACKGROUND INTRODUCTION
CHAPTER 2:SYSTEM ANALYSIS
2.1 PROBLEM DEFINITION
2.2 OVERVIEW OF THE EXISTING SYSTEM
2.2.1 OVERVIEW
2.2.2 SYSTEM STRUCTURE
2.3 OVERVIEW OF THE PROPOSED SYSTEM
2.3.1 SYSTEM OVERVIEW
2.3.2 OBJECTIVES OF THE PROPOSED SYSTEM
2.3.3 ADVANTAGES OF THE PROPOSED SYSTEM
2.3.4 DISADVANTAGES OF THE PROPOSED SYSTEM
2.3.5 SCOPE OF THE PROPOSED SYSTEM
2.3.6 COSTS AND BENEFITS ANALYSIS
2.4 FEASIBILITY STUDY
2.4.1 SCHEDULE FEASIBILITY
2.4.2 TECHNICAL FEASIBILITY
2.4.3 OPERATIONAL FEASIBILITY
2.4.4 ECONOMIC FEASIBILITY
2.5 FACT FINDING
2.6 SUMMARY OF FACT-FINDING METHODS USED
2.7 SYSTEM REQUIREMENTS AND SPECIFICATIONS
CHAPTER 3:SYSTEM DESIGN
3.1 PRELIMINARY DESIGN
3.1.1 OVERALL SYSTEM FLOWCHART
3.1.2 PROGRAM MODULE FLOWCHARTS
3.2 DETAILED DESIGN
3.2.1 TABLES
3.2.2 INPUT DESIGN (FORMS)
3.2.3 OUTPUT DESIGN (REPORTS)
3.2.4 RELATIONSHIPS
3.3 GENERAL SYSTEM SECURITY
3.3.1 VIRUS
3.3.2 THEFT
3.3.3 UNAUTHORIZED ACCESS
3.3.4 LOSS OF DATA
CHAPTER 4:SYSTEM CONSTRUCTION
4.1 DATABASE RELATIONSHIP DIAGRAM
4.2 ENFORCING INTERGRITY CONSTRAINTS
4.2.1 REFERENCIAL INTERGRITY
4.3 Database Tables
4.3.1 FARMER’S TABLE
4.3.2 PRODUCTS SEVICE SALES
4.3.3 HONEY/PRODUCTS PURCHASES
4.3.4 TRAININGS TABLE
CHAPTER 5:USER MANUAL
5.1 INTRODUCTION
5.1.1 Software Requirements
5.1.2 Hardware requirements
5.2 HOW TO INSTALL, START AND RUN THE SYSTEM INTERFACE
5.3 DATA MANIPULATION
5.4 NEW FARMER, TRAINEE, SERVICE AND TRANSPORTATION
5.4.1 New Farmer
5.4.2 New Training
5.4.3 New Service
5.4.4 New Honey/Product Purchase
5.5 GENERATING REPORTS
5.5.1 Farmers List
5.5.2 Training schedules
5.5.3 Product sales
5.5.4 Clients Sales
5.5.5 Honey Purchases
5.5.6 Company Income
5.6 ADVANCED FEATURES OF THE SYSTEM
5.7 TROUBLESHOOTING GUIDE
CHAPTER 6:SYSTEM IMPLIMENTATION
6.1 STAFF TRAINING
6.2 CHANGE-OVER STRATEGY
CHAPTER 7:SYSTEM REVIEW
7.1 OBJECTIVE APPRAISAL
7.2 CHALLENGES ENCOUNTERED DURING SYSTEM DEVELOPMENT
7.3 STRENGTH OF THE AUTOMATED SYSTEM
7.4 WEAKNESS OF THE AUTOMATED SYSTEM
7.5 RECOMMENDATIONS
7.6 CONCLUSIONS
7.7 BIBLIOGRAPHY
APPENDIX