Project Development Plan - AvengerDisassemble/KU-connect GitHub Wiki

🧭 KU Connect Project Plan

Authors: Phantawat Lueangsiriwattana, Sunthorn Kompita, Kristawan Jaroenrad, Nichapat Sirinantanakul, Katharina Viik Revised: 16 Aug 2025

πŸ“Œ Statement of Work

KU Connect is a specialized job platform designed to connect Kasetsart University’s Software and Knowledge Engineering (SKE) and Computer Engineering (CPE) students with verified employers.

The application will be developed using Node.js (Express.js) for the backend and Next.js for the frontend, and will run on Windows, Linux, or macOS environments.

πŸ—“οΈ 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.

🧩 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.

⚠️ 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

βœ… Summary

KU Connect will deliver a secure, scalable, and user-friendly job platform bridging KU’s SKE/CPE community with verified employers.
The project follows a structured 12-week timeline with defined milestones, testing standards, and risk management to ensure a successful and stable launch.