Writing the Project Documentation — Azani ISP KCSE 2026

Documentation is worth a huge share of your KCSE Computer Project marks. Here is the structure for the Azani ISP project.

Overview

Title page, declaration, acknowledgement, abstract, system analysis, design, implementation, testing, user manual and conclusion — each section explained with examples for the Azani ISP scenario.

Why Azani ISP?

The Azani Internet Service Provider scenario is the official KCSE 2026 Computer Studies Project case study. Every Form 4 Computer Studies candidate in Kenya is required to design and implement a database system for Azani ISP — covering customer management, internet package subscriptions, payments and complaint handling. Getting it right is critical for your final KCSE Computer Studies grade.

Milestone 1 — Ready

Milestone 1 covers the analysis and design phase: project proposal, system requirements, Entity-Relationship diagrams, Data Flow Diagrams, normalised database tables and the database schema. Our Milestone 1 package is complete, error-free and aligned to the KNEC marking rubric.

Milestone 2 — Ready

Milestone 2 covers the implementation and documentation phase: working MS Access database, all required tables and relationships, data entry forms with sub-forms, queries, reports, validation rules, user manual and the testing plan. Our Milestone 2 package is fully tested with sample data and ready to submit.

How to order

WhatsApp 0734002689 right now. We deliver instantly via WhatsApp or email. Both milestones available individually or as a complete bundle. Same-day delivery, countrywide.

Frequently Asked Questions

Is this the official KCSE 2026 project? Yes — Azani ISP is the official case study for KCSE 2026 Computer Studies.

Is documentation included? Yes — full project report with screenshots, ER diagrams and user manual.

How fast is delivery? Instant via WhatsApp 0734002689.

What the Azani ISP scenario actually asks you to build

The KCSE 2026 Computer Studies project drops you into a real Kenyan SME context: Azani Internet Service Provider, a fictitious but realistic ISP serving home and SME customers across Kenya. KNEC asks every candidate to analyse, design, implement, test and document a database-driven information system that lets Azani manage customers, internet packages, subscriptions, payments, technicians and customer complaints — end-to-end.

The scenario is deliberately broad so that examiners can test the full syllabus: data modelling (ER diagrams, normalisation to 3NF), DBMS implementation (MS Access tables, relationships, referential integrity), input design (forms with validation), output design (queries and parameterised reports), and finally professional documentation that an external moderator can follow without your help.

Required entities and relationships (Milestone 1)

• Customer (CustomerID PK, FullName, NationalID, Phone, Email, PhysicalAddress, County, DateRegistered)
• InternetPackage (PackageID PK, PackageName, SpeedMbps, MonthlyPriceKSh, DataCapGB, PackageType — Home/SME)
• Subscription (SubscriptionID PK, CustomerID FK, PackageID FK, StartDate, EndDate, Status)
• Payment (PaymentID PK, SubscriptionID FK, AmountKSh, PaymentDate, PaymentMethod — M-Pesa/Bank/Card, ReceiptNo)
• Technician (TechnicianID PK, FullName, Phone, Region)
• Complaint (ComplaintID PK, CustomerID FK, TechnicianID FK, DateLogged, IssueDescription, Status, DateResolved)

Relationships: a Customer has many Subscriptions; a Subscription has many Payments; a Customer has many Complaints; a Technician handles many Complaints. Enforce referential integrity with cascade-update where appropriate.

Implementation checklist (Milestone 2)

1. Build all six tables in MS Access with correct data types and primary keys.
2. Create the relationships diagram and enforce referential integrity.
3. Design data-entry forms for Customer, Subscription and Complaint (with combo-boxes, input masks for phone numbers, validation rules on Email and NationalID).
4. Build queries: active subscriptions, monthly revenue by package, unresolved complaints older than 7 days, top 10 customers by spend.
5. Build reports: monthly Azani revenue report, customer statement, technician workload report.
6. Add a switchboard / navigation form as the application entry point.
7. Populate at least 15 realistic sample records per table for testing.
8. Write the user manual (with screenshots) and the testing plan (test data, expected results, actual results).

How KNEC awards the marks

The KNEC Computer Studies Paper 3 project rubric weights marks roughly as follows: Problem definition & analysis (10), Design — ER diagram, DFD, normalised tables (20), Implementation — tables, relationships, forms, queries, reports (35), Testing with valid & invalid data (10), Documentation & user manual (15), Presentation & professionalism (10). Candidates who lose marks almost always lose them on testing and documentation — not on the database itself.

Most common pitfalls

• Forgetting to normalise — leaving repeating groups in the Customer or Subscription table.
• Storing the package price inside the Subscription table instead of linking to InternetPackage.
• No referential integrity (cascade delete will then orphan records).
• Forms without validation rules — examiners deduct marks instantly.
• Screenshots that are blurry, cropped, or do not match the described step.
• A user manual that reads like a syllabus instead of a step-by-step guide a non-technical user can follow.

Need the complete, marking-scheme-ready project?

We deliver both Milestone 1 (proposal, ER diagram, DFD, normalised schema) and Milestone 2 (complete MS Access file, forms, queries, reports, sample data, full documentation and user manual) — packaged exactly to the KNEC 2026 rubric. Same-day delivery via WhatsApp.