INTRODUCTION

INTRODUCTION

Online Foreign Students Information System is used to capture information about foreign
nationals admitted in Indian educational institutions. It is mandatory for all educational
institutions in India admitting foreign students for various courses to register themselves
first. After their user-id approved by the competent authority i.e. FRRO/ district FRO
concerned, the said institution will be able to fill the details of foreign students in Form-S viz
(Student Profile, Performance etc. in case of application for extension).

For first time, Institutions who are admitting foreign students for various courses for all
age groups should register through this website After their user credentials approved by the
competent authority, it is mandatory that respective institution should upload their foreign
student information after successful login.

All the Foreign National Student studying in Indian Educational Institutions and also staying
in Any Hostel / Hotel / Guest House / / Individual House / University / Hospital / Institute /
Others etc. who provide accommodation to foreigners must submit the details of the residing
foreigner in Form-C to the Registration authorities within 24 hours of the arrival of the
foreigner at their premises. This will help the registration authorities in locating and tracking
the foreign student.
Institutions who are admitting foreign students for first time in various courses for all age
groups should register online and get it approved by Competent Authority i.e FRRO / District
FRO's.

Online foreign student Information System is the primary systems for operating colleges. The
Student Information System is a student-level data collection system that allows the
Department to collect and analyze more accurate and comprehensive information. Student
information systems provide capabilities for entering student records, tracking student
attendance, and managing many other student-related data needs in a college or university.

Student Information System also supports:

Handling inquiries from prospective students.

Handling the Student details.

Maintaining the Student residing place Details.

Handling foreign Student Attendance Records.

Maintaining records of foreign students

Objective:

To make the application of online foreign Student Information System usable for the
College or Universities.

To access the students records and get the desired information which may require.

To automate the existing system of manually maintain the records of the student
records, Students Details, Attendance Details, Internal Marks etc.

To increase data accuracy, make student information management more secure,

effective, convenient and accessible.

To coordinate information across the system to simplify student access to University

resources

STUDY OF THE SYSTEM

In the flexibility of uses the interface has been developed a graphics concepts in mind,
associated through a browser interface. The GUIs at the top level has been categorized as
follows
 1. Administrative User Interface Design
2. The Operational and Generic User Interface Design
The administrative user interface concentrates on the consistent information that is
practically, part of the organizational activities and which needs proper authentication for the
data collection. The Interface helps the administration with all the transactional states like
data insertion, data deletion, and data updating along with executive data search capabilities.
The operational and generic user interface helps the users upon the system in
transactions through the existing data and required services. The operational user interface
also helps the ordinary users in managing their own information helps the ordinary users in
managing their own information in a customized manner as per the assisted flexibilities.
NUMBER OF MODULES
The system after careful analysis has been identified to be presented with the following
modules:
The Modules involved are
1. Administration
2. Students
3. Staff
4. Modules Registration
5. Results Announcement
6. Search
7. Reports
8. Authentication

Business Goals
From the business perspective, the following are the goals of the system
Manage the complexity and longevity of upcoming student records storage
requirements
Provide high quality of service in terms of uptime, reliability and backup.
Allow the inclusion of financial information, so that it can be used as the basis of full
 economic costing of courses and modules.
Provide a speedy response to all queries

The Student Record System maintains records of students, the courses and modules on
which they are registered and the outcome of their studies.
The system maintains personal information for each student registered at the university.
The information consists of the students registration number, forename, surname, gender,
home address, term-time address, and date of birth. There are two distinct categories of
student within the University
Undergraduate Students
Postgraduate Students
For regulatory reasons all students must be categorized into one of these two
categories. For each undergraduate student the system must also maintain a record of the
name of the students Local Education Authority and an indication of whether they have
taken out a student loan. For each postgraduate student the system must maintain a record of
the name of their sponsor and a flag which indicates whether they are a European or
International Student.
Each student registers for a Program of Study. Every programme of study has a
name, a programme code and a credit tariff which is the number of credits a student must
attain in order to successfully complete the programme. The basic unit of credit attainment is
20 credits and the credit tariff is always a multiple of 20.
A module is a separately taught and assessed element of a programme of study. If a
student studies and successfully completes a module they will be awarded 20 credits. If a
student studies but does not successfully completed a module they will be awarded zero
credit. Every module has a title and a module code.
A program of study is made up of one or more distinct levels of study. An
undergraduate program has three levels of study, one for each year of the course. A
postgraduate programme is taught within a single year and thus has only one level of study.
Each level of a course defines the set of core modules and optional modules which can be
studied in that year of study.
Every level has two sets of modules associated with it. The core modules are those
modules which every student taking the course of study. The optional modules are a set of
modules from which students may freely chose a certain number of modules that they wish to
study. This number of optional modules is referred to as the optional credit tariff and is a
fixed value of zero or more credits for each level of study.
Each student has a course registration record which defines their registration for a
particular programme of study. A students course registration record consists of an indicator
of the students current level of study and a set of level registration records, one for each level
in the programme of study for which they have registered, i.e. Three Levels of under
Graduate Programme and One Level for a Post Graduate Programme.
A level registration record consists of a weighted average mark for the level of study
and a set of module registration records, one for each module that the student will study or
has studied in that level of the programme. Module registration records exist for both core
and optional modules and record the students attendance of that module, the marks they
gained in the examination, the marks they gained in the course work, an overall mark for the
module and a pass/fail indicator.
Administration
Administrator is a super user treated as a owner of this site. He can have all the
privileges. Administrator can register user directly, and delete the information of a registered
users.
Administrator can register students as well as faculties, after approving the
registration a student or a faculty having authority to log into the system. He can add new
courses based the Programme of study. Different modules are added by administrator on
different courses.
Students
User is nothing but a registered Student. A registered student directly sees his
personal information, registered modules, and marks details updated by faculties for different
modules.
Faculties
A module is taught by a faculty in the university. The major responsible of a faculty
is giving credits to students. Based on the modules faculties need to correct the exam papers
and giving results.
Registration
The system has a process of registration. Every user need to submit his complete
details in the form of registration. Whenever a user registration completed automatically user
can get a user id and password. By using that user id and password user can log into the
system.
Search
Different kind of search available to users as well as administrator. A user can search
is personal queries like student search their personal information, results, modules they are
registered, and credit information.
INPUTS AND OUTPUTS
The major inputs and outputs and major functions of the system are follows:
Inputs:
Admin enter his user id and password for login.
User enters his user id and password for login.
User Create new folder for personnel usage.
Admin enter user id or date for track the user login information
New user gives his completed personnel, address and phone details for registration.
Admin gives different kind of user information for search the user data.
User gives his user id, hint question, answer for getting the forgotten password.
User gives the folder permission for sharing the folder to other users.
Outputs:
Admin can have his own home page.
Users enter their own home page.
The user defined folders can store in the centralized database.
Admin will get the login information of a particular user.
The new users data will be stored in the centralized database.
Admin get the search details of different criteria.
User can get his forgot password.
The user folder having permission for private or public purpose.
1.1. SYSTEM SPECIFICATIONS
1.1.1 HARDWARE SPECIFICATION
The hardware requirements may serve as the basis for a contract for the
implementation of the system and should therefore be a complete and consistent specification
of the whole system. They are used by software engineers as the starting point for the system
design. It should what the system do and not how it should be implemented.
PROCESSOR : Intel Pentium3
RAM : 4 GB RAM
MONITOR : 15 COLOR
HARD DISK : 250 GB
CDDRIVE : LG 52X
KEYBOARD : STANDARD 102 KEYS
MOUSE : 3 BUTTONS

1.1.2 SOFTWARE SPECIFICATION

The software requirements document is the specification of the system. It should include
both a definition and a specification of requirements. It is a set of what the system should do
rather than how it should do it. The software requirements provide a basis for creating the
software requirements specification. It is useful in estimating cost, planning team activities,
performing tasks and tracking the teams and tracking the teams progress throughout the
development activity.
Front end : ASP.Net.
Back end : Ms SQL
Tools : Microsoft Visual Studio 2010, Ms-office
Operating System : Windows 8

ASP.net Introduction:

ASP.NET is a web development platform, which provides a programming model, a

comprehensive software infrastructure and various services required to build up robust web
applications for PC, as well as mobile devices.

ASP.NET works on top of the HTTP protocol, and uses the HTTP commands and policies to
set a browser-to-server bilateral communication and cooperation.

ASP.NET is a part of Microsoft .Net platform. ASP.NET applications are compiled codes,
written using the extensible and reusable components or objects present in .Net framework.
These codes can use the entire hierarchy of classes in .Net framework.

The ASP.NET application codes can be written in any of the following languages:

C#

Visual Basic.Net

Jscript

J#

ASP.NET is used to produce interactive, data-driven web applications over the internet. It
consists of a large number of controls such as text boxes, buttons, and labels for assembling,
configuring, and manipulating code to create HTML pages.

ASP.NET Web Forms Model

ASP.NET web forms extend the event-driven model of interaction to the web applications.
The browser submits a web form to the web server and the server returns a full markup page
or HTML page in response.
All client side user activities are forwarded to the server for stateful processing. The server
processes the output of the client actions and triggers the reactions.

Now, HTTP is a stateless protocol. ASP.NET framework helps in storing the information
regarding the state of the application, which consists of:

Page state

Session state

The page state is the state of the client, i.e., the content of various input fields in the web
form. The session state is the collective information obtained from various pages the user
visited and worked with, i.e., the overall session state. To clear the concept, let us take an
example of a shopping cart.

User adds items to a shopping cart. Items are selected from a page, say the items page, and
the total collected items and price are shown on a different page, say the cart page. Only
HTTP cannot keep track of all the information coming from various pages. ASP.NET session
state and server side infrastructure keeps track of the information collected globally over a
session.

The ASP.NET runtime carries the page state to and from the server across page requests
while generating ASP.NET runtime codes, and incorporates the state of the server side
components in hidden fields.

This way, the server becomes aware of the overall application state and operates in a two-
tiered connected way.

The ASP.NET Component Model

The ASP.NET component model provides various building blocks of ASP.NET pages.
Basically it is an object model, which describes:

Server side counterparts of almost all HTML elements or tags, such as <form> and
<input>.

Server controls, which help in developing complex user-interface. For example, the
Calendar control or the Gridview control.
ASP.NET is a technology, which works on the .Net framework that contains all web-related
functionalities. The .Net framework is made of an object-oriented hierarchy. An ASP.NET
web application is made of pages. When a user requests an ASP.NET page, the IIS delegates
the processing of the page to the ASP.NET runtime system.

The ASP.NET runtime transforms the .aspx page into an instance of a class, which inherits
from the base class page of the .Net framework. Therefore, each ASP.NET page is an object
and all its components i.e., the server-side controls are also objects.

1.14 BACK END:MYSQL

It is a software, developed by Microsoft, which is implemented from the specification

of RDBMS.

It is also an ORDBMS.

It is platform dependent.

It is both GUI and command based software.

It supports SQL (SEQUEL) language which is an IBM product, non-procedural,

common database and case insensitive language.

Usage of SQLServer

To create databases.

To maintain databases.

To analyze the data through SQL Server Analysis Services (SSAS).

To generate reports through SQL Server Reporting Services (SSRS).

To carry out ETL operations through SQL Server Integration Services (SSIS).

SQL Server works in client-server architecture, hence it supports two types of components
(a) Workstation and (b) Server.

Workstation components are installed in every device/SQL Server operators

machine. These are just interfaces to interact with Server components. Example:
SSMS, SSCM, Profiler, BIDS, SQLEM etc.

Server components are installed in centralized server. These are services. Example:
SQL Server, SQL Server Agent, SSIS, SSAS, SSRS, SQL browser, SQL Server full
text search etc.

Instance of SQLServer

An instance is an installation of SQL Server.

An instance is an exact copy of the same software.

If we install 'n' times, then 'n' instances will be created.

There are two types of instances in SQL Server a) Default b) Named.

Only one default instance will be supported in one Server.

Multiple named instances will be supported in one Server.

Default instance will take the server name as Instance name.

Default instance service name is MSSQLSERVER.

16 instances will be supported in 2000 version.

50 instances will supported in 2005 and later versions.

Advantages of Instances

To install different versions in one machine.

To reduce cost.
 To maintain production, development, and test environments separately.

To reduce temporary database problems.

To separate security privileges.

To maintain standby server.

2. SYSTEM STUDY

2.1 EXISTING SYSTEM

The traditional cargo management system is completely manual and hence, tedious and much
time consuming. There is a high chance of losing and delivering the items to wrong recipients
due to misplacement of a single paper. So, a computerized and online management system is
an ultimate solution to such problems in Cargo-related systems.
2.2 PROPOSED SYSTEM
The proposed cargo management system application performs multi-task in effective
management of cargo companies. The major aim of the generated application from the
project is to reduce the manual work and provide fast, comfortable, reliable and effective
service. The software can record data in the database, display billing details, inquire modules,
and many more.
As the implementation of software in cargo agencies reduces the number of workers and
paper works, it ultimately minimizes the overall expenditure of the company. Moreover, it
helps the company in its promotion though web technology.
The key features of Cargo Management System Project are:

Easily Accessible: Being a web-based application, it can be accessed from

anywhere with internet. It is not necessary to visit the cargo office to inquire
about the services and features.

Secured: The whole system and database is fully password protected. Only the
admin and authorized users can access the data and information in the system.

Flexibility: The software has been designed in such a way that new features and
modules can be incorporated in the system as per requirement.

Reliable and Efficient: As this application works through computer and

internet, it has higher working efficiency and reliability.

3. SYSTEM DESIGN AND DEVELOPMENT

3.1 INPUT DESIGN

Input design encompasses internal and external program interfaces and the design of user
interfaces. Internal and external interface designs are guided by information obtained from
the analysis model. This defines user tasks and actions either in an elaborative or object
oriented approach. Design issues such as response time, error handling and help facilities are
considered and a design model for the system is defined. A set of generic design guidelines
governs general interaction, information display and data entry.

It is a process of converting user-oriented to a computer based format of the input

design and to make the data entry easier, logical, and free of error. Error in the input data is
controlled by the input design. The quality of the system input determines the quality of
system output in the system processing. Input design features can ensure the reliability of the
system and produce result from accurate data or they can result in Production of erroneous
information as result in feeding the faulty data.

3.2 OUTPUT DESIGN

An application is successful only when it provides effective and efficient
reports. Reports are actually presentable form of data, the reports are the main source of
information for user operated and managements. After any valid processing, the reports are
commenced and generated filed for future use. The reports are generated with great care
because it places an important design making. With the quality output the entire system may
appear to be unnecessary that user will avoid using it.
Reports are generated with the up-to-date details according to user requirement. The
report produced should be only concise with only necessary information. No unnecessary
information should be produced in the output reports.The systems objectives outlined during
the feasibility study serve as the basic from which the work of system design is initiated.
Much of the activities involved at this stage is of technical nature requiring a certain degree
of experience in designing systems, sound knowledge of computer related technology and
through understanding of computers available in the market and the various facilities
provided by the vendors. Nevertheless, a system cannot be designed in isolation without the
active involvement of the user. The user has a vital role to play at this stage too. As we know
that data collected during feasibility study wills we utilized systematically during the system
design. It should, however be kept in mind that detailed study of the existing system is not
necessarily over with the completion of the feasibility study. Depending on the plan of
feasibility study, the level of detailed study will vary and the system design stage will also
vary in the amount of investigation that still needs to be done. This investigation is generally
an urgent activity during the system. Sometimes, but rarely, this investigation may form a
separate stage between feasibility study and computer system design. Designing a new
system is a creative process, which calls for logical as will as lateral thinking. The logical
approach involves systematic moves towards the end product keeping in mind the capabilities
of the personnel and the equipment at each decision making step. Lateral thought implies
encompassing of ideas beyond the usual functions and equipment. This is to ensure that no
efforts are being made to fit previous solutions into new situations.

3.3 SYSTEM DESIGN

The system design process is not a step-by-step adherence of clear procedures and
guidelines. Though, certain clear procedures and guidelines have emerged in recent
 days,But still much of design work depends on knowledge and experience of the
designer.When designer starts working on system design, he will face different type of
problems. Many of these will be due to constraints imposed by the user or limitations
of the hardware and software available in the market. Sometimes, it is difficult to
enumerate the complexity of the problems and solutions there of since the variety of
likely problems is so great and no solutions are exactly similar. However, following
considerations should be kept in mind during the system designing phase:

3.4 DATABASE DESIGN

This activity deals with the design of the physical database. A key is to determine how
the access paths art to be implemented. Program design: In conjunction with database
design is a decision on the programming language to be used and the flowcharting,
coding, and debugging procedure prior to conversion. The operating system limits the
programming languages that will run of the system.System and program test
preparation. Each aspect of the system has a separate test requirement. System testing
is done after all programming and testing completed the test on system and program
test requirements become a part of design specifications a prerequisite to
implementation.
In contrast to the system testing is acceptance testing, which puts the system through a
procedure design to convince the user that the proposed system will meet the stated
requirements. Acceptance testing is technically similar to system testing but
politically it is different.

Design Process

The computer system design process is an exercise of specifying how, the system will
work. It is an iterative process, which is based on what the system will be do as shown
in the feasibility report.Mainly, following five parts have been included in the system
design process
Output Design
The starting point of the design process is the proper knowledge of system
requirements which will normally be converted in terms of output.
Input Design
Once the output requirements have been finalized, the next step is to find out what
 data need to be made available to the system to produce the desired outputs. The basic
documents in which these data are available need to be identified. If necessary, these
documents may have to be revised or new documents may have to be introduced.
File Design
Once the input data is captured in the system, these may to be preserved either for a
short or long period. These data will generally be stored in files in a logical manner.
The designer will have to devise the techniques of storing and retrieving data from
these files.
3.5 PROCEDURE DESIGN

This step involves specifications of how processing will be performed. In

this, there are two aspects:The computer procedure will specify what functions will be
carried out on computer, what will be different programs and in what sequence the
programs will be run.Non-computer procedure:The non-computer procedure will
specify the manual procedures for feeding input data, receiving outputs etc.

Control Design
The control design indicates necessary procedures which will ensure correctness of
processing, accuracy of data, timely output etc. this will ensure that the system is
functioning as per plan.
Development and Deployment Design
Major responsibilities include system Requirement Study, Preparing System Design
Document, Preparing the Program (Form) Specs, Peer Review of the Specs,
Implement Quality procedures as per the QMS Document, Documentation of SRS
Revalidation & Design Documents, thorough grasping of the user functionality and
applying, approving the same in the project, Developing, Testing & Debugging of
Forms, User Training and Implementation of the module.
INPUT DESIGN(Introduction)
Once the analysis and design of the system has been done, it would be necessary to
identify the data that are required to be processed to produce the outputs. Input is one
of the most expensive phases of the operation of a computerized system and creates
sometimes a major problem. Different type of problem with a system can usually be
traced back to faulty input design method needless to say, therefore, that the input data
are the lifeblood of a system and have to be analyzed and designed with utmost care
 and consideration proposed system & Replacement by an alternative source
document.
Input Design Guidelines

The design of input play very significant role in getting the correct output. It covers al
phases of input from creation of initial data (original recording) to actual entering the
data to the system for processing. The input design is the link that ties the information
system into the world of its users. Some features of design may vary depending on
whether the system is batch-oriented or on-line. Here, we will discuss the various
objectives of input design. They focus on:

Controlling amount of input

Avoiding delay
Avoiding errors in data
Avoiding extra steps
Keeping the process simple

3.36.MODULE DESCRIPTION
Department Module
Login Module
Staff Module
Registration Module
C#.NET
ACTIVE X DATA OBJECTS.NET

ADO.NET Overview
ADO.NET is an evolution of the ADO data access model that directly addresses
user requirements for developing scalable applications. It was designed specifically for the
web with scalability, statelessness, and XML in mind.

ADO.NET uses some ADO objects, such as the Connection and Command
objects, and also introduces new objects. Key new ADO.NET objects include the DataSet,
DataReader, and DataAdapter.

The important distinction between this evolved stage of ADO.NET and previous
data architectures is that there exists an object -- the DataSet -- that is separate and distinct
from any data stores. Because of that, the DataSet functions as a standalone entity. You can
think of the DataSet as an always disconnected recordset that knows nothing about the source
or destination of the data it contains. Inside a DataSet, much like in a database, there are
tables, columns, relationships, constraints, views, and so forth.
 A DataAdapter is the object that connects to the database to fill the DataSet.
Then, it connects back to the database to update the data there, based on operations
performed while the DataSet held the data. In the past, data processing has been primarily
connection-based. Now, in an effort to make multi-tiered apps more efficient, data processing
is turning to a message-based approach that revolves around chunks of information. At the
center of this approach is the DataAdapter, which provides a bridge to retrieve and save data
between a DataSet and its source data store. It accomplishes this by means of requests to the
appropriate SQL commands made against the data store.

The XML-based DataSet object provides a consistent programming model

that works with all models of data storage: flat, relational, and hierarchical. It does this by
having no 'knowledge' of the source of its data, and by representing the data that it holds as
collections and data types. No matter what the source of the data within the DataSet is, it is
manipulated through the same set of standard APIs exposed through the DataSet and its
subordinate objects.

While the DataSet has no knowledge of the source of its data, the managed
provider has detailed and specific information. The role of the managed provider is to
connect, fill, and persist the DataSet to and from data stores. The OLE DB and SQL
Server .NET Data Providers (System.Data.OleDb and System.Data.SqlClient) that are part of
the .Net Framework provide four basic objects: the Command, Connection, DataReader
and DataAdapter. In the remaining sections of this document, we'll walk through each part
of the DataSet and the OLE DB/SQL Server .NET Data Providers explaining what they are,
and how to program against them.

The following sections will introduce you to some objects that have evolved, and
some that are new. These objects are:

Connections. For connection to and managing transactions against a database.

Commands. For issuing SQL commands against a database.

DataReaders. For reading a forward-only stream of data records from a SQL

Server data source.
 DataSets. For storing, remoting and programming against flat data, XML data and
relational data.

DataAdapters. For pushing data into a DataSet, and reconciling data against a
database.

When dealing with connections to a database, there are two different options: SQL Server
.NET Data Provider (System.Data.SqlClient) and OLE DB .NET Data Provider
(System.Data.OleDb). In these samples we will use the SQL Server .NET Data Provider.
These are written to talk directly to Microsoft SQL Server. The OLE DB .NET Data Provider
is used to talk to any OLE DB provider (as it uses OLE DB underneath).

Connections
Connections are used to 'talk to' databases, and are respresented by provider-
specific classes such as SQLConnection. Commands travel over connections and resultsets
are returned in the form of streams which can be read by a DataReader object, or pushed
into a DataSet object.

Commands

Commands contain the information that is submitted to a database, and are

represented by provider-specific classes such as SQLCommand. A command can be a stored
procedure call, an UPDATE statement, or a statement that returns results. You can also use
input and output parameters, and return values as part of your command syntax. The example
below shows how to issue an INSERT statement against the Northwind database.

DataReaders

The DataReader object is somewhat synonymous with a read-only/forward-only

cursor over data. The DataReader API supports flat as well as hierarchical data. A
DataReader object is returned after executing a command against a database. The format of
the returned DataReader object is different from a recordset. For example, you might use the
DataReader to show the results of a search list in a web page.
DataSets and DataAdapters

DataSets
The DataSet object is similar to the ADO Recordset object, but more powerful, and
with one other important distinction: the DataSet is always disconnected. The DataSet object
represents a cache of data, with database-like structures such as tables, columns,
relationships, and constraints. However, though a DataSet can and does behave much like a
database, it is important to remember that DataSet objects do not interact directly with
databases, or other source data. This allows the developer to work with a programming model
that is always consistent, regardless of where the source data resides. Data coming from a
database, an XML file, from code, or user input can all be placed into DataSet objects. Then,
as changes are made to the DataSet they can be tracked and verified before updating the
source data. The GetChanges method of the DataSet object actually creates a second DatSet
that contains only the changes to the data. This DataSet is then used by a DataAdapter (or
other objects) to update the original data source.

The DataSet has many XML characteristics, including the ability to produce and consume
XML data and XML schemas. XML schemas can be used to describe schemas interchanged
via WebServices. In fact, a DataSet with a schema can actually be compiled for type safety
and statement completion.

DataAdapters (OLEDB/SQL)

The DataAdapter object works as a bridge between the DataSet and the source
data. Using the provider-specific SqlDataAdapter (along with its associated SqlCommand
and SqlConnection) can increase overall performance when working with a Microsoft SQL
Server databases. For other OLE DB-supported databases, you would use the
OleDbDataAdapter object and its associated OleDbCommand and OleDbConnection
objects.

The DataAdapter object uses commands to update the data source after changes
have been made to the DataSet. Using the Fill method of the DataAdapter calls the
SELECT command; using the Update method calls the INSERT, UPDATE or DELETE
command for each changed row. You can explicitly set these commands in order to control
the statements used at runtime to resolve changes, including the use of stored procedures. For
ad-hoc scenarios, a CommandBuilder object can generate these at run-time based upon a
select statement. However, this run-time generation requires an extra round-trip to the server
in order to gather required metadata, so explicitly providing the INSERT, UPDATE, and
DELETE commands at design time will result in better run-time performance.

1. ADO.NET is the next evolution of ADO for the .Net Framework.

2. ADO.NET was created with n-Tier, statelessness and XML in the forefront. Two
new objects, the DataSet and DataAdapter, are provided for these scenarios.

3. ADO.NET can be used to get data from a stream, or to store data in a cache for
updates.

4. There is a lot more information about ADO.NET in the documentation.

5. Remember, you can execute a command directly against the database in order to do
inserts, updates, and deletes. You don't need to first put data into a DataSet in order
to insert, update, or delete it.

6. Also, you can use a DataSet to bind to the data, move through the data, and
navigate data relationships

ASP.Net

Server Application Development

Server-side applications in the managed world are implemented through runtime
hosts. Unmanaged applications host the common language runtime, which allows your
custom managed code to control the behavior of the server. This model provides you with all
the features of the common language runtime and class library while gaining the performance
and scalability of the host server.

The following illustration shows a basic network schema with managed code
running in different server environments. Servers such as IIS and SQL Server can perform
standard operations while your application logic executes through the managed code.

Server-side managed code

 ASP.NET is the hosting environment that enables developers to use the .NET
Framework to target Web-based applications. However, ASP.NET is more than just a runtime
host; it is a complete architecture for developing Web sites and Internet-distributed objects
using managed code. Both Web Forms and XML Web services use IIS and ASP.NET as the
publishing mechanism for applications, and both have a collection of supporting classes in
the .NET Framework.

XML Web services, an important evolution in Web-based technology, are

distributed, server-side application components similar to common Web sites. However,
unlike Web-based applications, XML Web services components have no UI and are not
targeted for browsers such as Internet Explorer and Netscape Navigator. Instead, XML Web
services consist of reusable software components designed to be consumed by other
applications, such as traditional client applications, Web-based applications, or even other
XML Web services. As a result, XML Web services technology is rapidly moving application
development and deployment into the highly distributed environment of the Internet.

If you have used earlier versions of ASP technology, you will immediately notice
the improvements that ASP.NET and Web Forms offers. For example, you can develop Web
Forms pages in any language that supports the .NET Framework. In addition, your code no
longer needs to share the same file with your HTTP text (although it can continue to do so if
you prefer). Web Forms pages execute in native machine language because, like any other
managed application, they take full advantage of the runtime. In contrast, unmanaged ASP
pages are always scripted and interpreted. ASP.NET pages are faster, more functional, and
easier to develop than unmanaged ASP pages because they interact with the runtime like any
managed application.

The .NET Framework also provides a collection of classes and tools to aid in
development and consumption of XML Web services applications. XML Web services are
built on standards such as SOAP (a remote procedure-call protocol), XML (an extensible data
format), and WSDL (the Web Services Description Language). The .NET Framework is built
on these standards to promote interoperability with non-Microsoft solutions.

For example, the Web Services Description Language tool included with the
.NET Framework SDK can query an XML Web service published on the Web, parse its
WSDL description, and produce C# or Visual Basic source code that your application can use
 to become a client of the XML Web service. The source code can create classes derived from
classes in the class library that handle all the underlying communication using SOAP and
XML parsing. Although you can use the class library to consume XML Web services directly,
the Web Services Description Language tool and the other tools contained in the SDK
facilitate your development efforts with the .NET Framework.

If you develop and publish your own XML Web service, the .NET Framework
provides a set of classes that conform to all the underlying communication standards, such as
SOAP, WSDL, and XML. Using those classes enables you to focus on the logic of your
service, without concerning yourself with the communications infrastructure required by
distributed software development.

Finally, like Web Forms pages in the managed environment, your XML Web
service will run with the speed of native machine language using the scalable communication
of IIS.

Active Server Pages.NET

ASP.NET is a programming framework built on the common language runtime that

can be used on a server to build powerful Web applications. ASP.NET offers several
important advantages over previous Web development models:

Enhanced Performance.

ASP.NET is compiled common language runtime code running on the server. Unlike
its interpreted predecessors, ASP.NET can take advantage of early binding, just-in-time
compilation, native optimization, and caching services right out of the box. This amounts to
dramatically better performance before you ever write a line of code.

World-Class Tool Support.

 The ASP.NET framework is complemented by a rich toolbox and designer in the
Visual Studio integrated development environment. WYSIWYG editing, drag-and-drop
server controls, and automatic deployment are just a few of the features this powerful tool
provides.

Power and Flexibility.

Because ASP.NET is based on the common language runtime, the power and
flexibility of that entire platform is available to Web application developers. The .NET
Framework class library, Messaging, and Data Access solutions are all seamlessly accessible
from the Web. ASP.NET is also language-independent, so you can choose the language that
best applies to your application or partition your application across many languages. Further,
common language runtime interoperability guarantees that your existing investment in COM-
based development is preserved when migrating to ASP.NET.

Simplicity.

ASP.NET makes it easy to perform common tasks, from simple form submission and
client authentication to deployment and site configuration. For example, the ASP.NET page
framework allows you to build user interfaces that cleanly separate application logic from
presentation code and to handle events in a simple, Visual Basic - like forms processing
model. Additionally, the common language runtime simplifies development, with managed
code services such as automatic reference counting and garbage collection.

Manageability.

ASP.NET employs a text-based, hierarchical configuration system, which

simplifies applying settings to your server environment and Web applications. Because
configuration information is stored as plain text, new settings may be applied without the aid
of local administration tools. This "zero local administration" philosophy extends to
deploying ASP.NET Framework applications as well. An ASP.NET Framework application is
deployed to a server simply by copying the necessary files to the server. No server restart is
required, even to deploy or replace running compiled code.
 Scalability and Availability.

ASP.NET has been designed with scalability in mind, with features specifically
tailored to improve performance in clustered and multiprocessor environments. Further,
processes are closely monitored and managed by the ASP.NET runtime, so that if one
misbehaves (leaks, deadlocks), a new process can be created in its place, which helps keep
your application constantly available to handle requests.

Customizability and Extensibility.

ASP.NET delivers a well-factored architecture that allows developers to "plug-in"

their code at the appropriate level. In fact, it is possible to extend or replace any
subcomponent of the ASP.NET runtime with your own custom-written component.
Implementing custom authentication or state services has never been easier.

Security.

With built in Windows authentication and per-application configuration, you can

be assured that your applications are secure.

Language Support

The Microsoft .NET Platform currently offers built-in support for three languages:
C#, Visual Basic, and JScript.

What is ASP.NET Web Forms?

The ASP.NET Web Forms page framework is a scalable common language runtime
programming model that can be used on the server to dynamically generate Web pages.

Intended as a logical evolution of ASP (ASP.NET provides syntax compatibility with

existing pages), the ASP.NET Web Forms framework has been specifically designed to
address a number of key deficiencies in the previous model. In particular, it provides:

The ability to create and use reusable UI controls that can encapsulate common
functionality and thus reduce the amount of code that a page developer has to write.
 The ability for developers to cleanly structure their page logic in an orderly fashion
(not "spaghetti code").

The ability for development tools to provide strong WYSIWYG design support for
pages (existing ASP code is opaque to tools).

ASP.NET Web Forms pages are text files with an .aspx file name extension. They can
be deployed throughout an IIS virtual root directory tree. When a browser client requests
.aspx resources, the ASP.NET runtime parses and compiles the target file into a .NET
Framework class. This class can then be used to dynamically process incoming requests.
(Note that the .aspx file is compiled only the first time it is accessed; the compiled type
instance is then reused across multiple requests).

An ASP.NET page can be created simply by taking an existing HTML file and
changing its file name extension to .aspx (no modification of code is required). For example,
the following sample demonstrates a simple HTML page that collects a user's name and
category preference and then performs a form postback to the originating page when a button
is clicked:

ASP.NET provides syntax compatibility with existing ASP pages. This includes
support for <% %> code render blocks that can be intermixed with HTML content within
an .aspx file. These code blocks execute in a top-down manner at page render time.
Code-Behind Web Forms

ASP.NET supports two methods of authoring dynamic pages. The first is the method
shown in the preceding samples, where the page code is physically declared within the
originating .aspx file. An alternative approach--known as the code-behind method--enables
the page code to be more cleanly separated from the HTML content into an entirely separate
file.

Introduction to ASP.NET Server Controls

In addition to (or instead of) using <% %> code blocks to program dynamic content,
ASP.NET page developers can use ASP.NET server controls to program Web pages. Server
controls are declared within an .aspx file using custom tags or intrinsic HTML tags that
contain a runat="server" attribute value. Intrinsic HTML tags are handled by one of the
 controls in the System.Web.UI.HtmlControls namespace. Any tag that doesn't explicitly
map to one of the controls is assigned the type of
System.Web.UI.HtmlControls.HtmlGenericControl.

Server controls automatically maintain any client-entered values between round trips
to the server. This control state is not stored on the server (it is instead stored within an
<input type="hidden"> form field that is round-tripped between requests). Note also that no
client-side script is required.

In addition to supporting standard HTML input controls, ASP.NET enables developers

to utilize richer custom controls on their pages. For example, the following sample
demonstrates how the <asp:adrotator> control can be used to dynamically display rotating
ads on a page.

1. ASP.NET Web Forms provide an easy and powerful way to build dynamic Web UI.

2. ASP.NET Web Forms pages can target any browser client (there are no script library
or cookie requirements).

3. ASP.NET Web Forms pages provide syntax compatibility with existing ASP pages.

4. ASP.NET server controls provide an easy way to encapsulate common functionality.

5. ASP.NET ships with 45 built-in server controls. Developers can also use controls built
by third parties.

6. ASP.NET server controls can automatically project both uplevel and down-level
HTML.

7. ASP.NET templates provide an easy way to customize the look and feel of list server
controls.

8. ASP.NET validation controls provide an easy way to do declarative client or server

data validation.
SQL SERVER
DATABASE
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 Server 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.
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 table 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
 Data independence can be achieved.
Disadvantages of DBMS
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.
FEATURES OF SQL SERVER (RDBMS)

SQL SERVER is one of the leading database management systems (DBMS) because
it is the only Database that meets the uncompromising requirements of todays most
demanding information systems. From complex decision support systems (DSS) to the most
rigorous online transaction processing (OLTP) application, even application that require
simultaneous DSS and OLTP access to the same critical data, SQL Server leads the industry
in both performance and capability
SQL SERVER is a truly portable, distributed, and open DBMS that delivers unmatched
performance, continuous operation and support for every database.
SQL SERVER RDBMS is high performance fault tolerant DBMS which is specially designed
for online transactions processing and for handling large database application.
SQL SERVER with transactions processing option offers two features which contribute to
very high level of transaction processing throughput, which are

The row level lock manager

Enterprise wide Data Sharing
The unrivaled portability and connectivity of the SQL SERVER DBMS enables all the
systems in the organization to be linked into a singular, integrated computing resource.
Portability
SQL SERVER is fully portable to more than 80 distinct hardware and operating
systems platforms, including UNIX, MSDOS, OS/2, Macintosh and dozens of proprietary
platforms. This portability gives complete freedom to choose the database sever platform
that meets the system requirements.
Open Systems
SQL SERVER offers a leading implementation of industry standard SQL. SQL
Servers open architecture integrates SQL SERVER and non SQL SERVER DBMS with
industries most comprehensive collection of tools, application, and third party software
products SQL Servers Open architecture provides transparent access to data from other
relational database and even non-relational database.

Distributed Data Sharing

SQL Servers networking and distributed database capabilities to access data stored
on remote server with the same ease as if the information was stored on a single local
computer. A single SQL statement can access data at multiple sites. You can store data where
system requirements such as performance, security or availability dictate.

Unmatched Performance
The most advanced architecture in the industry allows the SQL SERVER DBMS to
deliver unmatched performance.

Sophisticated Concurrency Control

Real World applications demand access to critical data. With most database Systems
application becomes contention bound which performance is limited not by the CPU
power or by disk I/O, but user waiting on one another for data access . SQL Server employs
full, unrestricted row-level locking and contention free queries to minimize and in many
cases entirely eliminates contention wait times.

No I/O Bottlenecks
SQL Servers fast commit groups commit and deferred write technologies dramatically
reduce disk I/O bottlenecks. While some database
 4.6 DATA FLOW DIAGRAM

Data flow oriented techniques advocate that the major data items handled by a system must

be first identified and then the processing required on these data items to produce the

desired outputs should be determined. The DFD (also called as bubble chart) is a simple

graphical formalism that can be used to represent a system in terms of input data to the

system, various processing carried out on these data, and the output generated by the

system. It was introduced by De Macro (1978), Gane and Sarson (1979).The primitive

symbols used for constructing DFDs are:

Symbols used in DFD

A circle represents a process.

 A rectangle represents external entity

A square defines a source or destination of the system data.

An arrow identifies dataflow.

Double line with one end closed indicates data store

System Architecture Design

System Architecture
The SIMS is a system which contain major part which include: student
Detail, Student image and resume.
The user selects one of the available options as an input to the system.
According to the input by the user the system acts and the rest of the
functions are performed accordingly.The administartor can operate on any
student details.But the normal student or users can only access their
details of all the functionalities.
Entity Relationship Diagram :
 Entity Relationship Diagram

Functional Design Description

Data Flow Diagram :

Decision Tree :
 4. SYSTEM TESTING AND IMPLEMENTATION

INTRODUCTION:
Testing is the process of detecting errors for which the required open web application
secure employment portal specifications stated. Testing performs a very critical role for
quality assurance and for ensuring the reliability of software. The results of testing are used
later on during the software maintenance. The aim of testing is often used to demonstrate that
a program works by showing that it has no errors. The basic purpose of testing phase is to
detect the errors that may be present in the program. Hence one should not start testing with
the intent of showing that a program works, but the intent should be to show that a program
doesnt work. The main objective of testing is to uncover an error in systematic way with
minimum effort and time.

TESTING OBJECTIVES
The testing objectives are summarized in the following three steps:
Testing is process of executing a program with the intent of finding an error.
A good test case is one that has high probability of finding an undiscovered error.
A successful test is one that uncovers an as yet undiscovered error.

TESTING TYPES
The different types of testing are:
Unit testing
Integration testing
System testing
Acceptance testing

Unit Testing:
This test focuses on verification effort on the smallest unit of software module. Using the
detailed design and the process specifications testing is done to uncover errors within the
boundary of the module. All the modules must be successful in the unit test before the start of
the integration testing begins. In this project each service is a module like Login, Forms etc.
Each module has to be tested by giving different sets of inputs. The inputs are validated when
accepting from user.

Integration Testing:
After the unit testing the integration of modules has to be done and then integration
testing can be done. The goal here is to see if modules can be integrated properly, the
emphasis being on testing interfaces between different modules.
System Testing:
In the system testing the entire web portal is tested according the software requirement
specifications document.
Acceptance Testing:
The acceptance testing is performed with realistic data of the client, which focus on
the external behaviour of the system; the internal logic of the program is emphasized.
Software testing is a critical element of software quality assurance and represents the ultimate
review of specification, design and coding. Testing is the exposure of the system to trial input
to see whether it produces correct output.
TESTING PHASES:

Software testing phases include the following:

Test activities are determined and test data selected.
The test is conducted and test results are compared with the expected results.

TESTING METHODS:

Testing is a process of executing a program to find out errors. If testing is conducted

successfully, it will uncover all the errors in the software.
Any testing can be done basing on two ways:
White Box Testing
Black Box Testing

White Box Testing:

It is a test case design method that uses the control structures of the procedural design
to derive test cases.
Using this testing a software Engineer can derive the following test cases:
Exercise all the logical decisions on either true or false sides.
Execute all loops at their boundaries and within their operational boundaries.
Exercise the internal data structures to assure their validity.

Black Box Testing:

It is a test case design method used on the functional requirements of the software. It will
help a software engineer to derive sets of input conditions that will exercise all the functional
requirements of the program.
Black Box testing attempts to find errors in the following categories:
Incorrect or missing functions
Interface errors
Errors in data structures
Performance errors
Initialization and termination errors
By black box testing we derive a set of test cases that satisfy the following criteria:
Test cases that reduce by a count that is greater than one
The number of additional test cases that must be designed to achieve reasonable
testing.

TESTING PLANS:
Testing can be done in two ways:
Bottom up approach
Top down approach

SYSTEM IMPLEMENTATION
Implementation is the stage of the project when the theoretical design is turned in to a
working system. The most crucial stage is achieving a successful new system and is giving
the users confidence is that the new system will work and be effective in the implementation
stage. This stage consists of,
Testing the developed program with sample data
Detection and correction of errors
Testing whether the system meets user requirements
Creating filters of the system with actual data
Making necessary changes as desired by the user
Training user personnel
 It involves careful maintaining, investigation of the current system and its constrains
and implementation, design of methods to achieve the change over, and evaluation of change
over methods. Apart from maintenance, there are two major tasks of preparing for
implementations are education and training of users and system testing.
The system has been tested with sample data and adequate corrections were made as
per user requirements. The user has very little chances of making data entry errors since
enough validation checks and validation error message are provided in the system. The end
user with minimum amount of computer knowledge will able to key in the data and
understand the error messages. All reports have been found to satisfy their requirements.
 6. CONCLUSION

The main objective of the project is to bring a full-fledged computerized organization,

and to enable the transaction details to maintain records, which makes of the employees
easier.
Thus, the proposed system has been developed with good amount of flexibility
without compromising on the response time.
Computerization of the entire system will enhance more accuracy and reduces major
part of clerical works. Fast, clear and legible reports can be generated without any ambiguity.
Integrated database design and ease of maintenance is a major advantage of the system. User
friendliness is a unique feather of the system.
Hence by developing a system that is user-friendly in nature, many users are able to
work on the system with little of computer knowledge and training.
 7. FUTURE ENHANCEMENTS

There is a wide scope for future development of the software. The world of computer
fields is not static it is always subject to change. The technology which is famous today will
become outdated very next day. To keep abstract of technical improvements, the system may
be refinement. So it is not concluded. Yet it will improve with further enhancements.
It is essential to change the software when new software arrives with more advanced
feathers. So it is much necessary for further development. Further enhancements can be done
in an efficient manner with disruption to the system.
 7. BIBLIOGRAPHY

Elias Awath, SYSTEM ANALYSIS AND DESIGN, Tata McGraw Hill

Publication, Sixth Edition,2003
S.Ramachandran,COMPUTER AIDED DESIGN, Air Walk Publication, Third
Edition,2003
.Richard Fairley, SOFTWARE ENGINEERING CONCEPTS, Tata McGraw Hill
Publication, Second Edition,1997
Distributed .NET Programming in VB .NET by Tom Barnaby

Professional VB.NET, 2nd Edition by Fred Barwell, et al

The .NET Languages: A Quick Translation Guide by Brian Bischof

Programming VB.NET: A Guide for Experienced Programmers

by Gary Cornell, Jonathan Morrison

Learning Visual Basic.NET Through Applications by Clayton Crooks II

Visual Basic .NET How to Program (2nd Edition) by Harvey M. Deitel, Paul J.
Deitel, Tem R. Nieto
 APPENDIX:
A. DATA FLOW DIAGRAM
A data-flow diagram (DFD) is a graphical representation of the "flow" of data through an
information system DFDs can also be used for the visualization of data processing (structured
design).A DFD provides no information about the timing or ordering of processes, or about
whether processes will operate in sequence or in parallel.
DFD can be drawn during the requirements analysis and during structured design. During
design it represents how the data will flow in the system when it is built and also shows the major
transformations that the software will have and how the data will flow through different
transforms.
The general rules of drawing a DFD remain the same, we show what transforms are
needed in the software and are not concerned with the logic for implementing them. In the DFD
there are four symbols as shown below:-

A square defines a source and destination of system data.

An arrow identifies data flow. It is a pipeline through which information
flows
A circle or bubble represents a process that transforms incoming data flows
into out going data flows.
An open rectangle is a data store or a temporary repository of data.

A.3 ER DIAGRAM
An entity-relationship (ER) diagram is a specialized graphic that illustrates the
interrelationships between entities in a database. ER diagrams often use symbols to represent
three different types of information. Boxes are commonly used to represent entities.
Diamonds are normally used to represent relationships and ovals are used to represent
attributes. If the application is primarily a database application, the entity-relationship
approach can be used effectively for modeling some parts of the problem. The main focus in
ER modeling is the Data Items in the system and the relationship between them. It aims to
create conceptual scheme for the Data from the users perspective. The model thus created is
independent of any database model. The ER models are frequently represented as ER
diagram. Here we present the ER diagram of the above mentioned project.
There is no standard for representing data objects in ER diagrams. Each modeling
methodology uses its own notation. The original notation used by Chen is widely used in
academics texts and journals but rarely seen in either CASE tools or publications by non-
academics. Today, there are a number of notations used, among the more common are
Bachman, crow's foot, and IDEFIX.
All notational styles represent entities as rectangular boxes and relationships as lines
connecting boxes. Each style uses a special set of symbols to represent the cardinality of a
connection. The notation used in this document is from Martin. The symbols used for the
basic ER constructs are:

entities are represented by labeled rectangles. The label is the name of the entity.
Entity names should be singular nouns.

relationships are represented by a solid line connecting two entities. The name of the
relationship is written above the line. Relationship names should be verbs

attributes, when included, are listed inside the entity rectangle. Attributes which are
identifiers are underlined. Attribute names should be singular nouns.

cardinality of many is represented by a line ending in a crow's foot. If the crow's foot
is omitted, the cardinality is one.

existence is represented by placing a circle or a perpendicular bar on the line.

Mandatory existence is shown by the bar (looks like a 1) next to the entity for an
instance is required. Optional existence is shown by placing a circle next to the entity
that is optional

APPENDIX:
Screenshots:
Login screen:

Department:
Registration
StaffProfile
B.SOURCE CODE:

using System;
using System.Collections.Generic;
using System.Linq;
using System.Web;
using System.Web.UI;
using System.Web.UI.WebControls;
using System.Data.SqlClient;
using System.Data;

public partial class Department : System.Web.UI.Page

{

SqlConnection con;
SqlCommand cmd;

protected void Page_Load(object sender, EventArgs e)

 {

protected void linkbcomca_Click(object sender, EventArgs e)

{
string sql = " select * from StudentDetails where Depid='2'";

SqlConnection con = new SqlConnection();

con.ConnectionString = @"Data Source=.\SQLEXPRESS;Initial
Catalog=Student;Integrated Security=True";

SqlDataAdapter adpt = new SqlDataAdapter(sql, con.ConnectionString);

DataTable dt = new DataTable();
adpt.Fill(dt);

GridDepartment_View.DataSource = dt;
GridDepartment_View.DataBind();
GridDepartment_View.Visible = true;
}
protected void link_BCA_Click(object sender, EventArgs e)
{

string sql = " select * from StudentDetails where Depid='1'";

SqlConnection con = new SqlConnection();

con.ConnectionString = @"Data Source=.\SQLEXPRESS;Initial
Catalog=Student;Integrated Security=True";

SqlDataAdapter adpt = new SqlDataAdapter(sql, con.ConnectionString);

DataTable dt = new DataTable();
adpt.Fill(dt);

GridDepartment_View.DataSource = dt;
GridDepartment_View.DataBind();
GridDepartment_View.Visible = true;
}

protected void link_mscCS_Click(object sender, EventArgs e)

{
string sql = " select * from StudentDetails where Depid='5'";
 SqlConnection con = new SqlConnection();
con.ConnectionString = @"Data Source=.\SQLEXPRESS;Initial
Catalog=Student;Integrated Security=True";

SqlDataAdapter adpt = new SqlDataAdapter(sql, con.ConnectionString);

DataTable dt = new DataTable();
adpt.Fill(dt);

GridDepartment_View.DataSource = dt;
GridDepartment_View.DataBind();
GridDepartment_View.Visible = true;

}
protected void link_bsccs_Click(object sender, EventArgs e)
{
string sql = " select * from StudentDetails where Depid='4'";

SqlConnection con = new SqlConnection();

con.ConnectionString = @"Data Source=.\SQLEXPRESS;Initial
Catalog=Student;Integrated Security=True";

SqlDataAdapter adpt = new SqlDataAdapter(sql, con.ConnectionString);

DataTable dt = new DataTable();
adpt.Fill(dt);

GridDepartment_View.DataSource = dt;
GridDepartment_View.DataBind();
GridDepartment_View.Visible = true;

}
protected void link_bscmaths_Click(object sender, EventArgs e)
{

string sql = " select * from StudentDetails where Depid='6'";

SqlConnection con = new SqlConnection();

con.ConnectionString = @"Data Source=.\SQLEXPRESS;Initial
Catalog=Student;Integrated Security=True";

SqlDataAdapter adpt = new SqlDataAdapter(sql, con.ConnectionString);

 DataTable dt = new DataTable();
adpt.Fill(dt);

GridDepartment_View.DataSource = dt;
GridDepartment_View.DataBind();
GridDepartment_View.Visible = true;
}
protected void link_bbm_Click(object sender, EventArgs e)
{
string sql = " select * from StudentDetails where Depid='7'";

SqlConnection con = new SqlConnection();

con.ConnectionString = @"Data Source=.\SQLEXPRESS;Initial
Catalog=Student;Integrated Security=True";

SqlDataAdapter adpt = new SqlDataAdapter(sql, con.ConnectionString);

DataTable dt = new DataTable();
adpt.Fill(dt);

GridDepartment_View.DataSource = dt;
GridDepartment_View.DataBind();
GridDepartment_View.Visible = true;
}
protected void link_bcom_Click(object sender, EventArgs e)
{
string sql = " select * from StudentDetails where Depid='3'";

SqlConnection con = new SqlConnection();

con.ConnectionString = @"Data Source=.\SQLEXPRESS;Initial
Catalog=Student;Integrated Security=True";

SqlDataAdapter adpt = new SqlDataAdapter(sql, con.ConnectionString);

DataTable dt = new DataTable();
adpt.Fill(dt);

GridDepartment_View.DataSource = dt;
GridDepartment_View.DataBind();
GridDepartment_View.Visible = true;

}
protected void link_bbmca_Click(object sender, EventArgs e)
{
 string sql = " select * from StudentDetails where Depid='8'";

SqlConnection con = new SqlConnection();

con.ConnectionString = @"Data Source=.\SQLEXPRESS;Initial
Catalog=Student;Integrated Security=True";

SqlDataAdapter adpt = new SqlDataAdapter(sql, con.ConnectionString);

DataTable dt = new DataTable();
adpt.Fill(dt);

GridDepartment_View.DataSource = dt;
GridDepartment_View.DataBind();
GridDepartment_View.Visible = true;
}
}