Student information system literally means the general information systems for maintaining and
providing student information. It exists in all the schools, colleges, universities and any other
education institutions. However, those information systems vary. Some of them are paper based;
heavily manual work is involved in managing and maintaining information such as student
personal records files. However, recently, most schools, even down to the very smallest, utilize
computers in some way or another. The uses to which the computers are put vary enormously,
ranging from word processing and spreadsheet through to worldwide on-line access, complicated
user access permission system and vast functionalities.
Why do university schools need Student Information System?
It is probably true that many of todays business simply could not function effectively without
automated information processing systems of some form or another, so do university schools. All
of them have common tasks such as collecting, storing and processing information regarding
their students, staff and the work done within the department. With the increase of information, it
is unwise to adopting the traditional paper based system which is slow to access and therefore,
inefficient. Recent years, many systems were developed either by the universities or the software
companies in order to partially automate many of the processes carried out by the department.
Those developments dramatically reduce the time take in searching information and should
enable the school to maintain precise and up-to-date information. For example, previously,
students would have to enquire for much of his information from the school student office, which
required more time and effort, particularly from members of staff. The new system is more
efficient and also often presents more accurate information. However, those systems vary even
within the same university. Some are quite well developed and implemented, some still adopting
the inferior and out of-date technology.
Approaches to system development
The choice of system development approach will heavily influence the quality of the system
being produced. Therefore, make a right choice of appropriate system development approach is
vital before develop an actual system. Systems develop literature reviews showed two main
approaches - the original hard systems approach (more relevant to technical, engineered systems)
and the more recent soft systems approach (more relevant to human and social systems).
Without a Student information 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 .
Login module: Login module will help in authentication of user accounts. Users who have valid
login id and password can only login into their respective accounts.
Search module: Suppose there are hundreds of students and from this we have to search a
particular student and we know the name of the student .In manual system it is a tedious task
though we know the name of the student, but using this module we can easily search the student
by specifying the name of the student in the search criteria. Thus this module will help the
administrator in searching the student with various criteria easily.
Registration Module and Account Management: This module will help the student get
registered from anywhere if internet is present .This module will really simplify the task of on
paper registration. Also after successful registration the user can update information and change
their password as and when required.
User Management: This module will help the administrator in enabling/disabling a user account
and updating user information as required.
Purpose of project is to maintain details of the students such as storing information about:
Student id
Student password
Student name
Student DOB
Student mailing address
Gender
Registration date
Student status
Contact no
Qualification
City
Resume
Image
Technologies:
PHP.
MYSQL
JAVASCRIPT
HTML
CSS
The website Student Information 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.
Product Functions
There are two different users who will be using this product:
Administrator who can view and edit the details of any students.
Students who can view their details as well as they can edit their details.
The features that are available to the Administrator are:
An Administrator can login into the system and perform any of the available operations.
Can enable/disable student.
Can edit student information to the database.
Can make search for a specific student.
Can access all the details of the student.
The features that are available to the student are:
Student can login into the system and can perform any of the available options. Can view
his/her personal details.
Can edit his/her personal details Can upload his/her resume.
Can upload his/her image.
User Classes and Characteristics:
There are mainly two kinds of users for the product.
The users include:
Administrator
Student
Operating Environment:
The product can run on any browser.
Constraints:
Every user must be comfortable using computer.
All operations are in English so user must have basic knowledge of English.
USE CASE MODEL
Use Case Model
Administrator: Responsible for managing student records.
Login into the website
Update student details
Search student details
Display student details
Enable/Disable student
Student: Has the access rights to view and edit their personal details.
Login into the website
Display student details
Edit their details
Upload their images
Upload their resumes
Assumptions & dependencies
Administrator is created in the system already.
Roles and tasks are predefined.
Specific Requirements
Use Case Reports
Administrator: 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 users 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
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 personal
details of the students already existing in the database on the screen.
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.
The Administrator search the student from following keys:-
Student id
First/last name
Registration date
Status
The System prompts for the student detail from one of the above keys. The student details
are displayed on the screen.
Alternative Flow:
Student Not Found
If in the Display a student sub-flows, a student with the specified id number does not exist, The
system displays an error message. The Administrator can then enter a different id number or
cancel the operation, at which point the use case ends.
Post conditions:
The student details are displayed on the screen already existing in the system. The state of the
system remains unchanged.
Use Case: Edit student details
Goal in context: Edit the details of a student
Brief Description: This use case is used when the administrator wants to edit the personal
details of the himself/herself already existing in the database.
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
Basic Flow:
The Administrator logs onto the System.
The Administrator can edit following keys:-
o First/last name
o Gender
o DOB
o Contact no
o Qualification
o City
o Email1
o Email2
o Address
o Description
The Website updates the database according to edited details. The student details are edited in the
database.
Alternative Flow:
There is no alternative flow of this use case diagram.
Post conditions:
The student details get updated in the database.
The Administrator logs onto the System.
The Administrator can edit following keys:-
o First/last name
o Gender
o DOB
o Contact no
o Qualification
o City
o Email1
o Email2
o Address
o Description
The Website updates the database according to edited details. The student details are edited in the
database.
Alternative Flow:
There is no alternative flow of this use case diagram.
Post conditions:
The student details get updated in the database.
Student
Use Case: student registration
Goal in context: Registration of a student
Brief Description: This use case is used when the student register himself/herself in the database
online.
Preconditions:
The Student must accessed the website in order for this use case to begin.
The user id must be unique and entered correctly.
Basic Flow:
The Student enters into the website.
The student fill his/her details from the following keys:-
o Student id
o password
o First/last name
o Status
o Gender
o DOB
o Contact no
o Qualification
o City
o Email1
o Email2
o Address
o Description
o Resume
o Image
The System details are added to the database. The student details are
displayed on the screen.
Alternative Flow:
User ID not unique: if the user id entered is not unique then it will show an error message.
Post conditions:
The student get registered on the website and to login into that particular the administrator must
enable it
Use-case: Login into the website
Goal in context: Gain access to the website
Brief Description: This use case is used when the student wants to access the website
Preconditions: The Administrator must enabled the particular student onto the website in order
for this use case to begin.
Basic Flow:
The website prompts the student for the user name and password. The Student
enters the user name and password.
The website verifies the password and sets the users authorization. The Student is
given access to the website to perform his tasks.
Alternative Flow:
The Student enters invalid username and password then he will not be allowed to enter the
website.
Use Case Report- Login into the system
Use Case: Edit student details
Goal in context: Edit the details of a student
Brief Description: This use case is used when the student wants to edit the personal details of
the himself/herself already existing in the database.
Preconditions:
The Student 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 must be
enabled by administrator.
Basic Flow:
The Student logs onto the System.
The Student can edit following keys:-
First/last name
Gender
DOB
Contact no
Qualification
City
Email1
Email2
Address
Description
The Website updates the database according to edited details. The student details are edited in the
database.
Alternative Flow:
There is no alternative flow of this use case diagram.
Post conditions:
The student details get updated in the database.
Functional Requirements
The Administrator will be given more powers (enable/disable/ update) than other users.
It will be ensured that the information entered is of the correct format. For example name cannot
contain numbers. In case if incorrect form of information is added, the user will be asked to fill
the information again.
The system can be accessed anytime.
Non- Functional Requirement
Performance Requirements:
The proposed system that we are going to develop will be used as the Chief performance system
for providing help to the organization in managing the whole database of the student studying in
the organisation. Therefore, it is expected that the database would perform functionally all the
requirements that are specified.
Safety Requirements:
The database may get crashed at any certain time due to virus or operating system failure.
Therefore, it is required to take the database backup.
Security Requirements:
We are going to develop a secured database. There are different categories of users namely
Administrator, Student who will be viewing either all or some specific information form the
database.
Depending upon the category of user the access rights are decided. It means if the user is an
administrator then he can be able to modify the data, append etc. All other users only have the
rights to retrieve the information about database.
DESIGN PHASE
The Design Document will verify that the current design meets all of the explicit requirements
contained in the system model as well as the implicit requirements desired by the customer.
The overall system design objective is to provide an efficient, modular design that will reduce
the systems complexity, facilitate change and result in an easy implementation. This will be
accomplished by designing strongly cohesion system with minimal coupling. In addition, this
document will provide interface design models that are consistent user friendly and will provide
straight forward transition through the various system functions.
Structure of Design Document
System Architecture Design The System architecture section has detailed diagram of the
system, server and client architecture.
Data Design The data Design include an ERD as well as Database design.
Functional Design Description This section has the functional partitioning from the SRS, and
goes into great detail to describe each function.
System Architecture Design
System Architecture
The SIMS is a system which contain major part which include: student Detail, Student image and
resume.
The user selects one of the available options as an input to the system. According to the input by
the user the system acts and the rest of the functions are performed accordingly. The
administrator can operate on any student details. But the normal student or users can only access
their details of all the functionalities.
Data Design
Entity Relationship Diagram:
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.
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.
MySQL
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 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.
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. 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.
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.
