1.

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
course. It is intended o be complete specifications of what functionality the admission
provides. It will also facilitate keeping all the Online Student Registration 8 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 student of any organization. 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 manage its
student’s personal data.

1
 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 Online Student Registration 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
What contribution would the project make?
This is an era of information technology where automation of each and every activity is
gaining Importance. The site will lead to the automation of the examination system.
Moreover it is far better than the previous such websites.
Computerized vs. Manual Examination System
Automated process of examination is much better than the manual system as it has
followings advantages:
Time saving
Increased efficiency
Allows neat handling of data rather than error prone records.
Decreases overhead
Accurate

2
 1.3. Definitions, Acronyms, and Abbreviations

Personal Details: Details of student such as user id, phone number, address, image, e-mail
address etc.
Contact Details: Details of contact associated with the student.
SRS: System Requirement Specification
WWW: World Wide Web
OSRS: Online Student Registration System
MySQL: is a RDBMS based on SQL which is used for adding, removing, and modifying
information in the database.
RDBMS: Relational Database Management System
HTML: Hypertext Markup Language
PHP: Hypertext Preprocessor
CSS: Cascading Style Sheet
HTTP: Hypertext Transfer Protocol

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

3
 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.
2.1. Project Perspective
Library Management System is a replacement for the ordinary student registration
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 getting various set of reports.
2.1.1. System Study
System Study 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 user or manager begins a study of the program using existing system.
System study can be categorized into four parts.
System planning and initial investigation
Proposed System with objectives
Feasibility study
PROPOSED SYSTEM
In our proposed system we have the provision for adding the details of the students by
themselves. So the overhead of the school authorities is become less Another advantage
of the system is that it is very easy to edit the Details of the student and delete a student
when it found unnecessary.

4
 FEASIBILITY ANALYSIS
Whatever we think need not be feasible .It is wise to think about the feasibility of any
problem we undertake. Feasibility is the study of impact, which happens in the ganization
by the development of a system. Theimpact can be either positive or negative. When the
positives nominate thenegatives, then the system is considered feasible. Here the
feasibility study can be performed in two ways such as technical feasibility and conomical
Feasibility

Economical Feasibility
Development of this application is highly economically feasible .The organization needed
not spend much money for the development of the system already available. The only
thing is to be done is making an environment for the development with an effective
supervision. If we are doing so, we can attain the maximum usability of the corresponding
resources .Even after the development, the organization will not be in condition to invest
more in the organization .Therefore, the system is economically feasible.

2.1.2 Interfaces
In computing, an interface is a shared boundary across which three separate components
of computer system exchange information. User interfaces The application will have a
user friendly and menu based interface. Following screens will be provided:

2.1.3Hardware Interfaces
Minimum 350MB Hard Disk space for installation.
4GB HD space required for a typical live system with 1000-2000 events.
Recommended minimum CPU – Pentium 4, 3.2GHz
Recommended 1GB RAM for a Central Server with 3 Nodes
Network Card
Printer (If required)

5
Server side
The web application will 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
such as Mozilla Firebox 1.5, Internet Explorer 6, and Google Chrome

2.1.4 Software Interfaces

Adobe Dreamweaver
PHP Wamp Server For Windows(Apache)
Database Mysql For Backend
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).

ADOBE DREAMWEAVER (FRONT END)

Adobe Dreamweaver is a proprietary web development tool developed by Adobe
systems. Dreamweaver was created by Macromedia in 1997, and was maintained by them
until Macromedia was acquired by Adobe Systems in 2005.
Adobe Dreamweaver is available for OS X and for Windows.Following Adobe's
acquisition of the Macromedia product suite, releases of Dreamweaver subsequent to
version 8.0 have been more compliant with W3C standards. Recent versions have
improved support for Web technologies such as CSS, JavaScript, and various server-side
scripting languages and frameworks including ASP (ASP JavaScript, ASP VBScript, ASP.NET
C#, ASP.NET VB), ColdFusion, Scriptlet, and PHP.

6
Features
Adobe Dreamweaver CC is a web design and development application that combines a
visual design surface known as Live View and a code editor with standard features such as
syntax highlighting, code completion, and code collapsing as well as more sophisticated
features such as real-time syntax checking and code introspection for generating code
hints to assist the user in writing code. Combined with an array of site management tools,
Dreamweaver lets its users design, code and manage websites as well as mobile content.
Dreamweaver is positioned as a versatile web design and development tool that enables
visualization of web content while coding..
Dreamweaver, like other HTML editors, edits files locally then uploads them to
the remote web server using FTP, SFTP, or WebDAV. Dreamweaver CS4 now supports
the Subversion (SVN) version control system.
Since version 5, Dreamweaver supports syntax highlighting for the
following languages out of the box:
Action Script
Active Server Pages (ASP).
C#
Cascading Style Sheets (CSS)
ColdFusion
EDML
Extensible Hypertext Markup Language (XHTML)
Extensible Markup Language (XML)
Extensible Style sheet Language Transformations (XSLT)
Hypertext Markup Language (HTML)
Java
JavaScript
Hypertext Preprocessor (PHP)
Visual Basic (VB)
Visual Basic Script Edition (VBScript)

7
 3. Specific Requirements Software

This section provides software requirements to a level of detail sufficient to enable

designers to design the system an testers to test the system.This section contains all of
the functional and quality requirements of the system. It gives a detailed description of
the system and all its features.
Requirement Specification (SRS)
The following subsections of the SRS document provide an overview of the Entire SRS.
Purpose: The purpose of the project is to provide online student registration.
Scope: The website display student information of registered students
Benefits: This website reduces the manual work, maintaining accuracy, increasing
3.1. External Interface Requirements:
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 and
provides basic prototypes of the user interface.
User Interfaces:
Registration Screen: Various fields available on this screen will be:
Login Name
Institute Name
Email Id
Password
Online Student Registration
Login Screen: Fields available on this screen are:
Login Name
Password
Student List Screen: Various Fields are:
Student ID
Student Name
Student Login Screen: Various Fields are:

8
Student ID
Student Name
3.2. FUNCTIONAL REQUIREMENTS
It deals with the functionalities required from the system which are as follows:
The website will help the colleges/organizations/companies to conduct their student
registration.
Only authorized person can access related details.
Organizations can change their information regarding themselves. The students can
login through TEST-ID and PASSWORD.
Administrator will be responsible for updating the site.

3.3. Performance Requirements

This subsection specifies numerical requirements placed on the software or on the human
interaction with the software, as a whole..Numerical requirements will include:
300 terminals will be supported at a time
Only text information will be supported(HTTP)
3.4. System Analysis
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 user or manager begins a study of the program using existing system.
DATA FLOW DIAGRAM
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 system. It is a
graphical tool because it presents a picture. 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. Data flow is represented by an arrow.

9
PROCESS:- A circle or bubble represents a process that transforms incoming data to
outgoing data. Process shows a part of the system that transform inputs to outputs.
EXTERNAL ENTITY: - A square defines a source or destination of system data. External
entities represent any entity that supplies or receive Online Student Registration
information from the system but is not a part of the system.
DATA STORE:- The data store represents a logical file. A logical file can represent either
a data store symbol which can represent either a data structure or a physical file on disk.
The data store is used to collect data at rest or a temporary repository of data. It is
represented by open 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

10
 Context Diagram

.
USER:
Input:
Login with the authorized identification name.
Add necessary information regarding the registration.
Output:
Required Registration details.
Online Student Registration System:
The system will save the registration and their details.
Input:
Manages the Details of students
Output:
Delivers the details for the specified student.
My SQL Database:
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:
Saves the details of all the students as well as their information.
11
Output:
Gives the detail s of the students requested by the user.

LEVEL-1 DFD for Administrator/User

12
 3.5. Software System Attributes

There are a number of attributes of software that can serve as requirements. It is

important that required attributes by specified so that their achievement can be
objectively verified. The following items provide a partial list of examples. These are also
known as non-functional requirements or quality attributes. These are characteristics the
system must possess, but that pervade (or crosscut) the design. These requirements have
to be testable just like the functionl requirements. It’s easy to start philosophizing here,
but keep it specific.

3.5.1. Reliability
It means the extent to which program performs with required precision. The website
developed should be extremely reliable and secure so that information about any
questions etc. is not leaked. The system shall not be down more than 2 times in a year.

3.5.2. Availability
The software will be available only to authorized users like students to view their enrolled
course, admin to add an update/delete student details. Checking that the system always
has something to function and always pop up error messages in case of component ailure.
In that case the error messages appear when something goes wrong so to prevail
availability problems.
3.5.3. Security
The security requirements deal with the primarily security. The software should be andled
only by the administrator and authorized users. Only the administrator has right to assign
permissions like creating new accounts and generating password.
Specific requirements in this area could include the need to:
Utilize certain cryptographic techniques
Keep specific log or history data sets
Assign certain functions to different modules

13
Restrict communications between some areas of the program
Check data integrity for critical variable.
3.6. Organizing the specific Requirements

For anything but trivial systems the detailed requirements tend to be extensive. For this
reason, it is recommended that careful consideration be given to organizing these in a
manner optimal for understanding. There is no one optimal organization for all systems.
Different classes of systems lend themselves to different organizations of requirements in
section 3. Some of these organizations are described in the following subclasses.

3.6.1. System Mode

Some systems behave quite differently depending on the mode of operation. When
organizing by mode there are two possible outlines. The choice depends on whether
interfaces and performance are dependent on mode.

3.6.2 User Class

Some systems provide different sets of functions to different classes of users.
3.6.3 Objects
Objects are real-world entities that have a counterpart within the system. Associated with
each object is a set of attributes and functions. These functions are also called services,
methods, or processes. Note that sets of objects may share attributes and services. These
are grouped together as classes.
3.6.4 Feature
A feature is an externally desired service by the system that may require a sequence of
inputs to affect the desired result. Each feature is generally described in as sequence of
stimulus-response pairs.
3.6.5 Stimulus
Some systems can be best organized by describing their functions in terms of stimuli.
3. 6.6 Response
Some systems can be best organized by describing their functions in support of the
eneration of a response.

14
 3.6.7 Functional Hierarchy
When none of he above organizational schemes prove helpful, the overall functionality
can be organized into a hierarchy of functions organized byeither common inputs,
common outputs, or common internal data access. Data flow diagrams and data
dictionaries can be use dot show the relationships between and among the functions and
data.
4. System Design
The purpose of System Design is to create a technical solution. That satisfies the unctional
requirements for the system. At this Point in the project lifecycle there should be a
Functional Specification, written primarily in business terminology, containing a complete
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 Construction. Thee Functional Specification produced during System
Requirements Analysis is transformed into a physical architecture. System components
are distributed across the physical architecture, usable interfaces are designed and
rototyped, and 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
thetesting and data preparation activities.

15
 4.1. Database Design
The general theme behind a database is to handle information as an integrated whole. A
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 flexible for user. In database design several objectives are considered.
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 erformance.

Table Structure
Registration Table

16
17
18
 5. Designing Forms
RESULTS
HOME PAGE

19
5.1. ADMIN PAGE

20
5.2. STUDENT LOGIN

21
5.3. STUDENT SIGN UP

22
5.4. Registration Form

23
24
 6. System Testing
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.

6.1 Testing Methods

There are two major type of testing they are
1) White Box Testing.
2) Black Box Testing.
White Box Testing
White box sometimes called “Glass box testing” is a test case design uses the control
structure of the procedural design to drive test case.
Black box Testing
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 errors that white box methods like..
Interface errors
Performance in data structure
Performance errors
Initializing and termination errors
Unit testing
Unit testing is a software verification and validation method in which a programmer tests
if individual units of source code are fit for use. A unit is the smallest testable part of an
application. In procedural programming a unit may be an individual function or procedure.
Ideally, each test case is independent from the others: substitutes like method stubs,
objects, fakes and test harnesses can be used to assist testing a module in isolation.

25
Integration Testing:
This testing is sometimes called Integration and Testing. Integration testing is the phase in
software testing in which individual software modules are combined and tested as a
group. It occurs after unit testing and before system testing. Integration testing takes as
its input modules that have been unit tested, groups them in larger aggregates, applies
tests defined in an integration test plan to those aggregates and delivers as its output the
integrated system ready for system testing.
Validation Testing:
Validation Testing can be defined in many ways, but a simple definition is that validation
succeeds when the software functions in a manner that can reasonably expected by a
customer. After validation test has been conducted, one of the following two possible
conditions exists. The functions or performance characteristics confirm to specification
and are accepted.
In the administrator and login modules, all the fields must be filled.
In the student registration, contact number should contain exactly 10 numbers.
User Acceptance Testing:
User acceptance of a system is a key factor of any system. The system under consideration
is tested for the acceptance by constantly keeping in touch with the prospective system
users at the same time of developing and marketing changes whenever required. This is
done in regard to the following points:
Input Screen Design
Output Screen Design

26
6.2 Test Cases

27
7. CONCLUSION
The purpose of php is to have code that is structured and organized. For the most part,
you’ll 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.
Assumptions, if any None
Assumptions:
The user is familiar with basic computer components and operations.
Dependencies:
The system should work on all systems.

7.1. Future Scope and further enhancement of the Project

The Online Student Registration system is the next generation address book which will
provide these two basic services like portability, security. The future scope includes
expand the technologies like HTML and PHP we can also add new technologies like HTML,
php many more for improving the efficiency of the software. The project will be useful for
any schools and colleges with slightly modification. Project is flexible i.e. any change
/modification in database may be performing easily. Also this project could be made web
enabled.

28
8. References
Software Requirement Specifications from Internet.
Software Requirement Specifications, Online Examination System.
IEEE (Institute of Electrical and Electronics Engineers) Guide to Software
Requirements Specifications.
www.slideshare.com
www.google.com
www.wikipedia.com
www.project-online-system-basics.com
HTML for the World Wide Web with XHTML and CSS Guide, Fifth
Edition
IEEE Computer Society, 1998.

29