Download as doc, pdf, or txt
Download as doc, pdf, or txt
You are on page 1of 11

[Student Mentoring System]

Project Team

Full Name of Roll Program Contact Email Address


Student Numbers Number
Muhammad Zargham 9720 BSSE 03067210126 zarghamkhalique83@gmail.com
Umair Akbar 10176 BSSE 03462537821 Umairakbar4329@gmail.com
Muhammad Woyal 10829 BSSE 03326626670 muhammadwoyal176176@gmail.com

[Supervisor/ Co-Supervisor]

[Mam Shehla Afzal / Dr Sohail Jabbar]


(Lecturer/ Associate Professor)

Riphah College of Computing

RIPHAH INTERNATIONAL UNIVERSITY


FAISALABAD CAMPUS
[Student Mentoring System]

Change Record

Author(s) Version Date Notes Supervisor’s Signature


1.0 Original Draft
Changes Based on
Feedback From
Supervisor
Changes Based on
Feedback From Faculty
Added Project Plan
Changes Based on
Feedback From
Supervisor
Project Proposal

Project Title: Student Mentoring System

Introduction:
Some final year university students don’t know anything, they don't have any
skills and any direction. So we will provide An artificial intelligence-based web
application that allows final-year students to find ideas for their final-year project,
as well as learn relevant tools and techniques and learn what they can do and what
skills they have.

Existing System/ Description of the Current Situation:


There is no other project of its kind that provides complete mentorship to students
Problem Statement:
Some university’s final year students worry about their final year project,
unfortunately, they don’t have any skills, any direction or don’t know what to do
and how to do

Proposed Solution:
An artificial intelligence-based web application that helps final-year
students come up with project ideas, learn relevant tools and techniques,
and figure out what they can do and what talents they can have.
Tools That will use in the project:
1) React.Js
To Design the Front-end of the website
2) Node.Js
For Backend Development
3) MongoDB
For data storage
4) NLP
Natural language processing for analyzing the best content
5) TensorFlow. A Machine Machine framework for implementing algorithms
Scope of the Project:
Our Web-based project has 3 main modules and 6 sub-modules which are defined are as
follow

1) Find Project
In which the student puts the title of his project and a list of when and what has
been done before on this title and what more work is possible in it will display.
1.1) A database where FYP documentation store
It is the sub-Module of Find project when a final year student puts the
title of their project and the documentation of relevant project display
from website database that we will insert manually.
1.2) Fetch research papers and display:
2nd Sub-Module of find project, when a final year student puts the title of
their project our website take the title as input and finds the best relevant
research paper from different sources such as IEEEXplore, google scholar
etc
2) Find Course:
Students must master the necessary abilities for project implementation
after selecting a project and defining its scope. As a result, our website
analyses the relevant tutorials and then displays the best tutorial/course to
the student.
2.1) Display Best Course/Tutorial:
The website takes the given name as an input and searches from
different sources such as YouTube, Coursera, and Udacity to find the best
course by analyzing different factors such as highest views, highly
positive reviews, or high course sales, and then displays to the student.
2.2) Display Seminar/workshop relevant to the tutorial:
The website takes the given name as an input and searches from
different sources such as YouTube, Coursera, and Udacity to find the best
course by analyzing different factors such as highest views, highly
positive reviews, or high course sales, and then displays to the student
3) Freelancing Platform:
After selecting project ideas, defining their scope as well as learning
relevant skills (after the final year project) mostly students worry about
their career. Our website provides opportunities for the developer to start
their career as a freelancer and earn bread and butter.
3.1) As a Developer:
The developer must first register on the website as a developer before
applying for a profile setup. The developer will be presented with a list of
specialities from which to choose. The speciality is chosen by the
developer. An exam relevant to the niche will be conducted to validate the
developer's credibility.
3.2) As a Client:
The project will be posted initially by the client. The project will then be
bid on by several developers. After communicating with the developer
whose bid the client prefers, the client will award the job to the developer.
Developers must complete the project according to the client's
specifications within the specified time frame and submit it. The client
then pays the developer's fees and provides feedback on their work.
List of Faculty Proposed Changes
Project Title

Supervisor’s Signature: ______________

Proposed Change Proposed By Supervisor’s Decision


Name of Faculty Approved/Disapproved and/or
Member(s) who Comments
proposed this
change
Project Plan

Work Breakdown Structure: A work breakdown structure (WBS) is deliverable


based decomposition of project scope. The WBS includes 100% of the work defined by
the project scope and captures all deliverables – internal, external, interim – in terms of
the work to be completed, including project management.

Sample WBS:

1. Project Management
1.1. Work Breakdown Structure (WBS)
1.2. Roles & Responsibility Matrix
1.3. Change Control System
2. Reports / Documentation
2.1. Final Documentation Introduction
2.2. Literature / Markey Survey
2.3. Requirements Analysis
2.4. System Design
2.5. Implementation
2.6. Testing & Performance Evaluation
2.7. Conclusion & Outlook
2.8. End User Documentation
2.9. Application Administration Documentation
2.10. System Administrator Documentation
3. System
3.1. Development Environment
3.1.1. IDE
3.1.2. Version Control
3.1.3. Server
3.1.4. Database
3.2. Presentation Layer
3.2.1. Deliverable 1
3.2.2. Deliverable 2
3.2.3. ...
3.3. Business Logic Layer
3.3.1. Deliverable 1
3.3.2. Deliverable 2
3.3.3. ...
3.4. Data Management Layer
3.4.1. Deliverable 1
3.4.2. Deliverable 2
3.4.3. ...
3.5. Physical Layer
3.5.1. Deliverable 1
3.5.2. Deliverable 2
3.5.3. ...
Roles & Responsibility Matrix:
The purpose of roles & responsibility matrix is to identify who will do what.

WBS # WBS Deliverable Activity # Activity to Complete the Duration Responsible Team
Deliverable (# of Days) Member(s) & Role(s)
Approval

Project Supervisor
Comments_______________________________________________________________
________________________________________________________________________
________________________________________________________________________
________________________________________________________________________
Name:______________________________
Date:_______________________________ Signature:__________________________

Project Coordinator
Comments_______________________________________________________________
________________________________________________________________________
________________________________________________________________________
________________________________________________________________________
________________________________________________________________________
Name:______________________________
Date:_______________________________ Signature:__________________________

You might also like