Student Information Management

TABLES OF CONTENTS

CHAPTER NO. TITLE PAGE NO.

01 1.1 Introduction 6
1.2 Database 7
1.2.1 A Database Management System (DBMS) 7
1.2.2 Object-oriented database systems 8
1.2.3 Industry Profile 8
1.2.4 Historical Perspective 9
1.3 Characteristics of DBMS 10
1.3.1 Represent Some Aspects of real world applications 10
1.3.2 Self-Describing nature 10
1.3.3 Logical relationship between records and data 10
1.3.4 Control Data Redundancy 10
1.3.5 Query Language 10
1.3.6 Multi User and Concurrent Access 11
1.3.7 Multiple views of database 11
1.4 Purpose 12
1.5 Scope 12
1.5.1 Login module 12
1.5.2 Search module 12
1.5.3 Registration Module 12
1.5.4 User Management 13

1.6 Definitions, Acronyms and Abbreviations 13

02 2.0 Software Requirement and Specification 14
2.1 Front End: PHP 14
2.2 Early history 14
2.3 Features of php 15
2.3.1 Simple 16

Dept Of ISE, BTLITM 1

Student Information Management
2.3.2 Interpreted 16
2.3.3 Faster 16
2.3.4 Open Source 16
2.3.5 Platform Independent 16
2.3.6 Case Sensitive 16
2.3.7 Error Reporting 16
2.3.8 Real-Time Access Monitoring 16
2.3.9 Loosely Typed Language 16

2.4 Syntax 17
2.5 Back End: MySQL 18
2.5.1 Features of MySQL 18
2.5.2 Stored Procedure 20

2.6 Syntax 20
03 3.1 Database Design 21
3.2 Overall description 21
3.2.1 Product Perspective 21

3.2.2 Product Functions 22

3.2.3 User Classes and Characteristics 22
3.2.4 Operating Environment 22
3.2.5 Constraints 22
3.2.6 Use case model 22

3.2.7 Assumptions & dependencies 23

3.3 Specific Requirements 23

3.3.1 Use Case Reports 23
3.3.2 Basic Flow 23
3.3.3 Alternative Flow 24
3.3.4 Basic Flow 25

3.3.5 Basic Flow: The Administrator logs 27

3.4 Functional Requirements 29

Dept Of ISE, BTLITM 2

Student Information Management

3.5 Non- Functional Requirement 29

3.5.1. Performance Requirements 29

3.5.2. Safety Requirements 29

3.5.3. Security Requirements 29

3.6 Overall System Design Objectives 30

3.6.1 Structure of Design Document 30

3.7 System Architecture Design 31

3.7.1 System Architecture 31

3.8 Entity Relationship Diagram 32

3.9 Functional Design Description 33

3.9.1 Data Flow Diagram 33

3.10 Decision Tree 3

04 4.0 RESULTS 35

4.1 Home page 35

4.2 login page 36

4.3 login information page 37
4.4 Student Information 38
4.6 Search and Login Records 39

05 5.1 CONCLUSION 40
5.2 SCOPE OF THE PROJECT 40

06 BIBLIOGRAPHY 41

Dept Of ISE, BTLITM 3

Student Information Management

ABSTRACT

This project “Student Information Management System” provides us a simple

interface for maintenance of student information.It can be used by educational institutes or
colleges 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.

Throughout the project the focus has been on presenting information in an easy and
intelligible manner. The project is very useful for those who want to know about Student
Information Management Systems and want to develop softwares/websites based on the same
concept.

The project provides facilities like online registration and profile creation of students
thus reducing paperwork and automating the record generation process in an educational
institution.

Dept Of ISE, BTLITM 4

Student Information Management

ACKNOWLEDGEMENT

The satisfaction and euphoria that accompanies the successful completion of any task

would be incomplete without the people who made it possible, whose constant guidance and

encouragement crowned our efforts with success.

We fall short of words to thank and express gratitude to our beloved Principal,

Dr. Padmanabha S.

We wish to thank our Head of the Department Dr. Panduranga Rao M V, Professor

and HOD, Department of Computer Science and Engineering, for his kind co-operation and

encouragement. We thank him for providing us this opportunity.

We convey our regards and thanks to our guide Mr. Madhu C.K, M Tech for his

immense support, guidance, specifications and ideas without which the project would have

been completed without full merits.

We thank our friends and family for their immense support and encouragement in the

completion of the project.

Finally a note of thanks the department of ISE, the staff both teaching and

non-teaching staff for their co-operation extended to us.

We also thank VTU for providing such an interesting assignment, which helped us in

experiencing the intricate complexities of various phases of software development.

Dept Of ISE, BTLITM 5

Student Information Management

CHAPTER 1

1.1 Introduction

Student Information Management System deals with all kind of student details,
academic related reports, college details, course details, curriculum, batch details and other
resource related details too. It tracks all the details of a student from the day one to the end of
his 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 etc.

Our design can facilitate us to explore all the activities happening in the college, even
we can get to know which faculty is assigned to which course, the current status of a student,
attendance percentage of a student and upcoming requirements of a student. The student
management system is an automated version of manual Student Management System. It can
handle all details about a student. The details include college details, subject details, student
personnel details, academic details, exam details etc.

In case of manual system they need a lot of time, manpower etc. Here almost all work
is computerized. So the accuracy is maintained. Maintaining backup is very easy. It can do
with in a few minutes. Our system has two type of accessing modes, administrator and user.
Student management system is managed by an administrator. It is the job of the administrator
to insert update and monitor the whole process. When a user log in to the system. He/she
would only view details of the student. He/she can’t perform any changes. Our system has
seven modules, they are administrator, student, course, department, exam, attendance, and
section. These modules and its attributes with entity relationship module presented in the ER
diagram sesion.

Dept Of ISE, BTLITM 6

Student Information Management

1.2 Database

A database is simply an organized collection of related data, typically stored on disk,

and accessible by possibly many concurrent users. Databases are generally separated into
application areas. For example, one database may contain Human Resource (employee and
payroll) data; another may contain sales data; another may contain accounting data; and so
on. Databases are managed by a DBMS.

1.2.1 A Database Management System (DBMS)

A Database Management System (DBMS) is a set of programs that manages any

number of databases.

A DBMS is responsible for:

● accessing data
● inserting, updating, and deleting data
● security
● integrity, facilitated by:
a. locking
b. logging
c. application-defined rules, including triggers
● supporting batch and online programs
● facilitating backups and recoveries
● optimizing performance
● maximizing availability
● maintaining the catalogue and directory of database objects
● managing the buffer pools
● acting as an interface to other systems programs
● supporting user interface packages, such as the popular SQL interface for
relational database systems

Dept Of ISE, BTLITM 7

Student Information Management
There are 3 traditional types of database management systems: hierarchical, relational,
and network. Current popular database systems include Oracle; Sybase (same as
Microsoft's SQL Server but on a different platform); IBM's DB2, IMS, and
SQL/DS; Ingres; Informix; and smaller, but reasonably powerful off-the-shelf products such
as dBase, Access, Foxpro, Paradox, and dozens of others.

The choice of a database product is often influenced by factors such as:

● the computing platform (i.e., hardware, operating system)

● the volume of data to be managed
● the number of transactions required per second
● existing applications or interfaces that an organization may have
● support for heterogeneous and/or distributed computing
● cost

1.2.2 Object-oriented database systems

Object-oriented database systems are currently in development. They allow us to

model and manipulate complex data structures and objects, and hence support many new
applications, including CAD/CAM. As of 1996, object-oriented databases represent a very
small segment of the commercial market (perhaps 1%). It is interesting to note that some
major DBMS vendors are starting to support complex objects (such as images) in their
relational products.

1.2.3 Industry Profile

The database industry generated about $7 billion in revenue in 1994 and is growing at
35% per year. Among software industries, it is second only to operating system software. All
the leading corporations in this industry are US-based: IBM, Oracle, Sybase, Informix,
Computer Associates, and Microsoft. In addition, there are two large specialty vendors, both
also US-based: Tandem, selling over $1 billion per year of fault-tolerant transaction
processing systems, and AT&T-Teradata, selling about $500 million per year of data mining
systems. A relatively modest federal research investment, complemented by an also-modest
industrial research investment, has led directly to our nation's dominance of this key industry.

Dept Of ISE, BTLITM 8

Student Information Management
1.2.4 Historical Perspective

Companies began automating their back-office bookkeeping in the 1960s. COBOL

and its record-oriented file model were the work-horses of this effort. Typically, a batch of
transactions was applied to the old-tape-master, producing a new-tape-master and printout for
the next business day.

During this era, there was considerable experimentation with systems to manage an
online database that could capture transactions as they happened, rather than in daily batches.
At first these systems were ad hoc, but late in the decade "network" and "hierarchical"
database products emerged. A network data model standard (DBTG) was defined, which
formed the basis for most commercial systems during the 1970s. Indeed, in 1980
DBTG-based Cullinet was the leading software company.

Dept Of ISE, BTLITM 9

Student Information Management

1.3 Characteristics of DBMS

1.3.1 Represent Some Aspects of real world applications

A database represents some features of real world applications. Any change in the real
world is reflected in the database. For example, let us take railway reservation system; we
have in our mind some certain applications of maintaining records of attendance, waiting
list,train arrival and departure time, certain day etc. related to each train.

1.3.2 Self-Describing nature

A database is of self-describing nature; it always describes and narrates itself. It

contains the description of the whole data structure, the constraints and the variables. It
makes it different from traditional file management system in which definition was not the
part of application program. These definitions are used by the users and DBMS software
when needed.

1.3.3 Logical relationship between records and data

A database gives a logical relationship between its records and data. So, a user can
access various records depending upon the logical conditions by a single query from the
database.

1.3.4 Control Data Redundancy

DBMS follows the rules of normalization, which splits a relation when any of its
attributes is having redundancy in values. Normalization is a mathematically rich and
scientific process that reduces data redundancy.

1.3.5 Query Language

DBMS is equipped with query language, which makes it more efficient to retrieve and
manipulate data. A user can apply as many and as different filtering options as required to
retrieve a set of data. Traditionally it was not possible where file-processing system was used.

Dept Of ISE, BTLITM 10

Student Information Management
1.3.6 Multi User and Concurrent Access

DBMS supports multi-user environment and allows them to access and manipulate
data in parallel. Though there are restrictions on transactions when users attempt to handle the
same data item, but users are always unaware of them.

1.3.7 Multiple views of database

Basically, a view is a subset of the database. A view is defined and devoted for a user
of the system. Different users of the system may have different views of the same system.
Every view contains only the data of interest to a user or a group of users. It is the
responsibility of users to be aware of how and where the data of their interest is stored.

Dept Of ISE, BTLITM 11

Student Information Management

1.4 Purpose

The objective of Student information 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 Information Management 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
Student information System and is intended to help any organization to maintain and manage
its student’s personal data.

1.5 Scope

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.

1.5.1 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.

1.5.2 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.

1.5.3 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.

Dept Of ISE, BTLITM 12

Student Information Management
1.5.4 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

1.6 Definitions, Acronyms and Abbreviations

● Personal details: Details of student such as user id, phone number, address, image,
resume, e-mail address etc.
● Contact details: Details of contact associated with the student.
● SRS: System requirement Specification.
● WWW: World Wide Web.
● Administrator: A Login Id representing the user is an administrator & can access
all the records details.

Dept Of ISE, BTLITM 13

Student Information Management

CHAPTER 2
2.0 Software Requirement and Specification
2.1 Front End: PHP

PHP: Hypertext Preprocessor 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.

It was originally created by Rasmus Lerdorf in 1994, the PHP reference

implementation is now produced by The PHP Group. PHP originally stood for Personal
Home Page, but it now stands for the recursive initialism PHP: Hypertext Preprocessor.

PHP code may be embedded into HTML code, or it can be used in combination with
various web template systems, web content management systems, and web frameworks. PHP
code is usually processed by a PHP interpreter implemented as a module in the web server or
as a Common Gateway Interface (CGI) executable. The web server combines the results of
the interpreted and executed PHP code, which may be any type of data, including images,
with the generated web page. PHP code may also be executed with a command-line interface
(CLI) and can be used to implement standalone graphical applications.

2.2 Early history

PHP development began in 1994 when Rasmus Lerdorf wrote several Common
Gateway Interface (CGI) programs in C, which he used to maintain his personal homepage.
He extended them to work with web forms and to communicate with databases, and called
this implementation "Personal Home Page/Forms Interpreter" or PHP/FI.

PHP/FI could be used to build simple, dynamic web applications. To accelerate bug reporting
and improve the code, Lerdorf initially announced the release of PHP/FI as "Personal Home

Dept Of ISE, BTLITM 14

Student Information Management
Page Tools (PHP Tools) version 1.0" on the Usenet discussion group
comp.infosystems.www.authoring.cgi on June 8, 1995. This release already had the basic
functionality that PHP has today. This included Perl-like variables, form handling, and the
ability to embed HTML. The syntax resembled that of Perl, but was simpler, more limited
and less consistent. A development team began to form and, after months of work and beta
testing, officially released PHP/FI 2 in November 1997.

The fact that PHP was not originally designed, but instead was developed organically
has led to inconsistent naming of functions and inconsistent ordering of their parameters.
In some cases, the function names were chosen to match the lower-level libraries which PHP
was "wrapping", while in some very early versions of PHP the length of the function names
was used internally as a hash function, so names were chosen to improve the distribution of
hash values.

2.3 Features of php

It is most popular and frequently used world wide scripting language, the main
reason of popularity is; It is open source and very simple.

● Simple
● Faster
● Interpreted
● Open Source
● Case Sensitive
● Simplicity
● Efficiency
● Platform Independent
● Security
● Flexibility
● Familiarity
● Error Reporting
● Loosely Typed Language
● Real-Time Access Monitoring

Dept Of ISE, BTLITM 15

Student Information Management

2.3.1 Simple: It is very simple and easy to use, compare to other scripting language it is
very simple and easy, this is widely used all over the world.

2.3.2 Interpreted: It is an interpreted language, i.e. there is no need for compilation.

2.3.3 Faster: It is faster than other scripting language e.g. asp and jsp.

2.3.4 Open Source: Open source means you no need to pay for use php, you can free
download and use.

2.3.5 Platform Independent: PHP code will be run on every platform, Linux, Unix,
Mac OS X, Windows.

2.3.6 Case Sensitive: PHP is case sensitive scripting language at time of variable
declaration. In PHP, all keywords (e.g. if, else, while, echo, etc.), classes, functions, and
user-defined functions are NOT case-sensitive.

2.3.7 Error Reporting: PHP have some predefined error reporting constants to generate
a warning or error notice.

2.3.8 Real-Time Access Monitoring: PHP provides access logging by creating the
summary of recent accesses for the user.

2.3.9 Loosely Typed Language: PHP supports variable usage without declaring its
data type. It will be taken at the time of the execution based on the type of data it has on its
value.

Dept Of ISE, BTLITM 16

Student Information Management
2.4 Syntax
The following "Hello, World!" program is written in PHP code embedded in an
HTML document:

<!DOCTYPE html>
<html>
<head>
<title>PHP Test</title>
</head>
<body>
<?php echo '<p>Hello World</p>'; ?>
</body>
</html>

However, as no requirement exists for PHP code to be embedded in HTML, the

simplest version of Hello, World! may be written like this, with the closing tag omitted as
preferred in files containing pure PHP code

<?='Hello world';

Dept Of ISE, BTLITM 17

Student Information Management
2.5 Back End: 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.

2.5.1 Features of MySQL

● Relational Database Management System (RDBMS): MySQL is a relational

database management system.

● Easy to use: MySQL is easy to use. You have to get only the basic knowledge of
SQL. You can build and interact with MySQL with only a few simple SQL
statements.

● It is secure: MySQL consist of a solid data security layer that protects sensitive data
from intruders. Passwords are encrypted in MySQL.

● Client/ Server Architecture: MySQL follows a client /server architecture. There is a

database server (MySQL) and arbitrarily many clients (application programs), which
communicate with the server; that is, they query data, save changes, etc.

● Free to download: MySQL is free to use and you can download it from MySQL
official website.

● It is scalable: MySQL can handle almost any amount of data, up to as much as 50

million rows or more. The default file size limit is about 4 GB. However, you can
increase this number to a theoretical limit of 8 TB of data.

Dept Of ISE, BTLITM 18

Student Information Management
● Compatible on many operating systems: MySQL is compatible to run on many
operating systems, like Novell NetWare, Windows* Linux*, many varieties of UNIX*
(such as Sun* Solaris*, AIX, and DEC* UNIX), OS/2, FreeBSD*, and others.
MySQL also provides a facility that the clients can run on the same computer as the
server or on another computer (communication via a local network or the Internet).

● Allows roll-back: MySQL allows transactions to be rolled back, commit and crash
recovery.

● High Performance: MySQL is faster, more reliable and cheaper because of its
unique storage engine architecture.

● High Flexibility: MySQL supports a large number of embedded applications which

makes MySQL very flexible.

● High Productivity: MySQL uses Triggers, Stored procedures and views which
allows the developer to give a higher productivity.

The DBMS accepts SQL comma, panels generated from a variety of user interfaces,
produces query evaluation plans, executes these plans against the databc4'le, and returns the
answers. (This is a simplification: SQL commands can be embedded in host-language
application programs, e.g., Java or COBOL programs).

When a user issues a query, the parsed query is presented to a query optimizer, which
uses information about how the data is stored to produce an efficient execution plan for
evaluating the query. An execution plan is a blueprint for evaluating a query, usually
represented as a tree of relational operators (with annotations that contain additional detailed
information about which access methods to use, etc.).

The DBMS accepts SQL comma, panels generated from a variety of user interfaces,
produces query evaluation plans, executes these plans against the databc4'le, and returns the
answers. (This is a simplification: SQL commands can be embedded in host-language
application programs, e.g., Java or COBOL programs. When a user issues a query, the parsed
query is presented to a query optimizer, which uses information about how the data is stored
to produce an efficient execution plan for evaluating the query. An execution plan is a
blueprint for evaluating a query, usually represented as a tree of relational operators (with

Dept Of ISE, BTLITM 19

Student Information Management
annotations that contain additional detailed information about which access methods to use,
etc.).

Set of Basic Commands in SQL:

● CREATE
● INSERT
● DELETE
● UPDATE
● ALTER
● ADD
● MODIFY
● DROP
● SELECT

2.5.2 Stored Procedure:

A stored procedure is a set of SQL statements with an assignment name, which are
stored in a relational database management system as a group, so it can be reused and shared
by multiple programs.

2.6 Syntax:
CREATE PROCEDURE <procedure name><parameter>
< Local declaration>
< Procedure body>
CREATE FUNCTION <function name><parameter>
<Return type>
<Local declaration>
<Function body>

Dept Of ISE, BTLITM 20

Student Information Management

CHAPTER 3
3.1 Database Design
Database is critical for all businesses. A good database does not allow any form of
anomalies and stores only relevant information in an ordered manner. If a database has
anomalies, it is affecting the efficiency and data integrity. For example, delete anomaly arise
upon the deletion of a row which also forces other useful data to be lost. As such, the tables
need to be normalised. This fulfils the last objective of ensuring data are accurate and
retrieved correctly. For the database of this project, the tables are normalised to BCNF as
shown below.

admin(id, name, password)

faculty(id, name, password)

3.2 OVERALL DESCRIPTION

3.2.1 Product Perspective :

Student Information System is aimed towards recording a considerable number of

student records and needs database assistance for managing records of students. Interface
design should be user-friendly, ‘quick to learn’ and reliable for the above purpose.

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

depend on the availability of data. 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 database

3.2.2 Product Functions :

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.

Dept Of ISE, BTLITM 21

Student Information Management
3.2.3 User Classes and Characteristics :

There are mainly two kinds of users for the product.

The users include:

● Administrator
● Student

3.2.4 Operating Environment :

● The product can run windows operating system

3.2.5 Constraints :

● Every user must be comfortable using computer.

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

3.2.6 USE CASE MODEL :

Figure 3.1: shows the use case model of student information system

Dept Of ISE, BTLITM 22

Student Information Management

Administrator: Responsible for managing student records.

● Login
● Update student details
● Search student details
● Display student details
● Enable/Disable student

3.2.7 Assumptions & dependencies

● Administrator is created in the system already.

● Roles and tasks are predefined.

3.3 Specific Requirements:

3.3.1 Use Case Reports

Administrator: Responsible for managing student details.

Use-case: Login

Goal in context: Gain access to the database

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

Preconditions: The Administrator must be login in order for this use case to begin.

3.3.2 Basic Flow:

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

Dept Of ISE, BTLITM 23

Student Information Management
3.3.3 Alternative Flow:

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

Post conditions:

The database state is unchanged by this use case.

Figure 3.2 : Use Case Report- Login into the student database

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.

Dept Of ISE, BTLITM 24

Student Information Management
3.3.4 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.

Dept Of ISE, BTLITM 25

Student Information Management
Use Case Report:

Figure 3.3 Use Case Report- Edit Student Details Into Database

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

Dept Of ISE, BTLITM 26

Student Information Management
3.3.5 Basic Flow: The Administrator logs

The Administrator logs onto the System.

The Administrator can edit following keys:

● First/last name
● Gender
● DOB
● Contact no
● Qualification
● City
● Email
● Address
● Description

The system updates the database according to edited details.

The student details are edited in the database.

Dept Of ISE, BTLITM 27

Student Information Management
Alternative Flow: There is no alternative flow of this use case diagram.

Post conditions: The student details get updated in the database.

Figure 3.4 Use Case Report- Edit student detail into the database

Dept Of ISE, BTLITM 28

Student Information Management

3.4 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.

3.5 Non- Functional Requirement :

3.5.1. 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.

3.5.2. 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.

3.5.3. 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.

Dept Of ISE, BTLITM 29

Student Information Management

3.6 Overall System Design Objectives

The overall system design objective is to provide an efficient, modular design that
will reduce the system’s 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.

3.6.1 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.

Dept Of ISE, BTLITM 30

Student Information Management

3.7 System Architecture Design

3.7.1 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.

Figure 3.5 Architecture design

Dept Of ISE, BTLITM 31

Student Information Management

3.8 Entity Relationship Diagram

An entity-relationship diagram (ERD) is crucial to creating a good database design.

It is used as a high-level logical data model, which is useful in developing a conceptual
design for databases.

An entity is a real-world item or concept that exists on its own. Entities are equivalent
to database tables in a relational database, with each row of the table representing an instance
of that entity.

An attribute of an entity is a property that describes the entity. A relationship is the

association that describes the interaction between entities. Cardinality, in the context of ERD,
is the number of instances of one entity that can, or must, be associated with each instance of
another entity. In general, there may be one-to-one, one-to-many, or many-to-many
relationships.

Figure3.6 Entity Relationship Diagram

Dept Of ISE, BTLITM 32

Student Information Management

3.9 Functional Design Description

3.9.1 Data Flow Diagram :

Figure 3.7 Data flow diagram

Dept Of ISE, BTLITM 33

Student Information Management

3.10 Decision Tree

Figure 3.8 Decision Tree

Dept Of ISE, BTLITM 34

Student Information Management

CHAPTER 4

4.0 RESULTS

4.1 Home page

Snapshot 4.1 home page

This is the homepage / index page of the student information system

Dept Of ISE, BTLITM 35

Student Information Management
4.2 login page

Snapshot 4.2 login page

The system prompts the administrator for the username and password. The
Administrator enters the user name and password. The system verifies the password and sets
the user’s authorization.

Dept Of ISE, BTLITM 36

Student Information Management
4.3 login information page

Snapshot 4.3 login information page

The Administrator logs onto the System, and provides sufficient details of the student.
The system updates the database according to details.

Dept Of ISE, BTLITM 37

Student Information Management
4.4 Student Information

Snapshot 4.4 student information page

The Administrator can edit following keys:

● First/last name
● Gender
● DOB
● Contact no
● Qualification
● City
● Email
● Address
● Description

The system updates the database according to edited details.

Dept Of ISE, BTLITM 38

Student Information Management
4.6 Search and Login Records

Snapshot 4.5 search and login records

login records and state of the student database. 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

Dept Of ISE, BTLITM 39

Student Information Management

CHAPTER 5

5.1 CONCLUSION:

The need for available secure and reliable information solution is heightened by the
increasing dependence on systems and database technologies to provide educational services,
develop efficient academic products, administer daily activities and perform both short and
long term management functions.

Using database technology as a case study, this project has elaborated on the technical
and operational requirements of developing an academic information system. Issues on web
and database concept and technologies,analysis and design tools, security and content
maintenance were adequately explained,

These technologies have come to stay, no doubt that every organization, institution
and government parastatal wants to join the e-race.Designing a functional academic database.

5.2 SCOPE OF THE PROJECT

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.

● The Student Information Management System(SIMS) can be enhanced to include

some other functionality like marks,attendance management.
● Talent management of students based on their performance evaluation can be added.
● Online class functionality can be added.
● Online exam functionality can be added.
● Online resume builder functionality can also be added.

Dept Of ISE, BTLITM 40

Student Information Management

CHAPTER 6

BIBLIOGRAPHY
• PHP book by Vasvani (TMH publications).

• Beginning PHP5 by WROX.

• www.google.com.

• www.wikipedia.com

• www.w3schools.com

• Informatics practices by Sumita Arora.

• Head First PHP & MySQL by Lynn Beighley and Michael Morrison(O’Reilly)

Dept Of ISE, BTLITM 41