Name	GitHub
Aly Elaswad	alyelaswad
Mazin Bersy	mazinbersy
Omar Ganna	omarganna

Github Repo: https://github.com/alyelaswad/Package-Tracker

1. The Proposal

Elevator Pitch:

Every day, packages get lost, stolen, dropped, overheated, or tampered with, and nobody knows until it's too late. Existing consumer trackers only report location. They tell you where your package is, but not what happened to it.

Smart Package Tracker is a self-contained embedded device that attaches to any package and monitors it across two dimensions simultaneously: location and physical condition. It tracks GPS coordinates in real time, detects shock events from drops or rough handling, monitors temperature and humidity, and fires a tamper alert the moment the package is opened without authorization.

All of this streams wirelessly over WiFi using HTTP POST requests to a custom backend server, where it is visualized in real time with no physical connection required. The device runs on a battery and is fully untethered during operation.

Project Objectives & Scope:

Minimum Viable Product (MVP)

• GPS coordinates transmitted to Backend Server every 5 seconds
• Shock/drop detection with event logging and GPS location of incident
• Tamper alert triggered when package is opened (IR sensor)
• Temperature and humidity monitoring with threshold alerts
• Real-time dashboard displaying location and alerts

Stretch Goals

• Geofencing: alert when tracker leaves a predefined GPS boundary
• Trip report: distance, max temperature, tamper attempts.
• Dead reckoning fallback: uses accelerometer to estimate location when GPS is lost.

2. System Architecture

2.1 High-Level Block Diagram:

Subsystem Breakdown:

A brief text description of how the major modules (e.g., motor control, user interface, wireless communication) interact.

3. Hardware Design

Component Selection:

Schematics & Wiring:

Circuit diagrams, pinout tables, and breadboard layouts.

Bill of Materials (BOM):

A table listing component names, part numbers, quantities, costs, and links to datasheets.

Power Budget:

Calculations ensuring your power supply can handle the peak current draw of all components combined.

4. Software Implementation

4.1 Software Architecture:

Description of the firmware design (e.g., Bare-metal Superloop, Interrupt-driven, or RTOS).

4.2 Flowcharts & State Machines:

Visual diagrams mapping out the core logic, state transitions, and interrupt service routines (ISRs).

4.3 Key Algorithms:

Explanations of any complex logic used (e.g., PID control loops, digital filtering, sensor fusion).

4.4 Development Environment:

Compilers, IDEs, and toolchains used (e.g., Keil, PlatformIO, STM32CubeIDE).

5. Testing, Validation & Debugging

5.1 Unit Testing:

How individual hardware components and software functions were tested in isolation.

5.2 Integration Testing:

How the system was tested as a whole.

5.3 Challenges & Solutions:

A log of major bugs, hardware failures, or design flaws you encountered, and the engineering steps you took to solve them.

6. Results & Demonstration

6.1 Final Prototype:

High-quality photos of the completed build.

6.2 Video Demonstration:

A link to a short video showing the system working in real-time under various conditions.

6.3 Performance Metrics:

Data showing how well the project met its initial objectives (e.g., "Response time was measured at 12ms, well within our 50ms goal").

7. Project Management

7.1 Division of Labor:

A clear breakdown of who worked on what (professors usually require this to grade individual contributions).

7.2 Timeline

Date	Milestone	Status	Date of Completion
Apr 14, 2026	Team formation finalized and submitted	✅ Completed	Apr 14, 2026
Apr 15, 2026	Proposal presentation and requirements validation	🔄 In progress	—
Apr 20, 2026	Wiki deployment with system architecture and proposal documentation	⏳ Pending	—
Apr 22–25	Development and unit testing of sensor drivers (GPS, IMU, DHT, IR)	⏳ Pending	—
Apr 26–28	Implementation of WiFi communication pipeline and POST request integration(ESP8266)	⏳ Pending	—
Apr 29, 2026	Progress demo: GPS acquisition + data transmission over WiFi	⏳ Pending	—
May 1–5	Full system integration (sensor fusion, event handling, data pipeline) and system-level testing	⏳ Pending	—
May 6, 2026	Integration update and technical documentation on wiki	⏳ Pending	—
May 8–12	System refinement: edge-case handling, robustness testing, and demo validation	⏳ Pending	—
May 13, 2026	Final system demo and technical presentation	⏳ Pending	—

8. Appendices & References

8.1 Source Code Repository:

Link to your GitHub/GitLab repo.

8.2 References:

Links to datasheets, tutorials, academic papers, and course materials used during development.