Anjaliminiproj

VISVESVARAYA TECHNOLOGICAL UNIVERSITY
“JNANA SANGAMA”, BELAGAVI -590 018.
2022-2023
A Mini Project Report on
“STUDENT MAGEMENT ”
Submitted in partial fulfillment for the award of the degree of
BACHELOR OF ENGINEERING
In
COMPUTER SCIENCE AND ENGINEERING
Submitted By
Abhinav prakash
[1JB21CS008]
Under the guidance of

Dr. Prakruthi.M.K
Assistant Professor,
Dept. of CSE,SJBIT
DEPARTMENT OF COMPUTER SCIENCE AND ENGINEERING
SJB INSTITUTE OF TECHNOLOGY

#67, B G S HEALTH AND EDUCATION CITY
Kengeri, Bengaluru-560 060.
||Jai Sri Gurudev||
Sri Adichunchanagiri Shikshana Trust ®
SJB INSTITUTE OF TECHNOLOGY
BGS Health & Education City, Kengeri, Bengaluru-560 060.
DEPARTMENT OF COMPUTER SCIENCE AND ENGINEERING
CERTIFICATE
Certified that the Internship report entitled “student management” carried out by Abhinav prakash
[1JB21CS008] bonafide student of SJB Institute of Technology in partial fulfilment for the award
of “BACHELOR OF ENGINEERING” in 5rd semester as prescribed by VISVESVARAYA
TECHNOLOGICAL UNIVERSITY, BELAGAVI during the academic year 2022-23. It is
certified that all corrections/suggestions indicated for internal assessment have been incorporated in
the report deposited in the departmental library. This report has been approved as it satisfies the
academic requirements in respect of the Internship prescribed for the said degree.
Dr.Prakruthi.M.K Dr. Krishna .A.N Dr. K V Mahendra Prashanth

Assistant Professor Professor & Head Principal
Dept. of CSE, Dept. of CSE, SJBIT
SJBIT SJBIT
ACKNOWLEDGEMENT
I would like to express our profound grateful to His Divine Soul Jagadguru Padmabhushan Sri
Sri Sri Dr. Balagangadharanatha Mahaswamiji and His Holiness Jagadguru Sri Sri Sri Dr.
Nirmalanandanatha Swamiji for providing me an opportunity to be a part of this esteemed
institution.
I would also like to express our profound thanks to Revered Sri Sri Dr. Prakashnath Swamiji,
Managing Director, SJB Institute of Technology, for his continuous support in providing amenities
to carry out this Internship in this admired institution.
I express our gratitude to Dr. K V Mahendra Prashanth, Principal, SJB Institute of Technology,
for providing me excellent facilities and academic ambience, which helped me in satisfactory
completion of Internship work.
I extend our sincere thanks to Dr. Babu N V, Academic Dean, SJB Institute of Technology for
providing us constant support throughout the period of my internship work.
I extend our sincere thanks to Dr. Krishna A N, Professor & Head, Dept.of CSE for providing us
invaluable support throughout the period of my Internship work.
I wish to express our heartfelt gratitude to my guide, Dr.Prakruthi.M.K, for her valuable guidance,
suggestions and cheerful encouragement during the entire period of our project work.
Finally, I take this opportunity to extend my earnest gratitude and respect to our parents, teaching
& technical staff of the department, the library staff and all my friends, who have directly or
indirectly supported me during the period of project work.
Regards
Abhinav prakash
[1JB21CS008]
ABSTRACT
The problems regarding the current system in the college were analyzed and noted
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.
In the Software we can register as a user and user has of two types, student and administrator.
Administrator has the power to add new user and can edit and delete a user.
A student can register as user and can add edit and delete his profile. T
he administrator can add edit and delete marks for the student. All the users can see the marks.
CONTENTS
Sl.No CHAPTERS
1 INTRODUCTION 1
PROJECT DESCRIPTION 1
2. LITERATURE SURVEY 3
BACKGROUND STUDY 3
TOOLS AND TECHNOLOGY 4
3. HARDWARE AND SOFTWARE REQUIREMENTS 5
HARDWARE REQUIREMENTS 5
SOFTWARE REQUIREMENTS 5
4. SOFTWARE REQUIREMENTS SPECIFICATION 6
USERS 6
FUNCTIONAL REQUIREMENTS 7
NON-FUNCTIONAL REQUIREMENTS 10
5. SYSTEM DESIGN 11
ARCHITECTURE DIAGRAM 11
LEVEL-ZERO DATA FLOW DIAGRAM 12
LEVEL-ONE DATA FLOW DIAGRAM 13
6. DETAILED DESIGN 14
USE CASE DIAGRAM 14
ACTIVITY DIAGRAM 15
ER AND CONCEPTUAL DIAGRAM 17
6.4 CONCEPTUAL DIAGRAM 18
7. IMPLEMENTATION & RESULT 19
PSEUDO CODE 19
RESULT 27
8. SOFTWARE TESTING 41
TEST CASES 42
9. CONCLUSION 44
10. REFERENCES 45
List of Figures
Figure NO Title Page No
5.1 Architecture Diagram 11
5.2 Context Diagram 12

5.3 Data Flow Diagram 13
6.1 Use Case Diagram 14
6.2 Activity Diagram 15
6.3 ER Diagram 17
6.4 Conceptual Schema 18
7.1.1 Login page 19
7.1.2 Welcome Admin 20
7.1.3 Cources 21
7.1.4 Subjects 23
7.2.1 Register 27
7.2.2 View students 27
7.2.3 Session 28
7.2.4 Change password 28
7.2.5 Admin profile 29
7.2.6 Logout 29
LIST OF TABLES
Table No List of Table Page No
3.1 Hardware Requirements 5
3.2 Software Requirements 5

8.1.1 Test Cases for Admin Login 41
8.1.2 Test Cases for Adding students 41
8.1.3 Test Case for deleting students 42
8.1.4 Test Cases for logout 43
MINI PROJECT 2023-24
CHAPTER 1
INTRODUCTION
PROJECT DESCRIPTION
In today's educational landscape, the efficient management of student data and administrative tasks is
paramount for educational institutions to streamline operations and enhance overall productivity. A
Student Management System (SMS) serves as a comprehensive solution to address the diverse needs of
educational institutions, ranging from managing student records to facilitating communication between
stakeholders. This system integrates various functionalities to automate routine tasks, improve data
accuracy, and enhance collaboration among administrators, educators, students, and parents. In summary,
the Student Management System represents a vital tool for modern educational institutions seeking to
enhance efficiency, transparency, and collaboration across all facets of their operations. By harnessing the
power of technology, educational institutions can embrace innovation and adapt to the evolving needs of
students, educators, and administrators in an increasingly digital world.
PROPOSED SOLUTION
The proposed solution for a Student Management System (SMS) should be comprehensive, user-
friendly, and customizable to meet the specific needs of educational institutions. Below are key
components and features that could be included in the proposed solution:
Implement a centralized database to store and manage student information, including personal details,
contact information, academic history, attendance records, and health information. This database should
be easily accessible and searchable by authorized administrators.
Develop features to streamline the enrollment and registration process, allowing students to register for
courses online, view their class schedules, and track their academic progress.
Enable administrators to record and track student academic performance, including grades, transcripts,
and course history. Implement features for generating academic reports, transcripts, and certificates.
Department of CSE,SJBIT Page | 1

PURPOSE
The purpose of a Student Management Portal is to serve as a centralized platform that facilitates various
aspects of student administration, communication, and collaboration within an educational institution..
SCOPE
The scope of a Student Management Portal encompasses various functionalities and features aimed at
addressing the diverse needs of educational institutions, students, educators, parents, and administrators

CHAPTER
2
2. LITERATURE SURVEY
BACKGROUND STUDY
The background study of a Student Management System (SMS) involves understanding the context,
challenges, and existing systems in educational institutions, as well as identifying the motivations and
objectives for implementing or improving such a system. Here are the key components of a background
study for a Student Management System
EXISTING SYSTEM
 Student Information Systems (SIS)

SIS is a comprehensive software platform designed to manage student data, including personal
information, enrollment, attendance, grades, and transcripts. It typically includes features for
administrative tasks such as admissions, registration, scheduling, and reporting.
 Learning Management Systems (LMS)
LMS focuses more on the educational aspect of student management, providing tools for course deliver
content management, online assessments, and collaboration between students and instructors. While it may
not cover administrative functions extensively, some LMS platforms integrate with SIS to synchronize
student data
 Student Portals:
Student portals offer a centralized online platform where students can access various services and
resources related to their education. This may include viewing schedules, grades, assignments,
announcements, and communication with instructors and peers..

TOOLS AND TECHNOLOGIES

 PHP
PHP is a server side scripting language that is embedded in HTML. It is used to manage dynamic content,
databases, session tracking, even build entire e-commerce sites. It is integrated with a number of popular
databases, including MySQL, PostgreSQL, Oracle, Sybase, Informix, and Microsoft SQL Server..
 MYSQL
Mysql – it is a free open-source widely used relational database management system (RDBMS)
and is ideal for both small and large applications.
All backend operations of adding products and managing products orders, payment info and all
other activities are performed using mysql.
 HTML5
HTML (Hypertext Markup Language) is the code that is used to structure a web page and its content. For
example, content could be structured within a set of paragraphs, a list of bulleted points, or using images
and data tables In cake and bake application all the front end displaying hypertext mark up language is
used html is used to display font in various sizes.
 CSS
CSS is the language for describing the presentation of Web pages, including colors, layout, anfonts. It
allows one to adapt the presentation to different types of devices, such as large screens,small screens, or
printers. CSS is independent of HTML and can be used with any XML-based mark-up language.
 JAVASCRIPT
JavaScript is commonly used for creating web pages. It allows us to add dynamic behavior to the webpage
and add special effects to the webpage. On websites, it is mainly used for validation purposes. JavaScript
helps us to execute complex actions and also enables the interaction of websites with visitors.
 BOOTSTRAP
Bootstrap is a framework to help you design websites faster and easier. It includes HTML and CSS based
design templates for typography, forms, buttons, tables, navigation, modals, image carousels, etc. It also
gives you support for JavaScript plugins.
CHAPTER 3
3. HARDWARE AND SOFTWARE REQUIREMENTS
HARDWARE REQUIREMENTS
Processor Core i3 or Later
RAM 4GB RAM or More
Hard Disk 500 GB

Monitor 15 screen
Keybord Standard 104 keys
Table 3.1. Hardware Requirments
SOFTWARE REQUIREMENTS
Operating System Windows 8 and onwords

Front End HTML-5, CSS, PHP-7, JS
Database MySQL 8.0
Table.3.2. Software Requirements

CHAPTER 4
4. SOFTWARE REQUIREMENTS SPECIFICATION

The Software Requirements Specifications is produced at the culmination of the analysis task. The function
and performance allocated to software as part of the system engineering are refined by establishing a compl
-ete information description, a detailed functional and behavioural description,an indication of performanc
-e requirements and design constraints, appropriate validation criteria, and other data pertinent to requirem
-ent.
USERS
Users of the application are the admin and customers. Admin and customers will have same interface to
login but heir functionality differs.
 Admin
Admin can first login to the application by entering valid username and password. On successful login
admin can add category by entering category name and description. After adding category admin can
products by filling all the details required, after adding user can view, update, delete products anytime and
also can update status of products. Admin can view the orders placed by customers and go to view details,
receive information. By clicking on several icons tab from dashboard and can view their records .
 Customer
Customers have to first get registered by providing their name, email, password, mobile number, address,
click on signup and can login with email and password from next time. After successful login user can
vie
-w products, feedback, give feedback, add to cart and after adding products to cart can view cart and check
-out if any item need to be removed from cart can delete that item from cart and proceed to place order.if
user is not satisfied with the products available in store, users can request custom cake by customizing size
shape, flavour and request that product on successful transaction email notification will be received for ord
-er confirmation, custom cake price all the actions on custom cake by admin user will get email notification
and also can see update in user dashboard.

FUNCTIONAL REQUIREMENTS
 Register To Application
Only customers can register to the application by providing their username, password, System will check for
details and on successful registration will get account on site. Email and password entered at the time of
registration is their login details. Customers cannot get multiple accounts with one email id only one account
users can get registered with one email. By registering with student portal not only gets account with
site.teachers can view edit and modify the settings
 Login
Once the user register they will be customer for application. Both Admin and customers can login to the
application by providing valid credentials. Both users will have same interface based on role identified by
system, system will move to their respective dashboard.
 Manage student portal

Admin can add new student category to the system by entering category name and description and after
adding anytime can view the category, edit and delete.
 View students
Teacher’s can view category and search products by category.
 Manage databases
Managing the database of a Student Management System (SMS) involves several key steps to ensure data
integrity, security, and efficiency. Here's a guide on how to manage the database
 View student details
Students can view their progress in general or search by category.

 Manage students cources

Managing student courses in a Student Management System (SMS) involves several steps to ensure students
are enrolled in appropriate courses, have access to course materials, and can track their progress. Here's how
you can manage student courses effectively:
 View students details
Students can view their report available they can view details of cources...
 Add students
o add a student to a Student Management System (SMS), you typically follow a structured process within the
administrative interface of the system.
 View students performance

Viewing students in a Student Management System (SMS) typically involves accessing a dedicated section or
module within the administrative interface where you can search for and view student records. Here's how
you can view students in an SMS

NON-FUNCTIONAL REQUIREMENTS
 Usability
The application is web-based application if the user has access to good internet and a desktop, he/she can
use this application at any point of time and anywhere around the world without any confusion.
 Security
The application provides secure logging in into the system with required credentials.
 Extensibility
The system can be extensible for future enhancements for any developers who want to enhance and use the
system.
 Availability
Availability can be defined as the ability of an item to be retained and restored for any future reference of
the student . The user can access his services at any point of time.
Department of CSE,SJBIT Page |

IMINI PROJECT 2023-24
CHAPTER 5
5. SYSTEM DESIGN
5.1. ARCHITECTURE DIAGRAM
Fig 5.1 Architectural diagram
Fig 5. When creating an architecture diagram for a Student Management Portal, it's essential to illustrate
the system's components, their interactions, and how data flows between them. Here's a breakdown of what
to include in the architecture diagram

Frontend Interface:
This includes the user interface components that students, educators, administrators, and parents interact
with. It could consist of web pages, mobile apps, or other interfaces.
Backend Services:
These are the server-side components responsible for processing requests, handling business logic, and
interacting with the database. This may include authentication services, API endpoints, and other backend
functionalities.
Database:
The database stores all student-related data, including student records, course information, grades, attendance,
and administrative data. Specify the type of database management system (e.g., MySQL, PostgreSQL) being
used.
Third-party Integrations:
If the portal integrates with other systems or services (e.g., Learning Management Systems, Student
Information Systems), include these components in the diagram.

5.2 DATA FLOW DIAGRAM
Level 0 (Context level) Data Flow Diagram
Fig.5.2 Level 0 (Context level) Data Flow Diagram
Fig 5.2 is a context diagram (DFD level 0). The external entities are users and Admin.From user username
and password will go to system and system will verify, id details are valid user will get access to the syste
m.From admin product information like product name, price, shape, flavour etc will be sent to system. Us
-er can view products order them give feedback and that data can be viewed by admin.

5.3. DFD LEVEL-1
Fig.5.3 DFD LEVEL-1
Fig 5.3 is DFD level 1 diagram shows how the users will be interacting with the process and what they will
getting in return from the process. Here the external entities are users and admin.
User login process, users first have to get registered and registered details will be stored in the user databa
-se table. Then users have to login by providing username and password. After logging in the user can do
perform, products that details will be stored in order table, and users can give wokflow based on how the
product is, how it can be improved etc., all these will be stored in fed table. And also, users can edit and
delete and alter based on their desires giving all the details which will be stored in table. Admin login
process, admin has to login by providing username and password, after logging in admin can add the
products with the details will be stored in the product table.
In both login process respective user name and password is sent to the system. It will check for authorizatio
-n for the validity of user in the user data store.

CHAPTER 6
6. DETAILED DESIGN
USE CASE DIAGRAM
Fig.6.1 Use Case Diagram
Fig 6.1 To add a student to a Student Management System (SMS), you typically follow a structured process within
the administrative interface of the system. Here's a step-by-step guide on how to add a student:
Access the Student Management System: Log in to the administrative interface or dashboard of the SMS using
your authorized credentials.
Navigate to Student Management Section: Locate the section or module within the SMS specifically designed for
managing student records. This section may be labeled as "Students", "Enrollment", or something similar.
Initiate the Student Addition Process: Look for an option or button labeled "Add New Student", "Create Student", or
similar. Click on it to start adding a new student.
Enter Student Information: Fill in the required fields with the student's information. This typically includes:

 Personal details: Name, date of birth, gender, address, contact information, etc.
 Academic information: Previous school attended, grade level, enrollment status, etc.
 Emergency contact details: Name, relationship, phone number, etc.
Assign a Unique Identifier: Assign a unique identifier or student ID number to the student. This identifier helps
distinguish the student's record from others in the system.
Set Enrollment Details: Specify the enrollment details for the student, such as the academic program or course of
study, class or grade level, and any other relevant enrollment information.
Upload Supporting Documents (If Required): If the system allows for it, upload any supporting documents related to
the student's enrollment, such as academic transcripts, medical records, or consent forms.
Review and Verify Information: Review all entered information for accuracy and completeness. Ensure that all
required fields are filled correctly and that there are no discrepancies.

ACTIVITY DIAGRAM
Fig 6.2.1. Customer Activity Diagram
Fig 6.2.1 An activity diagram for users in a Student Management Portal can provide a visual representation of the
various actions or activities users can perform within the system. Here's a basic activity diagram outlining the typical
actions users may take:
Login Process:
 The activity diagram starts with the "Login" activity, where users enter their credentials to access the portal.
 If the login is successful, the system proceeds to the next activity. Otherwise, an error message is displayed,
and the user may retry the login.
View Dashboard:

 After successful login, users are directed to the dashboard activity, which serves as the main interface for
accessing different functionalities of the portal.
 From the dashboard, users can navigate to various sections of the portal based on their roles and permissions.
View Profile:
 Users have the option to view their profile information, including personal details, contact information, and
any other relevant information stored in the system.
Manage Courses:
 Depending on the user's role (e.g., administrator, educator), they may have the ability to manage courses
within the system.
 This activity includes actions such as creating new courses, updating course details, and assigning instructors
to courses.
Enrollment:
 Students can enroll in courses by selecting the desired courses from the course catalog and completing the
enrollment process.
 Administrators or educators may also manage enrollment by approving or rejecting student enrollments.

ACTIVITY DIAGRAM FOR ADMIN
Fig 6.2.2. Admin Activity Diagram
Under Admin again there are multiple activities, Admin activity starts by logging into the system, if
login fails it comes back to the same activity i.e., login. Otherwise, it will redirect to respective
admin activity. Admin can manage items list, view orders, take action on

ER DIAGRAM
Fig 6.3 ER Diagram
An activity diagram for users in a Student Management Portal can provide a visual representation of the
various actions or activities users can perform within the system. Here's a basic activity diagram outlining the
typical actions users may take:

Login Process:
 The activity diagram starts with the "Login" activity, where users enter their credentials to access the portal.
 If the login is successful, the system proceeds to the next activity. Otherwise, an error message is displayed,
and the user may retry the login.
View Dashboard:
 After successful login, users are directed to the dashboard activity, which serves as the main interface for
accessing different functionalities of the portal.
 From the dashboard, users can navigate to various sections of the portal based on their roles and permissions.
View Profile:
Users have the option to view their profile information, including personal details, contact information, and
any other relevant information stored in the system.
Manage Courses:
 Depending on the user's role (e.g., administrator, educator), they may have the ability to manage courses
within the system.
 This activity includes actions such as creating new courses, updating course details, and assigning instructors
to courses.
Enrollment:
 Students can enroll in courses by selecting the desired courses from the course catalog and completing the
enrollment process.
 Administrators or educators may also manage enrollment by approving or rejecting student enrollments.
View Grades:
 Students can view their grades for enrolled courses, including individual assignment grades, exam scores,

CONCEPTUAL SCHEMA
Fig 6.4 Conceptual Schema.
A conceptual schema for a Student Management System (SMS) provides a high-level overview of the
system's structure, including the main entities, their attributes, and the relationships between them. Here's a
conceptual schema outlining the core components of an SMS:

CHAPTER 7
7. IMPLEMENTATION AND RESULT
SOURCE CODE SNIPPET

Add Category
<?php
//Start session
session_start();
//Array to store validation errors

$errmsg_arr = array();
//Validation error flag

$errflag = false;
//Connect to mysql server

$link = mysql_connect('localhost','model','');
if(!$link) {
die('Failed to connect to server: ' . mysql_error());
}
//Select database
$db = mysql_select_db('model', $link);
if(!$db) {
die("Unable to select database");
}
//Function to sanitize values received from the form. Prevents SQL injection
function clean($str) {
$str = @trim($str);
if(get_magic_quotes_gpc()) {
$str = stripslashes($str);
}
return mysql_real_escape_string($str);
}
//Sanitize the POST values

$login = clean($_POST['username']);
$password = clean($_POST['password']);
//Input Validations
if($login == '') {
$errmsg_arr[] = 'Username missing';
$errflag = true;
}
if($password == '') {
$errmsg_arr[] = 'Password missing';
$errflag = true;
}
//If there are input validations, redirect back to the login form
if($errflag) {
$_SESSION['ERRMSG_ARR'] = $errmsg_arr;
session_write_close();
header("location: index.php");
exit();
}
//Create query
$qry="SELECT * FROM user WHERE username='$login' AND password='$password'";
$result=mysql_query($qry);
//Check whether the query was successful or not

if($result) {
if(mysql_num_rows($result) > 0) {
//Login Successful
session_regenerate_id();
$member = mysql_fetch_assoc($result);
$_SESSION['SESS_MEMBER_ID'] = $member['id'];
$_SESSION['SESS_FIRST_NAME'] = $member['name'];
$_SESSION['SESS_LAST_NAME'] = $member['position'];
//$_SESSION['SESS_PRO_PIC'] = $member['profImage'];
session_write_close();
header("location: main/index.php");
exit();
}else {
//Login failed
header("location: index.php");
exit();
}
}else {
die("Query failed");
}
?>
-- phpMyAdmin SQL Dump

-- version 5.2.1
-- https://www.phpmyadmin.net/
--
-- Host: 127.0.0.1
-- Generation Time: Feb 19, 2024 at 06:12 AM
-- Server version: 10.4.28-MariaDB
-- PHP Version: 8.2.4
SET SQL_MODE = "NO_AUTO_VALUE_ON_ZERO";

START TRANSACTION;
SET time_zone = "+00:00";
/*!40101 SET @OLD_CHARACTER_SET_CLIENT=@@CHARACTER_SET_CLIENT */;

/*!40101 SET @OLD_CHARACTER_SET_RESULTS=@@CHARACTER_SET_RESULTS */;
/*!40101 SET @OLD_COLLATION_CONNECTION=@@COLLATION_CONNECTION */;

/*!40101 SET NAMES utf8mb4 */;
--
-- Database: `studentrecorddb`
--
-- --------------------------------------------------------
--
-- Table structure for table `cities`
--
CREATE TABLE `cities` (

ìd` int(11) NOT NULL,
`name` varchar(30) NOT NULL,
`state_id` int(11) NOT NULL
) ENGINE=InnoDB DEFAULT CHARSET=latin1 COLLATE=latin1_swedish_ci;
--
-- Dumping data for table `cities`
--
INSERT INTO `cities` (ìd`, `name`, `state_id`) VALUES

(1, 'Bombuflat', 1),
(2, 'Garacharma', 1),
(3, 'Port Blair', 1),
(4, 'Rangat', 1),
(5, 'Addanki', 2),
(6, 'Adivivaram', 2),
(7, 'Adoni', 2),
(8, 'Aganampudi', 2),
(9, 'Ajjaram', 2),
(10, 'Akividu', 2),
(11, 'Akkarampalle', 2),
(12, 'Akkayapalle', 2),
(13, 'Akkireddipalem', 2),
(14, 'Alampur', 2),
(15, 'Amalapuram', 2),
(16, 'Amudalavalasa', 2),
(17, 'Amur', 2),
(18, 'Anakapalle', 2),
(19, 'Anantapur', 2),
(20, 'Andole', 2),
(21, 'Atmakur', 2),
(22, 'Attili', 2),
(23, 'Avanigadda', 2),
(24, 'Badepalli', 2),
(25, 'Badvel', 2),
(26, 'Balapur', 2),
(27, 'Bandarulanka', 2),
(28, 'Banganapalle', 2),
(29, 'Bapatla', 2),
(30, 'Bapulapadu', 2),
(31, 'Belampalli', 2),
(32, 'Bestavaripeta', 2),
(33, 'Betamcherla', 2),
(34, 'Bhattiprolu', 2),
(35, 'Bhimavaram', 2),
(36, 'Bhimunipatnam', 2),
(37, 'Bobbili', 2),
(38, 'Bombuflat', 2),
(39, 'Bommuru', 2),
(40, 'Bugganipalle', 2),
(41, 'Challapalle', 2),
(42, 'Chandur', 2),
(43, 'Chatakonda', 2),
(44, 'Chemmumiahpet', 2),
(45, 'Chidiga', 2),
(46, 'Chilakaluripet', 2),
(47, 'Chimakurthy', 2),
(48, 'Chinagadila', 2),
(49, 'Chinagantyada', 2),
(50, 'Chinnachawk', 2),
(51, 'Chintalavalasa', 2),
(52, 'Chipurupalle', 2),
(53, 'Chirala', 2),
(54, 'Chittoor', 2),
(55, 'Chodavaram', 2),
(56, 'Choutuppal', 2),
(57, 'Chunchupalle', 2),
(58, 'Cuddapah', 2),
(59, 'Cumbum', 2),
(60, 'Darnakal', 2),
(61, 'Dasnapur', 2),
(62, 'Dauleshwaram', 2),
(63, 'Dharmavaram', 2),
(64, 'Dhone', 2),
(65, 'Dommara Nandyal', 2),
(66, 'Dowlaiswaram', 2),
(67, 'East Godavari Dist.', 2),
(68, 'Eddumailaram', 2),
(69, 'Edulapuram', 2),
(70, 'Ekambara kuppam', 2),
(71, 'Eluru', 2),
(72, 'Enikapadu', 2),
(73, 'Fakirtakya', 2),
(74, 'Farrukhnagar', 2),
(75, 'Gaddiannaram', 2),
(76, 'Gajapathinagaram', 2),
(77, 'Gajularega', 2),
(78, 'Gajuvaka', 2),
(79, 'Gannavaram', 2),
(80, 'Garacharma', 2),
(81, 'Garimellapadu', 2),
(82, 'Giddalur', 2),
(83, 'Godavarikhani', 2),
(84, 'Gopalapatnam', 2),

INSERT INTO `tbl_login` (ìd`, `FullName`, ÀdminEmail`, `loginid`, `password`) VALUES

(1, 'admin', 'admin123@gmail.com', 'admin', 'Test@12345');
--
-- Indexes for dumped tables
--
--
-- Indexes for table `cities`
--
ALTER TABLE `cities`
ADD PRIMARY KEY (ìd`);
--
-- Indexes for table `countries`
--
ALTER TABLE `countries`
--
-- Indexes for table `registration`
--
ALTER TABLE `registration`
--
-- Indexes for table `session`
--
ALTER TABLE `session`
--
-- Indexes for table `states`
--
ALTER TABLE `states`
--
-- Indexes for table `subject`
--
ALTER TABLE `subject`
ADD PRIMARY KEY (`subid`);
--
-- Indexes for table `tbl_course`
--
ALTER TABLE `tbl_course`
ADD PRIMARY KEY (`cid`);
--
-- Indexes for table `tbl_login`
--
ALTER TABLE `tbl_login`
--
-- AUTO_INCREMENT for dumped tables
--
--
-- AUTO_INCREMENT for table `cities`
--
ALTER TABLE `cities`
MODIFY ìd` int(11) NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=47577;
--
-- AUTO_INCREMENT for table `countries`
--
ALTER TABLE `countries`
--
-- AUTO_INCREMENT for table `registration`
--
ALTER TABLE `registration`
--
-- AUTO_INCREMENT for table `session`
--
ALTER TABLE `session`
--
-- AUTO_INCREMENT for table `states`
--
ALTER TABLE `states`
--
-- AUTO_INCREMENT for table `subject`
--
ALTER TABLE `subject`
MODIFY `subid` int(11) NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=6;
--
-- AUTO_INCREMENT for table `tbl_course`
--
ALTER TABLE `tbl_course`
MODIFY `cid` int(11) NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=10;
--
-- AUTO_INCREMENT for table `tbl_login`
--
ALTER TABLE `tbl_login`
COMMIT;
/*!40101 SET CHARACTER_SET_CLIENT=@OLD_CHARACTER_SET_CLIENT */;

/*!40101 SET CHARACTER_SET_RESULTS=@OLD_CHARACTER_SET_RESULTS */;
/*!40101 SET COLLATION_CONNECTION=@OLD_COLLATION_CONNECTION */;

RESULT:
Fig 7.2.1 Welcome page.

Fig 7.2.1 is a Welcome page which is the starting page of an application. This page a way for navigation
into the system where user can register/login into the system to start using the application.
Fig 7.2.2 students Dashbord

Fig 7.2.2 is student dashbord page: here teachers can view students data and add and edit even can
delete and alter to
Fig 7.2.3 students view option

Fig 7.2.3 here teavhers can view their students record and delete and edit to

Fig 7.2.4 students admin page
Fig 7.2.4 is a it’s a user admin page here user get to know information relate to their students
n a Student Management System (SMS), the students' admin page serves as a central hub for
administrators to manage student-related tasks efficiently. Here's a breakdown of the key features and
functionalities typically found on the students' admin page:

Fig 7.2.5 register new students

Registering new students in a Student Management System (SMS) involves collecting relevant information
about the student and entering it into the system. Here's a step-by-step guide on how to register new students

Fig 7.2.27 students view

Fig 7.2.27 is a View option through which teachers can do their work and search for respective students

CHAPTER 9
CONCLUSION
In conclusion, a Student Management Portal serves as a crucial tool for educational institutions to streamline
administrative tasks, enhance communication, and support student success. Through the development and
implementation of such a portal, several key benefits emerge: The portal centralizes student-related information,
simplifying administrative processes such as enrollment management, attendance tracking, and grade recording.
This efficiency allows administrators to focus more on supporting students and improving educational outcomes. By
providing communication channels within the portal, stakeholders such as students, instructors, administrators, and
parents can easily collaborate, share information, and stay updated on important announcements, deadlines, and
events. The portal offers students convenient access to essential services and resources, such as course registration,
academic records, grades, and communication with instructors. This accessibility enhances the overall student
experience and fosters engagement with the educational institution.

CHAPTER 9
REFERENCE
The following books and online websites were referred during the analysis and execution phase of the
project.
Book References
1. Kavrin Tatroe, Programming Php : A comprehensive study, Edition 1(2013), PHI
2. Ray Harris, Php & My Sql: Solid ground on both PHP and MySQL in an easy and readable manner.
Websites References:
 https://getbootstrap.com/docs/5.0
 https://www,cake69.com
 https://www.warm-oven.com
 https://www.balkinyo.com


Anjaliminiproj

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Anjaliminiproj

Uploaded by

Copyright:

Available Formats

VISVESVARAYA TECHNOLOGICAL UNIVERSITY

“JNANA SANGAMA”, BELAGAVI -590 018.

COMPUTER SCIENCE AND ENGINEERING

Under the guidance of

DEPARTMENT OF COMPUTER SCIENCE AND ENGINEERING

SJB INSTITUTE OF TECHNOLOGY

DEPARTMENT OF COMPUTER SCIENCE AND ENGINEERING

Dr.Prakruthi.M.K Dr. Krishna .A.N Dr. K V Mahendra Prashanth

Figure NO Title Page No

5.1 Architecture Diagram 11

5.2 Context Diagram 12

Table No List of Table Page No

3.1 Hardware Requirements 5

3.2 Software Requirements 5

Department of CSE,SJBIT Page | 1

Department of CSE,SJBIT Page | 2

 Student Information Systems (SIS)

 Learning Management Systems (LMS)

Department of CSE,SJBIT Page | 3

TOOLS AND TECHNOLOGIES

Processor Core i3 or Later

RAM 4GB RAM or More

Hard Disk 500 GB

Table 3.1. Hardware Requirments

Operating System Windows 8 and onwords

Table.3.2. Software Requirements

Department of CSE,SJBIT Page | 5

4. SOFTWARE REQUIREMENTS SPECIFICATION

Department of CSE,SJBIT Page | 6

 Manage student portal

Department of CSE,SJBIT Page | 7

 Manage students cources

 View students performance

Department of CSE,SJBIT Page | 8

Department of CSE,SJBIT Page |

5.1. ARCHITECTURE DIAGRAM

Fig 5.1 Architectural diagram

Department of CSE,SJBIT Page | 11

Department of CSE,SJBIT Page | 12

5.2 DATA FLOW DIAGRAM

Level 0 (Context level) Data Flow Diagram

Fig.5.2 Level 0 (Context level) Data Flow Diagram

Department of CSE,SJBIT Page | 13

5.3. DFD LEVEL-1

Fig.5.3 DFD LEVEL-1

Department of CSE,SJBIT Page | 14

USE CASE DIAGRAM

Fig.6.1 Use Case Diagram

Department of CSE,SJBIT Page | 15

Department of CSE,SJBIT Page | 16

Fig 6.2.1. Customer Activity Diagram

Department of CSE,SJBIT Page | 17

Department of CSE,SJBIT Page | 18

ACTIVITY DIAGRAM FOR ADMIN

Fig 6.2.2. Admin Activity Diagram

Department of CSE,SJBIT Page | 19

Fig 6.3 ER Diagram

Department of CSE,SJBIT Page | 20

Department of CSE,SJBIT Page | 21

Fig 6.4 Conceptual Schema.

Department of CSE,SJBIT Page | 22

SOURCE CODE SNIPPET

//Array to store validation errors

/!40101 SET @OLD_CHARACTER_SET_CLIENT=@@CHARACTER_SET_CLIENT /;

/!40101 SET CHARACTER_SET_CLIENT=@OLD_CHARACTER_SET_CLIENT /;