1. Introduction
1.1 Overview
The Web-Based Final Year Project (FYP) Supervision Management System is designed to streamline and automate the traditional project assignment process for final-year students.
This platform enables teachers to upload projects under various categories such as:
- Web-based
- Mobile-based
- Artificial Intelligence
- IoT-based
- And more
Students can browse and select projects according to their interest. The project coordinator can then approve or reject student selections.
This system eliminates manual inefficiencies, brings transparency to the project allocation process, and ensures better coordination between teachers, students, and coordinators.
1.2 Problem Definition
1.2.1 Existing System
The current system relies on manual communication and document sharing. Teachers upload their project descriptions, and students arrange meetings to confirm availability. Coordinators manually verify whether a project has been assigned before approving it.
Disadvantages
- Difficult to determine which projects have already been assigned.
- Increased chances of project duplication and potential conflict among students.
- Difficult for users to efficiently manage project allocations.
1.2.2 Proposed Solution
A Web-Based FYP Portal will solve these problems by providing a centralized digital system for project management. Teachers can upload projects, students can view and select them, and coordinators can approve or reject selections.
Advantages
- Provides a centralized system for teachers to upload and manage projects.
- The portal maintains a complete database of all projects and their current status.
- Reduces duplication by marking previously assigned projects.
- Easily accessible for teachers, students, and coordinators from anywhere.
1.3 Scope
The system will be a web-based portal designed to assist teachers, coordinators, and students in managing final-year projects.
Scope Includes
- Teachers can upload and manage their projects.
- Students can view and select available projects.
- Coordinators can approve or reject student selections.
1.4 Objectives
The main objective of this system is to create a centralized digital environment for smooth communication and project allocation among teachers, students, and coordinators.
System Objectives
- Students can register, log in, and view projects.
- Students can select projects and view approval status.
- Students can view teacher profiles.
- Teachers can upload, update, delete, and view projects.
- Teachers can approve or decline student project requests.
- Teachers can forward project selection requests to coordinators.
- Coordinators can view and approve/decline project requests.
- System checks for duplicate projects previously uploaded.
- System alerts the teacher if the same project was done in the past.
- Students receive notifications once their project is approved.
1.5 Project Organization
1.5.1 Software Process Model
The Incremental Software Development Model is chosen for this project because:
- The system is built in small modules that are easy to test and analyze.
- Functionalities can be added gradually over time.
- Early prototypes help validate system requirements.
1.5.2 Roles and Responsibilities
Roles
- Developer: Responsible for building the system.
- Supervisor: Provides guidance, helps refine system requirements.
Responsibilities
- Understanding system workflow.
- Gathering requirements and necessary resources.
- Developing a fully functional web-based system.
1.6 Project Management Plan
1.6.1 Project Description and Understanding
This phase focuses on understanding system requirements, defining objectives, and creating an overall system description.
1.6.2 Software Project Management Plan Details
Description
The first step involves identifying all functional and non-functional requirements. These requirements form the basis for system modeling and implementation.
Deliverables and Milestones
- Understanding system requirements
- Defining the system scope
- Requirements gathering
- UML Diagrams
- Use Case documentation
- System Implementation
- Testing
Dependencies
Development depends on clear system requirements. Any unclear or incomplete requirement leads to functional mismatches during development.
Risks and Contingencies
- Poor understanding of requirements
- Incomplete system analysis
- These risks may result in a system that fails to meet user expectations.
2. System Requirements
2.1 Specific Requirements
This section explains the functional behavior of the system and identifies user types.
System Users
- Project Coordinator
- Teacher
- Student
2.2 Functional Requirements
Student Requirements
- Register on the system
- Login to the system
- View projects uploaded by teachers
- Select a project
- View project approval status
Teacher Requirements
- Login to the system
- Upload, update, view projects
- View project selection requests
- Forward or decline project selection requests
Coordinator Requirements
- Login to the system
- View uploaded projects
- Approve or disapprove project selection requests
System Requirements
- Check for project duplication
- Prevent teachers from uploading already-done projects
- Maintain an archive of all past projects
4. System Implementation
4.1 Introduction
This document provides the details of system implementation and user manual.
The system is implemented using the MERN Stack.
4.2 Languages / Technologies Used
- ReactJS (Frontend)
- Node.js & Express (Backend)
- MongoDB (Database)
- JavaScript (Core Language)
4.3 Tools Used
- Visual Studio Code (VS Code)
- Git / GitHub
- Postman (API Testing)
- Browser DevTools
4.4 User Interface Design
The user interface defines how users interact with the system through screens and navigation flow.
The design focuses on:
- Minimal steps to perform tasks
- Clean and responsive interface
- Consistency across all user roles
Screens include:
- Login Page
- Student Dashboard
- Teacher Dashboard
- Coordinator Panel
- Project Listing Page
- Project Upload Page
- Approval Management Screen
