Active Final Year Projects Showcase

The **Local SkillShare** platform directly solves the problem of financial drain and community fragmentation by transforming underutilized, dormant local human talent into an accessible, cashless resource marketplace. In modern neighborhoods, residents frequently spend significant sums of money hiring expensive commercial entities for minor tasks—such as configuring a home Wi-Fi router, fixing a basic mechanical issue, or obtaining foundational academic tutoring—while individuals with the exact skills to solve those problems live just a few doors away, completely invisible to their neighbors. By establishing a localized, barter-inspired digital ecosystem, this platform replaces monetary transactions with a direct exchange of services, allowing users to safely trade their unique skills (e.g., teaching a cooking recipe or an instrument) to "pay" for the practical help they need. This hyper-local framework not only makes hidden talent visible and breaks down accessibility barriers for hands-on, face-to-face learning, but it also bridges the digital-to-physical gap to foster deep real-world connections, building a cooperative neighborhood spirit and a stronger social safety net without any financial burden.

The primary users of this system are local community residents and neighbors (such as students, hobbyists, freelancers, and retirees), while HR Management is not a user at all. Because this project is built on a cashless, barter-inspired neighborhood system, it operates entirely outside of traditional corporate or company environments. University or school students living in the area who possess strong theoretical or modern technical skills but might be tight on budget.

1. User Account & Profile Management
Registration: The system must allow new users to create an account by providing their full name, unique email address, a password, and their specific neighborhood/locality.

Authentication & Session Security: The system must validate user credentials during login and initiate a secure server-side PHP session ($_SESSION) to restrict dashboard access to authenticated users only.

Profile Customization: Users must be able to view, edit, and update their profile details, including updating their neighborhood boundaries or optional coordinates via the HTML5 Geolocation API.

2. Skill Posting & Management (CRUD Operations)
Creating a Listing: Authenticated users must be able to submit a web form to post a skill listing, explicitly selecting whether it is an "Offer" (teaching/helping) or a "Request" (learning/needing help).

Categorization: The system must require users to map their skill postings to pre-defined relational categories (e.g., Tech, Academics, Cooking, Maintenance, Arts, Languages).

Reading & Displays: The application must fetch and display data dynamically, allowing users to view their own active posts on a personal management sub-page.

Updating & Deleting: Users must have exclusive authorization to update the description, change the status (e.g., mark as "Fulfilled"), or permanently delete their own listings from the MySQL database.

3. Search, Localized Filtering, & Discovery
Neighborhood Isolation: The system must automatically run an optimized SQL query upon dashboard initialization to fetch and display active skill postings where the poster's neighborhood matches the logged-in user's neighborhood.

Keyword Search: The system must execute case-insensitive database queries using the SQL LIKE operator to filter postings based on text strings entered into the search bar.

Multi-Criteria Filtering: The system must allow users to narrow down listings simultaneously by combining category drop-down filters and exchange type toggles (Offers vs. Requests).

4. Internal Micro-Communication Board
Message Routing: The system must provide a secure "Connect" action button on every skill card that routes the viewer to a private communication panel.
Thread Display: The system must retrieve and order text exchanges chronologically between any two interacting neighbors so users can coordinate meeting locations or times without exposing personal phone numbers.

5. Community Endorsement & Trust Management
Review Submission: Upon successful completion of an exchange, the system must allow a user to leave textual feedback and select a predefined positive recognition badge (e.g., Excellent Teacher, Great Learner, Super Helpful) for another user.

1. Security Requirements
Data Encryption: All sensitive user data, particularly passwords, must be securely encrypted before storage. The system must use PHP’s password_hash() with the PASSWORD_BCRYPT algorithm, ensuring passwords can never be read in plain text.

Session Security: Session identifiers used for user authentication must be securely managed via PHP standard configurations (session_start()). Sessions must automatically regenerate upon login using session_regenerate_id(true) to prevent session fixation attacks.

2. Performance & Scalability Requirements
Page Response Time: The application pages (especially the main dashboard marketplace feed) must load within 2 to 3 seconds under normal network conditions.

Query Optimization: Database read queries running on the skills and users tables must execute in under 500 milliseconds. Database indexes should be implemented on heavily searched relational foreign keys like user_id and filtered columns like neighborhood and category.

Concurrent Users: The system, running on a standard local Apache server bundle (XAMPP/WAMP), must be optimized to handle a benchmark baseline of at least 50 to 100 concurrent local neighborhood users navigating the marketplace or messaging simultaneously without performance degradation.

3. Usability & Accessibility Requirements
Responsive Web Design: The user interface layout must be fully responsive, scaling seamlessly across mobile phones, tablets, laptops, and desktop screens using a CSS framework like Bootstrap 5 or Tailwind CSS.

Intuitive Navigation: The dashboard navigation scheme must remain consistent across pages, allowing users to return to the marketplace feed or access their private message boards in no more than 2 clicks.

4. Availability & Reliability Requirements
System Availability: The platform web interface should maintain an operational uptime targets of 99% during standard community engagement hours, ensuring neighbors can coordinate real-time meetups without unexpected service dropouts.

5. Maintainability & Portability Requirements
Code Modularization: The PHP backend must separate architectural concerns clearly. Core utility operations, such as the database connection.

Cross-Browser Compatibility: The presentation web layer must look and function consistently across all modern web.