🧭 KU Connect Project Plan

Authors: Phantawat Lueangsiriwattana, Sunthorn Kompita, Kristawan Jaroenrad, Nichapat Sirinantanakul, Katharina Viik

Revised: 17 Aug 2025

📘 1. Statement of Work

KU Connect is a specialized job platform connecting Kasetsart University’s SKE/CPE students with verified employers and will run on Windows, Linux, or macOS environments.

The system is built using:

• Backend: Node.js (Express.js) + Prisma
• Frontend: React + TypeScript + Vite
• Database: PostgreSQL (production), SQLite (dev/test)
• Auth: JWT + Google OAuth

Supported user roles:

• 🎓 Students
• 🏢 Employers
• 🛡️ Admins
• 📊 Professors

The goal is to deliver a secure, reliable, and scalable job-matching system with clear role-based workflows.

🗓️ Development Timeline

Period	Major Work & Deliverables
Aug 7–24, 2025	Project Foundation & Planning• Stakeholder meetings and requirement gathering• Define system architecture and technology stack• Set up development environment and Git workflow• Conduct risk assessment and assign team roles
Aug 25–Sep 7, 2025	Core System Foundation• Database schema design and initial migration setup• UI/UX wireframes and prototyping in Figma• Security framework setup and environment configuration
Sep 8–Oct 19, 2025	Feature Development & Integration• Student module implementation (Weeks 6–7)• Employer module implementation (Weeks 8–9)• Admin and Professor dashboards (Week 10)• Integration between frontend and backend APIs
Oct 20–Nov 10, 2025	Finalization & Handover Phase• Submit final project documentation package• Customer review and revision feedback round• Create presentation materials and summary reports• Preparation of final documentation and deliverables for customer review
Nov 11–Nov 20, 2025	Testing, Deployment & Documentation• Full system integration and automated testing• User acceptance testing with KU stakeholders• Production deployment and performance optimization• Official handover and closure meeting with stakeholders

🚀 Milestones

Week	Key Milestones
Week 2	✅ Stakeholder meetings completed and requirements finalized.✅ System architecture designed and tech stack selected.✅ Team roles and project plan confirmed.
Week 5	✅ Core backend and frontend structure implemented.✅ Database schema and security framework operational.✅ UI/UX prototypes approved.
Week 6	✅ Student profile creation & editing functional.✅ Employer registration and verification active.✅ Company profile management implemented.
Week 7	✅ Employer job posting interface completed.✅ Job management dashboard functional.✅ Job display page available for students.
Week 8	✅ Student job application and browsing system ready.✅ Search and filtering features completed.✅ Saved opportunities (bookmark) feature added.
Week 9	✅ Authentication system integrated (students & employers).✅ Employer notifications active.✅ Candidate review page for employers completed.
Week 10	✅ Admin verification dashboard ready.✅ Admin moderation tools for posts and users working.✅ Professor analytics dashboard implemented.✅ System monitoring and logging setup.
Week 12	✅ Full system testing completed.✅ User acceptance testing with KU stakeholders.✅ Deployment finalized.✅ User guides and technical documentation delivered.✅ Platform officially launched.

🧩 Architecture & Technology Overview

Tech Stack

• Backend: Node.js (Express.js)
• Frontend: React 19 + TypeScript + Vite
• Database: PostgreSQL (prod), SQLite (dev/test)
• ORM: Prisma
• Auth: JWT + Google OAuth (HttpOnly encrypted cookies)
• Architecture Pattern: Layered modular monolith
• Storage: Local filesystem (development), S3 planned

Architecture Principles

• 🔒 Security-first design (bcrypt, RBAC, validation, rate limiting)
• 🧱 Clear separation of concerns
• 🧩 Modular feature structure
• 📦 Stateless backend API
• 🛠️ Strong typing using TypeScript

🧩 Code Quality & Maintenance

• Follow team Coding Guidelines strictly.
• Maintain >80% test coverage across backend and frontend.
• Implement proper error handling for all user-facing and system operations.
• Keep code self-documented with consistent naming and structure.

🔄 Development Process

Agile Methodology

Each iteration included:

• Planning and user stories
• Backend + frontend implementation
• Integration testing
• Documentation updates in Wiki
• Iteration review + retrospective

Documented in:

• Iteration 1–7 Plans
• Iteration 1–6 Meetings

Git Workflow

• main → stable
• dev → iteration integration
• feature/* → feature branches

Pull Request requirements:

• Clear title & description
• Completed checklist
• Reviewer approval
• Tests passing

🧪 Testing & Quality Strategy

Testing

• Unit tests → service logic
• Integration tests → API endpoints via SQLite
• Manual testing → all role flows
• Regression testing → pre-release
• User Acceptance Testing (UAT) → KU stakeholders

Definition of Done

A feature is DONE when:

• Code implemented
• Tests written & passing
• No critical bugs
• Wiki documentation updated
• Demoed in iteration review

⚠️ Risk Management

Key Risks

Risk	Potential Impact
Development or deployment delays	Extended timeline, missed deadlines
KU OAuth integration issues	Login or verification delays
Changing stakeholder requirements	Rework and timeline extension
Team unavailability or miscommunication	Task dependencies delayed
Security vulnerabilities or data breaches	Loss of trust, system downtime

Mitigation Strategies

• Weekly progress meetings for early issue detection.
• Code reviews and automated testing pipelines.
• Maintain clear documentation and backups.
• Use agile sprints with built-in buffer time.
• Regular stakeholder check-ins for alignment.

Contingency Plans

• Re-prioritize features if deadlines tighten.
• Redistribute tasks among developers.
• Perform emergency security patching and audits if needed.

👥 Roles & Responsibilities

Team Member	Role	Responsibilities
Phantawat Lueangsiriwattana	Backend Developer	Core API development, database integration
Kristawan Jaroenrad	Backend Developer & DevOps	Database management, CI/CD pipeline setup, authentication system
Sunthorn Kompita	Frontend Developer	UI implementation, responsive design, user interaction flows
Nichapat Sirinantanakul	Frontend Developer	Component design, styling, accessibility, testing and bug fixes
Katharina Viik	Backend Developer	API development, documentation

📦 Final Deliverables

• Live KU Connect deployment
• Backend + frontend repositories
• Unit + integration test suites
• Complete documentation (Wiki):
  • Project Vision & Scope
  • Requirements & Use Cases
  • ER Diagram & Domain Diagram
  • Software Architecture Document
  • API Endpoints
  • Coding / PR / Commit Guidelines
  • Iteration Plans & Meeting Notes
  • Test Plan + Test Results
• Final presentation slides
• Demo materials

✅ Summary

KU Connect delivers a secure, role-based, and user-friendly hiring platform that connects Kasetsart University’s SKE/CPE students with verified employers through streamlined job posting, application, and review workflows. Built with a modern Node.js + Express + Prisma + React + Vite + PostgreSQL architecture, the system ensures scalability, maintainability, and strong security using JWT authentication, RBAC, and validated data models.

The project was developed over a structured 12-week timeline, following Agile iterations with clearly defined milestones, documentation, testing standards, and risk mitigation practices. The final release includes all core features for students, employers, admins, and professors, supported by comprehensive documentation and a fully deployed platform ready for real-world use.