Featured Projects

Network Design

The network was divided into separate VLANs to improve organization and reduce unnecessary broadcast traffic.

Implementation

Inter-VLAN routing was implemented on the Cisco 3560 multilayer switch using switched virtual interfaces. DHCP pools were configured for each VLAN, allowing clients to automatically receive network addresses.

The Cisco 1941 router was configured to perform NAT/PAT for internal networks. A separate edge router provided the external network connection.

Network Security

An extended ACL was implemented on the multilayer switch to control communication between departments. Wireless users in VLAN 40 were restricted from accessing the Finance VLAN while other permitted communication remained available.

access-list 100 deny ip
192.168.40.0 0.0.0.255
192.168.20.0 0.0.0.255

access-list 100 permit ip any any

interface vlan 40
 ip access-group 100 in

Network Services

• DHCP addressing for all VLANs
• Inter-VLAN communication
• NAT/PAT for external connectivity
• Wireless connectivity
• Network printer access
• Access control using ACLs

Testing & Results

Connectivity and network services were tested using Cisco IOS verification commands and end-device connectivity tests.

Challenges & Troubleshooting

During implementation, several configuration issues were encountered, including subnet mask mismatches, routing problems, wireless adapter configuration, and ACL connectivity restrictions.

These issues were resolved using commands such as show ip route, show ip interface brief, show interfaces trunk, show access-lists, and ping.

Office Requirements

The proposed network was designed for a 20-user accounting office. Each workstation was provided with a dedicated network outlet, with additional capacity considered for shared resources and future expansion.

• 20 user workstations
• Centralized network rack
• Cat6 horizontal cabling
• Patch panel termination
• Organized cable routing
• Provision for future expansion

Office Floor Plan

A floor plan was developed to identify workstation locations, network outlets, cable routes, and the central network rack. Cable paths were planned to provide organized routing while minimizing unnecessary cable runs.

Office Floor Plan

Cable Routing Design

Cable routes were planned from the central network rack to individual workstation outlets. Cable tray routes and drops were represented on the design to provide a clear physical installation path.

Cable Routing Diagram

Network Rack Layout

A rack layout was created to organize the network equipment and support proper cable management. Components were positioned logically to simplify installation, maintenance, and troubleshooting.

Network Rack Layout

Patch Panel Layout

The patch panel was organized according to the workstation cable labels. Each horizontal cable run terminates at the patch panel, allowing the network connections to be managed centrally.

Patch Panel Layout

Cable Labeling Scheme

A standardized cable labeling scheme was created to make cable identification easier during installation, troubleshooting, and future maintenance.

Example:

PP01-01  →  Administration PC 01
PP01-02  →  Administration PC 02
PP01-03  →  Finance PC 01
PP01-04  →  Finance PC 02

The labels were designed to provide a clear relationship between the patch panel port and the corresponding workstation outlet.

Bill of Materials

A Bill of Materials was prepared to identify the materials required for the structured cabling installation.

Documentation

The project was documented using structured diagrams and technical documentation. The final documentation provides an installation reference and makes it easier for technicians to understand the physical network infrastructure.

• Floor plan
• Cable routing diagram
• Rack layout
• Patch panel layout
• Cable labeling schedule
• Bill of Materials

Skills Demonstrated

Authentication & User Access

The application includes user registration and authentication functionality. Users register with unique email addresses and access protected areas through session-based authentication.

• User registration
• Secure password hashing
• Session-based authentication
• Authenticated dashboard

Dashboard

The authenticated dashboard provides an overview of recent user activity. It displays information such as medication counts, health records, upcoming reminders, mood check-ins, and a daily health score.

AfyaSmart Dashboard

Health & Wellness Modules

AfyaSmart combines several health and wellness modules into one application.

Medication Management

The medication module provides CRUD functionality for managing medication information. Users can create, view, update, and delete medication entries while the system provides reminder notifications when medication becomes due.

Medication Management

Mental Wellness & Insights

The mental wellness module allows users to record mood check-ins and receive supportive responses. Mood data is stored and presented through trend and mix charts to help users understand their activity over time.

Mental Wellness & Insights

Symptoms Checker

The symptoms module allows users to record selected symptoms, severity levels, and temperature information. The system provides general guidance and red-flag warnings while storing the checks for use in the health timeline and daily health score.

Diet & Wellness Planner

The Diet & Wellness module provides personalized wellness guidance based on the user's selections. It forms part of AfyaSmart's broader approach to supporting healthy daily routines and wellness planning.

Diet & Wellness Planner

Health Timeline

A unified health timeline brings together information from different modules, including health records, medications, mood check-ins, and symptoms.

Unified Health Timeline

Data Visualization

Chart.js was used to present health insights visually, including mood trends and the seven-day health score trend.

Emergency Support

The emergency module provides an SOS action, browser geolocation support, an embedded map, nearby healthcare facility lookup, and external directions links. Leaflet and OpenStreetMap are used for the map functionality.

Emergency Support & Map Integration

AI Health Assistant

AfyaSmart includes a guided AI health assistant that provides general routines and suggested next steps. The assistant includes safety messaging and is designed as a non-diagnostic support feature.

Backend & Database

PHP was used for backend processing while MySQL or MariaDB provides the application's database layer. Backend handlers and database connectivity are organized within the backend directory.

Frontend
HTML + Bootstrap 5
Custom CSS + JavaScript

Backend
PHP

Database
MySQL / MariaDB

Additional Libraries
Chart.js
Leaflet + OpenStreetMap

Project Structure

dashboard.php
login.html
register.html
medication.php
mental-health.php
diet.php
health-records.php
symptoms.php
timeline.php
assistant.php
emergency.html

backend/
js/
css/
afya_smart.sql

Future Improvements

Planned improvements include role-based access, email and SMS reminder delivery, deeper analytics, exportable reports, optional external AI integration with safety controls, and API-based emergency service integration.

Skills Demonstrated