FEEDBACK MANAGEMENT SYSTEM

ABSTRACT

Online Feedback Management System is a web based application that provides platform
for the colleges to conduct student’s feedback online. This online system is the best place to find
feedback report according to the requirement such as feedback given by the various kind of
people and so on and it is the efficient place to get feedback analysis and maintain security.
Students will fill online feedback using a standard form. In this project security is also maintain
that is the result of feedback is only visible to authentic user. Online feedback is an integral
feature of effective & efficient learning & teaching. It can be one of the powerful way to enhance
& strengthen student learning.

The purpose of this project is to make the process of taking feedback from the students in
online regarding the lecturer’s teaching. With this, the institutes can access the feedback reports
in a faster way and without any loss of data. As of now this task was done manually with the use
of papers and pens. This has many drawbacks and evaluating this hand written forms is a
difficult process.
INTRODUCTION

In the previous system students can give feedback about the lecturers by doing manually.
By this process student can give feedback in online system without wasting his time in writing.
After giving feedback by every student papers are collected by the faculty and calculated the
overall grade for each subject and each lecturer. After that those all grade report is viewed by the
HOD which is given by the faculty. Hence estimating the performance of lecturers and giving
feedback to college staff. So, the existing system carries more time to do a piece of work for this
reason the online system feedback is implemented. This is the main advantage of the existing
system for giving feedback about the lecturers and viewing report of lecturers. Feedback
represents information communicated to the learner that is intended to modify the learners
thinking for purpose of improving learning. The idea of feedback to make corrective actions
based on the difference between the desired and the actual value can be implemented in many
different ways. Student feedback on courses is an essential element in quality assurance.

Questionnaires are of primary importance in the dialogue with students, since they are the
best tool we currently have for collecting objective, detailed and reasonably systematic
information on a wide range of questions, which: informs the teacher about students' perceptions
of the course's strengths and weaknesses; can prompt changes in delivery methods, course
content, the provision of resources and the structures of support and guidance for the course; are
useful to staff maintaining teaching portfolios; are central to monitoring of teaching standards. In
order to gain maximum advantage: students should be told how the data will be used, when and
how results will be published, and that their contribution is important and taken seriously.

Feedback represents information communicated to the learner that is intended to modify

the learners thinking for purpose of improving learning. The idea of feedback to make corrective
actions based on the difference between the desired and the actual value can be implemented in
many different ways. Student feedback on courses is an essential element in quality assurance.
PROBLEM STATEMENT:

The problem identified from the above systems are, it does not give a useful feedback
analysis. Then the system has limited features and doesn’t work efficiently and effectively.
It doesn’t fulfill many requirement of the administrative department.

EXISTING SYSTEM
In existing system students can give feedback about the lecturers by doing manually.
After giving feedback by every student papers are collected by the faculty and calculated the
overall grade for each subject and each lecturer. After that those all grade report is viewed by the
senior lecturers which is given by the faculty. Hence estimating the performance of lecturers and
giving feedback to college staff.

DISADVANTAGES
➢ It carries more time to do a piece of work for this reason the online system feedback is
implemented.
➢ Here staffs only collect the student feedback.
➢ Only staffs and senior staff can view the feedback.
➢ It takes more time to collect the information.
➢ There is no separate option to the Principal for view the feedback.
PROPOSED SYSTEM

In our proposed system students can give their feedback by using the online web
application. Head of the Department can view the feedback after that send the email regarding
feedback to the students. And the Principal of the College also can view the students feedback.
Here principal is act as a Administrator of the application.

Student needs to logging into the website of online feedback system and giving his/her
feedback and can perform modifications too. But the restriction here is once the student submits
the report then he cannot modify it later. With this the student can successfully submit feedback
on lecturer’s teaching in a very efficient manner without any loss of data. The administrator and
the faculty members can access these feedbacks from the students and take appropriate actions.

ADVANTAGES

➢ By this process student can give feedback in online system without wasting his time in
writing.
➢ It reduces the lecturer time by giving feedback on online system when compared to the
manual process this saves time of user.
➢ Here only Head of the Department and Principal of the college can view the feedback
details which are given by the students.
➢ Providing information to the students about teaching and curriculum enhancements made
in response to student evaluation data.
➢ the entire process of giving feedback and viewing that report after giving feedback can
manage easily The result is generated is automatically hence it gives easy and quick
feedback.
MODULES:
1. Home
2. Login
3. Student Login
4. HOD Login
5. Principal Login and Admin login
6. Feedback Details
7. Students Management
8. Student Reports
9. Logout

[Link]

This common module deals about the complete profile about the system, career guidance
profile and other information that are currently doing by the system direct to homepage. It is a
much broader commitment to organize a system around its user’s profile in order to anticipate
individual needs providing the organizational structure for good things.
[Link]:

This module is used by all the users to log into the account. The user is required to
enter his/her user name and password. The user will be prompted to enter the needed
page provided username and password are correct otherwise he/she will be asked to
reenter password and ​security authentication persevered. In our project have three login
pages. One is admin login another one is student login and the third one is HOD login.
3. STUDENT LOGIN:
This module is used for login to the student account. The student is required to enter user
name and password. The student will be prompted to enter the needed page provided username
and password are correct otherwise student will be asked to reenter password and ​security
authentication persevered.

After successfully login the student will update the mark details and certificate details to the
admin.

Enter username &

Password

Database
4. HOD LOGIN:

This module is used by all the users to log into the account. The user is required to enter
his/her user name and password. The user will be prompted to enter the needed page provided
username and password are correct otherwise he/she will be asked to reenter password and
security authentication persevered. Technically a validation certificate is sent to the browser
client verify whether it is a secured session. Then only the web page is loaded into the browser
on any app. This is to avoid the software forgery attacks. After verification the login page is
loaded for user authentication. The password and username is transferred to the server after
encryption.​ After successful login user will be redirected to the user’s home page.

Database
5. ADMIN LOGIN:
This module is used for login to admin account. The admin is required to enter
user name and password. The admin will be prompted to enter the needed page provided
username and password are correct otherwise admin will be asked to reenter password and
security authentication persevered. Technically a validation certificate is sent to the browser
client verify whether it is a secured session. Then only the web page is loaded into the browser
on any app. This is to avoid the software forgery attacks. After verification the login page is
loaded for user authentication. The password and username is transferred to the server after
encryption.​ After successful login admin will be redirected to the user’s request page.

Database
6. FEEDBACK DETAILS:

Feedback Management System is to provide an easy way not only to automate all
functionalities involved managing leaves and feedback for the employees of College, but also to
provide full functional reports to management of College lecturers with the details about usage of
leave facility. This module helps the administrator to enter the designation and the related
description .It is help to search the employee details department wise and designation wise.
7. STUDENTS MANAGEMENT:
This module helps to add the details of the employee like the personal detail and the
employee detail. Admin maintain a feedback details and students details .if new students are
joining the college admin can enter the details of new staff. All details are stored in the database
securely. If students are leave from college, admin remove the details from a database.
 Database

8. REPORTS:

​With the advent of a new feedback analysis application, the campus leadership group
determined that a set of predefined reports was necessary to better help analyze and present the
data in a friendly and usable format. This report lists only Principal and Head of the Depatment
of college with overrides for the given time period and accounting information. This report is
very helpful in providing what needs to be updated in the feedback management system.

Database

9. LOGOUT:

Each user logged in user properly logged out from the application for the security
 purpose. This module also used for security purpose.

OVERALL ARCHITECTURE DIAGRAM:

Report Details

Report
UML DIAGRAMS

USE CASE DIAGRAM:

SEQUENCE DIAGRAM:
CLASS DIAGRAM:
ACTIVITY DIAGRAM:
COLOBORATION DIAGRAM:
COMPONENT DIAGRAM:
 SYSTEM CONFIGURATION

SOFTWARE REQUIREMENTS

Server Side Programming : [Link]

Middleware Programming : C#

Operating System : Windows 7 ultimate

Web Server : Internet Information Server

Client Script : Java Script

Database : SQL-Server 2008

HARDWARE REQUIREMENTS

Processor : Intel Dual Core 2.8 GHz

Hard Disk : 80 GB
Monitor : LG 17” Color Monitor

RAM : 2GB DDR RAM

Keyboard : 104 Keys Multimedia Keyboard

Mouse : Logitech Optical Mouse

CD – ROM : 52X CD-ROM.

SOFTWARE DESCRIPTION
NET FRAMEWORK

Microsoft® .NET Framework version 1.1 the .NET Framework is an integral Windows
component that supports building and running the next generation of applications and XML Web services.
The key components of the .NET Framework are the common language runtime and the .NET Framework
class library, which includes [Link], [Link], and Windows Forms. The .NET Framework provides
a managed execution environment simplified development and deployment, and integration with a wide
variety of programming languages. For a brief introduction to the architecture of the .NET Framework

The .NET Framework is a new computing platform that simplifies application development in the
highly distributed environment of the Internet. The .NET Framework is designed to fulfill the following
objectives.

● To provide a consistent object-oriented programming environment whether object code is

stored and executed locally but Internet-distributed, or executed remotely.
● To provide a code-execution environment that minimizes software deployment and
versioning conflicts.
● To provide a code-execution environment that eliminates the performance problems of
scripted or interpreted environments.
● To make the developer experience consistent across widely varying types of applications,
such as Windows-based applications and Web-based applications.
● To build all communication on industry standards to ensure that code based on the .NET
 Framework can integrate with any other code.
The .NET Framework has two main components: the common language runtime and the .NET
Framework class library. The common language runtime is the foundation of the .NET Framework. You
can think of the runtime is an agent that manages code at execution time, providing core services such as
memory management, thread management, and remoting while also enforcing strict type safety and other
forms of code accuracy that ensure security and robustness. In fact, the concept of code management is a
fundamental principle of the runtime. Code that targets the runtime is known as managed code, while
code that does not target the runtime is known as unmanaged code. The class library, the other main
component of the .NET Framework, is a comprehensive, object-oriented collection of reusable types that
you can use to develop applications ranging from traditional command-line or graphical use interface
(GUI) applications based on the latest innovations provided by [Link], such as Web Forms and XML
Web Services.

The following illustration shows the relationship of the common language runtime and the class
library to your applications and to the overall system. The illustration also shows how managed code
operates within a larger architecture.

NET FRAMEWORK IN CONTEXT

 4.1.1. .NET Framework in context

FEATURES OF THE COMMON LANGUAGE RUNTIME

The common language runtime manages memory, thread execution, code execution, code
safety verification, compilation, and other system services. These features are intrinsic to the
managed code that runs on the common language runtime.

With regards to security, managed components are awarded varying degrees of trust,
depending on a number of factors that include their origin (such as the Internet, enterprise
network, or local computer). This means that a managed component might or might not be able
to perform file-access operations, registry-access operations, or other sensitive functions, even if
it is being used in the same active application.

The runtime enforces code access security. For example, users can trust that an
executable embedded in a Web page can play an animation on screen or sing a song, but cannot
access their personal data, file system, or network. The security features of the runtime thus
enable legitimate Internet-deployed software to be exceptionally feature rich.

The runtime also enforces code robustness by implementing a strict

type-and-code-verification infrastructure called the common type system (CTS). The CTS
ensures that all managed code is self-describing. The various Microsoft and third-party language
compilers generate managed code that conforms to the CTS. This means that managed code can
consume other managed types and instances, while strictly enforcing type fidelity and type
safety.

In addition, the managed environment of the runtime eliminates many common software
issues. For example, the runtime automatically handles object layout and manages references to
objects, releasing them when they are no longer being used. This automatic memory
management resolves the two most common application errors, memory leaks and invalid
memory references.

The runtime also accelerates developer productivity. For example, programmers can
write applications in their development language of choice, yet take full advantage of the
runtime, the class library, and components written in other languages by other developers. Any
compiler vendor who chooses to target the runtime can do so. Language compilers that target the
.NET Framework make the features of the .NET Framework available to existing code written in
that language, greatly easing the migration process for existing applications.

While the runtime is designed for the software of the future, it also supports software of
today and yesterday. Interoperability between managed and unmanaged code enables developers
to continue to use necessary COM components and DLLs.

The runtime is designed to enhance performance. Although the common language

runtime provides many standard runtime services, managed code is never interpreted. A feature
called just-in-time (JIT) compiling enables all managed code to run in the native machine
language of the system on which it is executing. Meanwhile, the memory manager removes the
possibilities of fragmented memory and increases memory locality-of-reference to further
increase performance.

Finally, the runtime can be hosted by high-performance, server-side applications, such as

Microsoft® SQL Server™ and Internet Information Services (IIS). This infrastructure enables
you to use managed code to write your business logic, while still enjoying the superior
performance of the industry's best enterprise servers that support runtime hosting.

.NET FRAMEWORK CLASS LIBRARY

The .NET Framework class library is a collection of reusable types that tightly integrate
with the common language runtime. The class library is object oriented, providing types from
which your own managed code can derive functionality. This not only makes the .NET
Framework types easy to use, but also reduces the time associated with learning new features of
the .NET Framework. In addition, third-party components can integrate seamlessly with classes
in the .NET Framework.

For example, the .NET Framework collection classes implement a set of interfaces that
you can use to develop your own collection classes. Your collection classes will blend
seamlessly with the classes in the .NET Framework.

As you would expect from an object-oriented class library, the .NET Framework types
enable you to accomplish a range of common programming tasks, including tasks such as string
management, data collection, database connectivity, and file access. In addition to these common
tasks, the class library includes types that support a variety of specialized development scenarios.
For example, you can use the .NET Framework to develop the following types of applications
and services:

● Console applications.
● Windows GUI applications (Windows Forms).
● [Link] applications.
● XML Web services.
● Windows services.

For example, the Windows Forms classes are a comprehensive set of reusable types that
vastly simplify Windows GUI development. If you write an [Link] Web Form application,
you can use the Web Forms classes.

CLIENT APPLICATION DEVELOPMENT

Client applications are the closest to a traditional style of application in Windows-based

programming. These are the types of applications that display windows or forms on the desktop,
enabling a user to perform a task. Client applications include applications such as word
processors and spreadsheets, as well as custom business applications such as data-entry tools,
reporting tools, and so on. Client applications usually employ windows, menus, buttons, and
other GUI elements, and they likely access local resources such as the file system and peripherals
such as printers.

Another kind of client application is the traditional ActiveX control (now replaced by the
managed Windows Forms control) deployed over the Internet as a Web page. This application is
much like other client applications: it is executed natively, has access to local resources, and
includes graphical elements.

In the past, developers created such applications using C/C++ in conjunction with the
Microsoft Foundation Classes (MFC) or with a rapid application development (RAD)
environment such as Microsoft® Visual Basic®. The .NET Framework incorporates aspects of
these existing products into a single, consistent development environment that drastically
simplifies the development of client applications.

The Windows Forms classes contained in the .NET Framework are designed to be used
for GUI development. You can easily create command windows, buttons, menus, toolbars, and
other screen elements with the flexibility necessary to accommodate shifting business needs.

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

[Link] is the hosting environment that enables developers to use the .NET Framework
to target Web-based applications. However, [Link] 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 [Link] as the publishing
mechanism for applications, and both have a collection of supporting classes in the .NET
Framework.

4.1.2. Server-side managed code

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 [Link] and Web Forms offer. 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. [Link] 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.

COMMON LANGUAGE RUNTIME

Compilers and tools expose the runtime's functionality and enable you to write code that
benefits from this managed execution environment. Code that you develop with a language
compiler that targets the runtime is called managed code; it benefits from features such as
cross-language integration, cross-language exception handling, enhanced security, versioning
and deployment support, a simplified model for component interaction, and debugging and
profiling services.

To enable the runtime to provide services to managed code, language compilers must emit
metadata that describes the types, members, and references in your code. Metadata is stored with
the code; every loadable common language runtime portable executable (PE) file contains
metadata. The runtime uses metadata to locate and load classes, lay out instances in memory,
resolve method invocations, generate native code, enforce security, and set run-time context
boundaries.

The runtime automatically handles object layout and manages references to objects, releasing
them when they are no longer being used. Objects whose lifetimes are managed in this way are
called managed data. Garbage collection eliminates memory leaks as well as some other
common programming errors. If your code is managed, you can use managed data, unmanaged
data, or both managed and unmanaged data in your .NET Framework application. Because
language compilers supply their own types, such as primitive types, you might not always know
(or need to know) whether your data is being managed.

The common language runtime makes it easy to design components and applications whose
objects interact across languages. Objects written in different languages can communicate with
each other, and their behaviors can be tightly integrated. For example, you can define a class and
then use a different language to derive a class from your original class or call a method on the
original class. You can also pass an instance of a class to a method of a class written in a
different language. This cross-language integration is possible because language compilers and
tools that target the runtime use a common type system defined by the runtime, and they follow
the runtime's rules for defining new types, as well as for creating, using, persisting, and binding
to types.

As part of their metadata, all managed components carry information about the
components and resources they were built against. The runtime uses this information to ensure
that your component or application has the specified versions of everything it needs, which
makes your code less likely to break because of some unmet dependency. Registration
information and state data are no longer stored in the registry where they can be difficult to
establish and maintain. Rather, information about the types you define (and their dependencies)
is stored with the code as metadata, making the tasks of component replication and removal
much less complicated.

Language compilers and tools expose the runtime's functionality in ways that are intended to
be useful and intuitive to developers. This means that some features of the runtime might be
more noticeable in one environment than in another. How you experience the runtime depends
on which language compilers or tools you use. For example, if you are a Visual Basic developer,
you might notice that with the common ​language runtime, the Visual Basic language has more
object-oriented features than before. Following are some benefits of the runtime.

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

If you use Microsoft® Visual C++® .NET, you can write managed code using the Managed
Extensions for C++, which provide the benefits of a managed execution environment as well as
access to powerful capabilities and expressive data types that you are familiar with. Additional
runtime features include:

● Cross- language integration, especially cross- language inheritance.

 ● Garbage collection, which manages object lifetime so that reference counting is unnecessary.
●  Self-describing objects, which make using Interface Definition Language (IDL) unnecessary.

[Link] ARCHITECTURE

4.1.3. [Link] Architecture

REMOTING OR MARSHALING DATA BETWEEN TIERS AND CLIENTS

The design of the ​Dataset enables you to easily transport data to clients over the Web
using XML Web services, as well as allowing you to marshal data between .NET components
using .NET Remoting services. You can also remote a strongly typed ​Dataset in this fashion. For
an overview of XML Web services..

An overview of remoting services can be found in the .NET Remoting Overview. Note
that ​Data Table objects can also be used with remoting services, but cannot be transported via
an XML Web service.
 

.NET FRAMEWORK DATA PROVIDERS

A .NET Framework data provider is used for connecting to a database, executing

commands, and retrieving results. Those results are either processed directly, or placed in an
[Link] ​Dataset in order to be exposed to the user in an ad-hoc manner, combined with data
from multiple sources, or remoted between tiers. The .NET Framework data provider is designed
to be lightweight, creating a minimal layer between the data source and your code, increasing
performance without sacrificing functionality.

The following table outlines the four core objects that make up a .NET Framework data
provider.

Object Description

Connection Establishes a connection to a specific data source.

Command Executes a command against a data source. Exposes

Parameters and can execute within the scope of a
Transaction​ from a ​Connection​.

Data Reader Reads a forward-only, read-only stream of data from

a data source.

Data Adapter Populates a ​Dataset and resolves updates with the

data source.

The .NET Framework includes the .NET Framework Data Provider for SQL Server (for
Microsoft SQL Server version 7.0 or later), the .NET Framework Data Provider for OLE DB,
and the .NET Framework Data Provider for ODBC.

Note​ The .NET Framework Data Provider for ODBC is not included in the .NET Framework version
1.0. If you require the .NET Framework Data Provider for ODBC and are using the .NET Framework
version 1.0, you can download the .NET Framework Data Provider for ODBC at
[Link] The namespace for the downloaded .NET Framework Data
Provider for ODBC is ​[Link]​.

THE .NET FRAMEWORK DATA PROVIDER FOR SQL SERVER

The .NET Framework Data Provider for SQL Server uses its own protocol to
communicate with SQL Server. It is lightweight and performs well because it is optimized to
access a SQL Server directly without adding an OLE DB or Open Database Connectivity
(ODBC) layer. The following illustration contrasts the .NET Framework Data Provider for SQL
Server with the .NET Framework Data Provider for OLE DB. The .NET Framework Data
Provider for OLE DB communicates to an OLE DB data source through both the OLE DB
Service component, which provides connection pooling and transaction services, and the OLE
DB Provider for the data source.

Comparison of the .NET Framework Data Provider for SQL Server and the .NET
Framework Data Provider for OLE DB

4.1.4. Comparison of .NET Framework Data Provider for SQL Server and OLEDB

To use the .NET Framework Data Provider for SQL Server, you must have access to
Microsoft SQL Server 7.0 or later. .NET Framework Data Provider for SQL Server classes are
located in the ​[Link] namespace. For earlier versions of Microsoft SQL Server,
use the .NET Framework Data Provider for OLE DB with the SQL Server OLE DB Provider
(SQLOLEDB).
 

4.2. VISUAL C# LANGUAGE

Microsoft C# (pronounced C sharp) is a new programming language designed for

building a wide range of enterprise applications that run on the .NET Framework. An evolution
of Microsoft C and Microsoft C++, C# is simple, modern, type safe, and object oriented. C# code
is compiled as managed code, which means it benefits from the services of the common language
runtime. These services include language interoperability, garbage collection, enhanced security,
and improved versioning support.

C# is introduced as Visual C# in the Visual Studio .NET suite. Support for Visual C#
includes project templates, designers, property pages, code wizards, an object model, and other
features of the development environment. The library for Visual C# programming is the .NET
Framework.

C# (pronounced “See Sharp”) is a simple, modern, object-oriented, and type safe

programming language. C# has its roots in the C family of languages and will be immediately
familiar to C, C++, and Java programmers. C# is standardized by ECMA International as the
ECMA-334 standard and by ISO/IEC as the ISO/IEC 23270 standard. Microsoft’s C# compiler
for the .NET Framework is a conforming implementation of both of these standards. C# aims to
combine the high productivity of Visual Basic and the raw power of C++.

Visual C#.NET is Microsoft’s C# development tool. It includes an interactive

development environment, visual designers for building Windows and Web applications, a
compiler, and a debugger. Visual C#.NET is part of suite of products, called Visual [Link],
that also includes Visual [Link], Visual C++.NET, and the Jscript scripting language. All of
these languages provide access to the Microsoft .NET Framework, which includes a common
execution engine and a rich class library. The .NET Framework defines a “Common language
Specification” (CLS), a sort of lingua franca that ensures seamless interoperability between CLS
compliant languages and class libraries. For C# developers, this means that even though C# is a
new language, it has complete access to the same rich class libraries that are used by seasoned
tools such as Visual Basic .NET and Visual C++.NET. C# itself does not include a class library.

C# is an object-oriented language, but C# further includes support for

component-oriented programming. Contemporary software design increasingly relies on
software components in the form of self-contained and self-describing packages of functionality.
Key to such components is that they present a programming model with properties, methods and
events; they have attributes that provide declarative information about the component; and they
incorporate their own documentation. C# provides language constructs to directly support these
concepts, making C# a very natural language in which to create and use software components.

Several C# features aid in the construction of robust and durable applications: Garbage
collection automatically reclaims memory occupied by unused objects; exception handling
provides a structured and extensible approach to error detection and recovery; and the type-safe
design of the language makes it impossible to have uninitialized variables, to index arrays
beyond their bounds, or to perform unchecked type casts.

C# has a unified type system. All C# types, including primitive types such as int and
double, inherit from a single root object type, Thus, all types share a set of common operations,
and values of any type can be stored, transported, and operated upon in a consistent manner.
Furthermore, C# supports both user-defined reference types and value types, allowing dynamic
allocation of objects as well as in-line storage of lightweight structures.

To ensure that C# programs and libraries can evolve over time in a compatible manner,
much emphasis has been placed on versioning in C#’s design. Many programming languages
pay little attention to this issue, and, as a result, programs written in those languages break more
often than necessary when newer versions of dependent libraries are introduced. Aspects of C#
’s design that were directly influenced by versioning considerations include the separate virtual
and override modifiers, the rules for method overload resolution, and support for explicit
interface member declarations.

C# 2.0 introduces several language extensions, including Generics, Anonymous Methods,

Iterators, Partial Types, and Nullable Types.

● Generics permit classes, structs, interfaces, delegates, and methods to be

parameterized by the types of data they store and manipulate. Generics are useful
because they provide stronger compile-time type checking, require fewer explicit
conversions between data types, and reduce the need for boxing operations and
run-time type checks.

● Anonymous methods allow code blocks to be written “in-line” where delegate

values are expected. Anonymous methods are similar to lambda functions in the
Lisp programming language. C# 2.0 supports the creation of “closures” where
anonymous methods access surrounding local variables and parameters.

● Iterators are methods that incrementally compute and yield a sequence of values.
Iterators make it easy for a type to specify how for each statement will iterate over
 its elements.

● Partial types allow classes, structs, and interfaces to be broken into multiple
pieces stored in different source files for easier development and maintenance.
Additionally, partial types allow separation of machine-generated and
user-written parts of types so that it is easier to augment code generated by a tool.

● Nullable types represent values that possibly are unknown. A nullable type
supports all values of its underlying type plus an additional null state. Any value
type can be the underlying type of a nullable type.

4.3. [Link]

The .NET framework includes tools that ease the creation of web services. [Link] is the
latest offering from Microsoft toward the creation of a new paradigm for server-side scripting. We will
see the basics of [Link], which provides a complete framework for the development of web
applications. Here we get introduced into [Link], the platform requirements for [Link]
applications, and the [Link] architecture. In addition, we get introduced to web forms of [Link]
applications, a new addition to [Link].

​ASP .NET differs in some ways from earlier versions Os ASP. [Link] has new features such
as better language support, a new set of controls, XML-based components, and more secure user
authentication. [Link] also provides increased performance by executing ASP code.

Usually a software product undergoes many evolutionary phases. In each release version of the
software product, the software vendor fixes the bugs form previous versions and adds new features. ASP
1.0 was released in 1996. Since then, two more versions of ASP (2.0 AND 3.0) have been released. In
various versions of ASP, new features have been added. However, the basic methodology used for
creating applications has not changed.

[Link] provides a unique approach toward web application development, so one might say
that [Link] has stared a new revolution in the world of web application development. [Link] is
based on the [Link] framework. The .NET framework. The .NET framework is based on the
common language runtime (CLR). There fore, it imparts all of the CLR benefits to [Link]
applications. These CLR benefits include automatic memory management, support for multiple
languages, secure user authentication, and ease in configuration, and ease in deployment.

BENEFITS OF [Link]

Support for various programming language [Link] provides better programming-language

support than ASP. It uses the new [Link] earlier versions of ASP support only scripting language
such as VBScript and Jscript. Using this scripting language, we can write applications used to perform
server-side processing, but this has two major drawbacks. First, scripting language is interpreted and not
complied. Therefore, the errors can only be checked at runtime. This affects the performance of web
applications. Second, scripting language is not strongly typed. The scripting languages do not have a built
–in set of predefined data types. This requires developers to cast the existing objects of the language to
their expected data type. Thus, these objects can be validated only at runtime. This validation leads to a
low performance of web applications. [Link] continues to support scripting languages, but it supports
complete Visual Basic for server-side programming [Link] also provides support for c# (pronounced c
sharp) and C++.

CROSS – LANGUAGE DEVELOPMENT

​[Link] provides flexibility to extend created in one language to another language. For example, if
we have an object in C++, [Link] enables us to extend this object in Visual Basic.
[Link] PAGE SYNTAX

DIRECTIVES
<% @ page language =”VB” […] %>

Code Declaration Blocks

<script run at=”server” […]>

[ lines of code]

</script>

CODE RENDER BLOCKS

<%

[inline code or expressions]

%>

HTML Control Syntax

<HTML element runat=”server” [attribute(s)]>

</HTML element>

CUSTOM CONTROL SYNTAX

​CUSTOM SERVER CONTROLS

<ASP: Textbox id=”My Tbi” run at=”server”>
SERVER CONTROL PROPERTY
<ASP: Textbox maxlength=”80” run at=”server”>

SUB PROPERTY

<ASP: Label font-size=”14” run at=”server”>

SERVER CONTROL EVEN BINDING

<ASP: Button On Click=”My Click” run at=”server”>

DATA BINDING EXPRESSION

< asp: label

Text=’<%# data binding expression %>’

Run at =”server”/>

SERVER-SIDE OBJECTS TAGS

<object id=”id” run at=”server”

Identifier=”idName”/>

SERVER-SIDE INCLUDE DIRECTIVES

<!-#include pathtype=filename -->

​SERVER-SIDE COMMENTS

%-- comment block -- %>

An application in [Link] consists of files, pages, modules, and executable code that reside in one
virtual directory and its subdirectories. Application state is stored in global variables for a given
[Link] application. For that Reason developers have to follow some implements rules .Variables for
storing application state occupy system resources.

A global variable has to be locked and unlocked to prevent problems with concurrent

access.
WEB FORMS SERVER CONTROLS

The term server controls always means Web Forms server controls, because they are
specially designed to work with Web Forms.

SERVER CONTROL FAMILIES

​Web Forms provide different server control families

➢ HTML server controls

➢ [Link] server controls
➢ Validation controls
➢ User controls
➢ Mobile controls

DATA BINDING

We can bind Web Forms control properties to any data in a data store. This so-called data
binding gives us nearly complete control over how data moves to the page and back again to the
data store.

PAGE CLASS
 When a page is loaded, the [Link] runtime generates and instantiates a page class.
This object forms a collection of our separate components (like visual elements and business
logic). So all (visual and code) elements are accessible through this object.

HTML SERVER CONTROLS

We can convert simple HTML elements to HTML server controls, let the [Link]
engine create an instance on the server, and now they are programmable on the server. The
conversion is done by simply adding attributes to the HTML tag. The attributes runat=server
informs the framework to create a server-side instance of the control. If we additionally assign
an ID, we can reference the control in our code.

For example, we can use the HTMLAnchor control to program against the HTML <a>
tag to dynamically generate the H Ref values, or use HtmlTable (HTML <table>) to
dynamically create tables and their content.

[Link] SERVER CONTROLS

[Link] server controls are abstract controls. There is no one-to-one mapping to

HTML server controls. But [Link] comes with a rich set of controls.

Another feature is the typed object model. This gives us the potential for type-safe
programming. Server controls can automatically detect what browser we are using and generate
the proper version of HTML output.

BUTTON
This is way to enable the user to finish editing a form. A Button enforces the submitting of the
page, and we can additionally raise events like the Click event.
TEXTBOX
A Textbox is an input box where the user can enter information like numbers, text, or dates
formatted as single line, multilane, or password. This control raises a Text Changed event when the focus
“leaves” the control.

VALIDATION CONTROLS
Another group of server controls are validation controls. These can be used to check the user’s
entries. Validation can be processed on the client and on the server.

Validation on the client side can be performed using a client script. In that case, the user will be
confronted with immediate feedback-without a roundtrip to the server. Server-side validation in addition
provides, for example, security against users bypassing client-side validation.

[Link] PROVIDES THE FOLLOWING TYPES OF VALIDATION

Required entry- the field must be filled in by the user. Comparison to a value- the entered value is
checked against another value of another field, a database, or a constant value by using comparison
operators. Range checking – the user’s entry is checked to see whether it resides between given
boundaries. Pattern matching- a regular expression is defined that the entered value must match. User’s
defined- implement our own validation logic. When the validation fails, an error message is generated and
sent back to the client browser. This can be done in several ways. For example, all error messages
related to a specific transaction could be collected and presented to the user in summary.

4.4. SQL SERVER INTRODUCTION

SQL stands for Structured Query Language. SQL is used to communicate with a database.
According to ANSI (American National Standards Institute), it is the standard language for relational
database management systems.

SQL statements are used to perform tasks such as update data on a database, or retrieve data from
a database. Some common relational database management systems that the SQL are: Oracle, Sybase,
Microsoft SQL Server, Access, Ingress, etc. Although most database systems use SQL, most of them
also have their own additional proprietary extensions that are usually only used on their system.

The standard SQL commands such as “Select”, “Insert”, “Update”, ”Delete”, ”Create”, and
“Drop” can be used to accomplish almost everything that one needs to do with a database. This tutorial
will provide you with the instruction on the basics of each of these commands as well as allow you to put
them to practice using the SQL Interpreter.

TABLE BASICS

A relational database system contains one of more objects called tables. The data or information
for the database is stored in these tables. Tables are uniquely identified by their names and are comprised
of columns and rows. Columns contain the column name, data type, and any other attributes for the
column. Rows contain the records or data for the columns.

SELECTING DATA

The select statement is used to query the database and relatives selected data that match the
criteria that you specify. Here is the format of a simple select statement.

​Select “column1” [,”column2”, etc] from “table name”

[Where “condition”]; [ ] =optional

The column names that follow the select keyword determine which columns will be returned in
the results. We can select as many column names that you’d like, or you can use a “*” to select all
columns. The table name that follows the keyword from specifies the table that will be queried to retrieve
the desired results.

The where clause (optional) specifies which data values or rows will be returned or displayed,
based on the criteria described after the keyword where.

Conditional selections used in the where clause

= Equal

> Greater than

< Less than

>= Greater than or equal

<= Less than or equal

< > Not equal to

LIKE

The LIKE pattern matching operator can also be used in the conditional selection of the where
clause. Like is a very powerful operator that allows you to select only rows that are “Like” what you
specify. The percent sign “%” can be used as a wild card to match any possible character that might
appear before or after the characters specified.

For example

​Select first, last, city

From empinfo

Where first LIKE ‘Er%’;

This SQL statement will match any first names that start with ‘Er’. Strings must be in single
quotes. Or we can specify

Select first, last

From empinfo where last LIKE ‘%s’;

 This statement will match any last names that end in‘s’.

Select * from user

Where first = ‘Erie’;

This will only select rows where the first name equals ‘Erie’ exactly.

CREATING TABLES

The create tables statement is used to create a new table. Here is the format of a simple
create table statement.
Create table “table name”

(“column1” “data type”,

“column2” “data type”,

“column3” “data type”);

FORMAT FOR CREATING TABLE BY USING OPTIONAL CONSTRAINTS

Create table “table name”

(“column1” “data type”

[Constraints],

“column2” “data type”

[Constraints],

“column3” “data type”

[Constraints],

[ ] = optional)

To create a new table, enter the keywords create table followed by the table name, followed by
an open parenthesis , followed by the first column name, followed by the data type for that column,
followed by any optional constraints, any followed by a closing parenthesis before the beginning table
and a closing parenthesis after the end of the last column definition. Make sure you separate each
column definition with a comma. All SQL statements should end with a “;”.

The table and column names must start with a letter and can be followed by letters, numbers, or
underscore – not to exceed a total of 30 characters in length. Do not use any SQL reserved keywords as
names for tables or column names (such as “select”, “create”, “insert”, etc).Data types specify what the
types of data can be for that particular column. If a column called “Last Name” is to be used to hold
names, then that particular column should have a “VarChar” (variable-length character) data type.

COMMON DATA TYPES

Char(size) Fixed-length character string. Size is specified in parenthesis. Max

255 bytes.

VarChar (size) Variable-length character string. Max size is specified in parenthesis.

Number (size) Number value with a max number of columns digits specified in
parenthesis.

Date Date value

Number(size, d) Number value with a maximum number of digits of “size” total, with a
maximum number of “d” digits to the right of the decimal

Number(size, d) Number value with a maximum number of digits of “size” total, with
a maximum number of “d” digits to the right of the decimal.
 What are constraints? When tables are created, it is common for one or more columns to have
constraints associated with them. A constraint is basically a rule associated with a column that the data
entered into that column must follow. For example, a ‘unique” constraints specifies that no two records
can have the same value in a particular column. They must all be unique.

The other two most particular constraints are “not null” which specifies that a column can’t be
left blank, and “primary key”. A “primary key” constraint defines a unique identification of each record
(or row) in a table. Constraints can be entered in this SQL interpreter, however, they are not supported in
this Intro to SQL tutorial & interpreter. They will be covered and supported in the future release of the
Advanced SQL tutorial- that is, if “response” is good.

INSERTING INTO A TABLE

The insert statement is used to insert or add a row of data into the table. To insert records into a
table, enter the key words insert into followed by the table name, followed by an open parenthesis,
followed by a list of column names separated by commas, followed by a closing parenthesis, followed by
the keyword values, followed by the list of values enclosed in parenthesis. The values that you enter will
be held in the rows and they will match up with the column names that you specify. Strings should be
enclosed in single quotes, and numbers should not.

Insert into “table name”

(First column...last column)

Values (first value...last value);

UPDATING RECORDS
The update statement is used to update or change records that match specified criteria. This is
accomplished by carefully constructing a where clause.
 Update “table name”

Set “column name”= “new value”

[ ,”next column” = “newvalue2”...]

Where “column name” OPERATOR “value”

[and/or “column” OPERATOR “value”];

DELETING RECORDS
The delete statement is used to delete records or rows from the table.

Delete from “table name”

Where “column name”

OPERATOR “value”

[and/or “column”

OPERATOR “value”]

To delete an entire record/row from a table, enter “delete form” followed by the table name,
followed by the where clause which contains the conditions to delete. If you leave off the where clause,
all records will be deleted.

DROP A TABLE
The drop table command is used to delete a table and all rows in the table. To delete an entire
table including all of its rows, issue the drop table command followed by the table name. Drop table is
different from deleting all of the records in the table. Deleting all of the records in the table leaves the
table including column and constraint information. Dropping the table removes the table definition as
well as all of its rows.

Drop table “table name”

TABLE JOINS

All of the queries up until this point have been useful with the exception of one major limitation-
that is, you’ve been selecting from only one table are a time with your SELECT statement. It is time to
introduce you to one of the most beneficial features of SQL & relational database system – the

Joins allow you to link data from two or more tables together into a single query result – from one
single SELECT statement. A “join” can be recognized in a SQL SELECT statement if it has more than
one table after the FROM keyword.

SCREEN SHOT:

CODING:

Admin login:

using System;
using [Link];
using [Link];
using [Link];
using [Link];
using [Link];
using [Link];
using [Link];
public partial class Adminview : [Link]
{
SqlConnection con;
SqlCommand cmd;
string s;
SqlDataAdapter da;
DataTable dt;
DataSet ds;

protected void Page_Load(object sender, EventArgs e)

{

}
protected void Button1_Click(object sender, EventArgs e)
{
[Link]("[Link]");
}

protected void LinkButton1_Click(object sender, EventArgs e)

{

con = new SqlConnection("Data Source=.\\SQLEXPRESS;Initial

Catalog=feedback;Integrated Security=True");
[Link]();
s = "select * from subjectfeedback";
cmd = new SqlCommand(s, con);
SqlDataAdapter da = new SqlDataAdapter(cmd);
DataTable dt = new DataTable();
ds = new DataSet();
[Link](ds);
[Link] = ds;
[Link]();
[Link]();
}
protected void LinkButton4_Click(object sender, EventArgs e)
{
con = new SqlConnection("Data Source=.\\SQLEXPRESS;Initial
Catalog=feedback;Integrated Security=True");
[Link]();
s = "select * from ";
cmd = new SqlCommand(s, con);
SqlDataAdapter da = new SqlDataAdapter(cmd);
DataTable dt = new DataTable();
ds = new DataSet();
[Link](ds);
[Link] = ds;
[Link]();
[Link]();
}
protected void LinkButton2_Click(object sender, EventArgs e)
{
con = new SqlConnection("Data Source=.\\SQLEXPRESS;Initial
Catalog=feedback;Integrated Security=True");
[Link]();
s = "select * from practicalfeedback";
cmd = new SqlCommand(s, con);
SqlDataAdapter da = new SqlDataAdapter(cmd);
DataTable dt = new DataTable();
ds = new DataSet();
[Link](ds);
[Link] = ds;
[Link]();
[Link]();
}
protected void LinkButton3_Click(object sender, EventArgs e)
{
con = new SqlConnection("Data Source=.\\SQLEXPRESS;Initial
Catalog=feedback;Integrated Security=True");
[Link]();
s = "select * from ";
cmd = new SqlCommand(s, con);
SqlDataAdapter da = new SqlDataAdapter(cmd);
DataTable dt = new DataTable();
ds = new DataSet();
[Link](ds);
[Link] = ds;
[Link]();
[Link]();
}
protected void LinkButton5_Click(object sender, EventArgs e)
{
con = new SqlConnection("Data Source=.\\SQLEXPRESS;Initial
Catalog=feedback;Integrated Security=True");
[Link]();
s = "select * from ";
cmd = new SqlCommand(s, con);
SqlDataAdapter da = new SqlDataAdapter(cmd);
DataTable dt = new DataTable();
ds = new DataSet();
[Link](ds);
[Link] = ds;
[Link]();
[Link]();
}
protected void LinkButton6_Click(object sender, EventArgs e)
{
[Link]("[Link]");
}
}
Category

using System;
using [Link];
using [Link];
using [Link];
using [Link];
using [Link];
using [Link];
using [Link];
using [Link];
public partial class category : [Link]
{
SqlConnection con;
SqlCommand cmd;
string s;
protected void Page_Load(object sender, EventArgs e)
{
}
protected void DropDownList1_SelectedIndexChanged(object sender, EventArgs e)
{
}
protected void Button1_Click(object sender, EventArgs e)
{
con = new SqlConnection("Data Source=.\\SQLEXPRESS;Initial
Catalog=feedback;Integrated Security=True");
[Link]();
s = "insert into menu values('" + [Link] + "','" +
[Link] + "','" + [Link] + "','" +
[Link] + "','" + [Link] + "','" +
[Link] + "','" + [Link] + "','" +
[Link] + "','" + [Link] + "')";
cmd = new SqlCommand(s, con);
[Link]();
[Link]();
}
protected void Button2_Click(object sender, EventArgs e)
{
[Link]("[Link]");
}
}

Continuous study:

using System;
using [Link];
using [Link];
using [Link];
using [Link];
using [Link];
using [Link];
using [Link];
public partial class continuing : [Link]
{
SqlConnection con;
SqlCommand cmd;
string s;
protected void Page_Load(object sender, EventArgs e)
{
}
 protected void CheckBox1_CheckedChanged(object sender, EventArgs e)
{
}
protected void Button1_Click(object sender, EventArgs e)
{
con = new SqlConnection("Data Source=.\\SQLEXPRESS;Initial
Catalog=feedback;Integrated Security=True");
[Link]();
s = "insert into student values('" + [Link] + "','" + [Link] +
"',)";
cmd = new SqlCommand(s, con);
[Link]();
[Link]();
}
}
Hod handle:

using System;
using [Link];
using [Link];
using [Link];
using [Link];
using [Link];
using [Link];
using [Link];
using [Link];
public partial class hodhandle : [Link]
{
SqlConnection con;
SqlCommand cmd;
string s;
MailMessage ms;
protected void Page_Load(object sender, EventArgs e)
{
}
protected void Button1_Click2(object sender, EventArgs e)
{
[Link]("[Link]");
}
protected void SqlDataSource1_Selecting(object sender,
SqlDataSourceSelectingEventArgs e)
{
}
protected void Button3_Click(object sender, EventArgs e)
{
}
protected void Button1_Click(object sender, EventArgs e)
{
con = new SqlConnection("Data Source=.\\SQLEXPRESS;Initial
Catalog=feedback;Integrated Security=True");
[Link]();
s = "insert into menu values('" + [Link] + "','" +
[Link] + "','" + [Link] + "','" +
[Link] + "','" + [Link] + "','" +
[Link] + "','" + [Link] + "','" +
[Link] + "','" + [Link] + "')";
 cmd = new SqlCommand(s, con);
[Link]();
[Link]();
}
protected void Button2_Click(object sender, EventArgs e)
{

}
protected void LinkButton1_Click(object sender, EventArgs e)
{
[Link]("[Link]");
}
}

Hod login:
using System;
using [Link];
using [Link];
using [Link];
using [Link];
using [Link];
using [Link];
using [Link];
using [Link];

public partial class hodlogin : [Link]

{
SqlConnection con;
SqlCommand cmd;
string s;
protected void Page_Load(object sender, EventArgs e)
{

}
protected void Button2_Click(object sender, EventArgs e)
{
[Link] = "";
[Link] = "";
[Link]("[Link]");
}
protected void Button1_Click(object sender, EventArgs e)
{
if ([Link] == "" && [Link] == "")
{
[Link]("[Link]");
}

}
}
Principal login:
using System;
using [Link];
using [Link];
using [Link];
using [Link];
using [Link];
using [Link];
using [Link];
using [Link];
using [Link];
using [Link];
using [Link];

public partial class principal : [Link]

{
protected void Page_Load(object sender, EventArgs e)
{

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

if ([Link]=="Admin" && [Link]=="Admin")

{
[Link]("[Link]");
}
else
{
[Link]("Invalid Username And Password");
}

}
}
Student login :
using System;
using [Link];
using [Link];
using [Link];
using [Link];
using [Link];
using [Link];
using [Link];
using [Link];

public partial class student_login : [Link]

{
SqlConnection con;
SqlCommand cmd;
string s;
SqlDataAdapter da;
SqlDataReader dr;
SqlDataSource ds;
DataTable dt;

protected void Page_Load(object sender, EventArgs e)

{

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

if ([Link] == "" && [Link] == "")

{
[Link]("sudent [Link]");
}
}

protected void Button2_Click(object sender, EventArgs e)

{
[Link] = "";
[Link] = "";
[Link]("[Link]");
}
}

Theory details:
using System;
using [Link];
using [Link];
using [Link];
using [Link];
using [Link];
using [Link];
using [Link];

public partial class theory : [Link]

{
SqlConnection con;
SqlCommand cmd;
string s;
protected void Page_Load(object sender, EventArgs e)
{

}
protected void Button1_Click(object sender, EventArgs e)
{
con = new SqlConnection("Data Source=.\\SQLEXPRESS;Initial
Catalog=feedback;Integrated Security=True");
[Link]();
s = "insert into student values('" + [Link] + "','" + [Link] +
"','" + [Link] + "','" + [Link] + "','"
+ [Link] + "','" + [Link] + "','" +
[Link] + "','" + [Link] + "','" +
[Link] + "','" + [Link] + "','" +
[Link] + "','" + [Link] + "','" +
[Link] + "','" + [Link] + "')";
cmd = new SqlCommand(s, con);
[Link]();
[Link]();
}
protected void LinkButton1_Click(object sender, EventArgs e)
{
[Link]("[Link]");
}
}

Reports view :
using System;
using [Link];
using [Link];
using [Link];
using [Link];
using [Link];
using [Link];
using [Link];

public partial class view : [Link]

{
SqlConnection con;
SqlCommand cmd;
string s;
SqlDataAdapter da;
DataTable dt;
DataSet ds;
protected void Page_Load(object sender, EventArgs e)
{

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

}
protected void Button1_Click(object sender, EventArgs e)
{
con = new SqlConnection("Data Source=.\\SQLEXPRESS;Initial
Catalog=feedback;Integrated Security=True");
[Link]();
s = "select * from hodhandle";
cmd = new SqlCommand(s, con);
SqlDataAdapter da = new SqlDataAdapter(cmd);
DataTable dt = new DataTable();
ds = new DataSet();
[Link](ds);
[Link] = ds;
[Link]();
[Link]();
}
}
Student menu:
using System;
using [Link];
using [Link];
using [Link];
using [Link];
using [Link];
using [Link];
using [Link];
using [Link];
public partial class weakstudents : [Link]
{
SqlConnection con;
SqlCommand cmd;
string s;
protected void Page_Load(object sender, EventArgs e)
{

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

}
protected void Button1_Click(object sender, EventArgs e)
{
con = new SqlConnection("Data Source=.\\SQLEXPRESS;Initial
Catalog=feedback;Integrated Security=True");
[Link]();
s = "insert into practicalfeedback values('" + [Link] + "','" +
[Link] + "','" + [Link] + "','" +
[Link] + "','" + [Link] + "','" +
[Link] + "','" + [Link] + "','" +
[Link] + "','" + [Link] + "','" +
[Link] + "')";
cmd = new SqlCommand(s, con);
[Link]();
[Link]();
}
protected void Button2_Click(object sender, EventArgs e)
{
[Link]("[Link]");
}
}

CONCLUSION

The ​STUDENT FEEDBACK MANAGEMENT SYSTEM ​is developed using

[Link] fully meets the objectives of the system which it has been developed​. ​The system is
providing information as high level of efficiency associated with the system. The system solves
the problem. It was intended to solve as requirement specification. It is very useful to maintain
the details of the online students feedbac in best level. This system not only maintains the details
of the feedback. Thus this system maintains the time consumption and needs of students.

FUTURE ENHANCEMENT

The developed project has been sampled in different scenarios with the purpose of future
enhancement for further development of the product with improved utility for better outputs.
Future strategy for the adoption in India should consider the problems of monitoring students,
lack of highly sophisticated technical centers. ​In the future, we plan to improve the user interface
from the psychological standpoint and to increase the confidentiality and security.

REFERENCES

[1] J. Hatie, H. Timperley, "The power of feedback", J. Review of Educational Research,

87(1),pp. 81-112, 2007

[2] Shute, V.J.:” Focus on formative feedback”, Research Report, Retrieved January 15.
pdf.2007.

[3] E. Vasilyeva, M. Pechenizkiy, T. Gavrilova, S. Puuronen, "Personalization of Immediate

Feedback to Learning Styles", In: Proc. of 7th IEEE Int. Conf. on Advanced Learning
Technologies, pp. 622-624,2007.

[4] Vasilyeva E., Puuronen S., Pechenizkiy M., Rasanen P., "Feedback adaptation in web-based
learning systems", Special Issue of Int. J. of Continuing Engineering Education and Life-Long
Learning 17(4-5), pp. 337-357, 2007.

[5] S.R. Viola, S. Graf, Kinshuk, T. Leo "Analysis of Felder-Silverman Index of Learning Styles
by a Data-driven Statistical Approach", Proc. of the 8th IEEE Int. Symposium on Multimedia,
pp. 959-964, 2006.

[6] E. Vasilyeva, M. Pechenizkiy, S. Puuronen, "The Challenge of Personalization of Feedback

to Learning Styles in Web-based Learning Systems", Proc. of AWELS Workshop at IEEE
ICALT 2006 Conf, pp. 1143-1144,2006.

[7] Mory, E. H. "Feedback research review". In Jonassen, D. (eds.) Handbook of research on

educational communications and technology, Erlbaum Associates, pp. 745-783, 2004.

[8] Sondergaard H. & Thomas D., “Effective feedback to small & large classes”, 34 th
ASEE/IEEE Frontiers in education conference, 2004.

[9] N. Bajraktarevic, W. Hall, & P. Fullick, "Incorporating learning styles in hypermedia

environment: Empirical evaluation". In Proc. of Workshop on Adaptive Hypermedia and
Adaptive WBSs, Nottingham, pp. 41-52, 2003.