KU-Connect Functional and Non-Functional Requirements

Functional Requirements

1. User Access and Verification

1.1. Only people with a KU account can access the system.
1.2. Four distinct user groups: Students (job seekers), Employers (job hirers), Administrators, and Professors.
1.3. Students and Employers must verify their identities through multi-layer verification to access the platform.
1.4. Administrators approve user registrations before account activation.

2. Job Application Eligibility

2.1. Faculty members cannot apply for jobs.
2.2. Only students from SKE and CPE (both current and graduated) can apply for jobs.
2.3. Only verified, KU-affiliated employers can post job opportunities.

3. Student Features

3.1. Students can create comprehensive profiles with personal information, and academic record.
3.2. Students can upload transcripts and portfolio documents to their profiles.
3.3. Students can search and filter job opportunities by field, salary, and work type.
3.4. Students can save job postings to their personal bookmark list for later review.
3.5. Students can apply for jobs with one click using their pre-uploaded transcript and profile information. 3.6. Students receive confirmation when applications are submitted and basic status updates.

4. Employer Features

4.1. Employers can register and get verified through KU affiliation validation.
4.2. Employers can create detailed job postings with requirement specifications.
4.3. Employers can manage their company profile with basic details and single contact point.
4.4. Employers receive instant notifications when students apply for their jobs.
4.5. Employers can review student profiles and applications through the platform.
4.6. Employers can manage their job postings (create, edit, delete).

5. Administrative Features

5.1. Administrative users can approve or reject student registration requests.
5.2. Administrative users can approve or reject employer registration requests.
5.3. Administrative users can approve or reject job posting submissions before they go live.
5.4. Administrative users can monitor platform activity and track usage metrics.
5.5. Administrative users can implement spam prevention and content moderation.

6. Professor Features

6.1. Professors can view dashboard with registered student information.
6.2. Professors can access job market insights and industry trends.
6.3. Professors can use data to align education curriculum with industry needs.

7. Platform Scope and Limitations

7.1. Platform serves exclusively SKE and CPE students (no other academic programs).
7.2. Web-based application only (no native mobile apps in current scope).
7.3. Services restricted to Kasetsart University community only.
7.4. No payment processing or subscription features in current scope.
7.5. No integration with external job boards or social media platforms.

8. Additional Considerations

8.1. System design should support focused, targeted user groups per employer feedback.
8.2. Platform concept similar to university-specific job hunting groups.
8.3. Monetization features planned for future phases, not current scope.

---

Non-Functional Requirements

1. Security

1.1. Ensure verified access only for KU-affiliated users through secure authentication integration.
1.2. Implement enterprise-grade security measures including data encryption and secure authentication.
1.3. Protect against bots, spam, and unauthorized access attempts.
1.4. Maintain privacy compliance with student personal information accessible only to verified employers.

2. Performance and Scalability

2.1. System must respond to user actions within 3 seconds under normal load conditions.
2.2. Support at least 100 concurrent users during peak usage periods.
2.3. Maintain 99.5% system uptime for reliable platform access.
2.4. Fast notification delivery to employers when new applications arrive.
2.5. Scalable architecture to support growing user base over time.

3. Usability

3.1. User interface must be intuitive and require minimal user training.
3.2. Responsive web design that works well on both desktop and mobile devices.
3.3. Minimal friction for user registration and job application processes.
3.4. Meet basic web accessibility standards (WCAG 2.1 compliance).

4. Reliability

4.1. System must reliably confirm application submissions to students.
4.2. Ensure consistent uptime during peak application and recruitment periods.
4.3. Secure integration with KU authentication systems without service disruption.
4.4. Zero major security incidents during operation.

5. Compatibility

5.1. Platform must work on major web browsers (Chrome, Firefox, Safari, Edge).
5.2. Accessible from common operating systems (Windows, macOS, iOS, Android).
5.3. Seamless integration with Kasetsart University's existing authentication infrastructure.

6. Maintainability and Future Growth

6.1. Clean, well-documented codebase for easy maintenance and updates.
6.2. Modular architecture that allows for easy addition of future features.
6.3. Support for future expansion to other university departments if needed.
6.4. Foundation ready for future monetization features and advanced analytics.

7. Data Management

7.1. Secure storage and backup of user profiles, job postings, and application data.
7.2. Efficient data retrieval for job search and filtering operations.
7.3. Proper data retention and deletion policies in compliance with university standards.