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

Developing a Web-Based Online Learning and Attendance Tracking System requires a comprehensive understanding of both Learning Management Systems (LMS) and Attendance Management Systems. Below is a detailed list of modules, their sub-modules, and 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.

Functions:

• 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.

Functions:

• 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.

Functions:

• 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.

Functions:

• 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.

Functions:

• 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.

Functions:

• 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.

Functions:

• Track lessons completed

• Course completion percentage

• Detailed progress dashboards

• Performance trend graphs

---

8. Assessments & Grading

Purpose: Measure student learning outcomes.

Functions:

• 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.

Functions:

• Auto-generate completion certificates

• Customizable templates (logo, signatures)

• Digital badges for milestones

---

10. Notifications & Communication

Purpose: Keep users informed.

Functions:

• Email/SMS/Push alerts for:

  • Attendance updates

  • Class start reminders

  • Assignment deadlines

  • Course enrollment confirmations

---

11. Discussion & Community

Purpose: Facilitate interaction.

Functions:

• Course forums and threads

• Chat between instructors and students

• Q&A boards

• Private messages

---

12. Reporting & Dashboards

Purpose: Data analysis and export.

Functions:

• 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.

Functions:

• Payment gateways (Stripe/PayPal)

• Course pricing/subscriptions

• Invoicing & receipts

• Refund processing

---

14. Parent/Guardian Portal

Purpose: Visibility into student performance.

Functions:

• View attendance records

• Progress and grades

• Notifications about absences

• Message teachers

---

15. Content & Resource Library

Purpose: Central repository of learning materials.

Functions:

• Upload files (docs, presentations, videos)

• Organize by subject or curriculum

• Version control

---

16. Integration & API

Purpose: Connect with external tools/services.

Functions:

• 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.

Functions:

• System configuration

• Role & permission settings

• Audit logs

• Data backup and restore

• Multi-language and timezone support

---

18. Security & Compliance

Purpose: Protect user data.

Functions:

• SSL encryption

• Data privacy controls (GDPR or local standards)

• Regular security audits

---

👩‍💻 Optional Advanced Modules

These aren’t required but are strong value-adds:

• AI-Powered Learning Analytics (adaptive suggestions)

• Gamification (points/levels)

• Mobile Apps (Android/iOS)

• Offline Content Sync

• Offline Attendance Capture

---

📌 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: 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
• TalentLMS / LearnDash: For corporate or custom e-learning

---

More:

• A database schema for this system
• Tech stack recommendations (e.g., React + Node.js + MongoDB)
• Wireframes or user flow diagrams
• Priority-based development roadmap (MVP vs full version)

Good luck with your project! 🚀

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!

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!