1. Page | 1
A
PROJECT REPORT
ON
STUDENT INFORMATION SYSTEM
Submitted to
CHHATTISGARH SWAMI VIVEKANAND TECHNICAL UNIVERSITY
BHILAI
In partial fulfillment of requirement for the award of degree
Of
Bachelor of Engineering
IN
MECHANICAL ENGINEERING
BY
Sourabh singh sen

2. Page | 2
D E C L A R A T IO N
We the undersigned solemnly declare that the report of the project work entitled STUDENT
INFORMATION SYSTEM, is based on our own work carried out during the course of study under the
supervisionof MRAnand Sharma Sir.We assertthat statementmade andthe conclusionsdrawnare the
outcome of the projectwork.I/We furtherdeclare thatto the bestof my/our knowledge and belief the
report does not contain any part of any work which has been submitted for the award of any other
degree in this University or any other University.
Name: sourabh singh sen
Roll No:

3. Page | 3
CER TI F I CA TE
This is to certify that the report of the project submitted is an outcome of the project work entitled
STUDENT INFORMATION SYSTEM carried out by Sourabh singh Sen bearing Roll No. :3333714102 carried
out under my guidance and supervision for the award of Degree of B.E. Engineering of Chhattisgarh
Swami Vivekananda Technical University, Bhilai (C.G.),India.
To the bestof my knowledgethe report
i) Embodies the work of the candidate him/herself/themselves,
ii) Has duly been completed,
iii) Fulfills the requirement of the Ordinance relating to the B.E. degree of the
University and
iv) Is up to the desired standard for the purpose for which it is submitted.
__________________
Name : ------------
Designation:--------------
Department of Computer Science
Engineering
The project work as mentioned above is forwarded for examination.
--------------------------------------------
(Head of Department)

4. Page | 4
ABSTRACT
Student Information System (SIS) provides a simple interface for maintenance of student
information. It can be used by educational institutes or colleges to maintain the records of
students easily. The creation and management of accurate, up-to-date information regarding a
students’ academic career is critically important in the university as well as colleges. Student
information system deals with all kind of student details, academic related reports, college
details, course details, curriculum, batch details, placement details and other resource related
details too. It tracks all the details of a student from the day one to the end of the course which
can be used for all reporting purpose, tracking of attendance, progress in the course, completed
semesters, years, coming semester year curriculum details, exam details, project or any other
assignment details, final exam result and all these will be available through a secure, online
interface embedded in the college’s website. It will also have faculty details, batch execution
details, students’ details in all aspects, the various academic notifications to the staff and students
updated by the college administration. It also facilitate us explore all the activities happening in
the college, Different reports and Queries can be generated based on vast options related to
students, batch, course, faculty, exams, semesters, certification and even for the entire college.

5. Page | 5
TA B LE OF CONTENTS
Chapter Page no.
1. Introduction
1.1. Description 7
1.2. Function 8
1.3. Objective 8
1.4. Pros & Cons 9
1.5 Application 9
2. Mathodology
2.1. Literature Review 11
2.2 Database design 12
2.3 GUI 12
2.4 Software Testing 12
2.5 Requirement Plan Phase 12
2.6 Requirement specification analysis Phase 12
2.7 Design Phase 13
2.7.1 Database Design 13
2.7.2 Interface Design 13
2.7.3 Coding Design 13
2.8 RAD Mathodology 14
3. Requirements
3.1 Tools & Platform 15
3.2 Hardware & Software requirements 15
3.3 Project Category 15

6. Page | 6
4. Project Diagrams
4.1 ER Diagram 16
4.2 DF Diagram 17
4.3 Sequence Diagram 18
4.4 Use Case Diagram 19
4.5 Class Diagram 20
4.6 Context Diagram 21
5. Snapshots
5.1 Registration page 22
5.2 Fee Submission Page 22
6. Flow of Project 23
7. Database Design
7.1 Admission Table 24
7.2 Registration Table 24
7.3 Attendance Table 25
7.4 Payment Table 25
7.5 User Table 25
7.6 Module used in the Project 26
8. Conclusion 27
9. Future Scope 28
10. References 29

7. Page | 7
Chapter 1
Introduction
The information system is important in collecting all data and information of all staff or member
in one organization to be in one place. The system is normally provided very helpful task that
will replace the human as to keep it in file as the inventory or other purposes
A student information system(SIS), student management system, school administration
software or student administration systemis a management information system for education
establishments to manage student data. Student information systems provide capabilities for
registering students in courses; documenting grading, transcripts, results of student tests and
other assessment scores; building student schedules; tracking student attendance; and managing
many other student-related data needs in a school. A SIS should not be confused with a learning
management system or virtual learning environment, where course materials, assignments and
assessment tests can be published electronically. The SIS can include features that can be
considered as an enterprise resource planning or ERP system for a corporate customer. As such,
many of the issues with ERP system selection methodology, implementation, and operation of
ERP system apply too.
Fig.1.1 Student information system

8. Page | 8
Student information system can handle all the detail about a student. The details include college
details, Students personal details, Academic details etc. The student information system is an
automated version of manual Student information System. These systems vary in size, scope and
capability, from packages that are implemented in relatively small organizations to cover student
records alone, to enterprise-wide solutions such as SAFSMS which aim to cover most aspects of
running large multi-campus organizations and their online schools with significant local
responsibility. Many systems can be scaled to different levels of functionality by purchasing add-
on "modules" and can typically be configured by their home institutions to meet local needs.
1.2 Function
It include:-
 Student health records,
 Canteen Management,
 Transportation Management,
 Maintenance and reporting of student data,
 Handling inquiries from prospective students,
 Handling the admissions process,
 Enrolling new students and enabling online scheduling,
 Student accounts and financial aid processing,
 Automatically creating class and teacher schedules,
 Handling records of examinations, assessments, marks, grades and academic progression,
 Maintaining records of absences and attendance,
 Recording communications with students,
 Maintaining discipline records,
 Providing statistical reports,
 Assignments and tasks,
 Special Education / Individual Education Plan (IEP) services
 Career services management for student portfolios and matching with potential employers
 Human resources services,
 Accounting and budgeting services.
1.3 Objectives
 To manage students’ information during admission and
examination.
 Efficient utilization of human resource.
 To reduce unnecessary paper work in maintaining student information.
 Student information system is a system for education establishment to
manage student data.
 It provide capability for registering student in courses.

9. Page | 9
 Admitting students, tracking student attendance and Submitting student
documents and fee payment online.
 Ensure data integrity, privacy and security in an open access environment.
1.4 Pros and Cons
Unlike an upgrade to a web browser or a word processor, changes and upgrades to these systems
tend to have significant impact on day-to-day operations, affecting all constituents across an
institution. These systems typically touch every aspect of school operations even when only the
base modules are used. For these reasons, campus leaders weigh in the balance the pros and cons
of investments and disruptions that will be inevitable whether doing an upgrade, adding
significant customizations or replacing the SIS altogether:
 Workflow: Since these programs are tightly tied to a school's business workflow and
processes, the SIS is often at the center of internal debates as to upgrading or replacing the
SIS. Either way, changes to a SIS can have a significant impact on daily operations if not
considered carefully prior to implementation.
 Data conversion: Data conversion of historic data (transcripts, attendance, health records,
etc.) for both current and past students can also be a significant issue when considering a
transition to a newer SIS. Since most schools are required to keep historical data on past
students, considerations should be given to what information will be converted and what will
be archived.
 Customized Reports: The standardization of how and where student information is stored
varies broadly, as does the levels of automation and interoperability of various SIS vendors'
products. Over time, schools develop their own processes and procedures, often designed
around their SIS's particular strengths or weaknesses (e.g. the layout of data reports and their
frequency, if made time-consuming by the SIS). As most SISs are not perfectly compatible
with the previous SIS, upgrading can be a long and tedious process. However, institutions
justify the return on investment based on gains in administrative efficiency, reduced costs of
owning a SIS and related systems, and academic effectiveness.
 Training: SIS programs, old and new, do vary in terms of the kinds of functionality,
workflows, reporting capabilities and so on. Upgrading or implementing a new SIS calls for
training employees to use the SIS; this is factored into the institution's assessment of any
return on investment.
Like with an ERP system, schools should consider processes similar to the ERP System
Selection Methodology when selecting a SIS system. Such a process, while it may be tedious,
ensures that a cross-section of future end-users of the system can suggest more efficient ways to
handle data, enhance services to students and reduce or eliminate bottlenecks of creating silos of
data due to the limitations of a current SIS or business process.
1.5 Application
 To use for various stream student.
 To gather students information.

10. Page | 10
 Different reports and Queries can be generated based of vast options related to students,
batch, course, quota, semesters and category and even for the entire college.
 Transportation Management.
 Fees Management.
 Inventory and Assets of the school.
 Regulatory reporting and reports for accrediting bodies.

11. Page | 11
Chapter 2
Mathodology
This project methodology is needed to make sure the project that consists of software
development will be developed systematically in order to acquire a better result. The overall of
the project methodology is shown as figure below.
Fig.1.2 Mathodology of SIS
The methodology is divided to four main components which are literature review, database
design, creating a Graphical user interface (GUI) and finally is the software testing.
2.1 Literature review
The project begins with literature review where the overview of the project needs to be known.
The literature review is done by finding out numbers of lectures student and class provided,
involved for Faculty of Electronics and Computer Engineering (FKEKK), how many class and
how many lecturers contribute to this faculty. All this information need to be known in order to
provide information inside the software that is useful in arranging the database.

12. Page | 12
2.2 Database design
Database is required to improve the functionality of this project. Therefore, the first stage of
software development is to create the database. Database is a body of information made up of
related pieces of data organized so that they can be easily been manipulated by the computer. As
for the software development, it is important to have database as all the information needed can
be saved for future used.
2.3 Creation of suitable Graphic user interface (GUI)
GUI is a way to interact with a computer using pictures and other visual elements displayed on a
computer screen. The pictures and buttons used to control many Internet sites are an example of
a GUI. GUI is important to make the user easy to understand what they need to do in order to use
the software GUI must be user friendly and easy to be understood. In order to make the GUI
function, Microsoft Visual Studio coding must be inserted to make the software work properly.
2.4 Software testing
Software testing is the process used to measure the quality of developed computer software to
determine that the software meets its required results. This testing process of executing a
program is intended of finding errors.
2.5 Requirement plan phase
Before developing the system, either small or large system the proper planning needs to be put in
the first place. This is to make sure that all the activities that will execute and overall
development are under control. The purpose of planning is to prepare the workflow for project
management start from early stages of project development until end of development. The
developer need to mention that it is very important to divide the project into subtasks to make
sure about time estimation and to identify source requirement to complete this Student
Information System project.
2.6 Requirement specification analysis phase
All the requirement analysis phase will be started after the study case for this system has been
completed. Through this phase, developer will determine clearly who will use the system,
function of the system, when and where the system will be executed. Developer will begin the
study from existing system to define the strength and weakness. This is important as it can
identify the opportunities to improve the existing system to a new system. If there are any
shortcomings or defects, it can be corrected in the new system. After this research, the concept of
new system is developed. Besides, the information is collected by using fact-finding techniques
such as background reading, interviewing and observation. As a developer, it needs to analyze
the feasibility of new system, which is to improve the system as to make sure that the new

13. Page | 13
system will fulfill the user requirement. All the constraints and limitation of the new system also
need to analyze.
2.7 Design phase
Design phase started after the specification and analysis phase completed. In this step, specified
technical designs were created to the smallest detail. It is common for several alternative
solutions to be identified, but only one must ultimately be chosen as the best of the system and
users. Tradeoff may become part of the reality for the project, which may include time, scopes
and functionality. The purpose of the system designing is to create a blueprint for the new system
that will satisfy all documented requirements. There are several things to identify during system
designing such as all necessary outputs, inputs, interfaces and processes. Furthermore, for this
phase, optimal solution of the designing was developed. The main objects for the system and
relationship between object are well defined to make sure that there will be an interaction on it,
so that all the objects need to classify on their own classes. Other than that, the attribute of class
also was defined.
Also in this phase, there are few designing, which applied into new system such as database
design, interface design and coding design.
2.7.1 Database design
To design database, it considers and concerns in many aspects. The specification will be
determined by what is the data need to be stored in database. In database design, each step of the
process needs to be done very carefully for avoiding any unexpected errors. The errors might
occur in database, it can give complex problem for the system. These databases are designed by
using Microsoft Access 2003. For Student Information System database, there are seven tables
involved such as student, lecturer, activity, position, and class, list of student and list of lecturer.
2.7.2. Interface design
The purpose of interface design is to determine how the layout of the system and to make sure
that this layout suitable with user requirement. The good designing can attract the users and
supposedly not confused the users with each functions of the system. For instance, the developer
also needs to concern about user-friendly interface during designing phase. Through this system,
there are some elements, which been used to design the interface.
2.7.3 Coding design
This coding designing showed how programming language would be implemented. It also will
explain the purpose for each coding development. SQL statement is used in order to make sure
that interfaces can be connected with database.

14. Page | 14
2.8 RAD (Rapid Application Design) Methodology
This Student Information System development used RAD (Rapid Application Design)
methodology. This methodology method follows the System Development Life Cycle (SDLC)
that in a sequential and structured away. RAD is a methodology for compressing the analysis,
design, build, and test phases into a series of short, iterative development cycles. This has a
number of distinct advantages over the traditional sequential development model. Iteration
allows for effectiveness and self-correction. Studies have shown that human beings almost never
perform a complex task correctly the first time. However, people are extremely good at making
an adequate beginning and then making many small refinements and improvements. RAD
projects are typically operated with small-integrated teams comprised of developers, end users,
and IT technical resources. Small teams, combined with short, iterative development cycles
optimize speed, unity of vision and purpose, effective informal communication and simple
project management.

15. Page | 15
Chapter 3
Requirements
3.1 Tools & Platform
 Basic used software for making this website are PHP, HTML, CSS and JavaScript.
 For saving the data of student, the mysql database.
 The entire websites executes on the XAMPP server.
 To access the website, we can use any kind of web browser.
3.2 Hardware & software requirements
 It needs most recent version of Google chrome, Firefox, internet explorer, or Safari.
 Hardware required:
-CPU: Single core 2.4 GHZ.
RAM: 512.MB.
Graphic card: Intel and Nvidia.
Hard Drive: 5 Gigabytes.
Network: Broadband recommended.
Processor: Pentium.
 Operating system: windows (XP, VISTA, 7, 8, 10), Mac OS, Linux, Unix.
3.3 Project category
 It is a web based application.
 Unlike traditional application, it is accessible anytime, anywhere, via a pc with an
internet connection.
 It needs lower requirement on the end user system and simplified architecture.

16. Page | 16
Chapter 4
Project Diagrams
4.1 ER (Entities Relationship) diagram
An Entity Relationship (ER) Diagram is a type of flowchart that illustrates how “entities” such as
people, objects or concepts relate to each other within a system. ER Diagrams are most often
used to design or debug relational databases in the fields of software engineering, business
information systems, education and research. Also known as ERDs or ER Models, they use a
defined set of symbols such as rectangles, diamonds, ovals and connecting lines to depict the
interconnectedness of entities, relationships and their attributes. They mirror grammatical
structure, with entities as nouns and relationships as verbs.
ER diagrams are related to data structure diagrams (DSDs), which focus on the relationships of
elements within entities instead of relationships between entities themselves. ER diagrams also
are often used in conjunction with data flow diagrams (DFDs), which map out the flow of
information for processes or systems.
Fig.1.3 ER Diagram

17. Page | 17
4.2 DFD (Data flow diagram)
It's easy to understand the flow of data through systems with the right data flow diagram
software. This guide provides everything you need to know about data flow diagrams, including
definitions, history, and symbols and notations. You'll learn the different levels of a DFD, the
difference between a logical and a physical DFD and tips for making a DFD.
Fig.1.4 Data Flow Diagram

18. Page | 18
4.3 Sequence Diagram
A sequence diagram shows object interactions arranged in time sequence. It depicts the objects
and classes involved in the scenario and the sequence of messages exchanged between the
objects needed to carry out the functionality of the scenario. Sequence diagrams are typically
associated with use case realizations in the Logical View of the system under development.
Sequence diagrams are sometimes called event diagram.
A sequence diagram shows, as parallel vertical lines (lifelines), different processes or objects that
live simultaneously, and, as horizontal arrows, the messages exchanged between them, in the
order in which they occur. This allows the specification of simple runtime scenarios in a
graphical manner.
Fig 1.5 Sequence Diagram

19. Page | 19
4.4 Use Case Diagram
A use case diagram at its simplest is a representation of a user's interaction with the system that
shows the relationship between the user and the different use cases in which the user is involved.
A use case diagram can identify the different types of users of a system and the different use
cases and will often be accompanied by other types of diagrams as well.
Fig 1.6 Use Case Diagram

20. Page | 20
4.5 Class Diagram
A class diagram is an illustration of the relationships and source code dependencies among
classes in the Unified Modeling Language (UML). In this context, a class defines the methods
and variables in an object, which is a specific entity in a program or the unit of code representing
that entity. Class diagrams are useful in all forms of object-oriented programming (OOP). The
concept is several years old but has been refined as OOP modeling paradigms have evolved.
Fig 1.7 Class Diagram

21. Page | 21
4.6 Context Diagram
The Context Diagram shows the system under consideration as a single high-level process and
then shows the relationship that the system has with other external entities (systems,
organizational groups, external data stores, etc.). Another name for a Context Diagram is a
Context-Level Data-Flow Diagram or a Level-0 Data Flow Diagram. Since a Context Diagram
is a specialized version of Data-Flow Diagram, understanding a bit about Data-Flow Diagrams
can be helpful.
Fig 1.8 Context Diagram

22. Page | 22
Chapter 5
Snapshots
5.1 Registration Page
Fig 1.9 Registration Page
5.2 Fee Submission Page
Fig 1.10 Fee Submission Page

23. Page | 23
Chapter 6
Flow of Project
Step1. Making SRS.
Step2. Coding and developments.
 Coding for Web page design.
 Coding for Database design.
 Connectivity of database.
Step3. Testing.
 Functionality Testing.
 Usability Testing.
 Interface Testing.
 Performance Testing.
Step4. Implementation and Maintenance.

24. Page | 24
Chapter 7
Database Design
7.1 Admission table
7.2 Registration table
Field Name Data Type
Session char
Course char
Student name char
Father’s name char
Mother’s name char
DOB varchar
Gender char
Category char
Email Id varchar
Mobile No. numeric
Address varchar
Field Name Data Type Description
Session varchar --------
Admit Date numeric --------
Student Id varchar primary key
Auto-increment
Student Name char --------
Course char -------

25. Page | 25
7.3 Attendance table
Field Name Data Type
Student Id varchar
Attendace Weekly varchar
Attendence Date varchar
7.4 Payment table
Field Name Data Type
Student Id varchar (foreign key)
Payment Id varchar
Payment Number varchar
Payment Date varchar
7.5 User Table
Field Name Data Type Description
User Id Varchar primary key,
Password Varchar ---------------

26. Page | 26
7.6 Modules used in the Project
 Admission Panel
 Registration.
 New admission.
 Edit admission details.
 Manage Students
 Add/Edit details.
 Attendance.
 Fee Payment
 Fee submission.
 Pending fee.
 Contact Administrator
 Report problem.

27. Page | 27
Chapter 8
Conclusion
This paper assists in automating the existing manual system. This is a paperless work. It can be
monitored and controlled remotely. It reduces the man power required. It provides accurate
information always. Malpractice can be reduced. All years together gathered information can be
saved and can be accessed at any time. The data which is stored in the repository helps in taking
intelligent decisions by the management. So it is better to have a Web Based Information
Management system. All the stakeholders, faculty and management can get the required
information without delay. This system is essential in the colleges/hostels and universities.
As for the conclusion, the objectives for this project were achieved and functioned well as the
desired target. This system will help the Student Information System database works
systematically and will make ease the user in order to manage all the student data in the system.
This system will give a better performance in arranging the lecturer and student information
without having to do it manually. This system will help faculty’s staff to arrange student matter
and schedule faster and easier. Furthermore it will allow the lecturer to focus on other important
task in the Faculty. As the future recommendation, the project is recommended to be built with
the fully functional software that fulfills all the criteria needed and also applied with more
complicated algorithm to the system.

28. Page | 28
Chapter 9
Future Scope
 In the future student can also be able to upload as well as download notes.
 We will see the entire system more accurate and also be able to given statistics data.
 We can run the entire system in any operating system and also we have an android
application of the entire system.
 Maintain students' biographical, status, and academic information in a secure, accessible
system.
 Provide a secure online system for faculty to enter final semester grades for each student

29. Page | 29
Chapter 10
References
 Wikipedia.
 Zhibing Liu, Huixia Wang,Hui Zan “Design and implementation of student information
management system.”
 Book of Java Scripts, CSS, Visual basics.