Osrs 170209130721

Online Student Registration
ONLINE STUDENT
REGISTRATION SYSTEM
Project Report
For the partial fulfillment of the degree in
BACHELOR OF COMPUTER APPLICATION (BCA)
PROJECT GUIDE: SUBMITTED BY:

Mrs. Anuja Sharma Sanjana Agarwal
Saloni Lohiya
Sachin Padhlani
Rohit Singh
Ravi Negi
Date of Submission:
12/01/2017
Faculty of Computer Science Applications

AMRAPALI GROUP OF INSTITUTE, HALDWANI
2016-2017
CERTIFICATE
This is to certify that the project entitled “Online Student Registration

System” has been developed by “Sanjana Agarwal, Rohit Singh, Sachin
Padhlani, Saloni Lohiya and Ravi Negi of Amrapali Group of Institute,
Haldwani towards partial fulfillment of the requirements for the award of the
degree of Bachelor of Computer Science is a bonafide record of the work
carried out by Him/her under My Supervision and Guidance and the project
report is the original work of student. She/he has worked on the project Online
Student Registration System. She/he has used PHP, CSS, HTML,
JAVASCRIPT and Xampp as Database for the project. His/her work is
satisfactory. I wish him/her all the best for his bright future.
Date: 12/01/2017 Signature of Guide
Place:Haldwani Mrs.Anuja Sharma
1
DECLARATION
We hereby declare that the work presented in the project report entitled
“Online Registration System “submitted to Mr. Mukesh Joshi, Amrapali
Group Of Institute, Haldwani for the award of degree of “BCA” is an
authentic record of my work carried out during the fifth semester Third year,
2016 under the supervision of Mrs. Anuja Sharma .The matter embodied in
this project report has not been submitted elsewhere by anybody for the award
of any other degree/diploma.
NAME UNIVERSITY CLASS

ROLL NO
Sanjana 1461330107 BCA 5sem, 3rd
Agarwal year
Saloni Lohiya 1461330106 BCA 5sem, 3rd
year
Sachin 1461330 BCA 5sem, 3rd
Padhlani year
Rohit Singh 1461330106 BCA 5sem, 3rd
year
Ravi Negi 1461330107 BCA 5sem, 3rd
year
2
ACKNOWLEDGEMENT
We gratefully acknowledge for the assistance, cooperation, guidance and

clarifications provided by Mrs.Anuja Sharma during the development of the
Online Student Registration System. Our extreme gratitude to Mrs.Anuja
Sharma who guided us throughout the project. Without his willing disposition,
spirit accommodation, frankness, timely clarification and above all faith in us,
this project could not have been completed in due time. Her readiness to
discuss all important matters at work deserves special attention of. We would
also like to thank whole of the faculty of the college for their cooperation and
important support. I would like to thank all other teaching stuff for their
valuable teaching and constant advice which made me to finish this program
successfully.
Finally our deepest gratitude goes to my parents who have given me
much needed comfort, support, encouragement and inspiration for completing
this project.
We perceive as this opportunity as a big milestone in my career

development. I will strive to use gained skills and knowledge in the best
possible way, and I will continue to work on their improvement, in order to
attain desired career objectives. Hope to continue cooperation with all of you
in the future. Sincerely,
NAME:
SanjanaAgarwal
Sachin Padhlani
Saloni Lohiya
Rohit Singh
Ravi Negi
3
Software Requirement Specification
Particulars Page Nos.
1. Introduction..................................................................................................7
1.1. Purpose..................................................................................................7
1.2. Scope……………………………………………………………….....8
1.3. Definitions, Acronyms, and Abbreviations......................................... 9
1.4. References.............................................................................................10
1.5. Overview..............................................................................................11
2. The Overall Description...............................................................................12
2.1. Product Perspective..............................................................................12
2.1.1. System Study………………………………………………….12
2.1.2. Interfaces………………………………………………………14
2.1.3. Hardware Interfaces...................................................................14
2.1.4. Software Interfaces.................................................................... 15
2.1.5. Communications Interfaces…………………………………...29
2.1.6. Memory Constraints....................................................................29
2.1.7. Operations...................................................................................29
2.1.8. Site Adaptation Requirements.....................................................29
2.2. Product Functions..................................................................................30
2.3. User Characteristics................................................................................30
2.4. Constraints..............................................................................................31
2.5. Assumptions and Dependencies.............................................................31
3. Specific Requirements...................................................................................32
3.1. External Interfaces.................................................................................32
3.2. Functions...............................................................................................33
4
3.3. Performance Requirements.................................................................33
3.4. System Analysis..................................................................................34
3.5. Software System Attributes............................................................... 40
3.5.1. Reliability.................................................................................40
3.5.2. Availability...............................................................................40
3.5.3. Security....................................................................................40
3.5.4. Maintainability.........................................................................41
3.5.5. Portability.................................................................................41
3.6. Organizing the specific Requirements.................................................43
3.6.1. System Mode............................................................................43
3.6.2. User Class.................................................................................43
3.6.3. Objects.....................................................................................43
3.6.4. Features....................................................................................44
3.6.5. Stimulus................................................................................... 44
3.6.6. Response...................................................................................44
3.6.7. Functional Hierarchy.................................................................44
4. System Design.............................................................................................45
4.1. File/Database Design…………………………………………………45
5. Designing forms…………………………………………………………..50
6. Coding……………………………………………………………………55
7. System Testing……………………………………………………………90
7.1. Testing Methods……………………………………………………..91
7.2. Unit Testing, Class Testing………………………………………….92
7.3. Test Cases…………………………………………………………...92
5
8. Conclusions………………………………………………………….94
8.1. Scope for Future Prospects……………………………………..94
6
1. Introduction
Project Title: Online Student Registration System
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.2. 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
7
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.3. 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
8
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
1.4. 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
9
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.5. 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.
10
1.6. 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.
11
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.
12
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.
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 organization by the development of a system. The
impact can be either positive or negative. When the positives nominate the
negatives, then the system is considered feasible. Here the feasibility study can
13
be performed in two ways such as technical feasibility and Economical
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.2Interfaces
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
14
 Printer (If required)
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.4Software 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).
15
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.
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.
16
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)
17
HTML
Hypertext Markup Language, commonly referred to as HTML, is the
standard markup language used to create web pages. Along with CSS,
and JavaScript, HTML is a cornerstone technology used to create web pages,
as well as to create user interfaces for mobile and web applications. Web
browsers can read HTML files and render them into visible or audible web
pages. HTML describes the structure of a website semantically along with
cues for presentation, making it a markup language, rather than a
programming.
HTML elements form the building blocks of HTML pages. HTML
allows images and other objects to be embedded and it can be used to
create interactive forms. It provides a means to create structured documents by
denoting structural semantics for text such as headings, paragraphs, lists, links,
quotes and other items. HTML elements are delineated by tags, written
using angle brackets. Tags such as <img /> and <input /> introduce content
into the page directly. Others such as <p>...</p> surround and provide
information about document text and may include other tags as sub-elements.
Browsers do not display the HTML tags, but use them to interpret the content
of the page.
History
November 24, 1995
HTML 2.0 was published as IETF RFC 1866. Supplemental RFCs added
capabilities:
 November 25, 1995: RFC 1867 (form-based file upload)
18
 May 1996: RFC 1942 (tables)
 August 1996: RFC 1980 (client-side image maps)
 January 1997: RFC 2070 (internationalization)
January 14, 1997
HTML 3.2was published as a W3C Recommendation. It was the first version
developed and standardized exclusively by the W3C, as the IETF had closed
its HTML Working Group on September 12, 1996.
Initially code-named "Wilbur", HTML 3.2 dropped math formulas
entirely, reconciled overlap among various proprietary extensions and adopted
most of Netscape's visual markup tags. Netscape's blink
element and Microsoft's marquee element were omitted due to a mutual
agreement between the two companies. A markup for mathematical formulas
similar to that in HTML was not standardized until 14 months later
in MathML.
December 18, 1997
HTML 4.0 was published as a W3C Recommendation. It offers three
variations:
 Strict, in which deprecated elements are forbidden
 Transitional, in which deprecated elements are allowed
 Frameset, in which mostly only frame related elements are allowed.
Initially code-named "Cougar",HTML 4.0 adopted many browser-specific
element types and attributes, but at the same time sought to phase out
Netscape's visual markup features by marking them as deprecated in favor of
19
style sheets. HTML 4 is an SGML application conforming to ISO 8879 –
SGML.
April 24, 1998
HTML 4.0 was reissued with minor edits without incrementing the version
number.
CSS
Cascading Style Sheets (CSS) is a style sheet language used for describing
the presentation of a document written in a markup language. Although most
often used to set the visual style of web pages and user interfaces written
in HTML and XHTML, the language can be applied to any XML document,
including plain XML, SVG and XUL, and is applicable to rendering in speech,
or on other media. Along with HTML and JavaScript, CSS is a cornerstone
technology used by most websites to create visually engaging webpages, user
interfaces for web applications, and user interfaces for many mobile
applications.
CSS is designed primarily to enable the separation of document
content from document presentation, including aspects such as
the layout, colors, and fonts. This separation can improve content accessibility,
provide more flexibility and control in the specification of presentation
characteristics, enable multiple HTML pages to share formatting by specifying
the relevant CSS in a separate .css file, and reduce complexity and repetition
in the structural content.
History
20
CSS1
The first CSS specification to become an official W3C Recommendation is
CSS level 1, published on December 17, 1996. Håkon Wium Lie and Bert
Bos are credited as the original developers. Among its capabilities are support
for
 Font properties such as typeface and emphasis
 Color of text, backgrounds, and other elements
 Text attributes such as spacing between words, letters, and lines of text
 Alignment of text, images, tables and other elements
 Margin, border, padding, and positioning for most elements
CSS 2
CSS level 2 specification was developed by the W3C and published as a
recommendation in May 1998. A superset of CSS 1, CSS 2 includes a number
of new capabilities like absolute, relative, and fixed positioning of elements
and z-index, the concept of media types, support for aural style sheets (which
were later replaced by the CSS 3 speech modules) and bidirectional text, and
new font properties such as shadows.
The W3C no longer maintains the CSS 2 recommendation.
CSS 3
"CSS3" redirects here. For other uses, see CSS3 (disambiguation).
Unlike CSS 2, which is a large single specification defining various features,
CSS 3 is divided into several separate documents called "modules". Each
module adds new capabilities or extends features defined in CSS 2, preserving
21
backward compatibility. Work on CSS level 3 started around the time of
publication of the original CSS 2 recommendation.
PHP (HYPERTEXT PREPROCESSOR)
PHP is a server-side scripting language designed for web development but
also used as a general-purpose programming language. 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 acronym 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
system and web frameworks. PHP code is usually processed by a
PHP interpreter implemented as amodule 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.
The standard PHP interpreter, powered by the Zend Engine, is free
software released under the PHP License. PHP has been widely ported and can
be deployed on most web servers on almost every operating
system and platform, free of charge.
22
The PHP language evolved without a written formal specification or
standard until 2014, leaving the canonical PHP interpreter as a de
facto standard. Since 2014 work has gone on to create a formal PHP
specification.
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.
History
8 June Officially called "Personal Home Page Tools (PHP

1.0
1995 Tools)". This is the first use of the name "PHP".
1 Officially called "PHP/FI 2.0". This is the first release

that could actually be characterized as PHP, being a
2.0 November
standalone language with many features that have
1997 endured to the present day.
Development moves from one person to multiple

6 June 20 October
3.0 developers. Zeev Suraski and Andi Gutmans rewrite
1998 2000[60]
the base for this version.[4]
22 May 23 June Added more advanced two-stage parse/execute tag-

4.0
2000 2001[60] parsing system called the Zend engine.
23
10
12 March Introduced "superglobals"
4.1 December
2002[60] ($_GET, $_POST, $_SESSION, etc.)
2001
Disabled register_globals by default. Data received

6
22 April over the network is not inserted directly into
4.2 September
2002 the globalnamespace anymore, closing possible
2002
security holes in applications.
27
31 March Introduced the command-line interface (CLI), to
4.3 December
2005 supplement the CGI.
2002
Fixed a memory corruption bug, which required

11 July 7 August
4.4 breaking binary compatibility with extensions
2005 2008
compiled against PHP version 4.3.x.
5
13 July
5.0 September Zend Engine II with a new object model.
2004
2005
Performance improvements with introduction of

24
24 August compiler variables in re-engineered PHP
5.1 November
2006 Engine.[64] Added PHP Data Objects (PDO) as a
2005
consistent interface for accessing databases.
2
6 January Enabled the filter extension by default.
5.2 November
2011 Native JSON support.
2006
Namespace support; late static bindings, jump label

(limited goto), closures, PHP archives (phar), garbage
collectionfor circular references,
improved Windows support, sqlite3, mysqlnd as a
30 June 14 August
5.3 replacement for libmysql as underlying library for the
2009 2014
extensions that work with MySQL, fileinfo as a
replacement for mime_magic for
better MIME support, the Internationalization
extension, and deprecation of ereg extension.
24
MY-SQL (BACKEND)
MySQL (officially pronounced as /maɪ ˌɛskjuːˈɛl/ "My S-Q-L",) is an open-
source relational database management system(RDBMS) in July 2013, it was
the world's second most[a] widely used RDBMS, and the most widely used
open-sourceclient–server model RDBMS. It is named after co-
founder Michael Widenius's daughter, My. The SQL abbreviation stands
for Structured Query Language. The MySQL development project has made
its source code available under the terms of theGNU General Public License,
as well as under a variety of proprietary agreements. MySQL was owned and
sponsored by a single for-profit firm, the Swedish company MySQL AB, now
owned by Oracle Corporation. For proprietary use, several paid editions are
available, and offer additional functionality.
MySQL is a popular choice of database for use in web applications,
and is a central component of the widely used LAMPopen-source web
application software stack (and other "AMP" stacks). LAMP is an acronym for
"Linux, Apache, MySQL,Perl/PHP/Python". Free-software open-source
projects that require a full- featured database management system often use
MySQL. Applications that use the MySQL database
include: TYPO3, MODx, Joomla, WordPress, phpBB, MyBB, Drupal and
other software. MySQL is also used in many high-profile, large-
scale websites, including Google (though not for searches), Facebook,
Twitter, Flickr and YouTube. On all platforms except Windows, MySQL
ships with no GUI tools to administer MySQL databases or manage data
contained within the databases. Users may use the included command
25
line tools,[20][21] or install MySQL Workbench via a separate download.
Many third party GUI tools are also available.
MySQL is a relational database management system (RDBMS) that
runs as a server providing multi- user which access to a number of databases..
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.
History
 Original development of MySQL by Michael Widenius and David
Axmark beginning in 1994
 First internal release on 23 May 1995
 Version 3.19: End of 1996
 Version 3.20: January 1997
 Windows version was released on 8 January 1998 for Windows 95 and NT
 Version 3.21: production release 1998, from www.mysql.com
 Version 3.22: alpha, beta from 1998
 Version 3.23: beta from June 2000, production release 22 January 2001
 Version 4.0: beta from August 2002, production release March 2003
(unions)
26
 Version 4.01: beta from August 2003, Jyoti adopts MySQL for database
tracking
 Version 4.1: beta from June 2004, production release October 2004 (R-
trees and B-trees, sub queries, prepared statements)
 Version 5.0: beta from March 2005, production release October 2005
(cursors, stored procedures, triggers, views, XA transactions)
Apache
The Apache HTTP Server is web server software notable for playing a key
role in the initial growth of the World Wide Web. In 2009 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. Since April 1996 Apache has
been the most popular HTTP server software in use. As of November 2010
Apache served over 59.36% of all websites and over 66.56% of the first one
million busiest websites.
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
27
version is a small package containing Apache HTTP Server, PHP, MySQL,
phpMyAdmin and SQL lite.
Obtaining and Installing XAMPP
As previously mentioned, XAMPP is a free package available for download
and use for various web development tasks. All XAMPP packages and add-
ons are distributed through the Apache Friends website at the address:
http://www.apachefriends.org/. Once on the website, navigate and find the
Windows version of XAMPP and download the self-extracting ZIP archive.
After downloading the archive, run and extract its contents into the root path
of a hard disk or USB drive. For example, the extract path for a local
Windows installation would simply be C:\. If extracted properly we will notice
a new xampp directory in the root of your installation disk. In order to test that
everything has been installed correctly, first start the Apache HTTP Server by
navigating to the xampp directory and clicking on the apache_start.bat batch
file.
Next we will test if the server is running correctly by opening an
internet browser and typing http://localhost/ into the address bar. If configured
correctly, we will be presented with a screen similar to that of the one below.
28
2.1.5 Communication Interfaces
The HTTP protocol will be used to facilitate communications between the
client and server. The system supports Google Chrome and Mozilla
Firefox web browsers.
2.1.6 Memory Constraints
Minimum memory of 512MB is required to run the exe file without any
lags. This constraint does not possess an issue now a days as the minimum
present RAM in a common system is 1GB.
At least 512 MB RAM and 5 MB space on hard disk will be required
for running the program.
2.1.7 Operations
The normal and special operations required by the user such as:
 The various modes of operations in the user organization
 Periods of interactive operations and periods of unattended
operations
 Data processing support functions
 Backup and recovery operations
2.1.8Site Adaptation Requirements
There should no site adaptation requirement since the Web Application
Server was setup.
29
2.2Product Functions
The website will allow access only to authorized users with specific roles
(Administrator- maintains the website, Institutes-Register the students,
Students-Fills the details).
Following are the System Functions:
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 information and provide the function to change password for
student.
Administration role
The system administrator must be able to: deactivate and reactivate student
account login
2.3User Characteristics
End Users
All specific knowledge or skills are required from the feeder.
 Educational level: Users should be comfortable with the English
language.
 Experience: Users should have prior information regarding the
online examinations.
 Skills: Users should have basic knowledge and should be
comfortable
30
Administrator
Administrator must be capable to manage user rights.
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.
2.4 Constraints
The Information of all users, subjects and allocations must be stored in a
database that is accessible by every connected system.
MySQL used for database.
Users may access from any system connected to the online database.
Users must have their correct usernames and passwords to enter into their
accounts.
2.5 Assumptions and Dependencies
The Software needs the following third party products-
 Adobe Dreamweaver for development of project.
 WAMP for database connectivity.
Although basic password authentication and role based security
mechanisms will be used to protect OPMS from unauthorized access;
functionality such as email notifications are assumed to be sufficiently
protected under the existing security policies applied by the University
network team. Redundant Database is setup as the role of backup Database
Server when primary database is failure.
31
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
32
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:
 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
33
 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.
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
34
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.
SYMBOLS
Function
File/Database
Input/output
Flow
35
Context Diagram
LEVEL-0/Context Diagram:-
Student
Administrator/ Details Online Student Details

User My SQL
Registration System
database
Final report Report
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.
Output:
36
 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
37
LEVEL-1 DFD for Student
Online Student
Student
Registration System
Fill Student
Registration Information
Login Form
Form
Generate Student
Information/
Database
38
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
N Board
Inter
Name E-id
Fname
6sem Course
Education
marks Details
Address 5sem Board
marks
4sem
marks University
2sem Roll no
3sem marks
marks 1sem
marks 39
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 cross-
cut) the design. These requirements have to be testable just like the functional
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 failure. 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 handled only by the administrator and authorized users. Only the
40
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
 Restrict communications between some areas of the program
 Check data integrity for critical variable.
3.5.4. Maintability
The application is to be designed so that it is easily maintained. Also it should

allow incorporating new requirements in any module of system. Backups for
database are available.
3.5.5. Portability
The software is a web based application and is built in PHP and My SQL. So
it is platform independent and is independent of OS. The application will be
easily portable on any window based system.
A chart like this might be used to identify the key characteristics (rating
them High or Medium), then identifying which are preferred when
trading off design or implementation decisions (with the ID of the
preferred one indicated in the chart to the right). The chart below is
optional (it can be confusing) and is for demonstrating tradeoff analysis
between different non-functional requirements. H/M/L is the relative
priority of that non-functional requirement.
41
ID Characteristic H/M/L 1 2 3 4 5 6 7 8 9 10 11 12
1 Correctness
2 Efficiency
3 Flexibility
4 Integrity/Security
5 Interoperability
6 Maintainability
7 Portability
8 Reliability
9 Reusability
10 Testability
11 Usability
12 Availability
 Correctness - extent to which program satisfies specifications, fulfills
user’s mission objectives
 Efficiency - amount of computing resources and code required to
perform function
 Flexibility - effort needed to modify operational program
 Interoperability - effort needed to couple one system with another
 Reliability - extent to which program performs with required precision
 Reusability - extent to which it can be reused in another application
 Testability - effort needed to test to ensure performs as intended
42
 Usability - effort required to learn, operate, prepare input, and interpret
output.
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.
43
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 generation of a response.
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 by
either 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.
44
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 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 prototyped, 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 the
testing and data preparation activities.
45
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 performance.
Table Structure
Registration Table
Field Name Data Type Constraint
student_name varchar(40)
father_name varchar(40)
mother_name varchar(40)
date int(10)
month varchar(20)
year int(10)
46
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)
university_rollno int(20) Primary Key
1sem_fees int(20)
2sem_fees int(20)
3sem_fees int(20)
4sem_fees int(20)
5sem_fees int(20)
47
6sem_fees int(20)
Login Table
id int(11) Primary Key
password varchar(60)
username varchar(30) Unique Key
email varchar(50)
User Table
username varchar(40) Unique Key
password varchar(40)
Update Table
fname varchar(30)
lname varchar(30)
session int(10)
rollno int(20) Primay Key
48
branch varchar(30)
year int(10)
semester int(10)
mm varchar(20)
dd int(10)
yy int(10)
address varchar(40)
Delete Table
rollno int(11) Primary Key
49
5. Designing Forms
HOME PAGE
50
2. ADMIN PAGE
51
3. STUDENT LOGIN
52
3. Registration Form
53
4. HEADER PAGE
5. FOOTER PAGE
54
6. Coding Phase
<html>
<title>OSRS</title>
</head>
<body>

<div id="">
<?php include("header.php");?>
</div>

<div>
<div align="center">
<table border="1" width="800" cellspacing="0" cellpadding="0"
style="border-collapse: collapse" id="table3" bordercolor="#434367">
<tr>
<td align="left" valign="top">
<table border="0" width="800" cellspacing="0" id="table4" height="548">
<tr>
<td background="images (11).jpg" height="133" align="left"valign="top"
width="796" colspan="2">
<div align="left">
<table border="0" width="796" id="table5" cellspacing="0">
<tr>
<td width="311" rowspan="5" colspan="2" align="left" valign="top">
55
<img border="0" src="images (2).jpg" width="321" height="131"></td>
<td width="30"> </td>
<td style="width: 417px"> </td>
</tr>
<tr>
<td style="width: 417px">
<p align="right"></td>
</tr>
<tr>
<tr>
<td width="30" style="height: 15px"> </td>
<td style="width: 417px; color:#36F; height: 15px;"> <h1 align="center">
ONLINE STUDENT REGISTRATION SYSTEM </h1></td>
</tr>
<tr>
<td width="289" align="left" style="height: 15px"> </td>
<td style="width: 417px; height: 15px;"> </td>
</tr>
56
<tr>
<td width="289" align="left"> </td>
</tr>
<tr>
<td width="289" align="left"> Home | <a href="Registration
Form.php">Registration</a> |
<a href="Administration Login.php">Administration</a> |<a
href="Onlinelogin.php">Student Online</a>
</tr>
</table>
</div>
</td>
</tr>
<tr>
57
<td width="135" align="left" valign="top" rowspan="2" style="border- left-
width: 1px; border-top-width: 1px; border-bottom-width: 1px">
<img border="0" src="images (5).jpg"width="157" height="500"></td>
<td align="left" valign="top" height="396" style=" padding-left:5pt; padding-
top :5pt;">
<table border="0" width="100%" cellspacing="1" id="table6">
<tr>
<td align="left" valign="top" style="padding- left: 1px; padding-right: 4px"
width="59%">
<p align="justify" style="font-size:16px"><span style="font-size-
adjust:inherit">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.</span>
<p align="justify" style="font-size:16px"><span style="font-size-
adjust:inherit">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.</span>
<p align="justify" style="font-size:16px">Our Student Online Registration
System deals with the various activities related to the students.<br>
</td>
align="left" valign="top" style="padding- left: 4px; padding-right: 6px">
58
<p>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 studen
</p>
<p>`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. </p>
<p>OSRS, are a vital part of any university’s running because students are
what keep a University alive</p>
<p align="justify" style="font-size-adjust:inherit"></td>
</tr>
<tr>
<td align="left" valign="top" colspan="2" style="padding-right: 6px">
<p align="justify" style="font-size:16px"><br />
</td>
</tr>
</table>
</td>
</tr>
</table>
<div align="center">
</div>

<div id="">
59
<?php include("footer.php");?>
</div>

</td>
</tr>
</table>
</td>
</tr>
</table>
</div>
</div>
</form>
</body>
</html>
<head>
<title>LogIn</title>
</head>
<body>

<div id="">
</div>

60
<h1 align="center" style="font-family: Arial, Helvetica, sans-serif;">LOGIN
FORM</h1>
<h2></h2>
</div>
</div>
<table border="0px" width="400px" align="center" height="400px">
<tr height="200px">
<td colspan="2"><img src="download.jpg" width="150px" style="margin-
left:100px;" width="250px"</td>
</tr>
<tr>
<td>USERNAME</td>
<td><input type="name" required name="username"
placeholder="USERNAME" id="text"></td>
</tr>
<tr>
<td>PASSWORD</td>
<td><input type="password" required name="password"
placeholder="PASSWORD" id="text"></td>
</tr>
<tr>
<td rowspan="2"><p> </p>
<p> </p></td>
61
<td><input type="submit" value="Login" id="text2" style="width:100px;
background-color:#F00; color:#FFF" ;/></td>
</tr>
<tr>
<td>
<a href="SignUp.php?name=Signup"><input type="submit"
style="width:100px; background-color:#f00; color:#fff;"value="Signup"
/></a>
</td>
</tr>
</form>
</table>

</div>
<div id="">
</div>

</div>
</form>
</table>
</body>
</html>
62
<html>
<title>SignUp</title>
</head>
<body>
<div id="">
</div>
<h1 align="center" style="font-family: Arial, Helvetica, sans-serif;">Sign
Up</h1>
<h2></h2>
</div>
</div>
<div id="admin_container"><br>
<form action="check.php" method="POST">
<tr height="200px">
<td colspan="2"> <img src="images (2).png" width="150px" style="margin-
</tr>
<tr>
<td>NAME</td>
<td><input type="name" required name="name" placeholder="Enter Name"
id="text"></td>
</tr>
63
<tr>
<td>EMAIL</td>
<td><input type="name" required name="email" placeholder="Enter Email"
id="text"></td>
</tr>
<tr>
<td>PASSWORD</td>
<td><input type="password" required name="password" placeholder="Enter
Password" id="text"></td>
</tr>
<tr>
<td rowspan="2"><p> </p>
<p> </p></td>
<td><input type="submit" value="Submit" id="text2" style="width:100px;
</form>
</table>
</div>
<div id="">
</div>
</div>
</form>
</table>
64
</body>
</html>
<head>
<title>Registration Form</title>
</head>
<body>

<div id="">
</div>

<h3 align="left" style="font- family:Verdana, Geneva, sans-serif;">STUDENT
REGISTRATION</h3>
<table border="0" width="50%" align="left" cellpadding="2" c
ellspacing="2">
<tr>
<td colspan="2"><img src="images (7).jpg" width="150px" style="margin-
65
</tr>
<tr>
<td colspan="2"><strong>Fill the form carefully all fields are
mandatory</strong></td>
</tr>
<td colspan="2"><strong>Personal Details</strong></td>
</tr>
<tr>
<td width="179" align="left" style=" HEIGHT: 15px"> Student Full
Name:</td
<td width="144"> <input type="name" size="24" maxlength="70"
name="uname" required="required" placeholder="ENTER FULL NAME"
id="text"> </td>
</tr>
<tr>
<td width="179" align="left" style=" HEIGHT: 15px"> Father's
Name:</td>
<td> <input type="name" size="24" maxlength="70" name="uname"
required="required" placeholder="ENTER FATHER'S NAME"
id="text"></td>
</tr>
<tr>
<td width="179" height="29" align="left" style=" HEIGHT:
15px"> Mother's Name:</td>
66
<td><label for="textfield267"></label ><input type="name" size="24"
maxlength="70" name="uname" required="required" placeholder="ENTER
MOTHER'S NAME" id="text"></td>
</tr>
<tr>
<td width="179" align="left" style=" HEIGHT: 15px"> Date of
Birth:</td>
<td><label for="textfield268"></label> <input type="name" size="24"
DOB" id="text">
</td>
</tr>
<tr>
<td width="179" align="left" style=" HEIGHT: 15px"> Address:</td>
ADDRESS" id="text"></td>
</tr>
<tr>
<td width="179" align="left" style=" HEIGHT: 15px"> Email
id:</td>
EMAIL" id="text"></td>
67
</tr>
<tr> <td width="179" align="left" style=" HEIGHT:
15px">Contact No:</td>
<td><input type="name" size="24" maxlength="70" name="text"
required="required" placeholder="ENTER CONTACT NUMBER" id="text2"
/></td>
</tr>
<tr>
<td height="32">Upload File:</td>
<td><input type="file" size="24" maxlength="70" name="text" required
name="abc" placeholder="Upload Resume" id="text2" /></td>
</tr>
<tr>
<td colspan="2" style="WIDTH: 174px; HEIGHT: 15px></td>
</tr>
<tr>
<td colspan="2"><strong>Education Details</strong></td>
</tr>
<tr>
<td width="179" align="left" style=" HEIGHT: 15px"> High School
Obtained Marks: </td>
MARKS" id="text"></td>
68
</tr>
<tr>
<td width="179" height="26" align="left" style=" HEIGHT:
15px"> Board:</td>
<td><label for="textfield273"> <input type="name" size="24"
BOARD" id="text"></label></td>
</tr>
<tr>
<td width="179" align="left" style=" HEIGHT: 15px"> Intermediate
Obtained Marks:</td>
</tr>
<tr>
<td width="179" align="left" style=" HEIGHT: 15px"> Course:</td>
<td><label for="select"></label>
<select size="1" name="course" id="select">
<option selected>BBA</option>
<option>MBA</option>
<option>BCA</option>
<option>MCA</option>
69
</select> </td>
</tr>
<tr>
<td width="179" align="left" style=" HEIGHT: 15px"> Board:</td>
BOARD" id="text"></td>
</tr>
<tr>
<td width="179" align="left" style=" HEIGHT: 15px"> 1sem
obtained marks:</td>
</tr>
<td width="179" align="left" style=" HEIGHT: 15px"> 2sem obtained
marks:</td>
</tr>
<tr>
70
marks:</td>
</tr>
<tr>
marks:</td>
<td> <label for="textfield279"></label ><input type="name" size="24"
</tr>
<tr>
marks:</td>
</tr>
<tr>
marks:
</td>
71
<td> <input type="name" size="24" maxlength="50" name="uname"
required="required" placeholder="ENTER MARKS" id="text"> </td>
</tr>
<tr>
<td width="179" align="left" style=" HEIGHT: 15px"> University
Roll No:</td>
ROLLNO" id="text"></td>
</tr>
<tr>
<td colspan="2" style="WIDTH: 174px; HEIGHT: 15px"></td>
</tr>
<tr>
<td colspan="2"><strong>Fees Details</strong></td>
<tr>
<td width="179" align="left" style=" HEIGHT: 15px">1sem:</td>
1SEM FEES" id="text"></td>
</tr>
<tr>
<td width="179" align="left" style=" HEIGHT: 15px"> 2sem:</td>
72
</tr>
<tr>
</tr>
<tr>
<tr>
</tr>
<tr>
<td width="179" align="left" style=" HEIGHT: 15px"> 6sem: </td>
73
</tr>
<tr>
<td colspan="2" align="left" style=" HEIGHT: 15px" WIDTH: 174px>
</td>
</tr>
<tr>
<td align="left" style=" HEIGHT: 15px"> </td>
<td>
<input type="submit" style="background-color:#F00; color:#FFF;
height:30px;" name="button" id="button" value="Submit" />
<tr>
<td height="22" colspan="2"> <strong>If you already registered click here to
preview <a href="Indexpage.php" title="Home">Home</a>
<strong>page</strong></td>
</tr>
</table></td>
</tr>

</div>

74
<div id="">
</div>

</table></td>
</tr>
</table></td>
</tr>
</table></td>
</tr>
</table></td></body>
</html>
<html>
<title>Admin</title>
</head>
<body>

<div id="">
</div>

75
<h1 align="center" style="font-family: Arial, Helvetica, sans-
serif;">ADMINSTRATION</h1>
<h2></h2>
</div>
</div>
<tr height="200px">
<td colspan="2"><img src="images.jpg" width="150px" style="margin-
</tr>
<tr>
<td>USERNAME</td>
<td><input type="name" required name="username"
placeholder="USERNAME" id="text"></td>
</tr>
<tr>
<td>PASSWORD</td>
<td><input type="password" required name="password"
placeholder="PASSWORD" id="text"></td>
</tr>
<tr>
<td><p> </p>
<p> </p></td>
76
<td><input type="submit" value="Login" id="text2" style="width:100px;
</tr>
</form>
</table>
</div>

<div id="">
</div>

</div>
</form>
</table>
</body>
</html>
<div id="">
<h1 align="center" style= "font-family:'Times New Roman', Times,
serif";>ONLINE STUDENT REGISTRATION SYSTEM</h1>
</div>
77
<p> </p>
<p> </p>
<p> </p>
<p> </p>
<p> </p>
<p> </p>
<p> </p>
<p> </p>
<p> </p>
<p> </p>
<p> </p>
<footer class="">
<div class="">
<div class="" align="center">
<p><b> Copyright ©2016-2017----All Rights Reserved
</b></p>
</div>
</div>
</footer>
</body>
</html>
78
<?php
$con=mysql_connect("localhost","root","");
mysql_select_db("osrs");
?>
<?php
session_start();
mysql_connect("localhost","root","");
mysql_select_db("osrs");
$t=mysql_query("select name,password from user where
name='$_POST[username]' && password='$_POST[password]'");
$rl=mysql_fetch_array($t);
$_SESSION['name']=$rl['name'];
$r=mysql_num_rows($t);
if($r==1){
echo "login sucessfull";
echo "<meta http-equiv='refresh' content='0;
URL=Administration Login.php' />";
else
echo "invalid login...";
79
?>
<?php
include('config.php'); ?>
<?php session_start(); ?>
<html>
<title>OSRS</title>
<head>
</head>
<body>

<div id="">
</div>

<tr>
<td><a href="SignUp.php" align="left"><input type="submit"
style="width:100px; color:#43484A; background-color:white;"
value="BACK"></a></td>
80
<td>
<?php
if($_SESSION['name'])
$name = $_SESSION['name'];
?>
</tr>
</table>
<br><br>
<?php
$y=$_GET['name'];
if($y=="login") {
$sql=mysql_query("SELECT * from login ");
echo "<table border='1px' align='center' width='800px'>";
echo "<tr align='center'>
<td width='30px'>id</td>
<td width='30px'>password</td>
81
<td width='30px'>username</td>
<td width='30px'>email</td>
</tr>";
while($r=mysql_fetch_array($sql))
echo "<tr align='center'>";
echo "<td width='100px'>".$r['id']."</td>";
echo "<td width='100px'>".$r['password']."</td>";
echo "<td width='100px'>".$r['username']."</td>";
echo "<td width='100px'>".$r['email']."</td>";
echo "</tr>";
echo "</table>"
elseif($y=="user") {
$sql=mysql_query("SELECT * from user ");
<td width='30px'>username</td>
<td width='30px'>password</td>
</tr>";
82
echo "<td width='100px'>".$r['username']."</td>";
echo "<td width='100px'>".$r['password']."</td>";
echo "</tr>";
echo "</table>";
elseif($y=="registration") {
$sql=mysql_query("SELECT * from registration ");
<td width='30px'>student_name</td>
<td width='30px'>father_name</td>
<td width='30px'>mother_name</td>
<td width='30px'>date</td>
<td width='30px'>month</td>
<td width='30px'>year</td>
<td width='30px'>address</td>
<td width='30px'>email_id</td>
<td width='30px'>contact</td>
<td width='30px'>high_school_marks</td>
<td width='30px'>board1</td>
<td width='30px'>intermediate_marks</td>
83
<td width='30px'>course</td>
<td width='30px'>board</td>
<td width='30px'>1sem_marks</td>
<td width='30px'>university_rollno</td>
<td width='30px'>1sem_fees</td>
</tr>";
echo "<td width='100px'>".$r['student_name']."</td>";
echo "<td width='100px'>".$r['father_name']."</td>";
echo "<td width='100px'>".$r['mother_name']."</td>";
echo "<td width='100px'>".$r['date']."</td>";
84
echo "<td width='100px'>".$r['month']."</td>";
echo "<td width='100px'>".$r['year']."</td>";
echo "<td width='100px'>".$r['addres']."</td>";
echo "<td width='100px'>".$r['email_id']."</td>";
echo "<td width='100px'>".$r['contact']."</td>";
echo "<td width='100px'>".$r['high_school_marks']."</td>";
echo "<td width='100px'>".$r['board1']."</td>";
echo "<td width='100px'>".$r['intermediate_marks']."</td>";
echo "<td width='100px'>".$r['course']."</td>";
echo "<td width='100px'>".$r['board']."</td>";
echo "<td width='100px'>".$r['1sem_marks']."</td>";
echo "<td width='100px'>".$r['university_rollno']."</td>";
echo "<td width='100px'>".$r['1sem_fees']."</td>";
85
echo "</tr>";
echo "</table>";
elseif($y=="update") {
$sql=mysql_query("SELECT * from update ");
<td width='30px'>fname</td>
<td width='30px'>lname</td>
<td width='30px'>session</td>
<td width='30px'>rollno</td>
<td width='30px'>branch</td>
<td width='30px'>year</td>
<td width='30px'>semester</td>
<td width='30px'>mm</td>
<td width='30px'>dd</td>
<td width='30px'>yy</td>
<td width='30px'>address</td>
</tr>";
86
echo "<td width='100px'>".$r['fname']."</td>";
echo "<td width='100px'>".$r['lname']."</td>";
echo "<td width='150px'>".$r['session']."</td>";
echo "<td width='100px'>".$r['rollno']."</td>";
echo "<td width='100px'>".$r['branch']."</td>";
echo "<td width='100px'>".$r['year']."</td>";
echo "<td width='100px'>".$r['semester']."</td>";
echo "<td width='100px'>".$r['mm']."</td>";
echo "<td width='100px'>".$r['dd']."</td>";
echo "<td width='100p0x'>".$r['yy']."</td>";
echo "<td width='100px'>".$r['address']."</td>";
echo "</tr>";
echo "</table>";
elseif($y=="delete") {
$sql=mysql_query("SELECT * from delete ");
<td width='100px'>rollnno</td>
</tr>";
87
echo "<td width='100px'>".$r['rollnno']."</td>";
echo "</tr>";
echo "</table>";
?>
</div>

<div id="">
</div>

</div>
</body>
</html>
<?php require("header.php");?>
echo "<h1>you are registered
<a href="Registration Form.php"></a></h1>";?>
echo"click here to login
<a href="Onlinelogin.php">
88
click here</a>";
?>
<?php require("footer.php");?>
<?php require("header.php");?>
echo "<h1>you are registered
<a href="Registration Form.php"></a></h1>";?>
echo"click here to login
<a href="Onlinelogin.php">
click here</a>";
?>
<?php require("footer.php");?
89
7. 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.
7.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
90
 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.
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.
91
 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
7.2 Test Cases
NO INPUT EXPECTED ACTUAL TEST ACTION
GIVEN OUTPUT OUTPUT PASS TAKEN
OCCURED
1 Admin , pass Admin Admin Yes -
Home page Home page
3 Admin, kumar Admin Invalid No The wrong
Home page password password
for user ***** is
Admin given for
user Admin.
92
4 SignUp,Sanjana Signup Page Please enter No The
a valid wrong
password. password
******* is
given for
user
sanjana.
93
8. 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.
8.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.
94
BIBLIOGRAPHY
 PHP VERSION 5.5
 WWW.GOOGLE.COM
 EXPERTIZE IN PHP 6.0
 PHP PROGRAMMING
 MYSQL DATABASE
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174

Osrs 170209130721

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Osrs 170209130721

Uploaded by

Copyright:

Available Formats

Online Student Registration

PROJECT GUIDE: SUBMITTED BY:

Faculty of Computer Science Applications

This is to certify that the project entitled “Online Student Registration

Date: 12/01/2017 Signature of Guide

Place:Haldwani Mrs.Anuja Sharma

NAME UNIVERSITY CLASS

We gratefully acknowledge for the assistance, cooperation, guidance and

We perceive as this opportunity as a big milestone in my career

Software Requirement Specification

Particulars Page Nos.

1.3. Definitions, Acronyms, and Abbreviations......................................... 9

2. The Overall Description...............................................................................12

2.1. Product Perspective..............................................................................12

2.1.1. System Study………………………………………………….12

2.1.3. Hardware Interfaces...................................................................14

2.1.4. Software Interfaces.................................................................... 15

2.1.5. Communications Interfaces…………………………………...29

2.1.6. Memory Constraints....................................................................29

2.1.8. Site Adaptation Requirements.....................................................29

2.2. Product Functions..................................................................................30

2.3. User Characteristics................................................................................30

2.5. Assumptions and Dependencies.............................................................31

3.1. External Interfaces.................................................................................32

3.3. Performance Requirements.................................................................33

3.4. System Analysis..................................................................................34

3.5. Software System Attributes............................................................... 40

3.6. Organizing the specific Requirements.................................................43

3.6.1. System Mode............................................................................43

3.6.2. User Class.................................................................................43

3.6.7. Functional Hierarchy.................................................................44

4.1. File/Database Design…………………………………………………45

7.1. Testing Methods……………………………………………………..91

7.2. Unit Testing, Class Testing………………………………………….92

7.3. Test Cases…………………………………………………………...92

8.1. Scope for Future Prospects……………………………………..94

most important activities within a university as one cannot survive without

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

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.

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

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

Without an Online Student Registration System, managing and maintaining

the details of the student is a tedious job for any organization.

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.

we have to update/search a particular student and 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.

What contribution would the project make?