TABLE OF CONTENTS

1. INTRODUCTION ...................................................................................................................... 3
1.1 Purpose: ...................................................................................................................................... 3
1.2 Scope : ........................................................................................................................................ 4
2. SYSTEM ANALYSIS ................................................................................................................. 5
2.1 Existing System: Student Management System:- ................................................................... 5
2.2 Proposed System - Student Management System ................................................................... 5
2.3 Feasibility Analysis - Student Management System ............................................................... 6
2.4 Technical Feasibility .............................................................................................................. 6
2.5 Economical Feasibility ........................................................................................................... 6
3. SYSTEM ARCHITECTURE ..................................................................................................... 8
3.1 Admin Module:- .................................................................................................................... 8
3.2 Faculty Module:- ................................................................................................................... 8
3.3 Student Module:-................................................................................................................... 8
3.4 Services Diagram of Modules. ............................................................................................... 9
3.5 Data Flow Diagram:- ........................................................................................................... 11
3.6 ER-DIAGRAM ................................................................................................................... 14
4. OVERALL DESCRIPTION..................................................................................................... 17
4.1 Product Perspective : ........................................................................................................... 17
4.2 Product Functions : ............................................................................................................. 17
4.3 User Classes and Characteristics : ........................................................................................ 18
4.4 Operating Environment : ..................................................................................................... 18
4.5 Constraints : ........................................................................................................................ 18
4.6 Use Case Model : ................................................................................................................ 19
5. TECHNOLOGY OVERVIEW................................................................................................. 27
5.1 PHP .................................................................................................................................... 27
5.2 MySQL ............................................................................................................................... 27
5.3 Apache ................................................................................................................................ 28
5.4 XAMPP .............................................................................................................................. 28
5.4.1 Obtaining and Installing XAMPP ................................................................................ 28
5.4.2 Creating a Database and Inserting Data ........................................................................ 29
6. PROJECT DESCRIPTION ...................................................................................................... 31
6.1 Introduction ........................................................................................................................ 31

1
 6.2 Description Of Root Directory Contents .............................................................................. 32
6.3 Description of Database tables:............................................................................................ 34
7. SCREENSHOTS ............................................................................ Error! Bookmark not defined.
7.1 HOME PAGE.................................................................................................................................. 40
7.2 STUDENT/USER LOGIN .................................................................................................................. 41
7.3 ADMIN DASHBOARD ..................................................................................................................... 42
7.4 ADD STUDENT............................................................................................................................... 43

2
 1. INTRODUCTION
Student Management System is software which is helpful for students as well as the school
authorities. In the current system all the activities are done manually. It is very time consuming
and costly. Our Student Management System deals with the various activities related to the
students.

There are mainly 3 modules in this software

 Administrator Module

 Faculty Module

 Student Module.

In the Software we can register as a faculty as well as a student for every student the
authentication code and the roll no is provided by the head of the department faculty and for
the registration of a faculty the Registration ID and the authentication code is provided by the
administrator the institute.

In this project an admin can manage the faculty and take decision about the students like
deletion of any student admin is authorized to create the token for the registration of the faculty
as same as a faculty is authorized for creating token for the registration of a student.

1.1 Purpose:

The objective of Student Management System is to allow the administrator of any

organization to edit and find out the personal 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 etc. So all the information
about an student will be available in a few seconds.
Overall, it’ll make Student Management System an easier job for the administrator and
the student of any organization.
The main purpose of this SRS document is to illustrate the requirements of the project

3
Student information System and is intended to help any organization to maintain and
manage its student’s personal data.

1.2 Scope :

Without a Student Management System, managing and maintaining the details of the
student is a tedious job for any organization.
Student Information 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 .

4
 2. SYSTEM ANALYSIS
2.1 Existing System: Student Management System:-

System Analysis is a detailed study of the various operations performed by a system and their
relationships within and outside of the system. Here the key question is- what all problems
exist in the present system? What must be done to solve the problem? Analysis begins when a
user or manager begins a study of the program using existing system.

During analysis, data collected on the various files, decision points and transactions
handled by the present system. The commonly used tools in the system are Data Flow
Diagram, interviews, etc. Training, experience and common sense are required for collection of
relevant information needed to develop the system. The success of the system depends largely
on how clearly the problem is defined, thoroughly investigated and properly carried out
through the choice of solution. A good analysis model should provide not only the mechanisms
of problem understanding but also the frame work of the solution. Thus it should be studied
thoroughly by collecting data about the system. Then the proposed system should be analyzed
thoroughly in accordance with the needs.

System analysis can be categorized into four parts.

 System planning and initial investigation

 Information Gathering
 Applying analysis tools for structured analysis
 Feasibility study
 Cost/ Benefit analysis.

In the current system we need to keep a number of records related to the student and want to
enter the details of the student and the marks manually. In this system only the teacher or the
school authority views the mark of the student and they want to enter the details of the student.
This is time consuming and has much cost.

2.2 Proposed System - Student Management System

In our proposed system we have the provision for adding the details of the students
by themselves. So the overhead of the school authorities and the teachers is become less.

5
Another advantage of the system is that it is very easy to edit the details of the student and
delete a student when it found unnecessary. The marks of the student are added in the database
and so students can also view the marks whenever they want.

Our proposed system has several advantages

 User friendly interface

 Fast access to database
 Less error
 More Storage Capacity
 Search facility
 Look and Feel Environment
 Quick transaction

All the manual difficulties in managing the student details in a school or college
have been rectified by implementing computerization.

2.3 Feasibility Analysis - Student Management System

Whatever we think need not be feasible .It is wise to think about the feasibility of any
problem we undertake. Feasibility is the study of impact, which happens in the
organization by the development of a system. The impact can be either positive or
negative. When the positives nominate the negatives, then the system is considered
feasible. Here the feasibility study can be performed in two ways such as technical
feasibility and Economical Feasibility.

2.3.1 Technical Feasibility:

We can strongly says that it is technically feasible, since there will not be much
difficulty in getting required resources for the development and maintaining the
system as well. All the resources needed for the development of the software as well
as the maintenance of the same is available in the organization here we are utilizing
the resources which are available already.

2.3.2 Economical Feasibility

Development of this application is highly economically feasible .The
organization needed not spend much money for the development of the system
already available. The only thing is to be done is making an environment for the

6
development with an effective supervision. If we are doing so, we can attain the
maximum usability of the corresponding resources .Even after the development, the
organization will not be in condition to invest more in the organization .Therefore,
the system is economically feasible

7
 3. SYSTEM ARCHITECTURE
In this chapter, modules of the website are described. It includes software interfaces,
hardware interfaces, software requirements, hardware requirements etc.

This project is made under an online project which is works as a website also it also use
for the advertisement of the institute it also include the information pages of the
institute like vision, about us, history, student management system page, syllabus for
the students, admission information and a notice board for the student of institute and as
well as a guest user.

3.1 Admin Module:-

This is the first and the base module of the project by this module a admin is
provided to the project to manage the faculty and student module. An admin have
the authority to add and remove the faculty, Add and delete the Notification, view
progress and attendance status of the students, update academic calendar etc.
3.2 Faculty Module:-

This module is for the faculty members of the institute all faculty are get a unique
token no and a pin for registration by the administrator of the institute by using the
registration id and pin the faculty will get registration page after filling that form the
faculty will get registered in the institute database and they choose a password for login
to their profile. After login the faculty have authorized to services for the student like
submit attendance of students, submit marks of their subjects, make result, add
notification for a particular department, send mail to individual or a group of student,
allot assignments and project to the students.

3.3 Student Module:-

As like faculty registration same the student will get a roll no and a pin to registered
themselves. After enter the roll no and pin students are redirect to the registration
page after submitting their general details student will get a roll no and a password
to login their profile. After login the student is able to view and update their
updatable information like mobile no, email, address and profile pictures but

8
 students are restricted to update their key details like Name, Father Name, Date of
birth in such a case in student is able to write a online application to their head of
department for approving to update these details. Students are able to view other
information related to their class like notification of their departments, own
attendance in individual subjects, previous test marks, and send message to other
students.

3.4 Services Diagram of Modules.

ADMIN MODULE

Add/Update Add/Delete Delete View Students Allot Subjects

Data to Faculty
Notification Faculty Student

FACULTY MODULE

Add Dept. Add Submit Submit Allot

Notification Students Attendance Result Data Assignments

9
 STUDENT MODULE

View Update Contact View Message to View/Submit

Details Assigments
Attendance Marksheet Classmates

10
 3.5 Data Flow Diagram:-

Registration Form

Student Student_registration_
system

Confirmed Letter

Figure 4 ( O Level DFD)

11
 Administrator

Request to
Database
Request to Login
view
Request to edit

Admin Module

Student module process

Request to edit Faculty module

Request to
Request to
view
Login

Login granted Request to

Request to edit
Login
Faculty

Faculty

Request to
view

12
Student 1.0
Verify _availabilty
Reg_form

2.0
Student_registration_
system Course_info

Course
Confirmed_letter
Course_enrolled

Stud
Up ent_
dat info
e_i
3.0
Student_registration_ nfo
system

Stud_database

13
 3.6 ER-DIAGRAM
3.6.1 INTRODUCTION:

An entity–relationship model (ER model) describes inter-related things of interest in a

specific domain of knowledge. An ER model is composed of entity types (which
classify the things of interest) and specifies relationships that can exist between
instances of those entity types. In software engineering an ER model is commonly
formed to represent things that a business needs to remember in order to perform
business processes. Consequently, the ER model becomes an abstract data model that
defines a data or information structure that can be implemented in a database, typically
a relational database.

Entity–relationship modeling was developed for database design by Peter Chen and
published in a 1976 paper. However, variants of the idea existed previously, some ER
modelers show super and subtype entities connected by generalization-specialization
relationships, and an ER model can be used also in the specification of domain-specific
ontology.

An ER model is typically implemented as a database. In a simple relational database

implementation, each row of a table represents one instance of an entity type, and each
field in a table represents an attribute type. In a relational database a relationship
between entities is implemented by storing the primary key of one entity as a pointer or
"foreign key" in the table of another entity There is a tradition for ER/data models to be
built at two or three levels of abstraction. Note that the conceptual-logical-physical
hierarchy below is used in other kinds of specification, and is different from the three
schema approach to software engineering.

14
15
 User_id
Admin_name
Password

Admin

Manages
Faculty_name
Qualification

Faculty
Contact_No Faculty_ID

Email Profile_pic

Manages
Manages
Stud_name Roll_No
Submit
Attendance
Profile_pic
Password
Student
Date_of_birth Course_ID

Have Course_ID

Subject_name Stud_roll
Course_name Course

Temp_roll_no
Subject Duration

Attendace_date Have
Attendace_Status

16
 4. OVERALL DESCRIPTION
4.1 Product Perspective :

The website Student Information Management System is aimed towards recording a

considerable number of student records and needs online assistance for managing
records of students. Website should be user-friendly, ‘quick to learn’ and reliable
website for the above purpose.

Student Information System is intended to be a stand-alone product and should

not depend on the availability of other 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.

4.2 Product Functions :

There are three different users who will be using this product:
 Administrator who can view and edit the details of any students &
faculty.
 Faculty who can view and edit the details of 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 enable/disable student.
 Can add & remove front page notifications.
 Can add & remove the faculty as well as student.
 Can edit student information to the database. Can make search for a
specific student.
 Add & Update Academic calendar.

17
  Allocate the subjects to the faculty.
 Can access all the details of the student.

The features that are available to the faculty are:-

 Can submit attendance of the students.

 Can upload his/her image.
 Can Submit students exam or Test marks.
 Can Approve their leave application
 Can Add & Remove Departmental Notifications.
 Update self Profile Details

The features that are available to the Students are:-

 Can view their profile.

 View their attendance in individual subjects.
 View their test or exam marks.
 Update their basic contact details.
 Send or view the message to the classmates.
 View the departmental notification which they are belongs to.
 Submit Leave application or other application.

4.3 User Classes and Characteristics :

There are mainly three kinds of users for the product.
The users include:
 Administrator
 Faculty
 Student

4.4 Operating Environment :

The product can run on any browser (preferable to use Chrome browser).

4.5 Constraints :

18
 Every user must be comfortable using computer.

All operations are in English so user must have basic knowledge of English.

4.6 Use case model :

19
 Use Case Model

1. Administrator: Responsible for managing faculty records.

 Login into the website

 Add / Remove Notification
 Add / Remove faculty
 Allocate Subjects to faculty.
 Update Academic Calendar
 View progress of the students.
 Search student details
o Display student details
o Enable/Disable student

2. Faculty : Responsible for managing Students records.

 Submit attendance of the students.
 Submit Marks of the students.
 Add/Remove departmental notifications.
 Approve leave applications of the students.
 view & update profile of self.

3. Student: Has the access rights to view and edit their personal details.

 Login into the website .

 Display student details
 Edit their details .
 View their attendance .
 View their results .
 Message to classmates.
 View departmental notifications.
 Upload their images.
 Upload their resumes.

20
  Assumptions & dependencies

· Administrator is created in the system already.

· Roles and tasks are predefined.

 Specific Requirements :

Use Case Reports

1Administrator: Responsible for managing student details.

Use-case: Login into the website

Goal in context: Gain access to the website

Brief Description: This use case is used when the administrator wants to access the
website to enable/disable/update the personal details of the student.

Preconditions: The Administrator must be logged onto the website in order for this
use case to begin.

Basic Flow:

The Website prompts the administrator for the user name and password. The
Administrator enters the user name and password. The Website verifies the password
and sets the user’s authorization. The Administrator is given access to the Website to
perform his tasks.

Alternative Flow:

The administrator enters invalid username and password then he will not be allowed to
enter the website.

Post conditions: The website state is unchanged by this use case.

21
 Use Case Report- Login into the website

Use Case : Display student details

Goal in context: View the details of a student

Brief Description: This use case is used when the administrator wants to view
the facilitate the services to the faculty and view the status of the students.

Preconditions: The Administrator must be logged into the system in order for
this use case to begin The details of the student must pre-exist in the database
The student id must be entered correctly.

Basic Flow:

The Administrator logs onto the System.

 Notification Service :-

o Admin can add the notification by the help of notification add

page in this page the admin just add the title of the notification
and the upload the related pdf or document file of that
notification.

o This notification is visible on the homepage.

o These notifications are accessible by all the user who visited on

the website.

o Admin can easily delete the notification.

 Faculty management :-

o In this section an admin can manages the faculty .

22
 o After login admin can generate token for the faculty. In tis token
the admin allot a registration id and the pin related with the
faculty name.

o After generation of the token page is redirect to the admin page.

 Update Academic Calendar:-

o In this section admin can update the academic calendar he can

add any holiday and the other events to the calendar which is
accessible by the students and the faculty of the institute.

Post conditions:

The token is generated for the faculty signup and the updated calneder is
visible to the students as well

as the faculty members.

Case Diagrams.

Login fails

Login to website

Add/remove Notification

Databse updated

23
. Faculty : Responsible for managing student details.

Use-case: Login into the website

Goal in context: Gain access to the website

Brief Description: This use case is used when the faculty wants to access the website
to enable/disable/update the personal details of the student.

Preconditions: The faculty must be logged onto the website in order for this use case
to begin.

Basic Flow:

The Website prompts the faculty for the user name and password. The faculty enters
the user name and password. The Website verifies the password and sets the user’s
authorization. The faculty is given access to the Website to perform his tasks.

Alternative Flow:

The faculty enters invalid username and password then he will not be allowed to enter
the website.

Post conditions: The website state is unchanged by this use case.

24
 Use Case Report- Login into the website

Use Case : Display Faculty services page

Goal in context: View the details of a student

Brief Description: This use case is used when the faculty wants to view the facilitate
the services to the faculty and view the status of the students.

Preconditions: The faculty must be logged into the system in order for this use case
to begin The details of the student must pre-exist in the database The student id must
be entered correctly.

Basic Flow:

The faculty logs onto the System.

 Submit Attendance :-

o Faculty can submit the attendance for every student in subject who is
allotted by the administrator.

o For submit attendance faclty has to navigate the submit attendance

page.

o There is two way available to submit the attendance.

 Submit attendance in list view.

 Quick attendance submit mode.

o To submit attendance in list view faculty have to select the class and
then the subject.

25
 o Then page is navigated to submit attendance page in this page the list
of the student is visible which are belongings to selected subject.

o To save a student as a present just tick the checkbox and to absent the
student just uncheck the checkbox.

 Submit marks:

o To submit the marks for student faculty has to navigate the page by
choosing submit marks option of menu from the faculty page.

o There are two way to submit marks of students.

 Submit marks to each student in list mode.

 Submit marks by uploading the excel file.

 Add/Remove Notification.

o Faculty can add the notification by the help of notification add page in
this page the faculty just add the title of the notification and the upload
the related pdf or document file of that notification.

o This notification is visible on the homepage.

o These notifications are accessible by all the user who visited on the
website.

o Faculty can easily delete the notification.

 Student management :-

o In this section an admin can manages the Student.

o After login admin can generate token for the student. In tis token the
faculty allot a Roll No and the pin related with the student name.

o After generation of the token page is redirect to the faculty page.

Post conditions:

The token is generated by the faculty is used by students to signup the students. And
the databse of the marks table and attendance table is updated.

26
 5. TECHNOLOGY OVERVIEW

The technology selected for implementing Student Information Management System is

PHP/MYSQL.Apache is used as the HTTP server.The development was done in a
‘windows’ environment using adobe dreamweaver CS5.

5.1 PHP

PHP is a general-purpose scripting language that is especially suited to server-side web

development where PHP generally runs on a web server.PHP code is embedded into the
HTML source document.Any PHP code in a requested file is executed by the PHP runtime,
usually to create dynamic web page content.It can also be used for command-line scripting
and client-side GUI applications. PHP can be deployed on many web servers and operating
systems, and can be used with many relational database management systems (RDBMS). It is
available free of charge, and the PHP Group provides the complete source code for users to
build, customize and extend for their own use.

5.2 MySQL

[1]
MySQL is a relational database management system (RDBMS) that runs as a server
providing multi-user access to a number of databases. MySQL is a popular choice of database
for use in web applications and is an open source product. The process of setting up a
MySQL database varies from host to host, however we will end up with a database name, a
user name and a password. Before using our

27
database, we must create a table. A table is a section of the database for storing related
information. In a table we will set up the different fields which will be used in that table.
Creating a table in phpMyAdmin is simple, we just type the name, select the number of fields
and click the ‘go’ button. we will then be taken to a setup screen where you must create the
fields for the database.Another way of creating databases and tables in phpMyAdmin is by
executing simple SQL statements.We have used this method in order to create our database
and tables.

5.3 Apache

The Apache HTTP Server is a web server software notable for playing a key role in the initial
growth of the World Wide Web. In 2009 it became the first web server software to surpass
the 100 million web site milestone. Apache is developed and maintained by an open
community of developers under the auspices of the Apache Software Foundation. Since April
1996 Apache has been the most popular HTTP server software in use. As of November 2010
Apache served over 59.36% of all websites and over 66.56% of the first one million busiest
websites.

5.4 XAMPP

XAMPP is a small and light Apache distribution containing the most common web
development technologies in a single package. Its contents, small size, and portability make it
the ideal tool for students developing and testing applications in PHP and MySQL. XAMPP
is available as a free download in two specific packages: full and lite. While the full package
download provides a wide array of development tools, XAMPP Lite contains the necessary
technologies that meet the Ontario Skills Competition standards.The light version is a small
package containing Apache HTTP Server, PHP, MySQL, phpMyAdmin, Openssl, and
SQLite.

5.4.1 Obtaining and Installing XAMPP

As previously mentioned, XAMPP is a free package available for download and use for
various web development tasks. All XAMPP packages and add-ons are

28
distributed through the Apache Friends website at the address: http://www.apachefriends.org/.
Once on the website, navigate and find the Windows version of XAMPP and download the self-
extracting ZIP archive. After downloading the archive, run and extract its contents into the root
path of a hard disk or USB drive. For example, the extract path for a local Windows installation
would simply be C:\. If extracted properly we will notice a new xampp directory in the root of
your installation disk. In order to test that everything has been installed correctly, first start the
Apache HTTP Server by navigating to the xampp directory and clicking on the apache_start.bat
batch file.
Next we will test if the server is running correctly by opening an internet browser and typing
http://localhost/ into the address bar. If configured correctly, we will be presented with a screen
similar to that of the one below.

Figure 1 (XAMPP Splash Screenshot)

In order to stop all Apache processes we do not close the running terminal application, but
instead run another batch file in the xampplite directory called apache_stop.bat.

5.4.2 Creating a Database and Inserting Data

29
Now that we have run and tested Apache and PHP, the next step is running MySQL and creating
a database and table which will hold information to be used by our website. In order to start
MySQL, navigate to the xampp directory and run the mysql_start.bat batch file.The XAMPP
package contains an application called phpMyAdmin which allows developers to administer and
maintain MySQL databases.We will be using phpMyAdmin to create a database and table, and
enter test data. Before testing phpMyAdmin, make sure that both Apache and MySQL are
running by opening their respective batch files: apache_start.bat and mysql_start.bat. Along with
Apache and MySQL running in the background, we type http://localhost/phpMyAdmin/ into our
web browser. If successful we will be presented with a phpMyAdmin start page similar to the
one shown below.

Figure 2 (PhpMyAdmin Start Page)

The first step with phpMyAdmin running is creating a new database.We create a new database
by directly executing SQL statements as shown below.The successful execution of the sql querry
creates a database ‘sims’ with tables in it.The tabels are admin_login and student_info. We also
inserted values in the admin table.The screenshot below shows the successful execution of the
query thus creation of a database named student.

30
 6. PROJECT DESCRIPTION

6.1 Introduction

Student Information Management System can be used by education institutes 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

The directory structure of the project is as follows:

31
 6.2 Description Of Root Directory Contents

css:-it contains the all css code for the pages of the website.

Data1: it contains the data files which helps to slide show of home page.

Docs: it contains all the documents which are related to the notification uploaded by the admin
or faculty.

Engine1: it contains the css and JavaScript code which helps to running the slideshow of
homepage.

Images: it contains all the images like logo, menu_icon, and the profile picture uploaded by the
students or faculty.

Add_faculty.php: this page contains the code which helps which navigate the token generation
page.

Add_notes.php : it this page code containing the information which is used to upload the
notification for home page.

Add_student_excel.php: this page contains the code for the uploading token excel file for the
student registration.

Add_stud.php : in this page the code is available which show the option for choosing the option
for which mode is selected for token generation.

Atten_indi.php : In this page code contain the token generation for any single student.

Connection.php : this php file contain the connection page which contains the caonnection code
for connecting the database.

Faculty_home.php: this page shows the services which is available for the faculty.

Login_handler.php : this page is used to authenticate the user id and password for admin,
student and faculty it redirect the page according to the user type.

Logout.php: this file contains the code for closing the session and disconnect the database.

Main.php: this is the main home page of website this page contains title bar, menu bar,
notification area, picture gallery, login area.

Notes_delete: this file is used to delete the notification which is uploaded by the admin.

32
Notify.php: this page shows all the notification which is acces by the admin to view and update
the notification.

Signup_handler: this file used to save the registration data on Databse.

Stud_page: this page show all the services available for the students.

Stud_signup.php : this page contains the registration form for the students.\

Stud_signup_handler: this file is used to save the student information to stud_info table.

Stud_token_gen.php: this file contains the code for generation the token for students.

Token_handler.php : this page contains the code for save the tokens data on databse.

33
 6.3 Description of Database tables:
Table1: Admin table

Admin:

Name: name of the admin

User_id: user id for login the admin page.

Password: password for authenticate and redirect the admin page.

Table2: faculty_details

Faculty_details:

Reg_id: id for login the faculty.

Fname: first name of faculty

Lname: Last Name of faculty.

Sex: Specify the gender of faculty.

Mobile: mobile no of the faculty.

Email: email id of the faculty.

34
 Address: address of the faculty.

City: city of the faculty.

Qualification: highest qualification of the faculty.

Father_name: father name of the faculty.

Password: password contains the password for the login to faculty.

Sec_ques: it contains the question which is selected by the faculty while signup.

Sec_ans: in caontains the answer of security question which again help to recover the
password

Table3:faculty_token

Faculty_token:

Faculty-name: name of the faculty and automatically fetched into signup page.

Pin: 4 digit pin to authenticate token.

F_id: registration id for then faculty.

Table4: images:

Images:

Reg_id: reg-id is the id of student or faculty which is related to the student’s images.

35
Passport: name of profile pic.

Sign: file name of student’s signature.

Doc1: file name of student’s doc.

Doc2: file name of student’s doc.

Table5: mca11(subject table)

Subject table:

This table automatically inserted into databse by the name of subject whenever the admin
allocate a new subject.and after it is used to save the attendance of the student.

Reg_id: reg_id of the student referenced to stud_info table’s primary key.

Sr_no: temporary roll no od students.

Date: date of attendance.

Status: status of student’s attendace saves “Y” for present “N” for absent.

36
Table6: stud_info

Stud_info :

Reg_id: primary key and the regid is also used by the student to login into website.

Fname: first name of student.

Lname: last name of the student.

Dob: date of birth of the student

Mobile: mobile no of the student

Email: email of the student.

Address; address of the student.

Course: course of the student .

Year: year of course.

Father_name: father’s name of the student.

City: city of the student.

Sex: specify the gender of student.

Password: password for login into website.

Sec_ques: question choosed by the student while signup.

37
 Sec_ans: answer of security question.

Table8: Stud_token

Stud_token:

Stud_name: name of the student which is automatically into signup page.

Pin: 4 digit pin code to authenticate the token.

S_id: roll no of the student.

Table9: uploaded_files

Uploaded_files:

File_name: name of the file uploaded for the notification.

User_id: user_id of the user who upload the notification.

Title: title of the notification.

38
7. OUTPUT SCREENSHOTS
7.1 HOME PAGE

39
7.2 STUDENT USER LOGIN

40
7.3 ADMIN DASHBOARD

41
7.4 ADD STUDENTS

42