Professional Documents
Culture Documents
Mounika Batch
Mounika Batch
Introduction
Student Online admissions are a vital part of any university’s running because students are
what keep a University alive. The Student admission is one of the most important activities within a
university as one cannot survive without students. A poor admissions system can mean fever
students being admitted into a university because of mistakes or an overly slow response time.
Online Student Registration is the software which is helpful for students as well as the
department In this project, the student is facilitated by the online system for registering students,
add subjects and fee structure 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 delete a user.Through this
online system we overcome many Problems. Time and Money is saved.Nothing is done
manually. Long lines in the department for these issues.
1.1 Purpose
The purpose of this SRS document is to allow the registration of students in particular
provides. It will also facilitate keeping all the records of students, such as their id, name,
address DOB, etc. So all the information about a student will be available in a few seconds.
Overall, it will make Student Online Registration System an easier job for the administrator and the
The main purpose of this SRS document is to illustrate the requirements of the project Online
Student Registration System and is intended to help any organization to maintain and
1.2 Scope
Without an Online Student Registration System, managing and maintaining the details of
the student is a tedious job for any organization.
Student online registration 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. User who have valid
login id and password can only login into respective accounts.
Update/Delete Module: Suppose there are hundreds of students and from this we have to
update/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 update/delete student by specifying the name of
the student in the search criteria .
User Management: This module will help the administrator in enabling
disabling a user account and updating user information as required.
1.3 Overview
The purpose this documents is to present a detailed description of the OSRS. It will explain the
purpose and features of the software , the interfaces of the software, what the software will do,
the constraints under which it must operates and how the software will react to external stimuli.
This document is intended for both the end users and the developers of the software.
Specific design and implementation details will be specified in a future document. The student
registration system has to handle records for many students and maintenance was difficult.
Though it has used an information system, it was totally manual. Hence there is a need to
upgrade the system with a computer based information system which is Online Student
Registration System.
2. Overall Description
This section will give an overview of the whole system. The system will be explained in its
context to show how the system interacts with other systems and introduce the basic functionality
of it. At last, the constraints and assumptions for the system will be presented.
In Online Student Registration System, the student is facilitated by the online system for
registering students, add subjects and fee structure Our Student Online Registration System deals
with the various activities related to the students.
systems which depend on paper work for recording book and user’s information. This software
is developed specifically to cater the flexible feeding requirement of a student and is totally self-
contained and works efficiently. In online student registration system minimize waste of time. It
provides a simple database and a good level of normalization will make sure that the user is
User interfaces
The application will have a user friendly and menu based interface.
4GB HD space required for a typical live system with 1000-2000 events.
Network Card
Printer (If required)
Server side
The web application wil be hosted on one of the department’s Linux servers and connecting to
one of the school Oracle Database server. The web server is listening on the web standard port, port
80.
Client Side
The system is a web based application; clients are requiring using a modern web browser
Adobe Dreamweaver
Server side
An Apache Web server will accept all requests from the client. A development database will
be hosted locally (using MySQL); the production database is hosted centrally (using Oracle
2.4 Operations
The normal and special operations required by the user such as:
Product Functions The website will allow access only to authorized users with specific roles (Administrator-
Student role
On the register form, student should enter all their detail such as their name,
numbers, Email and contact number. After, the system allow student to change
Administration role
The system administrator must be able to: deactivate and reactivate student account login
2.5 User Characteristics
End Users
examinations.
Administrator
This system will not take care of any virus problem, which might occur either on the Client
or the server system. Avoiding the use of pirated software and ensuring that floppies and
other removable media are
scanned for viruses before use could minimize the possibility of viral infection.
Constraints
The Information of all users, subjects and allocations must be stored in a database that
is accessible by every connected system.
Users may access from any system connected to the online database.
Users must have their correct usernames and passwords to enter into their accounts.
3. Specific Requirements Software
This section contains all of the functional and quality requirements of the system. It
The following subsections of the SRS document provide an overview of the Entire
SRS.
Benefits: This website reduces the manual work, maintaining accuracy, increasing
This section provides a detailed description of all inputs into and outputs from the
system. It also gives a description of the hardware, software and communication interfaces
User Interfaces:
Login Name
Institute Name
Email Id
Password
Login Screen: Fields available on this screen are:
Login Name
Password
Student ID
Student Name
Student ID
Student Name
It deals with the functionalities required from the system which are as follows:
student registration
3.3Performance Requirements
This subsection specifies numerical requirements placed on the software or on the
include:
System Analysis is a detailed study of the various operations performed by a system and
their relationships within and outside of the system. Here the key question is- what all problems
exist in the present system? What must be done to solve the problem? Analysis begins when a
A DFD also known as ‘bubble chart’, has the purpose of clarifying system
requirements and identifying major transformations. It shows the flow of data through a
Four simple notations are used to complete a DFD. These notations are given below:-
DATA FLOW: - The data flow is used to describe the movement of Information from one part
of the system to another part. Flows represent data in motion. It is a pipe line through which
information flows.
outgoing data. Process shows a part of the system that transform inputs to outputs.
entities represent any entity that supplies or receive information from the system but is not a
store symbol which can represent either a data structure or a physical file on disk. The data store
rectangle.
OUTPUT:-The output symbol is used when a hard copy is produced and the
user of the copies cannot be clearly specified or there are several users of the output.
SYMBOLS
Function
File/Database
Input/output
flow
Context Diagram
LEVEL-0/Context Diagram:-
Student
USER:Input:
Output:
Input:
Output:
This will stores each and every information that is saved by the user whether it is the
new registration or an old one. The modification or the updating of the registration is also very
quickly and efficiently updated in the database.
Input:
Output:
Gives the details of the students requested by the user.
LEVEL-1 DFD for Administrator/User
Online Student
User
Registration
System
Generate
Update
Delete Reports
User
User
Database
Entity-Relationship Diagram (ERD)
Username
Student Sign
Up Login
Password
Online Student
Administrator/
Registration
Has to User
System
Fill
Username Password
Registration form
Delete Give
Course Year
Roll No
2s Report
1s Generated
3s
Give Branch
Fees
Update
6s Details 4s Year
Mname
5s Address
Sem
Personal Details Board DOB
Name Roll
High no
DOB
School
Board
Name Inter
E-id
Fname
6sem Course
Education
marks Details
Address 5sem Board
marks
4sem
marks University
2sem Roll no
3sem marks
marks 1sem
4. System Design
The purpose of System Design is to create a technical solution. That satisfies the
functional requirements for the system. At this Point in the project lifecycle there should be a
description of the operational needs of the various organizational entities that will use the new
system. The Challenge is to translate all of this information into Technical Specifications that
accurately describe the design of the system, And that can be used as input to System
System components are distributed across the physical architecture, usable interfaces are
Technical Specifications are created for the Application Developers, enabling them to build and
test the system. Many organizations look at System Design primarily as the Preparation of the
system component specifications; however, Constructing the various system components is only
one of a setoff major steps in successfully building a system. The preparation of the
environment needed to build the system, the testing of the system, and the migration and
preparation of the data that will ultimately be used by the system are equally important. In
addition to designing the technical solution, System Design is the time to initiate focused
planning efforts for both the testing and data preparation activities.
4.1. Database design
database is a collection of interrelated data stored with minimum redundancy to serve many users
quickly and efficiently. The general objective is to make information access easy quick and
Control Redundancy:
Redundant occupies space and therefore, is wasteful. If versions of the data are in
different phases of updating the system often gives conflicting information. A unique aspect of
database design is storing only once, which controls redundancy and improves system
performance.
Table Structure
Registration Table
student_name varchar(40)
father_name varchar(40)
mother_name varchar(40)
date int(10)
month varchar(20)
year int(10)
address varchar(40)
email_id varchar(40)
contact int(10)
high_school_marks int(10)
board1 varchar(20)
intermediate_marks int(10)
course varchar(20)
board varchar(20)
1sem_marks int(10)
2sem_marks int(10)
3sem_marks int(10)
4sem_marks int(10)
5sem_marks int(10)
6sem_marks int(10)
1sem_fees int(20)
2sem_fees int(20)
3sem_fees int(20)
4sem_fees int(20)
5sem_fees int(20)
Login Table
password varchar(60)
email varchar(50)
User Table
password varchar(40)
Update Table
fname varchar(30)
lname varchar(30)
session int(10)
year int(10)
semester int(10)
mm varchar(20)
dd int(10)
yy int(10)
address varchar(40)
Delete Table
The testing process focuses on the logical intervals of the software ensuring that all
statements have been tested and on functional interval is conducting tests to uncover errors and
ensure that defined input will produce actual results that agree with the required results. Program
level testing, modules level testing integrated and carried out.
5.1Testing Methods
White box sometimes cal ed “Glass box testing” is a test case design uses the control
Black box testing focuses on the functional requirements of the software. This is black
box testing enables the software engineering to derive a set of input conditions that will fully
exercise all functional requirements for a program. Black box testing is not an alternative to white
box testing rather it is complementary approach that is likely to uncover a different class of
Interface errors
Performance errors
OCCURED
user Admin.
Screen Shots
DESIGNING FORMS
HOME PAGE
Conclusion
The purpose of php is to have code that is structured and organized. For the most part,
you’l find yourself in situations where you’ll be reusing code.For example, let’s say you had a
database class. A lot of people connect to databases. Some people may be looking for code
that can help them connect to a database easier and run certain functions.
References