Friday, January 23, 2026

Web-Based Online Learning and Attendance Tracking System Student Project | detailed list of modules, their sub-modules, and functions based on industry-standard platforms like Moodle, Google Classroom, Canvas, Blackboard, Edmodo, and custom-built academic systems

🎓 Web-Based Online Learning & Attendance Tracking System

Comprehensive Development Guide for LMS with Integrated Attendance Management

💡 Overview: Developing a Web-Based Online Learning and Attendance Tracking System requires a comprehensive understanding of both Learning Management Systems (LMS) and Attendance Management Systems. This documentation is based on industry-standard platforms like Moodle, Google Classroom, Canvas, Blackboard, Edmodo, and custom-built academic systems.

📚 Core System Modules & Their Functions

1

User & Role Management

Purpose: Control user access and permissions.
  • Admin, teacher, student, parent accounts
  • Role-based permissions
  • Profile management (update personal info, password)
  • Multi-school or multi-department support
2

Authentication & Security

Purpose: Secure access for multiple user types.
  • Login/logout with email/username
  • Two-factor authentication (optional)
  • Password reset via email/SMS
  • Session management and access logs
3

Online Learning / LMS (Learning Management System)

Purpose: Core teaching and learning platform.
  • Course creation and organization (modules, units)
  • Upload/host videos, PDFs, SCORM content, assignments
  • Categorize courses by subject, grade, or program
  • Module sequencing and learning paths
  • Course catalogs for public browsing
  • Course descriptions and prerequisites
4

Virtual Classroom / Live Sessions

Purpose: Deliver real-time online classes.
  • Integrated video conferencing (Zoom/BigBlueButton etc.)
  • Screen sharing, live chat, virtual hand-raise
  • Attendance capture within class sessions
  • Recording and playback for later access
5

Attendance Tracking & Management

Purpose: Track presence in courses and live classes.
  • Manual or automatic attendance marking
  • Attendance statuses: present, absent, late, excused
  • Daily, weekly, monthly tracking and roll-call
  • Bulk marking options
  • Track attendance tied to scheduled timetable
  • Attendance dashboards for quick insights
  • Optional biometric/RFID/QR/face ID attendance capture
  • Mobile app support for teacher marking
6

Timetable & Scheduling

Purpose: Organize classes & meetings.
  • Calendar views (day/week/month)
  • Conflict detection (room or instructor overlap)
  • Automated schedule generation
  • Recurring sessions and holiday/exam schedules
  • Sync to Google/Outlook calendar
7

Course Progress & Analytics

Purpose: Monitor learning progress.
  • Track lessons completed
  • Course completion percentage
  • Detailed progress dashboards
  • Performance trend graphs
8

Assessments & Grading

Purpose: Measure student learning outcomes.
  • Online quizzes and exams
  • Assignment upload and submissions
  • Automatic or manual grading
  • Rubric and feedback system
  • Gradebook for teachers and students
9

Certificates & Badges

Purpose: Recognize achievement.
  • Auto-generate completion certificates
  • Customizable templates (logo, signatures)
  • Digital badges for milestones
10

Notifications & Communication

Purpose: Keep users informed.
  • Email/SMS/Push alerts for:
    • Attendance updates
    • Class start reminders
    • Assignment deadlines
    • Course enrollment confirmations
11

Discussion & Community

Purpose: Facilitate interaction.
  • Course forums and threads
  • Chat between instructors and students
  • Q&A boards
  • Private messages
12

Reporting & Dashboards

Purpose: Data analysis and export.
  • Attendance reports (student, class, date range)
  • Progress and performance dashboards
  • Export to CSV/PDF
  • Custom report builder
13

Payment & Billing (Optional)

Purpose: Monetize courses if public/paid.
  • Payment gateways (Stripe/PayPal)
  • Course pricing/subscriptions
  • Invoicing & receipts
  • Refund processing
14

Parent/Guardian Portal

Purpose: Visibility into student performance.
  • View attendance records
  • Progress and grades
  • Notifications about absences
  • Message teachers
15

Content & Resource Library

Purpose: Central repository of learning materials.
  • Upload files (docs, presentations, videos)
  • Organize by subject or curriculum
  • Version control
16

Integration & API

Purpose: Connect with external tools/services.
  • Integrate live class tools (BigBlueButton, Zoom)
  • APIs for SIS / payment / SMS gateways
  • Webhooks for real-time events
17

Admin & System Settings

Purpose: Central administration controls.
  • System configuration
  • Role & permission settings
  • Audit logs
  • Data backup and restore
  • Multi-language and timezone support
18

Security & Compliance

Purpose: Protect user data.
  • SSL encryption
  • Data privacy controls (GDPR or local standards)
  • Regular security audits

👩‍💻 Optional Advanced Modules

💡 Note: These aren't required but are strong value-adds for enhanced functionality:

  • AI-Powered Learning Analytics - adaptive suggestions and personalized learning paths
  • Gamification - points, levels, leaderboards to boost engagement
  • Mobile Apps - native Android/iOS applications for on-the-go access
  • Offline Content Sync - download materials for offline viewing
  • Offline Attendance Capture - mark attendance without internet, sync later

📌 Module Summary

Module Core Functions
LMS Course management, content delivery
Attendance Marking, tracking, automated capture
Online Class Live sessions with attendance
Scheduling Timetables & conflict management
Assessment Quizzes, grading, certificates
User Management Roles & permissions
Communication Alerts, messaging
Reporting Dashboards & exports
Parent Portal Visibility & notifications
Payments Billing & invoicing

🔍 Real-World Examples to Study:

Moodle
Google Classroom
Canvas LMS
Edmodo
Blackboard
TalentLMS

Moodle: Open-source, highly modular
Google Classroom: Simple, integrates with G Suite
Canvas LMS: Modern UI, strong analytics
Edmodo: K-12 focused, includes badges & parent access

🚀 Additional Development Considerations

For a complete project implementation, consider the following additional components:

  • Database Schema Design - Comprehensive ER diagrams and table structures for user management, courses, attendance, assessments, etc.
  • Tech Stack Recommendations - Modern frameworks like React + Node.js + MongoDB, or Laravel + Vue.js + MySQL
  • Wireframes & User Flow Diagrams - Visual mockups for all user interfaces and interaction flows
  • Priority-Based Development Roadmap - MVP (Minimum Viable Product) features vs. full version enhancements
  • Security Best Practices - OWASP guidelines, data encryption, secure authentication protocols
  • Scalability Planning - Load balancing, database optimization, cloud deployment strategies
  • Testing Strategy - Unit tests, integration tests, user acceptance testing (UAT)
  • Deployment & DevOps - CI/CD pipelines, containerization (Docker), monitoring tools

Monday, December 29, 2025

ICT Internship opportunities in sri lanka IT Internship opportunities in sri lanka for students Internships for undergraduates Sri Lanka Internship Vacancies in Sri Lanka 2025 Paid internships in Sri Lanka Online internship opportunities in sri lanka Internship Vacancies 2025 Government Internships for undergraduates Sri Lanka Internship for undergraduates


---


# **Final Year Project Proposal & Software Requirements Specification (SRS)**

**Title:** *Small shops don’t track customers* → **Software Solution: Lightweight CRM for Small Retailers**


*Submitted in partial fulfillment of the requirements for the Bachelor of Information Technology (BIT) – External Degree Programme, University of Moratuwa*


---


## **1. Introduction**


### 1.1 Problem Statement

Small retail shops—such as boutiques, hardware stores, mobile repair centers, and online resellers like your own business—**rarely maintain structured customer records**. Most rely on:

- Memory or handwritten notes,

- WhatsApp chats or phone call logs,

- Spreadsheets with inconsistent or outdated data.


This leads to:

- **Missed repeat sales** (e.g., not recognizing loyal customers),

- **Inability to follow up** on inquiries or pending orders,

- **No personalized communication** (e.g., birthday offers, restock alerts),

- **Lost customer history** when staff change or phones are replaced,

- **Inefficient after-sales service** due to lack of purchase records.


In short, small shops **leave money on the table** because they can’t remember who their customers are, what they bought, or when they last interacted.


### 1.2 Proposed Solution

A **lightweight, web-based Customer Relationship Management (CRM) system** designed specifically for Sri Lankan small retailers and solo entrepreneurs.


The system enables shop owners to:

- **Capture customer profiles** (name, phone, address, preferences),

- **Log every interaction** (inquiry, quote, sale, complaint),

- **Track order and payment status**,

- **Set follow-up reminders** (e.g., “Call Amal about pending payment”),

- **Send bulk WhatsApp/SMS notifications** (e.g., “New stock arrived!”),

- **View customer lifetime value** and purchase trends.


Built with **zero accounting complexity**, **mobile-first design**, and **WhatsApp integration**, this CRM fits seamlessly into the workflows of non-technical shop owners.


---


## **2. Objectives**


- Digitize and centralize customer data for small retailers.

- Replace memory/WhatsApp with a structured interaction history.

- Increase repeat sales through timely follow-ups and reminders.

- Enable basic segmentation (e.g., frequent buyers, high-value customers).

- Improve customer service with quick access to past orders.

- Provide a **free, low-friction alternative** to enterprise CRMs like Salesforce or Zoho.


---


## **3. Scope**


### 3.1 In Scope

- **Web application** (mobile-optimized) for shop owners and staff.

- **Customer Management**:

- Add/edit customers (name, phone, address, notes).

- Tag customers (e.g., “VIP”, “Wholesale”, “Online Buyer”).

- **Interaction Logging**:

- Log calls, WhatsApp messages, in-person visits, inquiries.

- Attach photos (e.g., product image sent by customer).

- **Order & Payment Tracking**:

- Link interactions to orders.

- Track status: Inquiry → Quoted → Paid → Delivered.

- Record payment method and proof (e.g., bank deposit screenshot).

- **Follow-Up System**:

- Set reminders with due dates and notes.

- Get daily task list (e.g., “Follow up with 3 customers today”).

- **Bulk Communication**:

- Send WhatsApp/SMS to selected customers (e.g., restock alert).

- Message templates (e.g., “Hi [Name], your order is ready!”).

- **Dashboard & Insights**:

- Total customers, active inquiries, overdue follow-ups.

- Top customers by interaction frequency.

- **Data Export**: Export customer list or interaction history as CSV.


### 3.2 Out of Scope

- Integrated payment processing (e.g., Stripe, Genie).

- Inventory or POS functionality (can link to your other project separately).

- Email marketing (focus on WhatsApp/SMS only).

- Multi-user role permissions beyond basic staff access.

- AI-driven recommendations or predictive analytics.


---


## **4. Functional Requirements**


| Module | Feature | Description |

|-------|--------|------------|

| **Authentication** | Shop Owner Login | Secure access via email/password |

| | Staff Access (Optional) | View-only or limited edit rights |

| **Customer Management** | Add Customer | Name, phone (primary key), address, notes |

| | Customer Profile | View all interactions, orders, tags |

| | Search & Filter | By name, phone, tag, last contact date |

| **Interaction Log** | Log New Interaction | Type (call, WhatsApp, in-person), date, notes |

| | Attach Media | Upload image (e.g., product photo from customer) |

| | Link to Order | Optional association |

| **Order Tracking** | Create Order from Inquiry | Auto-generate from interaction |

| | Status Workflow | Inquiry → Quoted → Confirmed → Paid → Delivered |

| | Payment Proof Upload | Screenshot of bank deposit or transfer |

| **Follow-Up System** | Create Reminder | Set date/time, assign to self, add note |

| | Daily Task List | Show pending follow-ups due today |

| | Mark as Completed | With optional resolution note |

| **Bulk Messaging** | Select Customers | By tag, last purchase, or manual selection |

| | Send WhatsApp/SMS | Via WhatsApp Business API or Twilio |

| | Save Templates | Reusable message formats |

| **Dashboard** | Key Metrics | Total customers, active inquiries, overdue follow-ups |

| | Recent Activity Feed | Last 10 interactions |

| | Customer Insights | Top 5 most engaged customers |

| **Settings** | Shop Info | Name, contact, logo |

| | Notification Preferences | Enable/disable reminders, message logs |


---


## **5. Non-Functional Requirements**


- **Usability**: Fully operable on a smartphone; data entry in <30 seconds.

- **Privacy**: Customer phone numbers never exposed publicly; encrypted at rest.

- **Performance**: Load customer list in <1.5s with 1,000+ contacts.

- **Offline Support**: Allow draft interaction logging (sync when online)—optional.

- **Reliability**: Daily cloud backup; no data loss on refresh.

- **Cost Efficiency**: Free to deploy; uses low-cost SMS/WhatsApp APIs.

- **Localization**: Support Sinhala/English toggle (Phase 2).


---


## **6. System Architecture**


- **Frontend**: React.js + Tailwind CSS (mobile-first, fast)

- **Backend**: Node.js/Express **or** Django (Python)

- **Database**: PostgreSQL (relational, ideal for customer-interaction links)

- **Authentication**: JWT or Firebase Auth

- **Messaging**: WhatsApp Cloud API (Meta) + Twilio (SMS fallback)

- **File Storage**: Firebase Storage or Cloudinary (for inquiry images)

- **Hosting**: Vercel (frontend), Render (backend) — free tiers supported


---


## **7. Database Design (Key Entities)**


- **Users**

(`user_id`, `shop_name`, `email`, `password_hash`, `phone`, `created_at`)


- **Customers**

(`customer_id`, `user_id`, `name`, `phone`, `address`, `notes`, `tags`, `created_at`)


- **Interactions**

(`interaction_id`, `customer_id`, `type`, `date`, `notes`, `media_url`, `order_id` [nullable])


- **Orders**

(`order_id`, `customer_id`, `status`, `total_amount`, `payment_proof_url`, `created_at`, `updated_at`)


- **FollowUps**

(`followup_id`, `customer_id`, `due_date`, `note`, `completed`, `completed_at`)


- **MessageTemplates**

(`template_id`, `user_id`, `name`, `content`)


- **SentMessages**

(`message_id`, `customer_id`, `template_id`, `channel` [whatsapp/sms], `status`, `sent_at`)


*(Normalized structure: one customer → many interactions/orders/follow-ups.)*


---


## **8. Feature Comparison with Real-World Systems**


| Feature | **Proposed Lightweight CRM** | **Existing CRMs (e.g., Zoho CRM, HubSpot, Excel)** |

|--------|------------------------------|---------------------------------------------------|

| **Designed for Small Shops** | ✅ Yes — simple, no jargon | ❌ Enterprise-focused; overwhelming for 1-person shops |

| **WhatsApp Integration** | ✅ Native support for inquiry photos & bulk alerts | ❌ Requires paid add-ons or complex setup |

| **Order + Payment Tracking** | ✅ Built-in for resellers (like your business) | ❌ Requires separate invoicing module |

| **Follow-Up Reminders** | ✅ Task-based, mobile-friendly | ⚠️ Available but buried in menus |

| **Cost** | ✅ Free to self-host | ❌ Zoho: ~LKR 1,500+/user/month; HubSpot: starts free but limited |

| **Data Ownership** | ✅ Full control; export anytime | ❌ Locked in cloud; hard to migrate |

| **Offline Use** | ✅ Planned (drafts) | ❌ Most require constant internet |

| **Sri Lankan Context** | ✅ Optimized for phone-based, cash/deposit workflows | ❌ Assumes credit cards, email, formal invoicing |


> ✅ **Key Advantage**: This CRM **mirrors your real business workflow**—from receiving a product photo via WhatsApp to confirming a bank deposit—**without forcing you into complex sales pipelines**.


---


## **9. Development Roadmap**


| Phase | Duration | Deliverables |

|------|--------|-------------|

| **Phase 1** | Weeks 1–2 | Requirements, DB schema, UI wireframes |

| **Phase 2** | Weeks 3–5 | Auth, customer management, interaction logging |

| **Phase 3** | Weeks 6–8 | Order & payment tracking + follow-up system |

| **Phase 4** | Weeks 9–10 | WhatsApp/SMS integration + message templates |

| **Phase 5** | Week 11 | Dashboard, reporting, export features |

| **Phase 6** | Week 12 | Testing, deployment, documentation, demo video |


---


## **10. Expected Outcomes & Impact**


- Help small shop owners **retain 20–30% more customers** through systematic follow-ups.

- Reduce missed opportunities from forgotten inquiries.

- Provide **actionable insights** without data science complexity.

- Serve as a **real-world tool** you can use in your own buy-and-sell business.

- Fulfill all academic, technical, and innovation criteria for a BIT final-year project.


---


## **11. Conclusion**


The *Lightweight CRM for Small Retailers* solves a silent but costly problem: **customer invisibility**. By digitizing the informal relationships that drive small businesses, it turns memory and WhatsApp chaos into a strategic asset—**all within a simple, affordable, and locally relevant system**.


This document is **complete, detailed, and ready for immediate development**, meeting all standards for a **University of Moratuwa BIT final-year Project Proposal and SRS**.


---


Would you like any of the following to finalize your submission?

- **UML Diagrams** (Use Case: “Log Customer Inquiry”, Class Diagram)

- **UI Mockups** (Customer profile, interaction log, follow-up list)

- **Risk & Feasibility Analysis**

- **BIT-compliant formatting (cover page, ToC, references)**


Just let me know—I’m ready to help you deliver an outstanding project!

Sunday, December 28, 2025

Final Year Project Proposal & Software Requirements Specification (SRS) Software Solution: Smart Parking Finder Web Application

 





**Title:** *Drivers can’t find parking* → **Software Solution: Smart Parking Finder Web Application**


*Submitted in partial fulfillment of the requirements for the Bachelor of Information Technology (BIT) – External Degree Programme, University of Moratuwa*


---


## **1. Introduction**


### 1.1 Problem Statement

In urban areas of Sri Lanka—especially Colombo, Kandy, and major university towns—**finding available parking is a daily frustration** for drivers. Key issues include:


- **No real-time visibility** into parking availability; drivers circle blocks wasting time and fuel.

- **Manual parking lots** with no digital occupancy tracking.

- **Unpredictable pricing** and unclear operating hours.

- **Overcrowding** at commercial zones during peak hours, while nearby private or underused lots remain empty.

- **Illicit parking** on sidewalks or roads due to lack of alternatives, causing traffic congestion.

- **Tourists and visitors** struggle to locate legal, safe parking near malls, hospitals, or campuses.


This leads to:

- Increased traffic congestion and pollution,

- Lost productivity and customer dissatisfaction,

- Revenue loss for parking lot owners due to low utilization,

- Safety and legal risks from illegal parking.


### 1.2 Proposed Solution

A **web-based Smart Parking Finder Application** that aggregates real-time and scheduled parking data from public, private, and commercial lots, enabling drivers to:


- **Search** for nearby parking spaces by location or destination,

- **View real-time availability** (where sensors exist) or **predictive availability** (based on historical/reservation data),

- **Compare pricing, operating hours, and amenities** (e.g., CCTV, EV charging, covered),

- **Reserve a spot** (optional for partnered lots),

- **Navigate directly** via integrated maps,

- **Receive reminders** before reservation expiry.


The system is designed for **low-infrastructure environments**—supporting both **sensor-enabled lots** and **manual/admin-updated lots**—making it practical for Sri Lankan adoption.


---


## **2. Objectives**


- Reduce time and fuel wasted searching for parking.

- Increase parking space utilization through better visibility.

- Provide a unified platform for public, private, and commercial parking providers.

- Enable small parking lot owners to digitize operations with minimal cost.

- Improve urban mobility and reduce congestion.

- Deliver a scalable, deployable system for Sri Lankan cities and university campuses.


---


## **3. Scope**


### 3.1 In Scope

- **Web application** (mobile-first, responsive) for drivers and parking lot administrators.

- **Driver features**:

- Search parking by current location or destination (e.g., “near Colombo Fort” or “University of Moratuwa”).

- View real-time or estimated availability.

- Filter by price, distance, covered/uncovered, EV charging, security.

- See operating hours, contact info, and user ratings.

- Reserve a spot (for lots that support booking).

- Get turn-by-turn navigation (via Google Maps link).

- Receive SMS/email reminder 15 mins before reservation ends.

- **Parking Admin Portal**:

- Register lot (name, location, capacity, pricing, photos).

- Update real-time availability manually (e.g., “12/20 spots free”).

- Enable/disable reservations.

- View booking history and occupancy analytics.

- **Admin (System) Dashboard**:

- Approve/reject parking lot registrations.

- Monitor platform usage, popular zones, uptime.

- **Offline-Friendly Design**: Cache recent searches; allow basic use with low connectivity.


### 3.2 Out of Scope

- Hardware installation (e.g., IoT sensors, cameras)—system assumes manual or third-party data input.

- Native mobile apps (Android/iOS)—web app only (PWA-capable).

- In-app payments or wallet integration—reservations are free or “pay at lot”.

- Dynamic pricing algorithms (e.g., surge pricing).

- Integration with city traffic control systems.

- Enforcement or violation tracking (e.g., towing).


---


## **4. Functional Requirements**


| Module | Feature | Description |

|-------|--------|------------|

| **User Roles** | **Driver (Guest/Registered)** | Search, view, reserve, navigate |

| | **Parking Lot Owner** | Register lot, update availability, manage bookings |

| | **System Admin** | Moderate lots, view analytics, manage users |

| **Location & Search** | Geolocation Detection | Auto-detect user’s current location |

| | Destination Search | Search by place name, address, or point of interest |

| | Map View | Interactive map with parking pins (color-coded: green = available, red = full) |

| **Parking Details** | Lot Profile | Name, address, photos, operating hours |

| | Real-Time Status | “14/30 spots free” — updated manually or via API |

| | Pricing Info | Hourly/daily rates, discounts (e.g., student, early bird) |

| | Amenities | Covered, CCTV, EV charging, wheelchair access |

| | User Ratings & Reviews | 1–5 stars + comments |

| **Reservation System** | Book Spot | Select duration (e.g., 2 hours), confirm |

| | Booking QR Code | Generate digital pass (for lot staff verification) |

| | Cancellation | Allow free cancellation up to 15 mins before |

| **Navigation** | Google Maps Integration | “Navigate” button opens directions in Maps |

| **Notifications** | Booking Confirmation | SMS/email with QR code and expiry time |

| | Expiry Reminder | Alert 15 mins before reservation ends |

| **Admin Portal (Lot Owner)** | Lot Registration Form | Location (map pin), capacity, pricing, photos |

| | Availability Update | Slider or form to set current free spots |

| | Reservation Toggle | Enable/disable booking capability |

| | Booking Calendar | View upcoming reserved slots |

| **System Admin** | Lot Approval Workflow | Review and verify new lot submissions |

| | Platform Analytics | Top searched areas, avg. occupancy, user growth |

| **Reporting** | Occupancy Trends | Daily/weekly usage per lot |

| | Popular Destinations | Most-searched locations |


---


## **5. Non-Functional Requirements**


- **Performance**: Load parking results within 2 seconds (even with 200+ lots).

- **Usability**: Driver can find and reserve parking in <60 seconds.

- **Mobile-First**: Fully functional on 3G networks and low-end smartphones.

- **Accuracy**: Location precision within 50 meters; clear “last updated” timestamps.

- **Security**: User data protected; no payment info stored.

- **Scalability**: Support 5,000+ drivers and 200+ parking lots in Phase 1.

- **Reliability**: 99% uptime during business hours (7 AM–10 PM).

- **Privacy**: No tracking of user movements beyond active session.


---


## **6. System Architecture**


- **Frontend**: React.js + Leaflet/Google Maps API (lightweight, mobile-optimized)

- **Backend**: Node.js/Express **or** Django (RESTful API)

- **Database**: PostgreSQL (geospatial support via PostGIS for location queries)

- **Authentication**: Firebase Auth or JWT (optional for drivers; required for lot owners)

- **Geolocation**: Browser Geolocation API + Google Places API

- **Notifications**: Twilio (SMS) + Nodemailer (email)

- **Hosting**: Vercel (frontend), Render/Heroku (backend)

- **Optional Future**: Webhooks for IoT sensor integration (e.g., Ultrasonic + ESP32)


---


## **7. Database Design (Key Entities)**


- **Users**

(`user_id`, `name`, `email`, `phone`, `role`, `created_at`)


- **ParkingLots**

(`lot_id`, `owner_id`, `name`, `address`, `latitude`, `longitude`, `total_capacity`, `hourly_rate`, `daily_rate`, `open_time`, `close_time`, `amenities`, `photos`, `status` [active/pending/inactive])


- **LotAvailability**

(`availability_id`, `lot_id`, `free_spots`, `last_updated`, `source` [manual/api])


- **Reservations**

(`reservation_id`, `user_id`, `lot_id`, `start_time`, `end_time`, `qr_code`, `status` [active/expired/cancelled])


- **Reviews**

(`review_id`, `user_id`, `lot_id`, `rating`, `comment`, `created_at`)


- **SearchLogs** (anonymous)

(`log_id`, `lat`, `lng`, `timestamp`, `result_count`)


*(Geospatial indexing on `latitude/longitude` for fast proximity searches.)*


---


## **8. Feature Comparison with Real-World Systems**


| Feature | **Proposed Smart Parking Finder** | **Existing Systems (e.g., Google Maps, Parkopedia, JustPark)** |

|--------|----------------------------------|--------------------------------------------------------------|

| **Real-Time Availability** | ✅ Manual + sensor-ready (Sri Lankan context) | ❌ Google Maps: mostly static info<br>✅ Parkopedia: limited to partnered garages |

| **Reservation** | ✅ For any registered lot (even small private ones) | ❌ Google: no booking<br>✅ JustPark: only commercial lots |

| **Low-Cost for Small Lots** | ✅ Free registration; no hardware needed | ❌ Most require IoT sensors or monthly fees |

| **Local Relevance** | ✅ Built for Colombo, Kandy, campuses | ❌ Global apps lack Sri Lankan parking data |

| **Offline Use** | ✅ Caches recent searches | ❌ Requires constant internet |

| **No Payment Complexity** | ✅ Pay at lot — no in-app wallet | ❌ Many apps force digital payments |

| **University/Campus Focus** | ✅ Can deploy at UoM, SLIIT, etc. | ❌ Not tailored for academic zones |


> ✅ **Key Innovation**: This system **democratizes smart parking**—enabling even a small private garage owner in Maradana to appear alongside major malls, using only a smartphone.


---


## **9. Development Roadmap**


| Phase | Duration | Deliverables |

|------|--------|-------------|

| **Phase 1** | Weeks 1–2 | Requirements, DB schema, map integration setup |

| **Phase 2** | Weeks 3–5 | Driver search + map view + lot details |

| **Phase 3** | Weeks 6–8 | Parking lot owner portal + availability update |

| **Phase 4** | Weeks 9–10 | Reservation system + QR generation |

| **Phase 5** | Week 11 | Notifications + admin dashboard + reviews |

| **Phase 6** | Week 12 | Testing, deployment, documentation, demo video |


---


## **10. Expected Outcomes & Impact**


- Reduce average parking search time by **50%+** in pilot zones.

- Increase revenue for small parking providers through better visibility.

- Improve traffic flow and reduce emissions in congested urban cores.

- Provide a **practical, scalable smart city solution** for Sri Lankan municipalities.

- Deliver a **complete, portfolio-ready software project** for your BIT degree.


---


## **11. Conclusion**


The *Smart Parking Finder* bridges the gap between modern urban mobility needs and the realities of Sri Lanka’s mixed-infrastructure environment. By prioritizing **accessibility, simplicity, and local relevance**, it offers a realistic path toward smarter cities—starting with one parking spot at a time.


This document is **fully detailed, technically sound, and ready for development**, satisfying all requirements for a **University of Moratuwa BIT final-year Project Proposal and SRS**.


---


Would you like any of the following to support your submission?

- **UML Diagrams** (Use Case for driver, Class Diagram with geospatial entities)

- **Wireframes** (Map view, lot detail page, reservation flow)

- **Risk Assessment** (e.g., data accuracy, user adoption)

- **BIT-compliant title page & table of contents**


Just say the word—I’m here to help you succeed!

Tuesday, December 23, 2025

Smart Hostel Room Allocation & Management Web Application Final Year Project Proposal & Software Requirements Specification (SRS)

 


# **Final Year Project Proposal & Software Requirements Specification (SRS)**

**Title:** *Messy hostel management* → **Software Solution: Smart Hostel Room Allocation & Management Web Application**


*Submitted in partial fulfillment of the requirements for the Bachelor of Information Technology (BIT) – External Degree Programme, University of Moratuwa*


---


## **1. Introduction**


### 1.1 Problem Statement

University and private hostel management in Sri Lanka is overwhelmingly **manual, error-prone, and reactive**. Common pain points include:


- **Room allocation** done via spreadsheets or paper lists—leading to double bookings or vacant rooms going unnoticed.

- **No centralized tracking** of occupancy, check-in/check-out dates, or resident details.

- **Fee collection** handled offline with no digital receipts or arrears tracking.

- **Maintenance requests** submitted verbally or via WhatsApp—often forgotten or unassigned.

- **Visitor logs** maintained in notebooks—ineffective for security or emergency contact.

- **No integration** between admissions, room assignment, and billing.


This results in:

- Administrative chaos during peak intake periods,

- Revenue leakage from untracked occupants,

- Poor student experience due to disorganization,

- Safety and compliance risks (e.g., overcrowding, unknown visitors).


### 1.2 Proposed Solution

A **web-based Hostel Room Allocation & Management System** that digitizes the entire hostel lifecycle—from application to checkout—with automation, real-time visibility, and role-based access.


Designed for **university hostels, private student accommodations, and boarding facilities**, the system ensures:

- Fair, rule-based room allocation,

- Real-time occupancy dashboard,

- Digital fee management,

- Maintenance ticketing,

- Secure visitor logging,

- Mobile-friendly access for staff and students.


---


## **2. Objectives**


- Replace paper-based and spreadsheet-driven hostel operations with a unified digital platform.

- Automate room allocation based on gender, course, year, preferences, and availability.

- Reduce administrative workload for hostel wardens and managers.

- Improve student transparency (e.g., view room status, pay fees online).

- Enhance safety through visitor logs and emergency contact tracking.

- Prevent revenue loss via accurate occupancy and fee tracking.


---


## **3. Scope**


### 3.1 In Scope

- **Web application** (mobile-responsive) for admin, warden, and student users.

- **Student portal**: Apply for hostel, view allocation status, pay fees, raise maintenance requests.

- **Admin/Warden dashboard**: Manage buildings, rooms, residents, fees, maintenance, visitors.

- **Smart room allocation engine** with configurable rules (e.g., same department, gender, no-smoking).

- **Real-time occupancy tracking** (occupied/vacant/under maintenance).

- **Fee management**: Generate invoices, track payments, flag arrears, issue digital receipts.

- **Maintenance request system**: Submit, assign, track, and close tickets.

- **Visitor log**: Register guest name, purpose, time-in/out, resident host.

- **Reporting**: Occupancy rate, fee collection summary, maintenance backlog.

- **Notifications**: Email/SMS alerts for allocation, payment due, maintenance updates.


### 3.2 Out of Scope

- Biometric access control or IoT room sensors.

- Integration with university SIS (Student Information System)—manual student data entry allowed.

- Mobile native apps (Android/iOS).

- Online payment gateway integration (e.g., Stripe, Genie)—receipt upload for offline payments only.

- Meal/laundry service management.


---


## **4. Functional Requirements**


| Module | Feature | Description |

|-------|--------|------------|

| **User Roles** | **Student** | Apply, view room, pay fee (upload proof), raise tickets |

| | **Warden** | Approve applications, assign rooms, manage daily ops |

| | **Admin** | Full control: buildings, users, reports, settings |

| **Hostel Setup** | Add Buildings & Floors | Define structure (e.g., Block A, Floor 2) |

| | Define Room Types | Single, double, triple; with amenities (AC, attached bath) |

| | Set Room Capacity & Rules | Max occupants, gender restriction, smoking policy |

| **Student Application** | Online Application Form | Name, NIC, contact, course, year, gender, preferences |

| | Upload Documents | ID, admission letter, medical certificate |

| | Application Status Tracker | Pending → Approved → Room Assigned → Checked-in |

| **Room Allocation** | Auto-Allocation Engine | Match students to rooms using rules + availability |

| | Manual Override | Warden can reassign if needed |

| | Room Swap Requests | Students can request (warden approval needed) |

| **Occupancy Management** | Real-Time Dashboard | Color-coded room status (green = vacant, red = occupied) |

| | Check-in/Check-out | Record dates, collect key, final inspection |

| | Emergency Contact Info | Stored per resident |

| **Fee Management** | Generate Monthly Invoice | Based on room type |

| | Track Payments | Mark as paid (with receipt upload) |

| | Arrears Alert | Highlight overdue accounts |

| | Fee History | Per student, exportable |

| **Maintenance** | Submit Request | Student selects room, describes issue, uploads photo |

| | Ticket Assignment | Warden assigns to staff (plumber, electrician) |

| | Status Tracking | Open → In Progress → Resolved |

| **Visitor Management** | Visitor Registration | Guest name, NIC, purpose, expected duration |

| | Auto Time-Out Alert | Notify if visitor exceeds 2 hours (configurable) |

| **Reporting** | Occupancy Report | % filled per floor/block |

| | Fee Collection Summary | Paid vs. pending |

| | Maintenance Analytics | Most common issues, avg. resolution time |

| **Notifications** | Allocation Confirmation | SMS/email when room assigned |

| | Payment Reminder | 3 days before due date |

| | Maintenance Update | When ticket status changes |


---


## **5. Non-Functional Requirements**


- **Usability**: Intuitive for non-technical wardens; student onboarding < 2 minutes.

- **Performance**: Load room map in <1.5s with 200+ rooms.

- **Security**: Role-based access; student data never visible to other students.

- **Reliability**: Daily automated backups; audit log for critical actions (e.g., room reassignment).

- **Scalability**: Support up to 1,000 residents across 5 buildings.

- **Offline Resilience**: Allow data entry during internet outages (sync when restored)—optional Phase 2.

- **Compliance**: Adhere to Sri Lankan data privacy expectations (no public exposure of NIC).


---


## **6. System Architecture**


- **Frontend**: React.js + Material UI (responsive, accessible)

- **Backend**: Node.js/Express **or** Django (Python) — REST API

- **Database**: PostgreSQL (relational, supports complex room-resident relationships)

- **File Storage**: Cloudinary or Firebase Storage (for ID/docs/photos)

- **Authentication**: JWT with role middleware

- **Notifications**: Twilio (SMS) + Nodemailer (email)

- **Hosting**: Vercel (frontend) + Render/Heroku (backend)


---


## **7. Database Design (Key Entities)**


- **Users** (`user_id`, `name`, `email`, `role`, `phone`, `password_hash`)

- **Students** (`student_id`, `user_id`, `nic`, `course`, `year`, `gender`, `emergency_contact`)

- **HostelBuildings** (`building_id`, `name`, `address`, `warden_id`)

- **Rooms** (`room_id`, `building_id`, `room_number`, `type`, `capacity`, `gender_restriction`, `status`)

- **RoomAllocations** (`allocation_id`, `student_id`, `room_id`, `check_in`, `check_out`, `status`)

- **Applications** (`app_id`, `student_id`, `room_preference`, `documents_url`, `status`)

- **Fees** (`fee_id`, `student_id`, `month`, `amount`, `due_date`, `paid`, `receipt_url`)

- **MaintenanceTickets** (`ticket_id`, `room_id`, `student_id`, `description`, `photo_url`, `assigned_to`, `status`, `resolved_at`)

- **Visitors** (`visitor_id`, `resident_id`, `name`, `nic`, `purpose`, `time_in`, `time_out`, `checked_out`)


*(Normalized to prevent duplication; e.g., one student → one user → one application.)*


---


## **8. Feature Comparison with Real-World Systems**


| Feature | **Proposed System** | **Existing Solutions (e.g., HostelPro, RoomRaccoon, Excel)** |

|--------|--------------------|-----------------------------------------------------------|

| **Room Allocation** | Rule-based auto-assign + manual override | Manual (Excel) or rigid (commercial tools) |

| **Real-Time Occupancy Map** | Visual, color-coded dashboard | Not available in spreadsheets; paid tools only |

| **Maintenance Tracking** | Full ticket lifecycle with photos | WhatsApp/chat — no tracking or accountability |

| **Fee Management** | Digital invoices + arrears alerts | Cashbook or manual ledger — error-prone |

| **Visitor Logging** | Digital form with time-in/out | Paper register — easily bypassed |

| **Student Self-Service** | Apply, view room, request swap | None — all requests via warden |

| **Cost** | Free/low-cost open deployment | Commercial systems: LKR 20,000+/month |

| **Customization** | Built for Sri Lankan hostels (NIC, local rules) | Generic, Western-focused (e.g., dorm-style only) |

| **Tech Access** | Works on any smartphone/browser | Many require desktop + training |


> ✅ **Key Advantage**: This system is **designed for resource-constrained Sri Lankan hostels**—no payment gateways, no complex integrations, just **practical digitization**.


---


## **9. Development Roadmap**


| Phase | Duration | Deliverables |

|------|--------|-------------|

| **Phase 1** | Weeks 1–2 | Requirements finalization, DB schema, UI wireframes |

| **Phase 2** | Weeks 3–5 | Auth, user roles, hostel setup (buildings/rooms) |

| **Phase 3** | Weeks 6–8 | Student application + auto room allocation engine |

| **Phase 4** | Weeks 9–10 | Fee management + maintenance ticketing |

| **Phase 5** | Week 11 | Visitor log, reporting, notifications |

| **Phase 6** | Week 12 | Testing, deployment, documentation, demo video |


---


## **10. Expected Outcomes & Impact**


- Eliminate room allocation conflicts and vacant room waste.

- Reduce warden workload by 40–60% through automation.

- Improve student satisfaction with transparent, self-service access.

- Enhance hostel safety via digital visitor logs and emergency contacts.

- Provide a **real, deployable system** for University of Moratuwa hostels or private student accommodations.

- Fulfill all academic, technical, and innovation criteria for a BIT final-year project.


---


## **11. Conclusion**


The *Smart Hostel Room Allocation App* transforms chaotic, paper-based hostel operations into a **structured, efficient, and student-friendly digital experience**. By focusing on **Sri Lankan context**, **affordability**, and **core functionality**, it offers immediate value while serving as a robust software engineering project.


This document is **complete, detailed, and ready for development**—satisfying both **Project Proposal** and **SRS** requirements for your BIT final year submission.


---


Would you like any of the following to accompany this?

- **UML Diagrams** (Use Case, Class, Activity for room allocation)

- **Sample UI Mockups** (Room dashboard, student portal)

- **Risk Analysis & Testing Strategy**

- **BIT-compliant formatting (LaTeX or Word template)**


Just let me know—I’m ready to help you finalize and submit!



💥 WordPress https://computerclassinsrilanka.wordpress.com

💥 Facebook https://web.facebook.com/itclasssrilanka

💥 Wix https://itclasssl.wixsite.com/icttraining

💥 Web https://itclasssl.github.io/eTeacher/

💥 Medium https://medium.com/@itclasssl

💥 Quora https://www.quora.com/profile/BIT-UCSC-UoM-Final-Year-Student-Project-Guide

💥 mystrikingly https://bit-ucsc-uom-final-year-project-ideas-help-guide-php-class.mystrikingly.com/

💥 https://elakiri.com/threads/bit-ucsc-uom-php-mysql-project-guidance-and-individual-classes-in-colombo.1627048/

💥 https://bitbscucscuomfinalprojectclasslk.weebly.com/

💥 https://www.tiktok.com/@onlinelearningitclassso1

💥 https://payhip.com/eTeacherAmithafz/

💥 https://discord.gg/cPWAANKt

💥 https://6789f6ca695da.site123.me/blog

💥 https://itclasssl.github.io/eTeacher/

💥 https://www.tumblr.com/blog/computercoursesincolombo-blog

💥Subscribe on LinkedIn https://www.linkedin.com/build-relation/newsletter-follow?entityUrn=7072056309516304384

💥https://www.scribd.com/user/682883198/Online-Learning-IT-Class-Software-Dev



🚀 English Sinhala Tamil Medium Online Classes

✅ Final Year Software Web Project Guidance BIT UCSC UoM

✅ Grade 1 to GCE O/L A/L ICT GIT Classes

✅ PHP & Python Training

✅ Web & Software Development

✅ Social Media Marketing

📲 Learn, Build & Succeed! Join us today! 🚀


🚀 Looking for HIGH-ENGAGEMENT Student Groups to Share Your IT/CS Project Ideas?


Here’s the ULTIMATE list to get MASSIVE reach in 2025! 💥💥💥


🧨 1. University IT/CS Students Groups (SUPER ACTIVE!)


Search Keywords:

Computer Science Students • IT Students Community • Software Engineering Students • BSc IT Students • Final Year Project Group


🌏 2. Indian Engineering Groups (HUGE REACH!)


Millions of BTech/BCA/MCA students!

Search:

BTech Projects • Engineering Students India • BCA MCA Students • CSE Students Group • Polytechnic IT Group


🇧🇩 3. Bangladesh CS/IT Groups (VERY ENGAGED!)


Search:

CSE Bangladesh • ICT Bangladesh • University Students BD • Final Year Project BD


🇵🇰 4. Pakistan IT & CS Groups


Search:

CS Pakistan • IT Students Pakistan • Final Year Projects Pakistan • BSCS Students Pakistan


🇱🇰 5. Sri Lankan IT/SE Groups (HOME ADVANTAGE!)


Search:

UCSC Groups • SLIIT Groups • IT Students Sri Lanka • BIT External Groups • SL IT Jobs & Projects


💻 6. Global Programming & Coding Groups


Search:

Python Projects • JavaScript Developers • Web Developers Community • MERN Stack Devs • Full-Stack Developers


🤖 7. AI & Machine Learning Groups


Search:

AI Projects • Machine Learning Community • Data Science Projects • AI Engineers Group


📱 8. App Development Groups


Search:

Android Project Ideas • Flutter Developers • Mobile App Developers


🧑‍🎓 9. Assignment & Academic Help Groups


Search:

Assignment Help • University Students Help • Homework Help • Academic Projects


🌍 10. Tech Learning & Career Groups


Search:

Tech Learners Community • Learn Programming • Coding For Beginners • Computer Science Hub


🎯 Pro Tips for MAXIMUM Reach


🔥 Join 30–40 groups

🔥 Post 5–6 times per day

🔥 Change your caption slightly each time

🔥 Use strong hooks like:


“🔥 Final Year IT Project Idea (Problem + Solution)”


“💡 Real-World IT Problem You Can Solve With AI!”


“🚀 Best Project for BSc/BIT/MCA Students!”


#️⃣ Hashtags to BOOST Reach

#ITProjects #CSStudents #FinalYearProject #SoftwareEngineering #ComputerScience #BTechStudents #UniversityProjects #ProgrammingIdeas #AIProjects #WebDevelopment #MobileDevelopment #CodingCommunity #SriLankaIT #IndiaEngineering #BangladeshCSE #PakistaniStudents #StudentProjects #ProjectIdeas2025


Monday, December 22, 2025

Final Year Project Proposal & Software Requirements Specification (SRS) Clinics struggle with manual records Integrated E-Channeling and Digital Patient Record System Code

 


# ****

**Title:** *Clinics struggle with manual records* → **Software Solution: Integrated E-Channeling and Digital Patient Record System**


*Submitted in partial fulfillment of the requirements for the Bachelor of Information Technology (BIT) – External Degree Programme, University of Moratuwa*


---


## **1. Introduction**


### 1.1 Problem Statement

Small and medium-sized private clinics—especially in semi-urban and rural Sri Lanka—still rely on **paper-based patient records, manual appointment books, and phone-based booking**. This leads to:

- Lost or damaged medical files,

- Double-booking or missed appointments,

- Inefficient patient flow and long waiting times,

- Difficulty tracking patient history (e.g., allergies, chronic conditions),

- No centralized view of doctor availability or room usage,

- Poor communication between front desk, doctors, and patients.


In the post-pandemic era, patients increasingly expect **digital appointment booking (e-channeling)** and secure access to their records—yet most local clinics lack affordable, integrated systems.


### 1.2 Proposed Solution

A **web-based E-Channeling and Electronic Medical Record (EMR) System** designed specifically for small clinics. It combines:

- Online appointment booking (E-Channeling) for patients,

- Digital patient registration and health records,

- Doctor schedule and room management,

- Automated reminders (SMS/WhatsApp),

- Secure access controls for staff roles (receptionist, doctor, admin).


The system replaces paper files and phone logs with a **single, unified, low-cost digital platform** that improves clinic efficiency and patient experience—without requiring expensive hardware or IT staff.


---


## **2. Objectives**


- Eliminate paper-based patient records and appointment logs.

- Enable patients to book, reschedule, or cancel appointments online.

- Maintain a structured, searchable digital health record per patient.

- Reduce no-shows with automated SMS/WhatsApp reminders.

- Streamline clinic workflow: check-in → consultation → prescription → follow-up.

- Ensure data privacy and role-based access (HIPAA-inspired principles).

- Provide a scalable system usable by clinics with 1–5 doctors.


---


## **3. Scope**


### 3.1 In Scope

- Web application (mobile-responsive) for clinic staff and patients.

- **Patient Portal**: Register, view appointment history, book slots, receive reminders.

- **Clinic Admin Panel**: Manage doctors, rooms, working hours, holidays.

- **Doctor Dashboard**: View daily appointments, access patient records, add notes/diagnoses.

- **Receptionist Module**: Check-in patients, manage walk-ins, print tokens.

- **E-Channeling**: Real-time doctor availability, slot selection, instant confirmation.

- **Digital Patient Record**: Demographics, medical history, allergies, diagnoses, prescriptions, lab notes.

- **Automated Notifications**: WhatsApp/SMS reminders 24 hours before appointments.

- **Reporting**: Daily patient count, no-show rate, doctor utilization.

- **Data Export**: PDF prescriptions, printable medical summaries.


### 3.2 Out of Scope

- Integration with national health systems (e.g., eZ64, government EMRs).

- Telemedicine/video consultation (can share Zoom link manually).

- Pharmacy or billing/invoicing beyond basic prescription notes.

- Multi-branch clinic support (single-clinic focus).

- AI diagnostics or clinical decision support.


---


## **4. Functional Requirements**


| Module | Feature | Description |

|-------|--------|------------|

| **User Roles** | Patient | Book appointments, view history, update profile |

| | Receptionist | Manage walk-ins, check-in, print tokens |

| | Doctor | View schedule, access/edit patient records |

| | Admin | Manage users, doctors, rooms, clinic settings |

| **E-Channeling** | View Doctor Availability | Calendar with available time slots |

| | Book Appointment | Select doctor, date, time; receive confirmation |

| | Reschedule/Cancel | With reason (optional) |

| **Patient Management** | Patient Registration | Name, NIC, DOB, contact, address, blood group |

| | Unique Patient ID | Auto-generated (e.g., CLINIC-2025-001) |

| **Medical Records** | Problem List | Chronic conditions (e.g., diabetes, hypertension) |

| | Allergies & Medications | Track current/past drugs |

| | Visit Notes | Doctor adds diagnosis, symptoms, prescriptions |

| | Attachments | Upload lab reports or scanned documents |

| **Clinic Workflow** | Digital Token System | Auto-generated queue number at check-in |

| | Visit Status Tracking | Waiting → In Consultation → Completed |

| **Notifications** | Pre-Appointment Reminder | WhatsApp/SMS 24h before |

| | Cancellation Alert | Notify doctor/staff if patient cancels |

| **Reporting** | Daily Appointments | Filter by doctor/status |

| | No-Show Analytics | Track missed appointments |

| **Settings** | Clinic Info | Name, address, contact, logo |

| | Working Hours | Per doctor or clinic-wide |

| | Holiday Calendar | Block booking on public/national holidays |


---


## **5. Non-Functional Requirements**


- **Usability**: Simple UI for non-technical staff; <3 clicks to book/check-in.

- **Privacy & Security**: Role-based access; patient data encrypted; no public access.

- **Reliability**: 99.5% uptime; daily backups.

- **Performance**: Load appointment calendar in <1.5s with 500+ patients.

- **Compliance**: Follows basic medical data protection principles (no sensitive data exposed).

- **Offline Support**: None (cloud-first), but low-bandwidth optimized.

- **Mobile Responsiveness**: Fully functional on smartphones for patients and staff.


---


## **6. System Architecture**


- **Frontend**: React.js + Tailwind CSS (responsive, fast)

- **Backend**: Node.js with Express **or** Django (Python)

- **Database**: PostgreSQL (ACID-compliant, ideal for medical records)

- **Authentication**: JWT with role-based middleware

- **Notifications**: Twilio (SMS) + WhatsApp Cloud API

- **File Storage**: Cloudinary or AWS S3 (for lab reports, scanned docs)

- **Hosting**: Render (backend), Vercel (frontend) – low-cost/free tier compatible


---


## **7. Database Design (Key Entities)**


- **Users**

(`user_id`, `name`, `email`, `phone`, `role`, `password_hash`, `created_at`)


- **Patients**

(`patient_id`, `nic`, `dob`, `address`, `blood_group`, `allergies`, `created_at`)


- **Doctors**

(`doctor_id`, `user_id`, `specialization`, `room_no`, `working_hours`)


- **Appointments**

(`appointment_id`, `patient_id`, `doctor_id`, `date`, `time_slot`, `status` [scheduled/completed/cancelled/no-show], `notes`)


- **MedicalRecords**

(`record_id`, `patient_id`, `doctor_id`, `visit_date`, `diagnosis`, `symptoms`, `prescription`, `follow_up_date`)


- **Attachments**

(`attachment_id`, `record_id`, `file_url`, `description`)


- **ClinicSettings**

(`setting_id`, `clinic_name`, `address`, `contact`, `working_days`, `holidays`)


- **NotificationsLog**

(`log_id`, `patient_id`, `type`, `message`, `status` [sent/failed], `sent_at`)


*(Normalized schema to prevent duplication; patient identity linked securely.)*


---


## **8. Comparison with Existing Systems**


| System | Strengths | Weaknesses for Small Clinics |

|-------|----------|------------------------------|

| **Government E-Channeling (e.g., Lanka Hospitals)** | Brand trust, wide reach | Centralized, not for private small clinics |

| **Practo / Zesty** | Full EMR + billing | Expensive, over-engineered, subscription-based |

| **Google Calendar + Excel** | Free, familiar | No patient records, no reminders, no security |

| **Proposed System** | **Affordable**, **clinic-focused**, **Sri Lankan context**, **WhatsApp integration**, **no paper trail** | Limited to core functions (by design for simplicity) |


---


## **9. Development Roadmap**


| Phase | Duration | Deliverables |

|------|--------|-------------|

| **Phase 1** | Weeks 1–2 | Requirements, DB schema, tech stack setup |

| **Phase 2** | Weeks 3–5 | Auth, user roles, patient & doctor management |

| **Phase 3** | Weeks 6–8 | E-Channeling + appointment workflow |

| **Phase 4** | Weeks 9–10 | Digital medical records + check-in system |

| **Phase 5** | Week 11 | Notification system + reporting |

| **Phase 6** | Week 12 | Testing, deployment, documentation, demo |


---


## **10. Expected Outcomes & Impact**


- Replace error-prone paper records with structured digital health files.

- Reduce patient wait times and administrative burden.

- Increase clinic credibility through professional digital operations.

- Improve patient retention via reminders and easy rebooking.

- Deliver a **real-world, deployable system** that addresses a critical gap in Sri Lanka’s healthcare digitization—especially for small private practices.


---


## **11. Conclusion**


This project directly tackles the operational inefficiencies faced by local clinics through a **practical, privacy-aware, and user-friendly digital solution**. By integrating E-Channeling with electronic patient records in a single platform, it offers immediate value to both clinic staff and patients—while fulfilling all academic and technical requirements of a University of Moratuwa BIT final-year project.


This document is **ready for implementation** and serves as a complete **Project Proposal and SRS**.


---


Would you like any of the following?

- UML Use Case/Class Diagrams

- Sample patient record form (UI mockup)

- Risk assessment or testing plan

- BIT-compliant cover page & table of contents


Let me know—I'm happy to help finalize your submission!