A
MINI PROJECT REPORT ON
“Student Mentorship System”
SUBMITTED BY
“Roshani Rasal”
UNDER THE GUIDANCE OF
“Prof. Nishant Pachpor”
IN PARTIAL FULFILMENT OF
Award of the Degree of
MASTER OF COMPUTER APPLICATION
(Semester-I)
SUBMITTED TO
SAVITRIBAI PHULE PUNE UNIVERSITY
THROUGH
YASHASWI EDUCATION SOCIETY’S
INTERNATIONAL INSTITUTE OF MANAGEMENT SCIENCE
CHINCHWAD, PUNE
ACADEMIC YEAR 2021-2022
1
DECLARATION
I, Roshani Dilip Rasal, student of International Institute of Management Science, Chinchwad,
Pune, hereby declare that this Mini Project report entitled Student Mentorship System is a
bonafide record of work done by me for the partial fulfilment of the requirement for the degree
of Master of Computer Application (M.C.A) through Savitribai Phule Pune University.
I, hereby, declare that I have adequately referenced the original sources and this is my original
work. I also declare that I have adhered to all principles of academic honesty and integrity and
have not misrepresented or fabricated or falsified any idea/data/fact/source in my submission. I
understand that any violation of the above will be cause for disciplinary action by the Institute
and can also evoke penal action from the sources which have thus not been properly cited or
from whom proper permission has not been taken when needed.
Roshani Rasal
IIMS, Chinchwad, Pune.
2
ACKNOWLEDGEMENT
I am deeply indebted towards my project guide Prof. Nishant Pachpor who gave me the
opportunity and was instrumental in providing me all the knowledge and insight to do the
research. It is their inspiration that has kept me motivated all along my project and the
discipline and integrity they had expected from a mini project that made me to learn the
real live projects.
I would like to express my earnest gratitude and thanks to Dr. Shivaji Mundhe (Director
of IIMS) and my project guide Name of the Guide for providing me all the knowledge
and skills, resources, technical support, guidance as required to achieve this Endeavour.
I thank my all faculty members and friends for their support and blessings. The report is
the result of contribution of numerous people to mention individually.
I also thank all respondent who have given their value time, views and authentic
information for this mini project. I thank each and everybody who has contributed
directly or indirectly to the successful completion of this project.
Roshani Rasal
IIMS, Chinchwad, Pune.
3
INSTITUTE CERTIFICATE
4
INDEX
Sr. No.
1
Topic
Page No.
Introduction
1.1
Introduction
1.2
Existing system
1.3
Limitations of the System
1.4
Need of System
1.5
Hardware Specifications
1.6
Software Specifications
1.7
Business Objectives
1.8
System Objectives
1.9
Scope of Program
1.10
Objectives of the Project
1.11
Features of new System
2
Software Requirement Specification
3
Design
3.1
Entity Relationship Diagram
3.2
Use Case Diagram
3.3
Class Diagram
3.4
Sequence Diagram for Student Mentorship System
3.5
Activity Diagram for Student Mentorship System
3.6
Component Diagram
3.7
Deployment Diagram
5
4
Database Design
7
Data Dictionary
8
Bibliography and References
LIST OF TABLES
Table no.
Table Name
1
Student
2
Mentee Records
3
Drive
4
Student Attendance
5
Counsellor Remark
6
Admin
7
Meeting Record
Page no.
6
LIST OF FIGURES
Graph no.
GraphName
1
Login
2
Admin Dashboard
3
Student Dashboard
4
Drive Details
5
Attendance
6
Student Academic Performance
7
Meeting Details
Page no.
7
1 Introduction
1.1 Introduction
Student Mentorship System is software which is helpful for students as well as
the university’s authorities. In the current system all the activities are done
manually. It is very time consuming and costly. The objective of Student
Mentorship System is to allow the administrator of any organization to edit and
add details of a student and allows the student to keep up to date his profile.
It’ll also facilitate keeping all the records of students, such as their id, name,
mailing address, phone number, DOB, Attendance, Overall marks and Meeting
and drive attended by the students etc. Based on past marks of the student get
report of specific criteria. Where Student will be segregated as weak student ,
brilliant student.
Student Mentorship System is intended to be a stand-alone product and should
not depend on the availability of another website. The system will also have an
administrator who has full-fledged rights with regards to performing all actions
related to control and management of the website.
Student Mentorship System is software which is helpful for students as well as
the university’s authorities. In the current system all the activities are done
manually. It is very time consuming and costly. The objective of Student
Mentorship System is to allow the administrator of any organization to edit and
add details of a student and allows the student to keep up to date his profile.
It’ll also facilitate keeping all the records of students, such as their id, name,
mailing address, phone number, DOB, Attendance, Overall marks and Meeting
and drive attended by the students etc.
8
1.2 Existing system
The first problem is that there are loads of hard copied documents being
generated. This brings us to the age-old discussion of keeping information
in the form databases versus keeping the same on sheets of paper. Keeping
the information in the form of hard-copied documents leads to the
following problems.
i. Lack of space – It becomes a problem in itself to find space to keep the
sheets of paper being generated as a result of the ongoing discussion. The
documents being generated are too important to be ill-treated.
ii. Filing poses a problem – Filing the documents categorically is a time
consuming and tedious exercise.
iii. Filtering is not easy – It becomes hard to filter relevant documents for the
irrelevant ones if the count of the same crosses a certain manageable
number.
iv. Reviewing becomes time-consuming – All the process done manually at
the centers and all the records are maintained on the papers. So the
maintenance of the record is very difficult in the departments and as well
as it’s very difficult for the workers to check the record. The Existing
system is paper based, time consuming, monotonous, less flexible and
provides a very hectic working schedule. The chance of loss of records is
high and also record searching is difficult. Maintenance of the system is
also very difficult and takes lot of time.
v. File lost- When computerized system is not implemented file is always
lost because of human environment. due to some human error, there may be
a loss of records.
9
1.3
Limitations of the System
1) Time Constraint.
2) Insufficient information from students as they were being careful not to
reveal confidential information
1.4
Need of System
The use of student Mentorship system is to store and manage students’ data
at a single platform online. This is done to save manual paperwork and
automate data-related tasks, thereby preventing manual errors.
Student information, organized and saved once, gets synced across all
necessary departments like a attendance, classroom management, etc.
Admin has access to relevant student data, and updates and multiple
backups further help store the data safely.
All the information is present in a centralized location, making it easy to
search for necessary information. The student database management
system also has reporting features to analyze students’ academic
performance, attendance, and other parameters.
Student management system helps teachers make informed decisions to
create every student’s learning curve after communicating with parents.
10
1.5
Hardware Specifications
HARDWARE SPECIFICATION
Client side
RAM
512 MB
Hard Disk
40 GB
Processor
Intel Core Duo or higher
Server Side
RAM
1.6
2 GB or higher
Software Specifications
Client side
Operating System
Web Browser
Windows 7& above
IE 6 & above
Google Chrome 6 & above
Server Side
Operating system
• Web-Technology:
Windows 7 & above
JAVA
11
• Front-End:
CSS,JAVASCRIPT, HTML ,
BOOTSTRAP
• Back-End:
MySQL
1.7
Business Objectives
The main objective of the Student Management System is to manage the
details of Profiles, Courses , achievement, Attendance and marks.
To reduce the paper work and to eliminate manual processes and to save
significant staff time.
It helps evaluate the success of various programs, Drives and meeting
conducted.
Our core values support and guide our leadership in establishing the
strategic direction of the Company. Sound judgment shall be exercised in
the service of our reputation as a business leader, employer of choice, and
good corporate citizen. Our employees and representatives are expected to
conduct their business in accordance with these values and with our
Standards of Business Ethics and Conduct (“The Standards”). Student
Mentorship System reputation is based on the personal integrity of each of
its employees and those with whom we do business. We strive to be
compliant with laws, regulations and policies; we endeavor to conduct
ourselves in a manner beyond reproach. Actions speak louder than words.
12
1.8
System Objectives
The objective of Student Mentorship System is to allow the administrator of
any organization to edit and add details of a student and allows the student
to keep up to date his profile. It’ll also facilitate keeping all the records of
students, such as their id, name, mailing address, phone number, DOB,
Attendance, Overall marks and Meeting and drive attended by the students
etc. Based on past marks of the student get report of specific criteria. Where
Student will be segregated as weak student , brilliant student.
The project is about to handle all the information of the student regarding
achievement, attendance drive conducted and examination. Also, it manages
resources which were managed and handled by manpower previously. The
main purpose of the project is to integrate distinct sections of the
organization into consistent manner so that complex functions can be
handled smoothly by any technical or non-technical persons.
1.9
Scope of Program
Student Mentorship system will store all the details of the students including
their background information, educational qualifications, personal details and all
the information related to their resume. without a student Mentorship System,
managing and maintaining the details of the student is a tedious job for any
organization. Student will also able be to download this information.
University’s facilities are not limited to basic operations, but rather, the
administrators have been hoping for an advanced system. This model is proposed
for the full, user-friendly, fast, and effective management of various tasks. These
tasks can cover registering new students, managing the attendance, managing
13
student meeting derive records, so many of the important features required to
make the university administration department successful.
1.10 Objectives of the Project
• The objective of Student Mentorship System is to allow the administrator of
any organization to edit and add details of a student and allows the student
to keep up to date his profile.
•
It’ll also facilitate keeping all the records of students, such as their id, name,
mailing address, phone number, DOB, Attendance, Overall marks and
Meeting and drive attended by the students etc. Based on past marks of the
student get report of specific criteria. Where Student will be segregated as
weak student , brilliant student.
• The project is about to handle all the information of the student regarding
achievement, attendance drive conducted and examination. Also, it manages
resources which were managed and handled by manpower previously. The
main purpose of the project is to integrate distinct sections of the
organization into consistent manner so that complex functions can be
handled smoothly by any technical or non-technical persons.
1.11 Features of new System
• Our project is only a humble venture to satisfy the needs of our organization.
Several user-friendly coding have also adopted.
• This project shall prove to be satisfying all the requirements of the
organization.
• Student Information Management System can be used by education institutes
14
to maintain the records of students easily. Achieving this objective is difficult
using a manual system as the information is scattered, can be redundant and
collecting relevant information may be very time consuming. All these
problems are solved using this project.
15
2
Software Requirement Specification
2.1 Product Perspective
Student Mentorship System is intended to be a stand-alone product and should
not depend on the availability of another website. The system will also have
an administrator who has full-fledged rights with regards to performing all
actions related to control and management of the website.
The various system tools that have been used in developing both the front end,
back end and other tools of the project are being discussed in this section.
2.2 Product Functions
The primary function of the Student Mentorship System web server is
essentially to save the whole system information in sequentially into database
server. The administration department will have access to whole system
environment and that can be modified as per their needs. The architecture of
whole system is made easy that any person can login to system and use the
functions. The system database is only accessible to admin and admin can
only modify the changes.
There are two different users who will be using this product:
• Administrator who can view and edit the details of any students.
• Students who can view their details as well as they can edit their details.
The features that are available to the Administrator are:
• An Administrator can login into the system and perform any of the available
operations.
• Can access all the details of the student.
16
• Can access all the details of the student.
• Can add student attendance , marks, meeting and drive details.
The features that are available to the student are:
•
Student can login into the system and can perform any of the available
options.
•
Can view his/her personal details.
•
Can edit his/her personal details
•
Can fill mentor mentee form.
•
Can view feedback.
2.3 User Classes and Characteristics
There are mainly two kinds of users for the product.
•
Administrator
•
Student
2.4 Operating Environment
•
Front End
-
Using Java web technologies.
•
Back End
-
MySQL as DataBase Server and XAMP as middleware
interface.
•
GUI Interface -
The product can run on chrome and Internet explorer.
2.5 Design and Implementation Constraints
•
Every user must be comfortable using computer.
•
All operations are in English so user must have basic knowledge of English.
2.6 User Documentation
17
•
Synopsis
•
Project Presentation
2.7 Assumptions and Dependencies
•
Administrator is created in the system already.
•
Roles and tasks are predefined.
2.8 Other Nonfunctional Requirements
Performance Requirements
The proposed system that we are going to develop will be used as the Chief
performance system for providing help to the organization in managing the
whole database of the student studying in the organization. Therefore, it is
expected that the database would perform functionally all the requirements that
are specified.
Safety Requirements
The database may get crashed at any certain time due to virus or operating system
failure. Therefore, it is required to take the database backup.
Security Requirements
We are going to develop a secured database. There are different categories
of users namely Administrator ,Student who will be viewing either all or some
specific information form the database. Depending upon the category of user the
access rights are decided. It means if the user is an administrator, then he can be
18
able to modify the data, append etc. All other users only have the rights to retrieve
the information about database.
• Software Quality Attributes
Performance
The Student Management System shall be built upon the web development
technique and
put on the web server online. The system and the server must be capable of
handling the realtime error functionality occurs by the defined users. In addition, the system must
be safety
critical. All failures reported by the server side must be handled instantaneously to
allow for user
and system safet
Performance:
The Student Mentorship System shall be built upon the web development
technique and put on the web server online. The system and the server must be
capable of handling the real- time error functionality occurs by the defined users.
In addition, the system must be safety critical. All failures reported by the server
side must be handled instantaneously to allow for user and system safety.
Reliability
The system is safety critical. If it moves out of normal operation mode, the
requirement to drop or down the server and fix it as soon as possible and open it
again. This emergency behavior shall not occur without reason.
19
Availability
When in normal operating conditions, request by a user for an online system
shall be handled within 1 second. Immediate feedback of the systems activities
shall be communicated to the user by clearing the system and giving space n speed
to their hospitality
Security
There shall be a strong security mechanism should be place in the server side
of the system to keep unwanted users to hack or damage the system. However, all
users of the system give and store the details of privacy related to personal
information and many other. However, our system can be accessed online so we
need very secured system as far as security is concerned.
Maintainability
There shall be design documents describing maintenance of the software and
database used to save the user details as well as the daily updated and modification
done in system. There shall be an access on the control system by the admin to
maintained it properly at the front end as well as at back end.
Portability
There is portability requirement as far as our system is concern because it is
an online as well as offline (local server based) system so we can access it from
anywhere through the internet connection. And we have to maintain the copy of
stored data into our database
20
Business Rules
Our core values support and guide our leadership in establishing the strategic
direction of the Company. Sound judgment shall be exercised in the service of our
reputation as a business leader, employer of choice, and good corporate citizen.
Our employees and representatives are expected to conduct their business in
accordance with these values and with our Standards of Business Ethics and
Conduct (“The Standards”). Student Mentorship System reputation is based on the
personal integrity of each of its employees and those with whom we do business.
We strive to be compliant with laws, regulations and policies; we endeavor to
conduct ourselves in a manner beyond reproach. Actions speak louder than words.
Other Requirements
A degraded mode of operation should be possible in which each system can
operate independently of central scheduling. The software shall have failure and
error recognition codes acting as a safety net, thus keeping the software from
performing any major catastrophic functions.
21
3
Design
3.1
Entity Relationship Diagram
The Entity-Relationship (ER) model was originally proposed by Peter in 1976
[Chen76] as a way to unify the network and relational database views. Simply
stated the ER model is a conceptual data model that views the real world as entities
and relationships. A basic component of the model is the Entity-Relationship
diagram which is used to visually represent data objects. Since Chen wrote his
paper the model has been extended and today it is commonly used for database
design For the database designer, the utility of the ER model is:
• it maps well to the relational model. The constructs used in the ER model
can easily be transformed into relational tables.
• it is simple and easy to understand with a minimum of training. Therefore,
the model can be used by the database designer to communicate the design
to the end user.
• In addition, the model can be used as a design plan by the database
developer to implement a data model in a specific database management
software.
22
3.2 Use Case Diagram
Use case diagrams model behavior within a system and helps the developers
understand of what the user require. The stick man represents what’s
called an actor.
Use case diagram can be useful for getting an overall view of the system and
clarifying who can do and more importantly what they can’t do.
Use case diagram consists of use cases and actors and shows the interaction
between the use case and actors.
•
The purpose is to show the interactions between the use case and actor.
•
To represent the system requirements from user’s perspective.
•
An actor could be the end-user of the system or an external system.
23
3.3 Class Diagram
24
3.4 Sequence Diagram for Student Mentorship System
• Sequence diagram and collaboration diagram are called Interaction
Diagrams.
• An interaction diagram shows an interaction, consisting of set of objects and
their relationship including the messages that may be dispatched among
them.
• A sequence diagram is an introduction that empathizes the time ordering of
messages. Graphically a sequence diagram is a table that shows objects
arranged along the X-axis and messages ordered in increasing time along the
Y-axis
25
3.5 Activity Diagram for Student Mentorship System
26
3.6 Component Diagram
3.7 Deployment Diagram
27
4
Database Design
Student:
Field Name
Data Type
ID
int
Roll No
varchar
Constraint
Description
Primary Key
ID of user
Roll
no
of
student
Password
varchar
Password
mentees_record:
Field Name
Data Type Constraint
Description
Id
int
ID of user
fname
Varchar
First name of user
mname
Varchar
Middle name of user
lname
Varchar
Last name of user
division
Varchar
division
Primary key
28
DOB
date
Date of birth
Blood_group
varchar
Blood group
wh_mobile_no
int
WhatsApp contact
number of student
Linked_in-id
Varchar
LinkedIn profile ID
strength
varchar
Strength of student
weakness
Varchar
Weakness of student
address
Varchar
Permanent Address
Parent_name
Varchar
Name of parent
Parents_email
Varchar
Email id of parents
Mentor_name
Varchar
Name of mentor
S_id
Varchar
Student id
Admin
Field Name
Data Type
Constraint
Description
id
int
Primary key
Serial no
name
varchar
Name of admin
email
varchar
Email id of admin
password
varchar
password
type
varchar
Admin login type
29
Meeting_record :
Field Name
Data Type
Constraint
Description
id
int
Primary key
Serial no of meeting
record
date
varchar
Date of meeting
name
varchar
Meeting name
remark
varchar
Remark of meeting
s_id
int
Student Id
attend
varchar
Attended remark
Drive
Field Name
Data Type
Constraint
Description
id
int
Primary key
Serial no of
drive
conducted
semester
varchar
Semester details
date
varchar
Date of drive
d_name
varchar
Drive name
30
Student_attendance_table
Counsellor remark
31
5
Screen Shots
➢ Login
➢ Admin Dashboard
32
➢ Student Details:
Drive Details:
33
➢ Attendance
➢ Meeting details:
34
➢ Student login Attendance
➢ Academic Performance
35
6 Bibliography and References
➢
N.D. Oye, S. Marlena, and N.A.
Iahad, ‘‘Challenges of E-learning in
Nigerian University Education Based on the Experience of Developed
Countries’’. International Journal of Managing Information Technology.
➢
M. Landry, ‘‘There Are Good and Bad Ways To Set Up An Appointment
System’’. CMA Journal Vol.
➢
http://www.pcworld.com/article/230943/crossplatform.html
➢
http://www.pcworld.com/article/230943/crossplatform.html
➢
http://www.jguru.com
➢
Introduction to visual studio Microsoft.com/Wikipedia.com
➢
Introduction to mysql https://www.tutorialsweb.com
➢
homepage Design https://meeraacademy.com/
➢
pictures/images Google Image Search
➢
Sql Database WampServer
36