Web Based Examination Cell Application

Web Based Examination Cell Application
1. INTRODUCTION
Web Based Examination Cell Application (WECA) helps many colleges that
are facing the problem of seat allotment of students to classes during examinations and
other similar problems. WECA solves the problem of arranging manually and
randomizing the students roll numbers. Software is actually defined as the combination
of programs with different functionalities. This particular software helps the people of
the examination cell to simplify their operations. This software’s main need is to
automate the manual process done by the examination cell personnel. The unified
Modelling Language (UML) is one of the most exciting tools in the world of system
deployment today, the UML enables system builders to create blue prints to capture
their vision in a standard, easy to understand way and communicate them to other. .NET
is the Microsoft Web services strategy to connect information, people, systems, and
devices through software. Integrated across the Microsoft platform, .NET technology
provides the ability to quickly build, deploy, manage, and use connected, security-
enhanced solutions with web services. .NET connected solutions enable businesses to
integrate their systems more rapidly and in a more agile manner and help them realize
the promise of information anytime, anywhere, on any device. By using this software,
we give roll numbers and room numbers and we get allotted rooms as output.
S.V.COLLEGE OF ENGINEERING, Dept. of C.S.E Page |1

2. PROJECT DESCRIPTION
2.1 INTRODUCTION
For any organization, maintenance of the information is very important.
The collection of information and a set of programs to access that data are called
DATABASE MANAGEMENT SYSTEM. Design of a database management
system involved defining data structure for storing the data and providing
mechanisms to retrieve and manipulate the data. The database of the engineering
college consists of the data regarding Students, Staff and Library.
2.2 USERS
Database Administrator
The specification responsibility is to manage the data. The special set of
privileges given to him is the complete authority over the database. His job is to
control the space allocation for database objects, take back-up of the data and perform
the data insertion, deletion, updating and retrieval.
End User
The functionality is, will access the database through a query language or an
application program.
The important phases regarding the database maintenance are insertion,
deletion and updating.
Insertion: This phase allows adding data to the existing files or records.
Deletion: The user has full authority to delete any file from the system.
Updating: The user can add, delete and modify the files data. Updating includes
writing the file initially rewriting it completely or in part and removing all or a portion
of the data.
Access can be provided to the following classes of users
Specific User: Individual user designated with a specific User-ID.
User Groups: A set of users who are not individually define. The system must have
some way of keeping track of the Membership of User Groups.
All: These are the public files. All users have access to this system.

2.3 CAPABILITIES OF WECA

Supports access to more than one user simultaneously in a LAN:
Local area networks are privately-owned networks with in a single building or
campus of up to a few kilometres in size. They are widely used to connect personal
computers and workstations in company offices and factories to share resources such as
printers and exchange information. As WECA supports LAN throughout the campus
data can be accessed to more than one user simultaneously.
The database administrator can regulate some parts of the database by
authorization to access only a limited portion of the database. The data stored in the
database need protection from unauthorized access such as
 Unauthorized reading of data.
 Unauthorized modification of data.
 Unauthorized destruction of data.
As the users are provided with specific User-ID only an authorized user can
modify the data and access to only a particular part in the database.
Supports user related search
User can search for the information needed through authorization.
Supports for a well-defined extension mechanism
As WECA supports LAN which has the property of resource sharing helps to extend
system for further enhancements in the future development.
2.4 SUMMARY
As the above project is developed using .NET it provides a user friendly
graphical user interface which navigates him throughout the program by providing
various task related to the authorized user. It provides all the facilities, which are
provided to the user by the database administrator. Present project is capable of
configuring the authorized user to access the data which has the entire control over the
database management. In the above project the client is either student or staff or the
administrator, depending on the authorization the user can easy communicate with
respective database and access his details with all the facilities provided to him.

3. COMPUTATIONAL ENVIRONMENT
3.1 INTRODUCTION
This chapter deals with the computational environment required to run our
project. It also defines what a software requirement specification is and also defines the
software and hardware requirements of our project. Later in this chapter we discuss the
functionalities in our software.
3.2 REQUIREMENTS
3.2.1 Software Requirements
Operating system : Windows XP/2000

Front end : ASP.NET
Back end : SQL server 2000
Browser : Internet Explorer
3.2.2 Hardware Requirements
Processor : P4 processor, (1.1GHZ)
RAM : 256 MB or more
Hard Disk : 40 GB HDD
3.3 INTRODUCTION TO .NET

System Architecture
Fig 3.3.1 .NET Architecture

.NET
Fig 3.3.1 describes the .NET Architecture. .NET is the Microsoft Web services
strategy to connect information, people, systems, and devices through software.
Integrated across the Microsoft platform, .NET technology provides the ability to
quickly build, deploy, manage, and use connected, security-enhanced solutions with

web services. .NET connected solutions enable businesses to integrate their systems
more rapidly and in a more agile manner and help them realize the promise of
information anytime, anywhere, on any device.
.NET Framework
The .NET Framework is Microsoft’s application development platform that
enables developers to easily create Windows applications, web applications, and web
services using a myriad of different programming languages, and without having to
worry about low-level details like memory management and processor-specific
instructions.
Fig 3.3.2: .NET Framework

Language Independence
One of the most important facts of the .NET Framework is language
independence. Fig 3.3.2 describes this .NET Framework. You can write .NET
applications using any number of different programming languages. The most popular
languages tend to be C# and VB.NET, but many other languages now have .NET
versions including Python, COBOL, and more.
Language independence is attained through the use of an intermediate language
(IL). What this means is that instead of code being compiled in actual machine code
(code that the CPU would run), it is instead compiled into a high-level generic
language. This means that whatever language you write your code in, when you
compile it with .NET it will become IL. Since all languages eventually get translated
into the intermediate language, the runtime only has to worry about understanding and
working with the intermediate language instead of the plethora of languages that you
could actually use to write code.

The .NET Framework consists of

Common Language Runtime (CLR)
A language-neutral development and execution environment that provides
services to help “manage” application execution. .NET-compatible compilers do not
translate source code into Win32 API calls, but rather translate this high-level source
code into a special intermediate language, Microsoft Intermediate Language (MSIL).
The CLR, then, takes this intermediate language (IL) and, on the fly, converts it into
machine-specific instructions. A diagram of this process can be seen below:
Source code .NET MSIL

COMPILER
Running program
CLR
Fig 3.3.3: CLR
Fig 3.3.3 shows the working of CLR. Realize that the CLR-to-Running
Program step only occurs when you execute a program. The compiler creates a file that
contains MSIL. When this is “executed,” the MSIL is streamed to the CLR, which then
performs just-in-tine (JIT) compilation, converting the IL to instructions the computer
can understand. The divisions of CLR are defined in the Fig 3.3.4
The following are some of the benefits of the CLR:
 Performance improvements.
 The ability to easily use components developed in other languages.
 Extensible types provided by a class library.
 New language features such as inheritance, interfaces, and overloading for
object- oriented programming; support for explicit free threading that allows
creation of multithreaded, scalable applications; support for structured
exception handling and custom attributes.

COMMON LANGUAGE RUNTIME
CTS CLS
Fig 3.3.4: Division of CLR
Common Type System (CTS)
The common type system defines how types are declared, used, and managed in the
runtime, and is also an important part of the runtime’s support for cross-language
integration. The common type system performs the following functions:
 Establishes a framework that enables cross-language integration, type

o Safety and high performance code execution.
 Provides an object-oriented model that supports the complete

 Implementation of many programming languages.
 Defines rules that languages must follow , which helps ensure that
 Objects written in different languages can interact with each other.
For Example, if you have created a class in VB.NET, you can inherit from it using
them called the Common Language Specification (CLS) has been defined.
Components that follow these rules and expose only CLS features are considered CLS-
compliant. To fully interact with other objects regardless of the language they were
implemented in, objects must expose to callers only those features that are common to
all the languages they must interoperate with. If your component uses only CLS
features in the API that it exposes to other code (including derived classes), the
component is guaranteed to be accessible from any programming language that
supports the CLS. Components that adhere to the CLS rules and use only the features
included in the CLS are said to be CLS-complaint components.

Framework Class Library

A consistent, object-oriented library of pre-packaged functionality. This is defined
in Fig 3.3.5. Windows programmers coding in C, tend to rely on the Windows API and
functions in third-party DLLs to get their job done. C++ programmers often use class
libraries of their own creation or standard class libraries such as MFC. In the .NET
Framework, all these anachronistic API’s are done away with. Rather a new set of
functions branches in a C# program.
Fig 3.3.5: Framework Class Library
Common Languages Specification (CLS)

Languages interoperability is the ability of code to interact with code that is written
using a different programming language. Language interoperability can help maximize
code reuse and, therefore, improve the efficiency of the development process.
However, language compilers and tools that target the common language runtime
benefit from the runtime’s built-in support for language interoperability. To ensure that
you can develop managed code that can be fully used by developers using any
programming language, a set of language features and rules for ded as the framework
class library are introduced which contain more than 7000 types.
To make learning and using the FCL more manageable, Microsoft has divided the
FCL into hierarchical namespaces. The FCL has about 100 namespaces in all. Each

Namespace holds classes and other types that share a common purpose. For example,
much of the window manager portion of the windows API is encapsulated in the
System. Windows. Forms namespace. In this namespace classes that represent
windows, dialog boxes, menus, and other elements commonly used in GUI
applications are present. A separate namespace called Systems. Collections holds
classes representing hash tables, resizable arrays, and other data containers. Yet
another namespace, System.IO, contains classes for doing file I/O.
.NET Data Providers
ADO.NET relies on the services of .NET data providers. These provide access
to the underlying data source, and they comprise four key objects (connection,
command, Data Reader, and Data Adapter). These are shown in Fig 3.3.6.
Fig 3.3.6: .NET Data Providers

ADO.NET ships with two categories of providers: bridge providers and native
providers. Bridge providers, such as those supplied for OLE DB and ODBC, allow you
to use data libraries designed for earlier data access technologies. Native providers,
such as the SQL Server and Oracle providers, typically offer performance
improvements.
 The SQL .NET Data Provider. This is a provider for Microsoft SQL Server
7.0 and later databases. It is optimized for accessing SQL server, and it
communicates directly with SQL Server by using the native data transfer
protocol of SQL Server. Always use this provider when you connect to SQL
Server 7.0.

 The Oracle .NET Data Provider. The .NET Framework Data Provider for
Oracle enables data access to Oracle data sources through Oracle client
connectivity software. The data provider supports Oracle client software
version 8.1.7 and later.
 The OLE DB .NET Data Provider. This is a managed provider for OLE DB
data sources. It is slightly less efficient than the SQL Server .NET Data
Provider, because it calls through the OLE DB layer when communicating with
the database. Note that this provider does not support the OLE DB provider for
Open Database Connectivity (ODBC), MSDASQL.
Other .NET data providers currently in beta testing include:
 The ODBC .NET Data Provider. The .NET Framework Data Provider for
ODBC uses native ODBC Driver Manager (DM) to enable data access by
means of COM interoperability.
 A managed provider for retrieving XML from SQL Server 2000. The XML
for SQL Server Web update 2 (currently in beta) includes a managed provider
specifically for retrieving XML from SQL Server 2000.
Namespace Organization
The types (classes, structs, enums, and so on) associated with each .NET data
provider are located in their own namespaces:
 System.Data.SqlClient. Contains the SQL Server .NET Data Provider types.

 System.Data.OracleClient. Contains the Oracle .NET Data Provider.
 System.Data.OleDb. Contains the OLE DB .NET Data Provider types.
 System.Data.Odbc. Contains the ODBC .NET Data Provider types.
 System. Data. Contains provider-independent types such as the DataSet and
Data table.
Within its associated namespace, each provider provides an implementation of
the Connection, Command, Data Reader, and Data Adapter objects. The SqlClient
implementations are prefixed with “Sql” and the OleDb implementations are prefixed
with “OleDb”. For example, the SqlClient implementation of the Connection object
is SqlConnection, and the OleDb equivalent is OleDbConnection. Similarly, the two
incarnations of the Data Adapter objects are SqlDataAdapter and
OleDbDataAdapter, respectively.
Namespace Hierarchy
S.V.COLLEGE OF ENGINEERING, Dept. of C.S.E P a g e | 10

(* The Dataset, which is an in-memory cache of data retrieved from a data source, is a
major component of ADO.NET architecture. Build and fill each DataTable in a
Dataset with data from a data source using a Data Adapter.)
Syntax
For Database Connectivity
Con.connectionString=”Provider=MicroSoft.Jet.Oledb.4.0; Data source= F:/tms.mdb”
To execute a command
cmd= New OleDbCommand(“select * from master specification”, con)
dr= cmd.ExecuteNonQuery
Using Data Adapter
da= New OleDbDataAdapter(“select * from master specification”, con)
ds= New Dataset
da.Fill(ds)
ASP.NET
ASP.NET is a set of web application development technologies marketed by
Microsoft. Programmers can use it to build dynamic websites, web applications and
XML web services. It is part of Microsoft’s .NET platform and is the successor to
Microsoft’s Active Server Pages (ASP) technology. ASP.NET is built on the Common
Language Runtime, meaning programmers can write ASP.NET code using any
Microsoft .NET language.
ASP.NET Platform Requirements
ASP.NET is supported on Windows 2000 (Professional, Server, and Advanced
Server), Windows XP Professional, and the Windows Server 2003 family for both
client and server applications. In addition, to develop ASP.NET server applications,
the following software is also required:
 Windows 2000 Server or Advanced Server with Service Pack 2,
Windows XP
Professional or 64-Bit Edition, or one of the Windows Server 2003 family
products.

 MDAC 2.7 for Data

 Internet Information Services.
ASP.NET-Where does it fit with in .NET?
ASP.NET is Microsoft’s next “version” of ASP- it is basically ASP utilizing
the .NET factors. ASP.NET pages need to be created with .NET-compatible languages,
which include VB.NET, C#, and Jscript.NET.
When an ASP.NET page is visited via a Web browser, the ASP.NET engine
first checks to see if there already exists an up-to-data version of the IL code for the
ASP.NET page. If there does, this IL is squirted to the CLR, and the HTML output
generated by the ASP.NET page is then sent to the client’s browser that requested the
ASP.NET Web page. If, however, the IL does not exists at all or the ASP.NET pages
source code has changed since the last IL was generated, the ASP.NET page must be
recompiled. Depending on what language the ASP.NET page was written in, the
proper compiler is instantiated and the IL created. This IL is saved on disk so that, for
future requests, this recompilation, an expensive process, does not need to recur.
If you’ve created ASP.NET pages, you most likely aware of concept of Web
control. These are controls that can be used in ASP.NET Web page to produce HTML
elements like text boxes, labels, list boxes, etc. for example, to create a text box using a
Web control, one can do:
<asp: text id=”Name” runat=”server”/>
In fact, an ASP.NET Web page can contain a mix of server-side code (in server-side
SCRIPT blocks) along with in-line HTML, like:
<script language=”VB” runat=”server”/?
Sub page load (sender as object, e as EventArgs)
IblMessage.text=”Hello, Welcome to .NET!” End Sub</script>
<Html><body>
<h1>simple ASP.NET Demo</h1>
<asp: label id=” IblMessage” runat=”server”/>
</body></html>
So how does that HTML/server-side get translated into something that the
VB.NET compiler can understand? One of the ASP.NET engine’s most important
tasks is translating the HTML/server-side code into a class that the VB.NET compiler
(or C# or Jscript.NET compilers) can understand. This process is a difficult one does

be aware that your pages are turned into a class that inherits from the Page class (one
of the classes in the .NET Framework). In fact, all of the Web controls that you can use
in your ASP.NET Web pages are represented as classes in the .NET Framework.
ASPX file format
ASPX is a text file format used to create Web form pages; in programming
jargon, the ASPX file typically contains static HTML or XHTML markup, as well as
markup defining Web Controls and Web User Controls where the developer places all
the required static and dynamic content for the web page. Additionally, dynamic code
which runs on the server can be placed in a page within a block
<%--dynamic code-- %>
which is similar to other web development technologies such as PHP, JSP, and ASP,
but this practice is generally discouraged except for Data binding. The recommended
method for dealing with dynamic program code is to use the code-behind model,
which places this code in a separate file or in a specially designated script tag. Code-
behind files are typically named something to the effect of MyPage.aspx.cs or
MyPage.aspx.vb based on the ASPX file name (this practice is automatic in Microsoft
Visual Studio and other IDEs). When using this style of programming, the developer
writes code to respond to different events, like the page being loaded, or a control
being clicked, rather than a procedural walk through the document.
Performance
ASP.NET aims for performance benefits over other script-based technologies
(including ASP Classic) by compiling the server-side code to one or a few DLL files
on the web server. This happens transparently in background the first time a page is
requested (i.e., the developer need not perform a separate compilation step for pages).
This provides the ease for development offered by scripting languages with the
performance benefits of a compiled binary.
The ASPX and other resource files are placed in a virtual host on an Internet
Information Services (or other compatible ASP.NET servers; see Other
Implementation, below). The first time a client requests a page, the .NET framework
parser and compiles the file(s) into a .NET assembly and sends the response;
subsequent requests are served from the dll files.

3.4 INTRODUCTION TO MYSQL

A database management, or DBMS, gives the user access to their data and
helps them transform the data into information. Such database management systems
include dBase, paradox, IMS, SQL Server and SQL Server. These systems allow users
to create, update and extract information from their database.
A database is a structured collection of data. Data refers to the characteristics
of people, things and events. SQL Server stores each data item in its own fields. In
SQL Server, the fields relating to a particular person, thing or event are bundled
together to form a single complete unit of data, called a record (it can also be referred
to as raw or an occurrence). Each record is made up of a number of fields. No two
fields in a record can have the same field name.
During an SQL Server Database design project, the analysis of your business
needs identifies all the fields or attributes of interest. If your business needs change
over time, you define any additional fields or change the definition of existing fields.

SQL TABLES
SQL Server stores records relating to each other in a table. Different tables are
created for the various groups of information. Related tables are grouped together to
form a database.
Table 3.1: Branches
The Table 3.1 is created to store the different branches available in the college.
Table 3.2: Generate Roll Numbers
The Table 3.2 is created to generate and store the roll numbers according to the
university specifications.
Table 3.3: Holidays
The Table 7.3 is used to store the holidays to avoid the admin from allotting on that day.
Table 3.4: Lecture Halls
The Table 3.4 stores the details of the Lecture halls to which students are to be allotted.

Table 3.5: New Admission
The Table 3.5 is used to store the newly admitted student details at the beginning of the
academic year.
Primary Key
Every table in SQL Server has a field or a combination of fields that uniquely
identifies each record in the table. The Unique identifier is called the Primary Key, or
simply the Key. The primary key provides the means to distinguish one record from
all other in a table. It allows the user and the database system to identify, locate and
refer to one particular record in the database.
Relational Database
Sometimes all the information of interest to a business operation can be stored
in one table. SQL Server makes it very easy to link the data in multiple tables.
Matching an employee to the department in which they work is one example. This is

what makes SQL Server a relational database management system, or RDBMS. It

stores data in two or more tables and enables you to define relationships between the
tables and enables you to define relationships between the tables.
Foreign Key
When a field is one table matches the primary key of another field is referred to
as a foreign key. A foreign key is a field or a group of fields in one table whose values
match those of the primary key of another table.
Referential Integrity
Not only does SQL Server allow you to link multiple tables, it also maintains
consistency between them. Ensuring that the data among related tables is correctly
matched is referred to as maintaining referential integrity.
Data Abstraction
A major purpose of a database system is to provide users with an abstract view
of the data. This system hides certain details of how the data is stored and maintained.
Data abstraction is divided into three levels.
Physical level: This is the lowest level of abstraction at which one describes how the
data are actually stored.
Conceptual Level: At this level of database abstraction all the attributed and what
data are actually stored is described and entries and relationship among them.
View level: This is the highest level of abstraction at which one describes only part of
the database.
Advantages of RDBMS
 Redundancy can be avoided
 Inconsistency can be eliminated
 Data can be Shared
 Standards can be enforced
 Security restrictions ca be applied
 Integrity can be maintained
 Conflicting requirements can be balanced

Disadvantages OF RDBMS
A significant disadvantage of the DBMS system is cost. In addition to the cost
of purchasing of developing the software, the hardware has to be upgraded to allow for
the extensive programs and the workspace required for their execution and storage.
While centralization reduces duplication, the lack of duplication requires that the
database be adequately backed up so that in case of failure the data can be recovered.
3.5 INTRODUCTION TO SQL SERVER
Microsoft SQL Server is a Structured Query language (SQL) based,
Client/Server relational database. Each of these terms describes a fundamental part of
the architecture of SQL Server.
Database
A database is similar to data file in that it a storage space for data. Like a data
file, a database does not present information directly to the user; the user runs an
application that accesses data from the database and presents it to the user in an
understandable format.
A database typically has two components; the file holding the physical database
and the database management system (DBMS) software that applications use to access
the data. The DBMS is responsible for enforcing the database structure, including:
 Maintaining the relationships between data in the database.
 Ensuring that data is stored correctly and that the rule defining data
relationships are not violated.
 Recovering all data to a point of known consistency in case of system failures.
Relational Database
There are different ways to organize data in the database but relational database
are one of the most effective. Relational database systems are an application of
mathematical set theory to the problem of effectively organizing data. In a relational
database, data is collected into tables (called relations in relational theory).
Client/Server
In Client/Server system the server is a relatively large computer in a central
location that manages a resource used by many people. When individuals need to use
the resource, they connect over the network from their computers, or clients, to the
server.

Examples of servers are: In Client/Server database architecture, the database

files and DBMS software resides on a server. A communications component is
provided. So applications can run on separate clients and communicate to the database
server over a network. The SQL Server communication component also allows
communication between an application running on the server and SQL Server.
Structured Query Language (SQL)
To work with data in database, you must use a set of commands and statements
(language) defined by the DBMS Software. There are several different languages that
can be used with relational databases; the most common is SQL.Both the American
National Standards Institute (ANSI) and the international Standards Organization
(ISO) have defined standards for SQL. Most modern DBMS products support the
Entry Level of SQL-92, the latest SQL standard (published in 1992). SQL Server
Features:
Microsoft SQL Server supports a set of features that result in the following benefits:
 Ease of installation, deployment, and use: SQL Server includes a set of
administrative and development tools that improve your ability to install, deploy,
manage, and use SQL Server across server sites.
 Scalability: The same database engine can used across platforms ranging from
laptop computers running Microsoft Windows 95/98 to large, multiprocessor
servers running Microsoft Windows NT, Enterprise Edition.
 Data Warehousing: SQL Server includes tools for extracting and analyzing
summary data for Online Analytical Processing (OLAP). SQL Server also
includes tools for visually designing databases and analyzing data using English-
based Questions.
 System integration with other server software: SQL Server integrates with
E-Mail, the Internet, and Windows.
 Databases: A database in Microsoft SQL Server consists of a collection of
tables that contains data, and other objects, such as views, indexes, stored
procedures, and triggers, defined to support activates performed with the data.
SQL Server can support many databases, and each database can store either
inter related data or data unrelated to that in the other databases. For example, a server
can have one database that stores personnel data and another that stores product related
data. Alternatively, one database can store current customer order data, and another;

related database can store historical customer orders that are used for yearly reporting.
Before you can create a database, it is important to understand the parts of a database
and how to design these parts to ensure that the database performs well after it is
implemented.
3.6 SOFTWARE REQUIREMENT SPECIFICATION
The SRS is a document that completely describes what the proposed software
should do without describing how the software will do it.
3.6.1 Characteristics of a good SRS document
 It should be concise and at the same time unambiguous.
 It should be consistent.
 It should be well structured and easily modifiable.
 It should specify all goals and constraints concerning implementation.
 It should record references to maintainability, portability and
adaptability.
3.6.2 Advantages of SRS
 An SRS provides a reference for validation of the final product.
 A high quality SRS is a perquisite to high quality software.
 A high quality SRS reduces the development cost.
3.6.3 Requirement Specification
Overview
 No need of approaching the administrator.
 Student can view the progress details.
 Staff can council the student.
The basic goal of requirement phase is to produce the SRS document which
describes the behaviour of the software system. This project is designed for the
administration to maintain the college database. It is also used to view the required
information regarding an engineering college and its activities based on the
authorization of the user.
Purpose
The main purpose for preparing this document is to give a general insight into the
analysis and requirements of the existing system or situation and for determining the
operational characteristics of the system.

Scope
This document plays a vital role in the Software Development Life Cycle (SDLC) as it
describes the complete requirements of the system. It is meant for use by the developers
and will be the basis for testing the system.
3.6.4 Functional Requirement
Admin Module
Background
This module facilitates in creating the organizational structure of the college. It is
maintained by the administrator who manages the database of the college.
Functionalities
It allows the authorized user to create, control and view the information regarding the
entities like Departments, Subjects and also the other main aspects which come under
admin level.
Student Module
Background
This module facilitates in creating and maintaining the entire database of a student. The
Report feature of this module facilitates in generation of reports pertaining to all the
major aspects of student affairs.
Functionalities
It provides the user to view the required details of a particular student. The main
activities include student admissions and marks details of a particular student.
3.6.5 Non Functional Requirements
User Interface and Human Factors
User interface should be in such a way that even layman can understand it. So
GUI is preferred. There should be a login form after getting authorized to authenticate
the user. Main menu form regarding the available modules should also exist.
Users of the system are from various backgrounds, so at most help should be
provided such as placing icons for easy understanding. The user is intimated then and
there so when he enters invalid data.
3.6.6 Performance Requirements
Performance is measured in terms of different facilities provided to the authorized user.
The efficiency of the system should be more. It must be able to handle heavy work.
Response time should be fast. Accuracy is very important for the information retrieval.

Error Handling
If the user enters invalid data, the system should warn the user. Validation of inputs
should be done.
Quality Issues
System should be available to the authorized users whenever required. The system
should not crash even if the user gives an invalid username or password.
Security Issues
System should not allow any unauthorized user to extract information from it.
3.7 SUMMARY
In this chapter, we have completely learned about the requirements for running
our project. We have also studied thoroughly the computational environment of our
project.

4. FEASIBILITY STUDY
4.1 INTRODUCTION
In this chapter, we are going see about the feasibility of our project. We are
going to study technical, operational and economical feasibility of WECA. This helps in
getting an optimal product.
4.2 TECHNICAL FEASIBILITY
Evaluating the technical feasibility is the trickiest part of a feasibility study. This
is because, at this point of time, a detailed design of the system is not available, making
it difficult to access issues like performance, costs (on account of the kind of technology
to be deployed) etc. A number of issues have to be considered while doing a technical
analysis.
Understand the different technologies involved in the proposed system
Before commencing the project, we have to be very clear about what are the
technologies that are to be required for the development of the new system.
Find out whether the organization currently possesses the required technologies
Is the required technology available with the organization? If so, is the capacity
sufficient? For instance- “Will the current database be able to handle the new reports
and forms required for the new system?”
4.3 OPERATIONAL FEASIBILITY
Proposed projects are beneficial only if they can be turned into information
systems that will meet the organizations operating requirements. Simply stated, this test
of feasibility asks if the system will work when it is developed and installed. Are there
major barriers to implementation? Here are questions that will help test the operational
feasibility of a project:
Is there sufficient support for the project from management from users?
If the current system is well liked and used to the extent that persons will not be
able to see reasons for change, there may be resistance.
Are the current business methods acceptable to the user?
If they are not, users may welcome a change that will bring about a more
operational and useful system.
Have the users been involved in the planning and development of the project?
Early involvement reduces the chances of resistance to the system and in
general, increases the likelihood of a successful project. Since the proposed system was

to help reduce the hardships encountered in the existing manual system, the new system
was considered to be operationally feasible.
4.4 ECONOMIC FEASIBILITY
Economic feasibility attempts to weigh the costs of developing and
implementing a new system, against the benefits that would accumulate from having the
new system in place. This feasibility study gives the top management the economic
justification for the new system. A simple economic analysis which gives the actual
comparison of costs and benefits are much more meaningful in this case. In addition,
this proves to be a useful point of reference to compare actual costs as the project
progresses. There could be various types of intangible benefits on account of
automation. These could include increased customer satisfaction, improvement in
product quality, better decision making, timeliness of information, expediting activities,
improved accuracy of operations, better documentation and record keeping, fast
retrieval of information and better employee morale.
4.5 SUMMARY
In this chapter, we have clearly understood the optimality and feasibility of our
product. We have discussed that we have technical, operational and economical
feasibility for our product.

5. SYSTEM ANALYSIS
5.1 INTRODUCTION
Requirement Analysis is done in order to understand the problem the software
system is to solve. The problem could be automating an existing manual process,
developing a new automated, or a combination of the two. For large systems that have
many features, and that need to perform many different tasks, understanding the
requirement of the system is a major task. The emphasis in requirement analysis is on
identifying what is needed from the system, not how the system will achieve its goals.
There are two major activities in this phase: problem understanding or analysis
and requirements specification. In the problem analysis, the analyst has to understand
the problem and its context. Such analysis, typically requires a through understand is
needed of the important data entities in the system, major centres where action is taken
the purpose of the different actions that are performed, the inputs and the outputs.
Understanding the existing system is usually just the starting activity in problem
analysis, and is relatively simple. The goal of this activity is to understand the
requirements of the new system that is to be developed. Understanding the properties
of system that does not exist is more difficult and requires creative thinking. Once the
problem is analysed and the essential understood, the requirements must be specified
in the requirement specification.
5.2 EXISTING SYSTEM

Current system describes the present process of the system. It has a number of
drawbacks like waste of user time, communication time, more computation and
calculation time. Whenever a user wants to perform any activity in maintaining or
managing the database, he has to contact the administration for each and every
information retrieval.
5.2.1 Drawbacks in Existing System
• The existing allocation of seating plan consumes a lot of time.
• It is heavy burden to the person allocating the students roll numbers.
• The randomizing might not be effective.

5.3 PROPOSED SYSTEM

A system should be developed in such a way that it facilitates the user in
performing any activities on his own. Here WECA is designed in a well-structured and
efficient way as it provides the user a login name and a password to get access through
the whole database based on the authorization of the user.
The features which are included are in the below list:

• Different types of login such as Admin & Student
• Updating the database accordingly
• Admin Module
• Student Module
• Retrieving the information required
5.3.1 Advantages of proposed system
• This takes very less time compared to existing system.
• This reduces a lot of burden to the people in examination department.
• The randomizing of students roll numbers is going to be very effective.
• User Interface will be User friendly.
5.4 SUMMARY
In this chapter, we have clearly analysed the product system. We have seen the
existing system and its drawbacks. We have also seen the proposed system and its
advantages. Hence we have clearly understood the system analysis of our product.

6. SYSTEM DESIGN
6.1 INTRODUCTION
The purpose of the design phase is to plan a solution of the problem specified
by the requirement document. This phase is the first step in moving from the problem
domain to the solution domain. In other words, starting with what is needed; design
takes us toward how to satisfy the needs. The design of a system is perhaps the most
critical factor affection the quality of the software; it has a major impact on the later
phase, particularly testing, maintenance. The output of this phase is the design
document. This document is similar to a blueprint for the solution and is used later
during implementation; testing and maintenance. The design activity is often divided
into two separate phases System Design and Detailed Design.
System Design also called top-level design aims to identify the modules that
should be in the system, the specifications of these modules, and how they interact with
each other to produce the desired results. At the end of the system design all the major
data structures, file formats, output formats, and the major modules in the system and
their specifications are decided.
During Detailed Design, the internal logic of each of the modules specified in
system design is decided. During this phase, the details of the data of a module is
usually specified in a high-level design description language, which independent of the
target language in which the software will eventually be implemented.
In system design the focus is on identifying the modules, whereas during
detailed design the focus is on designing the logic for each of the modules.
6.2 ARCHITECTURAL DESIGN
6.2.1 Logical Design (interfacing)
The two basic modern design strategies employed in software design are
1. Top Down Design
2. Bottom Up Design
Top Down Design is basically a decomposition process, which focuses on the
flow of control. At later stages it concern itself with the code production. The first step
is to study the overall aspects of the tasks at hand and to break it into a number of
independent modules. The second step is to break each one of these modules further
into independent sub-modules. The process is repeated one to obtain modules, which
are small enough to group mentally and to code in a straightforward manner. One

important feature is that each level that details of design at the lower level are hidden.
Only the necessary data and control that must be called back and forth over the interface
are defined. In a bottom-up design one first identifies and investigates parts of design
that are most difficult and necessary designed decision are made the reminder of the
design is tailored to fit around the design already choose for crucial part. It vaguely
represents a synthesis process explained in previous section. One storage point of the
top-down methods is that it postpones details of the decision until the last stage of the
decision. It allows making small design changes when the design is half way through.
6.3. UML DIAGRAMS
Introduction to UML
The unified Modeling Language (UML) is one of the most exciting tools in the
world of system deployment today, the UML enables system builders to create blue
prints to capture their vision in a standard, easy to understand way and communicate
them to other.
How the UML Came To Be
The UML is the brainchild of Grady Booch, James Rumbaugh and Invar
Jacobson. Recently dubbed “The Three Amigos”, these gentlemen worked in separate
organizations through the “80’s and early 90’s”, each devising his own methodology for
object oriented analysis and design. Their methodologies achieved pre-eminence over
those of numerous competitors .By the mid 90’s, they began barrow ideas from each
other, so they decided to evolve their work together. In 1994, Rumbaugh joined rational
software corporation, where such was already working Jacobson enlisted at rational a
year later.
The rest, as they say in history. Draft version of the UML began to circulate
throughout the software industry and the resulting feedback brought substantial
changes. As many corporations felt the UML would serve their strategic purposes UML
consolation felt the UML would save their strategic purposes, a UML consortium
sprang up. Members include DEC, Hewlett-Packard, intellicorp, Microsoft, Oracle,
rational and others. In 1997, the consortiums produced version 1.0 of the UML and
submitted it to the object management group (OMG).In response to OMG request for a
proposal for a standard modelling language.

The Components of UML

UML consists of number of graphical elements to combine to form diagrams.
Because it’s language, the UML has rules for combining these elements. Rather than
telling you about these elements and rules. The purpose of the diagrams to present
multiple views of the system and this set of multiple views is called a model. A UML
model of a system is something like a scale model of a building along with an artist
rendition of building. It’s important to note that a UML model describing what a system
is supposed to do. It doesn’t tell how to implement the system.
Some Important Components Used In UML Diagrams:
1. Use Cases
2. Class Diagrams
3. Sequence Diagrams
4. Activity Diagrams
5. Collaboration Diagrams
Use Case Diagrams

Use case diagrams are one of the five diagrams in the UML for modeling the
dynamic aspects of the system (activity diagrams, state chart diagrams, sequence
diagrams and collaboration diagrams are the four kinds of diagrams in the UML
modeling the dynamic aspects of systems).Use case diagrams are central to modeling
the behaviour of a system, a subsystem, or a class. A use case diagram shows a set of
use cases and actors and their relationships.
Use case Diagrams are especially important in organizing and modeling the behaviours
of a system. No system exists in isolation. Every interesting system interacts with
human or automated actors that use that system for some purpose and those actors
expected that system to behave in predictable ways. A use case specifies that behaviour
of a system or a part of a system and is a description of a set of sequences of actions,
including variants that a system to yield an observable result of value to an actor.
Terms and Concepts
A use case describes a set of sequences of actions, including variant that a
system performs to yield an observable result to value to an actor. A use case is a
description of a set of sequences of actions, including variants that a system performs to

yield and observable result to value an actor. Graphically, a use case is rendered as an
ellipse.
Names
Every use case must have a name that distinguishes it from other use cases. A
name is a textual string. That name alone is known as a simple name, a path name is the
use case prefixed by the name of the package in which that use case lives. A use case is
typically drawn showing only its name.
Use cases and Actors
An actor represents a coherent set of roles that users of use cases play when
interacting with these use case. Typically, an actor represents a role that a human, a
hardware device or even another system plays with a system.
FIG 6.3.1: Use case diagram for Administrator

Actors may be connected to use cases only by association. An association
between an actor and use case indicates that the actor and the use case communicate
with one another, each one possibly sending and receiving messages.
Use case diagrams are important for visualizing, specifying and documenting
the behaviour of an element. They make system, subsystems and classes approachable

and understandable by presenting an outside view of how those elements may be used
in context. Use case diagrams are also important for testing executable systems through
forward engineering and for comprehending executable systems through reverse
engineering.
Use case diagrams commonly contain:
 Use cases
 Actors
 Dependency, generalization and association relationships
FIG 6.3.2: Use case diagram for Student

Class Diagrams
Class diagrams are the backbone of almost every object-oriented method
including UML. They describe the static structure of a system. Illustrate classes with
rectangles divided into compartments. Place the name of the class in the first partition
(centred, bolded, and capitalized), list the attributes in the second partition, and write
operations into the third. Active classes initiate and control the flow of activity, while
passive classes store data and serve other classes. Illustrate active classes with a thicker
border. Associations represent static relationships between classes. Place association
names above, on, or below the association line. Use a filled arrow to indicate the
direction of the relationship. Place roles near the end of an association. Roles represent
the way the two classes see each other. Classes represent an abstraction of entities with
common characteristics. Associations represent the relationships between classes.
FIG 6.3.3: Class Diagram for Administrator

Sequence Diagrams
In a functioning system, however objects interact with one another and these
interactions occur over time. The UML sequence diagram shows the time based
dynamics of the interaction. Sequence diagrams represent the objects participating in
the interaction horizontally and time vertically. Each column represents object that
participates in the interaction. Solid lines show messages. Labels on solid arrows
represent message, names and may contain arguments. Activation are depicted by
vertical rectangles the actor who initiates the interaction is shown in the left most
column. The linkage coming from the actor represent the interaction described in the
use case diagram.
FIG 6.3.4: Sequence Diagram

Collaboration diagrams
A collaboration diagram describes interactions among objects in terms of
sequenced messages. Collaboration diagrams represent a combination of information
taken from class, sequence, and use case diagrams describing both the static structure
and dynamic behavior of a system. Unlike sequence diagrams, collaboration diagrams
do not have an explicit way to denote time and instead number messages in order of
execution. Sequence numbering can become nested using the Dewey decimal system.
For example, nested messages under the first message are labeled 1.1, 1.2, 1.3, and so
on. The condition for a message is usually placed in square brackets immediately
following the sequence number. Use a * after the sequence number to indicate a loop.
FIG 6.3.5: Collaboration Diagram

Activity Diagrams
Activity diagrams illustrate the dynamic nature of a system by modeling the
flow of control from activity to activity. An activity represents an operation on some
class in the system that results in a change in the state of the system. Typically, activity
diagrams are used to model workflow or business processes and internal operation. The
outing transitions in a state chart representations are triggered by the completion of
action associated with the state this is called an action state. By convention the name of
the state denotes a condition where the name of the action state denotes an action.
Activity diagrams are state chart diagrams whose states are action states.
FIG 6.3.6: Activity Diagram

6.4 DATABASE DESIGN

Detailed Design
In High level Design we are just concerning about the context diagrams and
DFD etc. were as here we are concerning about the database tables, screens etc.
Normalization
The process of analysing the data to be represented and breaking it down into
separate tables in accordance to the principles of relational structure. It can be defined
as a process of putting data right making it normal.
Need For Normalization
Normalization reduces repetition of data i.e. Data Redundancy. When the same
data is repeatedly stored it causes storage and access problems. Redundant data can lead
to
 Inconsistency in data retrieval
 Errors while updating data tables
There is high likelihood of updating or deleting data in one relation. While
omitting to make corresponding changes in other relations.
During the process of normalization, we can identify dependency, which can
cause problems when deleting or updating. Normalization also helps to simplify the
structure of tables full-normalized record consists of the primary key that identifies the
entity. The set of attributes that describes the entity.
Normal Forms
Dr. Codd originally defines five levels of normalization. These five levels were
called first normal form, third normal form, fourth normal form, fifth normal form
respectively. Normalization is usually discussed in terms of forms. Normal forms are
table structures with minimum redundancy. The normal forms that have been identified
are:
 First Normal Form (1st NF)
 Second Normal Form (2nd NF)
 Third Normal Form (3rd NF)
 Fourth Normal Form (4th NF)
 Fifth Normal Form (5th NF)

First Normal form

This form is represented as 1 NF. To put data into 1NF all the repeating information
has to be removed. A relation R in the first normal forms if and only if all underlined
domains values only.
Second Normal form
To bring table to its second normal form, data that is dependent on part of the key
should be separated.
To convert a table to 2NF, following steps are required
 Find and remove fields that are related to only a part of the key.
 Assign the new table with a key that is a part of the composite key.
 A relation R is in the second normal form if and only if it is in 1NF and every
non-key attribute is dependent on the primary key.
Third Normal form
A table is said to be in third normal form, if it is in its 2NF and every field
which is not a key is functionally dependent on just the primary key. A relation R is in
third normal form if and only if it is in 2NF and every non-key attribute is not
transitively dependent on the primary key.
Fourth Normal form
In this model, the detailed records of the master are linked through forward and
backward pointers to its next and previous records respectively. All the master records
are again linked to one another in the same fashion. In the hierarchical model, each of
the detailed record is linked to only one master record.
Boyce-codd Normal form
A relation is in Boyce-codd normal form (BCNF) if and only if every
determinant is a candidate key. An attribute is fully dependent on other attributes is a
dependent
Fifth Normal form
A relation is in fifth normal form also called project-join normal form (PJNF) if
and only if the candidate keys of R imply every join dependency in R.
6.5 SUMMARY
In this chapter, we have completely understood the system design of our
product. We have seen all the UML diagrams of our product. We have also analysed
and studied the complete database design and studied its properties.

7. SYSTEM IMPLEMENTATION
7.1 INTRODUCTION
In this chapter, we are going to see how our product is implemented. We are
also going to study the different ways of building software like the waterfall model. We
are also going to see the architecture of .Net and how it works. We have also seen how
the SQL server works
7.2 SOFTWARE ANALYSIS

The waterfall model
The waterfall model was derived from engineering model to put some order in the
development of large software products. It consists of different stages which are
processed in a linear fashion.
Brief description of the phases in the waterfall model is as follows
 Requirements are the phase where the ‘What’ of the software system is
defined. It involves extensive user participation and ends with an approved set
of requirements documented in a software requirement specification (SRS)
document. The SRS from the basis of all further work in the project.
 Design phase is ‘How’ of the system is defined. Here, the problem definition
specified in the SRS is translated into design which will solve the problem. The
design phase is the bridge between ‘What’ the user wants and the code that will
be created to satisfy the requirements.
 Construction phase deals during the generation of code. During this stage, the
software design is realized as a set of programs or program units.
 Testing phase deals with the testing of code that is developed. This involves
unit testing for the lowest level components, integration testing for group of
components and testing of the system as a whole. The last activity in testing is
usually that of acceptance testing. Accepting testing validates that the system
fulfils the ‘user’s needs’ and requires considerable user involvement.
 Development phase deals with the development of operating system. The main
activities in this phase include training of the user’s installation of the system,
switchover from the existing (manual, semi-automated or automated) system to
the new system.

 Operational and Maintenance phase deals with the correction of leftover

defects. If required, the system is made more efficient, new requirements are
added and existing functionality and features modified to meet the ever
changing needs.
Evolution of waterfall model
In the early days of computing, software development was mainly a single-
person task. The problem to be solved very often of mathematical nature was well
understood and there was no distinction between the programmer and the end user of
the application as a support to his or her activity. The application, by today’s standards
was rather simple. The model used in these early days may be called the code-and-fix
model. Basically, software development was essentially seen as a ‘programming’
activity followed by the ‘implementation’ activity, with other tasks seen as an extension
of the programming and implementation. This lead to considerable amount of bug
fixing during the implementation which resulting in delay and cost over runs. To
overcome these problems, developers started performing ‘testing’ as an activity
between the programming and implementation. Over time, requirements, design and
development were identified as important activities and converted into phases.
7.3 MODULES
Login
In this module, we have provided the login with two different functionalities.
One of them is administrator login and another is student login. Admin login leads to
higher functionalities whereas student login has limited permissions.
Database Entry
This is a one-time entry module. Admin enters into this module at the
beginning of the academic year and updates all the students’ details and also the room
numbers and their respective capacities. This has to be done only once an academic
year.

New Seating Allotment
This is the main module or central module. In this module, we select the
semester and branch of the students to be allotted in a room. We also give subject
codes, date of exam and room number we are allotting as inputs. We can also modify
the mode of arrangement in three styles (Alternate, column-wise, Random). Finally by
clicking “Generate”, allotment is generated accordingly. By clicking on “Save”,
allotment details are updated into the database.
Edit Seating Allotment
In this module, we can edit the already allotted rooms’ details. Editing of Roll
numbers is blocked. But, you can edit details like subject codes, Date of exam, etc...
View Room-wise Allotment
In this module, we can view the rooms already allotted. We get the branches
allotted in each room and the beginning and ending roll numbers in each room.
Print
This module is integrated into the modules “Edit Seating Allotment” and
“View Room-wise Allotment”. This is nothing but an option to print the respective
pages by hiding the buttons in the respective pages and printing only the content.
Update Student Details
This is the module where the admin can edit the details of the student which are
entered at the beginning of the academic year.
7.4 SUMMARY
In this chapter, we have thoroughly studied how the system in our product is
implemented. We have also seen all the modules of our project and understood the work
done in the respective modules.

8. TESTING
8.1 INTRODUCTION
In this chapter, we are going to see how the testing process works. We are also
going to test our product using all the testing techniques and we are going to write some
test cases for our product. We are going to make sure it is going to work without any
flaws after the release.
8.2 TESTING STRATEGIES
In a software development project, errors can be injected at any stage during the
development. These errors will be reflected in the code, so the application should be
thoroughly tested, validating its operations and seeking feedback on user interfaces.
There are two basic approaches to testing, functional and structural. In
functional or black box testing, the structure of the program is not considered. Test
cases are decided solely on the basis of functional requirements of the program or
module. Structural or white box testing, this is concerned with testing the
implementation of the program. Its aim is to exercise the different programming and
data structures used in the program. We are having the following levels of testing.
 System Testing
 Unit Testing
 Integration Testing
 Stress Testing
 Volume Testing
 Recovery Testing
System Testing
This is a series of tests whose purpose is to fully exercise the entire software
system. System testing verifies that all elements mesh properly and the overall system
function/performance is achieved. System testing is done using real data. The system
performance was found to be working as per the requirements specified.
 Test for security risk factors- unauthorized access both by individuals and by
programs.
 Implement the system in a simulated environment and test it.
 Introduce errors and test for error handling

Unit Testing
In this testing different modules are tested against the specification produced
during the design of the modules. The main aim of this testing is to test the internal
logic of the modules.
 Add test cases of data flow coverage.
 Add intuitive test cases based on experience (error guessing) such as testing for
boundary conditions minimum, maximum and off by one boundary.
 Add test cases for path or branch coverage (use structured basis testing method).
 Give test cases for testing against the requirements of the unit being tested.
Integrated Testing
Many tested modules are combined into sub system, which are then tested. The
emphasis is on testing interface between modules. This activity can be considered to
test the design. This testing is looked for the following types of programs.
 Data integrity violation.

 Missing or overlapping functions.
 I/O formats are protocol mismatches.
Stress testing
 Test for effect of extended operation.
 Test for increased frequency of transactions as peak items.
 Test for abnormal shutdown.
Volume testing
 Check for ability to handle large volumes of data as well as bad data.
 Apply large of data and check correctness.
Recovery testing
 If the system involves remote facilities and distributed processing, simulate a

communication link failure and test.
 Simulate disaster and test if the system behaves gracefully.
 Test for the consistency of the database/data store after recovery.

8.3 TEST REPORTS

Validation testing
As the culmination of integration testing, software is completely assembled as a
package, interfacing errors has been uncovered and corrupted, and a final series of
software tests validation testing may begin. Validation can be defined in many ways but
a simple definition is that validation succeeds when software functions in a manner that
can be reasonable expected by the customer. Software validation is achieved through
black box testing. Test plans and test procedures are designed to ensure that all
functional requirements are satisfied, all behavioral characteristics are achieved, all
performance requirements attained, documentation is correct, and human engineered
and other requirements are met.
Test Case 1
SIGNIN ----- USERNAME

Test Case 2
SIGNIN ----- PASSWORD

Test Case 3
STUDENT ----- STUDENT SEARCH
8.4 SUMMARY
In this chapter, we have clearly understood the testing process of our product
and also have analysed some of the test cases from our product. By this we have assured
that our product will work flawlessly after being released.

9. SAMPLE CODE
LOGIN CODE
using System;
using System.Data;
using System.Configuration;
using System.Web;
using System.Web.Security;
using System.Web.UI;
using System.Web.UI.WebControls;
using System.Web.UI.WebControls.WebParts;
using System.Web.UI.HtmlControls;
public partial class _Default : System.Web.UI.Page
protected void Page_Load(object sender, EventArgs e)
//if(!IsPostBack)
//txtUserNm.Focus();
protected void OnSignInClick(object sender, EventArgs e)
DAL dalobj;
lblErr.Text = "";
Session.Clear();

if (drpUsrTyp.SelectedValue == "A")
if (txtUserNm.Text.Trim() == "ecap")// && txtPsd.Text.Trim() ==

"ecap")//Membership.ValidateUser(txtUserNm.Text.Trim(),txtPsd.Text.Trim()))
//Server.Transfer("EmpMaster.aspx");//Response.Redirect("EmpMaster.aspx");
if (txtPsd.Text.Trim() == "ecap")
//FormsAuthentication.DefaultUrl="EmpMaster.aspx";
FormsAuthentication.RedirectFromLoginPage(txtUserNm.Text.Trim(),
false);
if (Request.QueryString["ReturnUrl"] == null)
Response.Redirect("empmaster.aspx");
else
lblErr.Text = "InValid Password";
else
lblErr.Text = "InValid Username";
else if(drpUsrTyp.SelectedValue == "ST")
dalobj=new DAL();

if(dalobj.isEmployee(txtUserNm.Text.Trim()))// &&
txtPsd.Text=="rec")//txtUserNm.Text=="std")//
if (txtPsd.Text == "rec")
false);
Session["empId"] = txtUserNm.Text;
Response.Redirect("staffMaster.aspx");
else
else
lblErr.Text = "InValid Username";
else
dalobj=new DAL();
if (dalobj.isStudent(txtUserNm.Text.Trim()))// && txtPsd.Text ==

"rec")//txtUserNm.Text=="std")//
if (txtPsd.Text == "rec")

false);
Session["stdID"] = txtUserNm.Text;
Response.Redirect("stdmaster.aspx");
else
else
lblErr.Text = "InValid RollNo";
//protected void OnStdLoginClk(object s, EventArgs e)
//{
// lblStdErr.Text = "";
// if (txtStdUserName.Text.Trim() == "123456" && txtStdPsd.Text.Trim() ==

"123456")//Membership.ValidateUser(txtUserNm.Text.Trim(),txtPsd.Text.Trim()))
// //Server.Transfer("StdMaster.aspx");
// {
// //FormsAuthentication.DefaultUrl = "StdMaster.aspx";
// FormsAuthentication.RedirectFromLoginPage(txtUserNm.Text.Trim(), false);
// }

ALLOTMENT CODE
using System.Data;
using System.Configuration;
using System.Collections;
using System.Web;
using System.Web.Security;
using System.Web.UI;
using System.Web.UI.WebControls;
using System.Web.UI.WebControls.WebParts;
using System.Web.UI.HtmlControls;
public partial class subjects : System.Web.UI.Page
DAL dalobj;
protected void Page_Load(object sender, EventArgs e)
if (!IsPostBack)
dalobj = new DAL();
drpBranch.DataTextField = "BranchName";
drpBranch.DataValueField = "Code";
drpBranch.DataSource = dalobj.getDataTable("select * from branches");
drpBranch.DataBind();

drpBranch0.DataTextField = "BranchName";
drpBranch0.DataValueField = "Code";
drpBranch0.DataSource = dalobj.getDataTable("select * from branches");
drpBranch0.DataBind();
protected void editValues(object s, DataGridCommandEventArgs e)
hdnLblId.Text = e.Item.Cells[0].Text;
txtExamCode.Text = e.Item.Cells[1].Text;
txtyear.Text = e.Item.Cells[2].Text;
drpBranch.SelectedIndex=drpBranch.Items.IndexOf(drpBranch.Items.FindByValue(e.It
em.Cells[3].Text));
drpSem.SelectedIndex=drpSem.Items.IndexOf(drpSem.Items.FindByText(e.Item.Cells[
4].Text));
txtRoomNo.Text = e.Item.Cells[6].Text;
btnsave.Text = "Update";

public void getRollNo()
string a = drpBranch.SelectedValue; string b = drpBranch0.SelectedValue; string

str5 = "";
if (!(a.Equals(b)))
dalobj = new DAL(); int r = 0, r1 = 0;
string room = ""; string allot = "no";
string room1 = "delete from RoomList where RoomNo='" + txtRoomNo.Text +

"'"; dalobj.ExecuteActionQuery(room1);
DataTable table = dalobj.getDataTable("SELECT [StudentId]

,[Batch],[BranchCode],[RollNo],[Semester] FROM [dbo].[NewAdmission] where
[BranchCode]='" + drpBranch.SelectedValue + "' and [Semester]='" +
drpSem.SelectedValue + "' and [Alloted]='" + allot + "' ORDER BY [StudentId] Asc");
DataTable table1 = dalobj.getDataTable("SELECT [StudentId]

,[Batch],[BranchCode],[RollNo],[Semester] FROM [dbo].[NewAdmission] where
[BranchCode]='" + drpBranch0.SelectedValue + "' and [Semester]='" +
drpSem0.SelectedValue + "' and [Alloted]='" + allot + "' ORDER BY [StudentId]
Asc");
if (drpArr.SelectedValue == "Alternate")
if (r < table.Rows.Count)
TextBox1.Text = table.Rows[r][3].ToString();

TextBox2.Text = table1.Rows[r1][3].ToString();
r++; r1++;
r++; r1++;
r++; r1++;
r++; r1++;

r++; r1++;
r++; r1++;
r++; r1++;
r++; r1++;

r++; r1++;
r++; r1++;
r++; r1++;
r++; r1++;

room = " insert into RoomList values('" + txtRoomNo.Text + "','" +

drpBranch.SelectedItem.Value + "','" + TextBox1.Text + "','" + TextBox24.Text + "','"
+ drpBranch0.SelectedItem.Value + "','" + TextBox2.Text + "','" + TextBox23.Text +
"')"; dalobj.ExecuteActionQuery(room);
if (drpArr.SelectedValue == "Columnwise")
r++; r1++;
r++; r1++;

r++; r1++;
r++; r1++;
r++; r1++;
r++; r1++;

r++; r1++;
r++; r1++;
r++; r1++;
r++; r1++;

r++; r1++;
r++; r1++;

if (drpArr.SelectedValue == "Random")

r++; r1++;
r++; r1++;
r++; r1++;
r++; r1++;

r++; r1++;
r++; r1++;
r++; r1++;
r++; r1++;

r++; r1++;
r++; r1++;
r++; r1++;
r++; r1++;



else
str5 = "Please allot different branches";
ClientScript.RegisterStartupScript(this.GetType(), "scds", "<script>alert('" +

str5 + "')</script>");
protected void OnSaveUpdt(object s, EventArgs e)
string str = ""; string allot1 = "yes";
try
dalobj = new DAL();
if (btnsave.Text == "Save")
str = " insert into RoomAllotment values('" + txtRoomNo.Text + "','" +

drpBranch.SelectedItem.Value + "','" + drpSem.SelectedItem.Value + "','" +
txtExamCode.Text + "','" + drpBranch0.SelectedItem.Value + "','" +
drpSem0.SelectedItem.Value + "','" + txtExam0.Text + "','" + txtyear.Text + "','" +
TextBox1.Text + "','" + TextBox2.Text + "','" + TextBox3.Text + "','" + TextBox4.Text

+ "','" + TextBox5.Text + "','" + TextBox6.Text + "','" + TextBox7.Text + "','" +

TextBox8.Text + "','" + TextBox9.Text + "','" + TextBox10.Text + "','" +
TextBox23.Text + "','" + TextBox24.Text + "')";
DataTable edit2 = dalobj.getDataTable("SELECT

RoomNo,BranchCode1,first1,last1,BranchCode2,first2,last2 FROM RoomList where
RoomNo='" + txtRoomNo.Text + "'");
string RoomNo = edit2.Rows[0][0].ToString();
string BranchCode1 = edit2.Rows[0][1].ToString();
string first1 = edit2.Rows[0][2].ToString();
string last1 = edit2.Rows[0][3].ToString();
string BranchCode2 = edit2.Rows[0][4].ToString();
string first2 = edit2.Rows[0][5].ToString();
string last2 = edit2.Rows[0][6].ToString();
string edit3 = " insert into RoomListf values('" + txtRoomNo.Text + "','" +

drpBranch.SelectedItem.Value + "','" + first1 + "','" + last1 + "','" +
drpBranch0.SelectedItem.Value + "','" + first2 + "','" + last2 + "')";
dalobj.ExecuteActionQuery(edit3);
string edit4 = " delete from RoomList"; dalobj.ExecuteActionQuery(edit4);
string roll1 = "update NewAdmission set alloted='" + allot1 + "' where

RollNo='" + TextBox1.Text + "'"; dalobj.ExecuteActionQuery(roll1);

























if (dalobj.ExecuteActionQuery(str))
str = btnsave.Text + "d";
else
str = "not " + btnsave.Text + "d";
ClientScript.RegisterStartupScript(this.GetType(), "scds", "<script>alert('" + str

+ "')</script>");
setDefault(s, e);

string room = "delete from RoomList where RoomNo='" + txtRoomNo.Text +

"'"; dalobj.ExecuteActionQuery(room);
catch
ClientScript.RegisterStartupScript(this.GetType(), "scds", "<script>alert('" + str

+ " Error Occured')</script>");
protected void setDefault(object s, EventArgs e)
txtExamCode.Text = "";
txtyear.Text = "";
drpBranch.SelectedIndex = 0;
drpSem.SelectedIndex = 0;
txtRoomNo.Text = "";
btnsave.Text = "Save";
protected void btnsave0_Click(object sender, EventArgs e)

getRollNo();
protected void drpArr_SelectedIndexChanged(object sender, EventArgs e)
dalobj = new DAL(); ; string room = "";
room = "delete from RoomList where RoomNo='" + txtRoomNo.Text + "'";

dalobj.ExecuteActionQuery(room);
protected void Reset_Click(object sender, EventArgs e)
dalobj = new DAL(); string room = ""; string room1 = ""; string room2 = "";string
room3 = "";string allot = "no";
room = "delete from RoomList"; dalobj.ExecuteActionQuery(room);
room1 = "delete from RoomListf"; dalobj.ExecuteActionQuery(room1);
room2 = "delete from RoomAllotment"; dalobj.ExecuteActionQuery(room2);
room3 = "update NewAdmission set alloted='" + allot + "'";

dalobj.ExecuteActionQuery(room3);

10. SCREEN LAYOUTS

Screen 1
Form Name: LOGIN PAGE
Description:
This form consists of the user login,where we have three types of users
Admin,Student and Staff who can login with their respective username and
password,which are valid.

Screen 2
Form Name: MAIN PAGE(Admin)
Description:
As the name implies this is the main page, where the admin accesses all his
objects. He can perform different operations like adding new student, edit existing
student details, seating allotment, e.t.c..

Screen 3
Form Name: ADD NEW STUDENT
Description:
In this page, we are going to add a new student to the database. We are going to
update the details of the student like name, hallticket number, marks ,e.t.c..

Screen 4
Form Name: EDIT STUDENT
Description:
The below form is used to search for the details of a student, and edit if there
are any corrections to be made to the existing entries.

Screen 5
Form Name: BRANCHES
Description:
This submodule is used to add a new branch if required,modify the existing
branches and also allows the administrator to delete any branch if not required.

Screen 6
Form Name: LECTURE HALLS
Description:
This submodule facilitates the administrator to allot room numbers for a
particular branch belonging to a particular year,also contains the information regarding
the numbers of benches,rows,columns etc.

Screen 7
Form Name: NEW ALLOTMENT
Description:
This is going to assign the students roll numbers to the classrooms available in
one of the three arrangements like alternate, columnwise, random. We have also
provided option to give subjects as input.

Screen 8
Form Name: EDIT/PRINT ALLOTMENT
Description:
In this page, admin has the option to view the already alotted classrooms and
print the allotment sheet.
Screen 9

Screen 10
Form Name: ROOM ALLOTMENT
Description:
In this page, we can see all the rooms alloted. Also, the branches alloted in
each room and the beginning and ending roll numbers of each alotted branch. In the
second screen, we can see the print layout of the room allotments.
Screen 11

Screen 12
Form Name: MAIN PAGE(STUDENT LOGIN)
Description:
Here the student can view only his details, depending on the roll number of the
student. It also consists of the branch and semester dropdown list as shown in the screen
below.

11. CONCLUSION & FURTHER ENHANCEMENT
Therefore WECA plays a major role in fulfilling the need for the storage,
retrieval and updation of the data and information regarding an educational institution
which can be maintained by the administrator and all the other users like students and
staff can just view the data present in the database in an efficient way.
Using SQL server, procedures are created to perform operations such as
selection, insertion etc. which is very efficient than writing a query. It also minimizes
the code and errors. Security is maintained by placing primary keys for certain fields so
that data is not repeated. Data is consistent, reliable and integrated.
 System is checked for the data entry, it doesn’t allow the user to enter invalid
data.
 User friendly screens are designed. Operations are done by the way of GUI.
 Code is scalable and portable to advanced versions of front end and back end.
Web Based Examination Cell Application can be developed using other software tools
also maintaining the same restrictions and validations.

12. BIBLIOGRAPHY
12.1 BOOKS AND REFERENCES
[1] Kelvin Hoffman and Lonny Krugger, Visual C#.NET 2003, ISBN 81-297-0939-2
[2] Jessie Liberty, Programming C#: Building .NET Applications with C#
[3] Rob Vietra, SQL Server 2000 Programming, ISBN 81-7366-206-1 (Wrox
Publications)
12.2 WEBSITES
[4] www.w3schools.com/asp/
[5] www.asp.net/
[6] www.stackoverflow.com/

Web Based Examination Cell Application

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

Web Based Examination Cell Application

Uploaded by

Copyright:

Available Formats

Web Based Examination Cell Application

S.V.COLLEGE OF ENGINEERING, Dept. of C.S.E Page |1

S.V.COLLEGE OF ENGINEERING, Dept. of C.S.E Page |2

2.3 CAPABILITIES OF WECA

S.V.COLLEGE OF ENGINEERING, Dept. of C.S.E Page |3

3.2.1 Software Requirements

Operating system : Windows XP/2000

3.3 INTRODUCTION TO .NET

Fig 3.3.1 .NET Architecture

S.V.COLLEGE OF ENGINEERING, Dept. of C.S.E Page |4

Fig 3.3.2: .NET Framework

S.V.COLLEGE OF ENGINEERING, Dept. of C.S.E Page |5

The .NET Framework consists of

Source code .NET MSIL

Fig 3.3.3: CLR

S.V.COLLEGE OF ENGINEERING, Dept. of C.S.E Page |6

COMMON LANGUAGE RUNTIME

Fig 3.3.4: Division of CLR

Common Type System (CTS)

 Establishes a framework that enables cross-language integration, type

 Provides an object-oriented model that supports the complete

S.V.COLLEGE OF ENGINEERING, Dept. of C.S.E Page |7

Framework Class Library

Fig 3.3.5: Framework Class Library

Common Languages Specification (CLS)

S.V.COLLEGE OF ENGINEERING, Dept. of C.S.E Page |8

Fig 3.3.6: .NET Data Providers

S.V.COLLEGE OF ENGINEERING, Dept. of C.S.E Page |9

 System.Data.SqlClient. Contains the SQL Server .NET Data Provider types.

S.V.COLLEGE OF ENGINEERING, Dept. of C.S.E P a g e | 10

Con.connectionString=”Provider=MicroSoft.Jet.Oledb.4.0; Data source= F:/tms.mdb”

cmd= New OleDbCommand(“select * from master specification”, con)

Using Data Adapter

da= New OleDbDataAdapter(“select * from master specification”, con)

ds= New Dataset

S.V.COLLEGE OF ENGINEERING, Dept. of C.S.E P a g e | 11

 MDAC 2.7 for Data

S.V.COLLEGE OF ENGINEERING, Dept. of C.S.E P a g e | 12

S.V.COLLEGE OF ENGINEERING, Dept. of C.S.E P a g e | 13

3.4 INTRODUCTION TO MYSQL

S.V.COLLEGE OF ENGINEERING, Dept. of C.S.E P a g e | 14

Table 3.1: Branches

Table 3.2: Generate Roll Numbers

Table 3.3: Holidays

Table 3.4: Lecture Halls

S.V.COLLEGE OF ENGINEERING, Dept. of C.S.E P a g e | 15

Table 3.5: New Admission

S.V.COLLEGE OF ENGINEERING, Dept. of C.S.E P a g e | 16

what makes SQL Server a relational database management system, or RDBMS. It

S.V.COLLEGE OF ENGINEERING, Dept. of C.S.E P a g e | 17

S.V.COLLEGE OF ENGINEERING, Dept. of C.S.E P a g e | 18

Examples of servers are: In Client/Server database architecture, the database

S.V.COLLEGE OF ENGINEERING, Dept. of C.S.E P a g e | 19

S.V.COLLEGE OF ENGINEERING, Dept. of C.S.E P a g e | 20

S.V.COLLEGE OF ENGINEERING, Dept. of C.S.E P a g e | 21

S.V.COLLEGE OF ENGINEERING, Dept. of C.S.E P a g e | 22

S.V.COLLEGE OF ENGINEERING, Dept. of C.S.E P a g e | 23

S.V.COLLEGE OF ENGINEERING, Dept. of C.S.E P a g e | 24

5.2 EXISTING SYSTEM

S.V.COLLEGE OF ENGINEERING, Dept. of C.S.E P a g e | 25

5.3 PROPOSED SYSTEM

The features which are included are in the below list:

S.V.COLLEGE OF ENGINEERING, Dept. of C.S.E P a g e | 26