PROJECT REPORT ON QUERY ON DEMAND

Submitted as a part of course curriculum for the degree Of Bachelor of Technology In Information Technology (Session: 2009-2013)

Submitted to: Er. Shobhit Gupta Asst. Professor, IT department

Submitted by: Akarsh Kathpalia Roll No. 2909627

Department of Information Technology

KURUKSHETRA INSTITUTE OF TECHNOLOGY & MANAGEMENT Kurukshetra

ACKNOWLEDGEMENT
The satisfaction that accompanies the successful completion of any task would be incomplete without mentioning the people who made it possible and whose constant guidance and encouragement crown all the effort with success. First and foremost, I Akarsh Kathpalia deem it my foremost duty to express our sincere gratitude to our supervisor Ms Astha. I am thankful to her for providing the right direction for the conduct of the dissertation and also for her keen interest, methodological approach, and timely suggestions and faith in me. I feel privileged to have carried out this report under her able guidance. I am also thankful to Dr. P.J. George , the Director principle of Kurukshetra Institute of Technology & Management, Kurukshetra. I am glad to Dr. Rajesh Verma, Head CSE/IT for proper guidance regarding training. I acknowledge continous guidance and incessant rendered by Er. Sunil Saini not only for this project but also for overall development. Without any dilution, I would also like to thank all the staff members of the IT Department since their co-operation and help to arrange the entire necessary infrastructure for the carrying out the project was invaluable. Last but not the least, I offer my deepest gratefulness and thus owe a large amount of credit for this success to our respected parents, brother and sister for being our support throughout the ups and downs, sharing the most precious bond of love and affection, we have ever known in this life.

AKARSH KATHPALIA

CANDIDATES DECLARATION
I hereby declare that the project work which entitiled QUERY ON DEMAND in Partial fulfillment the requirement for the award of the course curriculum of Bachelor of Degree with specification in INFORMATION TECHNOLOGY , submitted in the Department of, Computer Enginnering Kurukshetra Institute of Technology & Management, Kurukshetra is an authentic record of my own original work carried out my Training period , under the guidance and supervision of Ms Aastha,CMC limited

Place: DELHI

AKARSH KATHPALIA

CONTENTS
Acknowledgement Candidate Declaration

Company TITLE

Certificate PAGE NO.

6 7 8,9,10

Chapter 1: Introduction to Project Chapter 2: Features of Project Chapter 3: Sections And modules of project

Chapter 4: Platform/Technology Used Chapter 5: Hardware & Software Requirements Chapter 6: Data Flow Diagrams Chapter 7: Snapshots Chapter 8: Advantages of Project Chapter 9: Limitations of Project Chapter 10: Scope of Project Chapter 11: Conclusion References

11-25 26 27,28,29 30-40 41 42 43 44 45

Chapter 1: Introduction to Project

QUERY ON DEMAND:Query on demand is a question and answers site that allows students to submit questions to be answered by expert. Query On Demand is basically the platform between student and Experts. It serves the all the possible queries of the students, who have enrolled themselves and answer provides by the experts. Expert Section:There is expert login where the expert will login to enter his section of page. The expert username and password will be given by the site owner to whom he feel trustworthy. At his page the expert will be able to se various queries presented by students to answered. He can wish to answer any query he feels to answer. Student Section:A student is allowed to create profile to administer his login. After creating the profile an enrolment no. will be auto generated by the system. Hence the student will login to his page where he can update his profile, change his password, submit queries, view queries and can logout

Keypoints:-.
-

The front end is C# with Asp.net and backend is SQL server. When either user will logout he will be requested to directed to login page. More information can be checked out with the help of various given links.

Hence, I have readily tried to accomplish this project with the respective language I have dealt with named ASP.NET

Chapter 2: Features of Project

The project Query On Demand implemented through Asp.Net technique has the following features with respect to what all has been fixed in it or facilitated with it: Providing user friendly interface To get all the information regarding queries Easy access of data Easy maintenance Maintaining data consistency Providing better performance Increasing the efficiency through automation Adequate validation checks for data entry Facility to update the data time to time Adequate security of the database

Chapter 3: Sections And modules of project

Login Panel:It corresponds to the login page where This page contain following field:Expert & Student Login:Here the expert and student can sign in by entering the expert id/enrolment no. and password authentication is to be provided. Only authenticated person will enter the next page via login page.

Expert id:The expert id is provided by the site owner, to whomever he wish trustworthy. As the expert id will be entered it will get match with the username in the database then only that username will be taken by the expert page to go into the next page which is match by the username in the database. Enrolment No.:Here different students who feel to have queries to be sorted out can sign in to their respective page, where they can update their profile, change password, view query and submit query. A Student will fill his enrolment no given to him at the time of creating his profile, the enrolment will match with the database then only the student can login. Password:For very expert id and enrolment no. there is password to verify his presence and so the login must be secured, it will contain password to login to the either page(Student/expert). The password will be saved in the database. And whenever the 8

password will be entered only that password will be used by the login page to go further. There should be use of the spaces and the special characters in the password so that the hacker will not be able to crack the password otherwise it will prove very costly to the company Login button:-

It will be used submit the username and the password to the database to login to the
repective page. By clicking on to the submit button, if the username and password will be matched by the data on to the database then the repective page will be open, otherwise the next page will not be open and user will remain on that page

Create Profile:A new student can create his respective page by signing up through create profile. This helps to unite various students on a single platform.

Database Design:This module is related with identification of tables that is to be used in the project. There are 3 tables used that are Expert_profile, Student_profile, Student_Query. Tables that are used in database for storing different type of data about whole website are shown as follows:-

Expert Profile:-

Student Profile:-

Student Query:-

10

Chapter 4: Platform/Technology Used

Introduction the .NET Platform:
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, 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 guarantees safe execution of code, including code created by an unknown or semi-trusted third party. 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.

11

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. The runtime as an agent that manages code at execution time, providing core services such as memory management, thread management, and remoting, 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 user

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

12

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. The runtime also enforces code robustness by implementing a strict type- and codeverification 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. 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 localityof-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

13

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 objecting 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. 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. Scripted or hosted applications. Windows GUI applications (Windows Forms). ASP.NET applications. 14

XML Web services. Windows services.

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

Compiling to MSIL
When compiling to managed code, the compiler translates your source code into Microsoft intermediate language (MSIL), which is a CPU-independent set of instructions that can be efficiently converted to native code. MSIL includes instructions for loading, storing, initializing, and calling methods on objects, as well as instructions for arithmetic and logical operations, control flow, direct memory access, exception handling, and other operations. Before code can be executed, MSIL must be converted to CPU-specific code, usually by a just-in-time (JIT) compiler. Because the common language runtime supplies one or more JIT compilers for each computer architecture it supports, the same set of MSIL can be JIT-compiled and executed on any supported architecture. When a compiler produces MSIL, it also produces metadata. Metadata describes the types in your code, including the definition of each type, the signatures of each type's members, the members that your code references, and other data that the runtime uses at execution time. The MSIL and metadata are contained in a portable executable (PE) file that is based on and extends the published Microsoft PE and Common Object File Format (COFF) used historically for executable content. This file format, which accommodates MSIL or native code as well as metadata, enables the operating system to recognize common language runtime images. The presence of metadata in the file along with the MSIL enables your code to describe itself, which means that there is no need for type

15

libraries or Interface Definition Language (IDL). The runtime locates and extracts the metadata from the file as needed during execution.

Assemblies Overview
Assemblies are a fundamental part of programming with the .NET Framework. An assembly performs the following functions: It contains code that the common language runtime executes. Microsoft intermediate language (MSIL) code in a portable executable (PE) file will not be executed if it does not have an associated assembly manifest. Note that each assembly can have only one entry point (that is, DllMain, Win Main) It forms a security boundary. An assembly is the unit at which permissions are requested and granted. For more information about security boundaries as they apply to assemblies. It forms a type boundary. Every type's identity includes the name of the assembly in which it resides. A type called MyType loaded in the scope of one assembly is not the same as a type called MyType loaded in the scope of another assembly. It forms a reference scope boundary. The assembly's manifest contains assembly metadata that is used for resolving types and satisfying resource requests. It specifies the types and resources that are exposed outside the assembly. The manifest also enumerates other assemblies on which it depends.

16

Meta data Overview:

Metadata is binary information describing your program that is stored either in a common language runtime portable executable (PE) file or in memory. When you compile your code into a PE file, metadata is inserted into one portion of the file, while your code is converted to Microsoft intermediate language (MSIL) and inserted into another portion of the file. Every type and member defined and referenced in a module or assembly is described within metadata. When code is executed, the runtime loads metadata into memory and references it to discover information about your code's classes, members, inheritance, and so on.

Metadata describes every type and member defined in your code in a language-neutral fashion. Metadata stores the following information: Description of the assembly. Identity (name, version, culture, public key). The types that are exported. Other assemblies that this assembly depends on. Security permissions needed to run. Description of types. Name, visibility, base class, and interfaces implemented. 17

Members (methods, fields, properties, events, nested types). Attributes

Garbage Collection
The .NET Framework's garbage collector manages the allocation and release of memory for your application. Each time you use the new operator to create an object, the runtime allocates memory for the object from the managed heap. As long as address space is available in the managed heap, the runtime continues to allocate space for new objects. However, memory is not infinite. Eventually the garbage collector must perform a collection in order to free some memory. The garbage collector's optimizing engine determines the best time to perform a collection, based upon the allocations being made. When the garbage collector performs a collection, it checks for objects in the managed heap that are no longer being used by the application and performs the necessary operations to reclaim their memory.

Introduction to C# :C# is a multi-paradigm programming language encompassing imperative, declarative, functional, generic, object-oriented (class-based), and component-oriented programming disciplines. It was developed by Microsoft within the .NET initiative and later approved

18

as a standard by Ecma (ECMA-334) and ISO (ISO/IEC 23270). C# is one of the programming languages designed for the Common Language Infrastructure. C# is intended to be a simple, modern, general-purpose, object-oriented programming language. Its development team is led by Anders Hejlsberg. The most recent version is C# 4.0, which was released on April 12, 2010

Versions of c# :In the course of its development, the C# language has gone through several versions: Language specification ECMA ISO/IEC Microsoft January 2002 December 2002 C# 1.2 September 2006 April 2003 October 2003 April 2003 September 2005[note 1] August 2007 None C# 4.0 April 2010 November 2005 November 2007 April 2010 .NET Framework 1.1 .NET .NET Framework .NET Framework 1.0

Version

Date January 2002

Visual Studio Visual Studio 2002 Visual Studio .NET 2003 Visual Studio .NET

C# 1.0

C# 2.0 C# 3.0

June 2006

Framework 2.0 2005 .NET Visual Studio Framework 3.5 2008 .NET Visual Studio Framework 4 2010

C# is the programming language that most directly reflects the underlying Common language Infrastructure (CLI). Most of its intrinsic types correspond to value-types 19

implemented by the CLI framework. However, the language specification does not state the code generation requirements of the compiler: that is, it does not state that a C# compiler must target a Common Language Runtime, or generate Common Intermediate Language (CIL), or generate any other specific format. Theoretically, a C# compiler could generate machine code like traditional compilers of C++ or FORTRAN.

Some notable distinguishing features of C# are:

There are no global variables or functions. All methods and members must be declared within classes. Static members of public classes can substitute for global variables and functions. Local variables cannot shadow variables of the enclosing block, unlike C and C+ +. Variable shadowing is often considered confusing by C++ texts. C# supports a strict Boolean data type, bool. Statements that take conditions, such as while and if, require an expression of a type that implements the true operator, such as the Boolean type. While C++ also has a Boolean type, it can be freely converted to and from integers, and expressions such as if(a) require only that a is convertible to bool, allowing a to be an int, or a pointer. C# disallows this "integer meaning true or false" approach on the grounds that forcing programmers to use expressions that return exactly bool can prevent certain types of common programming mistakes in C or C++ such as if (a = b) (use of assignment = instead of equality ==). In C#, memory address pointers can only be used within blocks specifically marked as unsafe, and programs with unsafe code need appropriate permissions to run. Most object access is done through safe object references, which always either point to a "live" object or have the well-defined null value; it is impossible to obtain a reference to a "dead" object (one which has been garbage collected), or to a random block of memory. An unsafe pointer can point to an instance of a value-type, array, string, or a block of memory allocated on a stack. Code that is

20

not marked as unsafe can still store and manipulate pointers through the System.IntPtr type, but it cannot dereference them.

Managed memory cannot be explicitly freed; instead, it is automatically garbage collected. Garbage collection addresses the problem of memory leaks by freeing the programmer of responsibility for releasing memory which is no longer needed. In addition to the try...catch construct to handle exceptions, C# has a try...finally construct to guarantee execution of the code in the finally block. Multiple inheritance is not supported, although a class can implement any number of interfaces. This was a design decision by the language's lead architect to avoid complication and simplify architectural requirements throughout CLI. C# is more type safe than C++. The only implicit conversions by default are those which are considered safe, such as widening of integers. This is enforced at compile-time, during JIT, and, in some cases, at runtime. There are no implicit conversions between Booleans and integers, nor between enumeration members and integers (except for literal 0, which can be implicitly converted to any enumerated type). Any user-defined conversion must be explicitly marked as explicit or implicit, unlike C++ copy constructors and conversion operators, which are both implicit by default. Enumeration members are placed in their own scope. C# provides properties as syntactic sugar for a common pattern in which a pair of methods, accessor (getter) and mutator (setter) encapsulate operations on a single attribute of a class. Full type reflection and discovery is available. C# currently (as of version 4.0) has 77 reserved words.

Data Provider - ADO.NET

We know that ADO.NET allows us to interact with different types of data sources and different types of databases. However, there isn't a single set of classes that allow you to accomplish this universally. Since different data sources expose different protocols, we 21

need a way to communicate with the right data source using the right protocol. Some older data sources use the ODBC protocol, many newer data sources use the OleDb protocol, and there are more data sources every day that allow you to communicate with them directly through .NET ADO.NET class libraries. ADO.NET provides a relatively common way to interact with data sources, but comes in different sets of libraries for each way you can talk to a data source.

Deploying ASP.NET
After creating and testing your ASP.NET application, the next step is to deploy the application. Deployment is the process of distributing the finished application to be installed on other computer. We can use the built-in deployment feature that comes with Visual studio .NET to create a Windows Installer file - a .msi file for the purpose of deploying applications.

Deploying Applications
To start, open the Web Application project you want to deploy. Say, you have a project named "Deploy" with ten Web pages in it. Select File->Add Project->New Project from the main menu. From the Project Types pane select Setup and Deployment Projects and from the Templates pane select Web Setup Project. Type WebSetup1 for name and specify a location in the location box and click OK. When you click OK on the above dialogue box, the project is added to the solution explorer window and also a File System Editor window appears as shown in the image below. The File System Editor window has two panes. Select Web Application Folder in the left pane in this window. From the Action menu (on main menu), select Project Output to open the Add Project Output Group dialog boxMake sure that Deploy is selected in the Project drop-down list and select Primary Output from the list and click OK. You also can select other options depending upon the users of your application. Now, in the File System Editor window, select Web Application Folder and open it's Properties window. In this window, set the VirtualDirectory property to any name, say FinishedApp. FinshedApp will be the folder on the target machine where you will install this application. The name you set for this VirtualDirectory property should not already 22

exist on the target machine. If it does, the contents in the folder will be overwritten. Also, set the DefaultDocument property to any page in the application. The page you set in this property will be the default page for the Web Application. Once you are finished with the Properties window build the solution by selecting Build->Build WebSetup1 from the main menu. After the solution is built sucessfully, a WebSetup1.msi file is created in the Debug directory of the Web Setup project. The default path to the debug directory is as follows: C:\Documents and Settings\Administrator\MyDocuments\Visual Studio Projects\deploy\WebSetup1\Debug

XML Web Services

A Web Service (XML Web Service) is a unit of code that can be activated using HTTP requests. Stated another way, a Web Service is an application component that can be remotely callable using standard Internet Protocols such as HTTP and XML. One more definition can be, a Web Service is a programmable URL. Web Services came into existence to deliver distributed computing over the Internet. A major advantage of the Web services architecture is, it allows programs written in different languages on different platforms to communicate with each other in a standards-based way. Simply said, a Web service is a software service exposed on the Web through SOAP, described with a WSDL file and registered in UDDI.

Foundational elements of Web Services

The .NET Framework provides an excellent foundation for building and consuming Web Services. A key to the broad-reach capabilities of these Web Services is a foundation built on Internet Standards that does not rely on any platform, protocol or OS. This foundation provides the following capabilities to Web Services: (i) A standard method for describing data (ii)A standard message format for communicating request and response (iii)A standard method for describing the capabilities of Web Services (iv)A method to discover what Web Services are available at any site (v)A method to describe what sites provide Web Services

23

Microsoft SQL Server:

Microsoft SQL Server is a relational database server, developed by Microsoft: It is a software product whose primary function is to store and retrieve data as requested by other software applications, be it those on the same computer or those running on another computer across a network (including the Internet). There are at least a dozen different editions of Microsoft SQL Server aimed at different audiences and for different workloads (ranging from small applications that store and retrieve data on the same computer, to millions of users and computers that access huge amounts of data from the Internet at the same time). True to its namesake, Microsoft SQL Server's primary query languages are TSQL and ANSI SQL.

SQL Server 2008

The next version of SQL Server, SQL Server 2008, was released (RTM) on August 6, 2008 and aims to make data management self-tuning, self organizing, and self maintaining with the development of SQL Server Always On technologies, to provide near-zero downtime. SQL Server 2008 also includes support for structured and semistructured data, including digital media formats for pictures, audio, video and other multimedia data. In current versions, such multimedia data can be stored as BLOBs (binary large objects), but they are generic bitstreams. Intrinsic awareness of multimedia data will allow specialized functions to be performed on them. According to Paul Flessner, senior Vice President, Server Applications,Microsoft Corp., SQL Server 2008 can be a data storage backend for different varieties of data: XML, email, time/calendar, file, document, spatial, etc. as well as perform search, query, analysis, sharing, and synchronization across all data types. Other new data types include specialized date and time types and a Spatial data type for location-dependent data Better support for unstructured and semi-structured data is provided using the new FILESTREAM data type, which can be used to reference any 24

file stored on the file system Structured data and metadata about the file is stored in SQL Server database, whereas the unstructured component is stored in the file system. Such files can be accessed both via Win32 file handling APIs as well as via SQL Server using T-SQL; doing the latter accesses the file data as a BLOB. Backing up and restoring the database backs up or restores the referenced files as well. SQL Server 2008 also natively supports hierarchical data, and includes T-SQL constructs to directly deal with them, without using recursive queries. The Full-Text Search functionality has been integrated with the database engine. According to a Microsoft technical article, this simplifies management and improves performance. Spatial data will be stored in two types. A "Flat Earth" (GEOMETRY or planar) data type represents geospatial data which has been projected from its native, spherical, coordinate system into a plane. A "Round Earth" data type (GEOGRAPHY) uses an ellipsoidal model in which the Earth is defined as a single continuous entity which does not suffer from the singularities such as the international dateline, poles, or map projection zone "edges". Approximately 70 methods are available to represent spatial operations for the Open Geospatial Consortium Simple Features for SQL, Version 1.1. SQL Server includes better compression features, which also helps in improving scalability. It enhanced the indexing algorithms and introduced the notion of filtered indexes. It also includes Resource Governor that allows reserving resources for certain users or workflows. It also includes capabilities for transparent encryption of data (TDE) as well as compression of backups. SQL Server 2008 supports the ADO.NET Entity Framework and the reporting tools, replication, and data definition will be built around the Entity Data Model. SQL Server Reporting Services will gain charting capabilities from the integration of the data visualization products from Dundas Data Visualization, Inc., which was acquired by Microsoft. On the management side, SQL Server 2008 includes the Declarative Management Framework which allows configuring policies and constraints, on the entire database or certain tables, declaratively. The version of SQL Server Management Studio included with SQL Server 2008 supports IntelliSense for

25

SQL queries against a SQL Server 2008 Database Engine. SQL Server 2008 also makes the databases available via Windows PowerShell providers and management .

Chapter 5 : Software And Hardware Requirements

Software Interfaces
Following software are required for developing OLSE application: i) Operating System: ii) Platform: iii) Environment: v) RDBMS: Windows NT, 2000, XP Prof,Windows7 . ASP.NET, C#. VisualStudio.NET 2.0. SqlServer2005

Hardware Interfaces
It's a webbased project, so a robust hardware configuration is required. The hardware requirements are: i) Processor iii) RAM iv)Hard Disk : : : Intel(R) Pentium(R) Dual CPU Intel 1 GB minimum 2.5 GB for visual studio.net and 2.5GB for SQL server 2008

ii) Motherboard:

26

Chapter 6: Data Flow Diagrams

Login Data Flow:-

27

Student Query Flow:-

28

Flow Of Query:-

29

Chapter 7: Snapshots
Login Page:-

This is the main login page, where an expert and student can login also a new student can create his profile. Further if he need some more information regarding the query he check out various given links.

30

Expert Page:-

This is the account of expert. The Expert username and password is known and own by the site owner. He can pass these to whomsoever he feels trustworthy.

Here the the expert gets the list of various queries submitted by students. He can answer whichever query he feels like.

31

Create Profile Page:-

This is a a create profile page. If a user/student is new to the website he has to create his account by filling up the details. All the details have validation. When the profile of the student is created an enrolment no is autogenerated by the system, which is his username.

32

Student Page:-

33

This is the account of student where he can, as you can see the snapshot, update his profile, change his password, submit his query, view his previous queries and can logout.

Submit Query Page:-

34

Here the user will submit his query by filling up the details for subject, topic and the query.

View Query Page:-

35

The student can review his query after submission for any purpose.

Logout:36

When student clicks on the logout, he is directed to this page where he can further be directed to Login Page.

Submit Answer Page:37

Here the expert will answer the queries

Change Password Page:38

Here the student can change his password.

Update Profile Page:39

Here Student can update his profile by filling up extra details.

Validation Controls:40

The snapshots here show that validation controls are being used.

Chapter 8: Advantages Of Project -

Easy to use 41

Timesharing in getting information Data is secured. Serves all possible queries. The best platform for students and experts. helps in real time projecting. Providing a specific expert that can help in avoiding the leakage of information.

42

Chapter 9: Limitation of Project

This website is developed in Visual Studio 2010, and sql server 2008. When the website is to be transferred from one system to another system, it creates some problem of database, means database has to be executed on that system separately. Only admin can add new clients. If some third party want to join, they have to contact the admin or the agency.

43

Chapter 10: Scope of the project

The project Query On Demand is a website that can be launched by any consultancy agency. This website is very useful for the leading companies which provide consulting services. In this website every data is stored electronically so no paper work is required and information can be retrieved very easily and efficiently without any problem.

44

Chapter 11: Conclusion

From this project we can conclude that this is a good website that is developed for any business consultancy agency. It can be easily used and implemented in any consultancy agency. This website can be easily managed by single administrator. So one can say that this project can be easily used in any consultancy services agency and efficiently.

45

References
1. 2. 3. 4. 5. A press Beginning C# C# Schools www.google.com www.dotnetspider.com www.w3cschools.com

46