0% found this document useful (0 votes)
33 views4 pages

TTU Hackathon 2025 Project Guidelines

The TTU / ITSU Hackathon 2025 focuses on two main software team projects: a Digitized Academic Document Request & Delivery System and a Location-Based Student Field Attendance System. Each project requires teams to submit various technical documents including system architecture diagrams, use case diagrams, and UI wireframes before coding begins. Bonus points are available for additional features such as audit logs and role-based access control.

Uploaded by

langoshivburley
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
33 views4 pages

TTU Hackathon 2025 Project Guidelines

The TTU / ITSU Hackathon 2025 focuses on two main software team projects: a Digitized Academic Document Request & Delivery System and a Location-Based Student Field Attendance System. Each project requires teams to submit various technical documents including system architecture diagrams, use case diagrams, and UI wireframes before coding begins. Bonus points are available for additional features such as audit logs and role-based access control.

Uploaded by

langoshivburley
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd

TTU / ITSU Hackathon 2025

July 11, 2025 | 9:00 AM


Software Team Projects
Each team must select and work on a single project.

1
PROJECT 1
Project Title:
“Digitized Academic Document Request & Delivery System for TTU”
Problem Statement:
TTU currently handles most academic document requests manually resulting in delays, errors, and
administrative overload. Design and develop a secure, end-to-end web-based system to allow
students and alumni to remotely request transcripts, attestations, and certificates. The system must
allow soft or hard copy delivery, verify identity using Ghana Card, support mobile money
payments, and notify users via SMS.

What Teams Must Submit (Before Any Coding):


1. System Architecture Diagram
• Clearly label components: frontend, backend, database, file storage, SMS gateway, and
payment systems.
• Show how requests flow from user to admin to delivery.
2. Use Case Diagrams or User Flow
• Define all user roles (e.g., Student, Admin).
• Show how users interact with the system step-by-step.
3. Entity Relationship Diagram (ERD)
• Define all necessary database tables/entities
• Show relationships (1-to-many, many-to-many).
4. UI Wireframes or Mockups
• Build static designs using tools like Figma, Adobe XD, or even hand-drawn sketches.
• Include pages like:
o Login (with OTP)
o Ghana Card upload
o Request Form
o Payment Screen
o Request Status
o Admin Dashboard
5. Technology Stack Justification
• List tools/languages
• Justify your choices based on scalability, local tech support, and ease of integration.
Design:
Teams can then proceed to:
• Implementation
• Testing (Unit + Integration)
• Deployment

Bonus Points:
• Adding audit logs or request history
• Including role-based access control
• Providing a mini demo of the SMS or payment feature with test keys

2
PROJECT 2
Project Title:
FieldLink: Location-Based Student Field Attendance System
Core Goals:
• Ensure students physically report to the assigned job site every day.
• Use live GPS to mark attendance only if the student is within the approved location
radius.
• Require supervisor approval of the student’s presence.
• Allow departments to monitor attendance reports in real-time.
Core Features:
Student App Portal:
• Login via student ID + mobile number (OTP-based)
• Upload Ghana Card (for identity validation)
• View assigned job site location (preloaded by admin)
• "Mark Attendance" button only activates if within GPS radius
• Take selfie (optional) as part of check-in verification
• View attendance history
Live Location Locking Logic:
• Each student has a unique daily geo-location lock.
• Uses mobile GPS and checks if user is within X meters (e.g., 50m–100m) of job site.
• No attendance allowed outside location.
• Use reverse geocoding to store readable address.
Supervisor Verification Portal:
• Supervisor logs in to see the list of students assigned to them
• Can see real-time attendance logs
• Manually approve (or flag) student attendance
• Can leave feedback or incident notes
University Department Dashboard:
• View all students under field work by program/department
• See attendance charts, export reports
• Filter by student, supervisor, day, or location
• Trigger follow-ups or warnings for low attendance
Security & Integrity Features:
• Geo-fencing to restrict attendance marking outside jobsite
• Timestamped logs for every attendance
• Supervisor dual-approval system
• Daily change prevention (student can't spoof GPS or change location daily)
• Possible photo check-in or QR from supervisor as extra step
Extra Features (Advanced/Optional):
• Offline check-in cache with delayed sync (useful in rural areas)
• Automated reminders via SMS every morning
• Photo + GPS cross-validation using image metadata
• Attendance leaderboard for motivational engagement
Deliverables for Hackathon Participants:
1. System Architecture Diagram
2. ERD (User, Attendance, Location, Supervisor, Department)

3
3. Wireframes (Student, Supervisor, Admin Views)
4. Working Web App
5. Testing Demonstration (GPS spoof prevention, logs)

You might also like