1.

Introduction:
Student admissions are a vital part of any college’s running because students are
what keep a College alive. The student admission is one of the most important
activities within a college as one cannot survive without students. A poor
admissions system can mean fewer students being admitted into a college
because of mistakes or an overly slow response time. The process begins with a
potential student completing an application form through the Universities and
Colleges Admissions Service, the first step for students is to apply directly to
the college through a custom online form. The next step is for the Admissions
service center has to review the application and ensure that all of the required
information has been provided, from the form itself to the supplementary
documentation, such as language and degree certificates. If any of the required
information is missing, it is the secretary for the department to which the
application concerns that contacts the potential student and arranges for the
delivery of the outstanding data. The application in its entirety is then
forwarded, complete with a recommendation, to the respective department’s
Admissions Head, who has the final say as to whether each potential student is
accepted or rejected. Before making a decision, the Admissions head reviews
the application and the additional documentation, comparing the academic
credentials to a list of college rankings and previous, similar applications.
Online Admission System is web based system that provides the facility to
conduct online Admission Process.

There are three types of people who participate in this system first one is the
student second is user and last one is the administrator.

Following are the modules of Online Examination System:-

(1) Administrator:
The Administrator can add course, & branch to the database, add new user to
the database and issue a valid ID & password for student.

(2) Student:
New Student can fill the admission form online. After verification when user ID
and Password is granted then he can also view and modify own details.

1
(3) HOD:
HOD can search the record of student by name, rollno, and sem of own
department and he can also able to view full profile of selected student.

(4) Account Section:

Account Section(STAFF) can verify the admission form of student and also
able to change the information if required. And also verify the fees when
received the chalan.

2 Requirements and Analysis:

The following sections will introduce the numerous requirements of the system
from the point of view of different users and will introduce a number of
decisions that have been made regarding implementation. These sections also
attempt to somewhat describe the role of each user group in the system,
discussing their individual roles through the functions they can perform.

2.1 User Requirements:

2.1.1 User Interface

The user interface for this system will have to be simple and clear.
Most importantly, the ages must be easy to read, easy to understand and
accessible. The color scheme should be appropriate to provide familiarity with
the college and there should be no contrast issues.

2.1.2 Student View Functionality:

Registration and Login System: Applicants will carry out their own
registration, providing the system with a way to associate a user to their
application(s). This will enable the system to display personalized information
when the user logs in and certain information, such as name and address, to be
added to each application automatically. Giving each student a specific ID will
also allow a user to apply to a number of courses, while giving the system a way
to prevent unnecessary duplication of applications.
2
Application System: The application process will be as straightforward as
possible, using an intuitive form layout, with the necessary information being
completed in stages. When regarding supplementary documentation, such as
degree transcripts, these could be uploaded through the form in digital format,
upon which it will be saved to the database and associated with the application,
being accessible by both the admissions office staff and heads.

2.1.3 Admissions View Functionality:

View Submitted Applications: Viewing all of the recently submitted

applications is something the admissions office will do on a regular basis. A list
of all the submitted applications, oldest to newest to prevent some applications
remaining unread, will be viewable, each of which expandable to view the
entire details. This list will be a set size, for example the last two days, but this
value will be variable to enable more or fewer applications to be displayed.
2.1.4 Admin:

View Approved Application: Much like the view submitted applications page
for admissions office staff, view approved applications will list the applications,
oldest to newest, that were deemed of a suitable quality to forward to an
admissions head. The main difference with the approved applications is that
each is only sent to one head, thus there is no need for a locking mechanism.

2.1.5 System

Validation: On the completion of each form in the system, the system will use
a set of validation functions to ensure that information is of the right type in
each field.

Make Recommendations: The system should be able to make

recommendations to the head which will be decided once an application has
been submitted by the admissions office. The system could make its
recommendation based on the ranking of the application, where any rank above
a certain threshold would be accepted and any below would be rejected.

3
Report Generation: Generate reports based on the selected criteria.

2.2 Existing System:

In present, all work is done manually by hand in bulk of files which is hard to
operate and
hard to maintain the reports of the student presently, took admission in institute.
1. When the student comes in college.
2. First of all, he/she takes admission form from reception.
3. Fills it and submits it into office.
4. Filled form is first checked with documents like merit list and details came
from college and verified by an official person, if there is any mistake then it is
corrected.
5. At the time of submission of it the fees is deposited by the candidate.
6. At the time of submission of admission form Enrollment no. is assigned to
the candidate by the institute.
7. Candidate gets the receipt of fees deposition.
2.3 Proposed System:

1. It is automated computerized web based software system.

2. It uses latest technologies like ASP.NET and SQL Server.
3. It is easy to operate.
4. Attractive User Interface.

2.4 System Requirements and Analysis:

4
User Side:

Hardware:
 Processor Pentium IV 2.0 GHz
 Ram 512 MB
 Hdd-80 GB Capacity With 256 MB Free Space
 LAN Card

Software:
 Any Operating System
 Compatible Browser

Developer Side:

Hardware:
 Processor Pentium IV 2.0 GHz
 Ram 1 GB
 Hdd-80 GB Capacity With 4 GB Free Space
 LAN Card

Software:
Front-end Tools:

 Windows XP SP2 or Higher

 ASP.NET 3.5
 VISIUAL STUDIO 2010/ VISIUAL STUDIO 2008

Back-end Tools:

 MS-SQL SERVER

3. Plan of Software Development

5
The project of “Online Admission System” has been developed in following
stages:

 Analysis
 Modules
 Design
 Coding
Analysis: In the analysis phase, information about the current technology in the
field of web application and on .net has been collected and studied from the
concerned websites and books. We have also gone through the already available
software in the concerned field, to have a look & feel of their mode of
operation. Also questioned were asked from general public for their
requirements and view for the concerned software.

Modules : To implement all the features, the SSTBOS system needs to have the
following modules:

 Login module to check the credentials of registered users.

 Registration module to register a new user.

Design : In the design phase DFD’s and flow charts of the software are
developed, and the software has been modularized. To develop the interface
referenced has been taken from the already available software in the concerned
field. To develop the Software we create two type design phase.

1. DataBase Design Phase

2.User Interface Design Phase

3.1E-R Diagram :
6
formno course

name branch

cname
fname dob
cid
sem
mname email

Student * 1 Course
Offers
sem
* *
paddress

Takes
rollno Contains

photo
1
*
password Branch

bname
bid
cid

3.2 DataBase Design Phase:

In this phase we create database .We are use following database in our project.

7
1.admin

2.course

3. branch

4. newStudent

8
User Interface Design Phase:

In this phase we are develop the Data Flow Diagram and E-R Diagram. We are
following DFDS and ERD use in our project.

3.3.Data Flow Diagram

1.Student
9
 Student login

Invalid

Check login studentlogin

Valid

Show profile

Logout

2.admin

10
 Admin login

Invalid
Check login
Adminlogin

Valid

Menu

Add course
Add user Add B ranch

USER COURSE BRANCH

3. newStudent

New student registration

11
 Fill student information

Print form

Account department

Check details Verify details

Details checked Details verified

12
 4. Account Section

Staff Login

Invalid
Check login
Staff Login

Valid

Menu

Verify Admission
Check Student Details Verify fee

Coding : The coding part of the software is done in .net framework, and the
interfaces are developed using ASP.net2.0 .

13
4 TESTING
The Process of analyzing a s/w item to detect the differences between existing
and required conditions (i.e. Bugs) and to evaluate the features of the s/w items
is called the Testing.The process of analyzing a program with the intent of
finding errors is called the testing.

During testing, the program to be tested is executed with a set of test cases, and
the output of the program for the test cases is evaluated to determine if the
program is performing as expected. From this it is clear that testing is used to
find out errors rather than to tell the exact nature of error. Also, the success of
the testing process clearly depends upon the test cases used.

Testing is a complex process. In order to make the process simpler, the testing
activities are broken into smaller activities. Due to this, for a project,
incremental testing is generally performed. In incremental testing process, the
system is broken into set of subsystems and these subsystems are tested
separately before integrating them to form the system for system testing.

4.1TEST CASES

In this project we had run different types of web pages separately & check there
output & also we make some test cases for the pages.

1. Entering a wrong user id and password into the login request

Result – failure occur to login
2. Submitting the form without fulfilling the necessary condition into the
login form.
Result- failure occur to login.
3. Entering a right user id and password into the login request
Result – Successful login
4. Submitting the form after fulfilling the necessary condition into the login
form.
.

14
4.2 Testing Techniques
S.No. Test Cases Expected O/P on 1st O/P on 2nd O/P on 3rd
Output run run run
1 Student Success Fail Success Success
Registration
2 Add Users Success Fail Fail Success

3 Add Course Success Success Success Success

4 Add Branch Success Fail Success Success

5 Photo Upload Success Fail Success Success

6 Edit profile Success Success Success Success

7 Date Of Birth Success Fail Fail Success

4.2.1 BLACK BOX TESTING

In this type of testing there is no need to know the codes work. A person
without the knowledge of internal schema could perform this test. In the testing
approach test data is derived from the specification of the program and is
carefully selected to test every possible combination of the inputs

Every possible combination of input is inserted to check whether the code is

giving the expected result of not.

4.2.2 WHITE BOX TESTING

Suppose the program code is to be submitted to a professional.

And the presentation might disclose some bugs, which are otherwise hard to
find, resulting in a strong psychological influence on the programmer. During
such a presentation the internal structure of the program is disclosed with the
main goal to detect faults.

The test data is selected to test every bit of code. This requires a detailed
knowledge of the code to be tested. Since the emphasis of the test is the
15
individual codes, the test data may be illogical when compared with the
program specifications.

Namespace Used :

1. System Namespace
Contains classes that allow you to match URIs against URI Templates and
groups of URI Templates.

2. System.Web.UI Namespace

The System.Web.UI namespace provides classes and interfaces that enable you
to create ASP.NET server controls and ASP.NET Web pages for the user
interface of your ASP.NET Web applications.

This namespace includes the Control class, which provides a common set of
functionality for all server controls, which includes HTML server controls, Web
server controls, and user controls. It also includes the Page class. This class is
generated automatically whenever a request is made for an .aspx file in an
ASP.NET Web application. You can inherit from both of these classes.

The namespace also includes classes that provide the server controls with data-
binding functionality, the ability to save the view state of a given control or
page, and parsing functionality.

3.System.Web.UI.WebControls Namespace

The System.Web.UI.WebControls namespace contains classes that allow you to

create Web server controls on a Web page. Web server controls run on the
server and include form controls such as buttons and text boxes. They also
include special-purpose controls such as a calendar. Because Web server
controls run on the server, you can programmatically control these elements.
Although Web server controls are rendered as HTML, their object model does
not necessarily reflect HTML syntax.

The System.Web.UI.WebControls namespace contains classes that are rendered

as HTML tags, such as the TextBox control and the ListBox control. The
16
namespace also contains classes that are not rendered on the Web page, but
support data operations, such as the SqlDataSource and ObjectDataSource
classes. Other controls, such as the GridView and DetailsView controls, support
data display and editing. The WebControl class serves as the base class for
many of the classes in the System.Web.UI.WebControls namespace.

4. System.Web.UI.WebControls.WebParts Namespace
The System.Web.UI.WebControls.WebParts namespace contains classes and
interfaces known collectively as the Web Parts control set. You can use these
classes to create Web pages whose appearance and behavior can be modified
(personalized) by end users. Each user's personalized settings for a page are
saved for future browser sessions.

5. System.Web.UI.HtmlControls Namespace

The System.Web.UI.HtmlControls namespace contains classes that allow you to

create HTML server controls on a Web Forms page. HTML server controls run
on the server and map directly to standard HTML tags supported by most
browsers. This allows you to programmatically control the HTML elements on
a Web Forms page.

6. System.Xml.Linq Namespace
Contains the classes for LINQ to XML. LINQ to XML is an in-memory XML
programming interface that enables you to modify XML documents efficiently
and easily.

Using LINQ to XML, you can:

Load XML from files or streams.

Serialize XML to files or streams.

Create XML trees from scratch using functional construction.

Query XML trees using LINQ queries.

Manipulate in-memory XML trees.

Validate XML trees using XSD.

Use a combination of these features to transform XML trees from one shape
into another.
17
7. System.Collections.Generic Namespace
The System.Collections.Generic namespace contains interfaces and classes that
define generic collections, which allow users to create strongly typed
collections that provide better type safety and performance than non-generic
strongly typed collections.

8. System.Data Namespace

The System.Data namespace provides access to classes that represent the

ADO.NET architecture. ADO.NET lets you build components that efficiently
manage data from multiple data sources.

In a disconnected scenario such as the Internet, ADO.NET provides the tools to

request, update, and reconcile data in multiple tier systems. The ADO.NET
architecture is also implemented in client applications, such as Windows Forms,
or HTML pages created by ASP.NET.

The centerpiece of the ADO.NET architecture is the DataSet class. Each

DataSet can contain multiple DataTable objects, with each DataTable
containing data from a single data source, such as SQL Server.

9. System.Configuration Namespace
The System.Configuration namespaces contain types for handling configuration
data, such as data in machine or application configuration files. Child
namespaces contain types that are used to configure an assembly, to write
custom installers for components, and to support a pluggable model for adding
functionality to, or removing functionality from, both client and server
applications.

10. System.Collections Namespace

The System.Collections namespaces contain types that define various standard,

specialized, and generic collection objects

18
11. System.Web.Security Namespace

The System.Web.Security namespace contains classes that are used to

implement ASP.NET security in Web server applications.

The Membership class is used by ASP.NET applications to validate user

credentials and manage user settings such as passwords and e-mail addresses.
The Roles class enables you to manage authorization for your application based
on groups of users assigned to roles in the Web application.

12. System.Data.SqlClient Namespace

The System.Data.SqlClient namespace is the.NET Framework Data Provider

for SQL Server.

The.NET Framework Data Provider for SQL Server describes a collection of

classes used to access a SQL Server database in the managed space. Using the
SqlDataAdapter, you can fill a memory-resident DataSet that you can use to
query and update the database.

13. System.Net Namespace

The System.Net namespaces contain classes that provide a simple programming

interface for a number of network protocols, programmatically access and
update configuration settings for the System.Net namespaces, define cache
policies for web resources, compose and send e-mail, represent Multipurpose
Internet Mail Exchange (MIME) headers, access network traffic data and
network address information, and access peer-to-peer networking functionality.
Additional child namespaces provide a managed implementation of the
Windows Sockets (Winsock) interface and provide access to network streams
for secure communications between hosts.

14. System.Net.Mail Namespace

The System.Net.Mail namespace contains classes used to send electronic mail

to a Simple Mail Transfer Protocol (SMTP) server for delivery.

19
The MailMessage class represents the content of a mail message. The
SmtpClient class transmits email to the SMTP host that you designate for mail
delivery. You can create mail attachments using the Attachment class.

6. Change management Process

As a team, we will update and evaluate our SRS document every week as we
make changes in our design and requirements. We will add new detailed
information which will include: research, references, charts and graphs, and
more specifications and requirements that we find along the way in the
designing and implementation of the product.

5. SWOT Analysis:

20
S : Strength
W : Weakness
O : Future Opportunities
T : Threats

Subject of SWOT analysis: Online Admission System

Strengths Weaknesses

 Cost Production is low.  May take more time to load.

 High quality and reliability.  Already enrolled students have to fill
 Manual work is reduced. form again.
 https not used.

Opportunities Threats

 End users provide new ideas  Website may be hacked.

 Online submission of fees. 

6 CONCLUSION

21
 The Project “Online admission system” is very useful for any organization,
company for taking online test of student. This is web based project so any
organization take exam of many students in intranet (LAN).It shows result of
exam immediately. In this project I am given to security to all user, student and
administrator.

This project is easy to deploy in LAN. It is very user-friendly

project. It’s not difficult. This project is save time of taking exam process of any
organization. Here administrator can create, update and delete batches. User can
register the student information, he can also update and delete information of
student.

7 References: -

22
 Ian Somerville, “Software Engineering”, Sixth Edition,
Pearson Education Ltd, 2002.
 Elamsri and Navathe, “Fundamentals of Database Systems”, Pearson
Asia Edition 2000.
 Google.
 Wikipedia.
 WWW.ASP.NET

23