Essay Writing

• Essay Writing Services
• Essay Prices
• Order Your Essay
• Order Essay Marking
• Essay Marking
• Free Example Essays

Resources

• Essay Scam Warning
• Plagiarism Scanner
• Essay Writers
• Get Verified

SERVICE ORIENTED computing

1.1 Aim of the Project

SERVICE ORIENTED computing (SOC) is designing distributed applications. SOC applications are obtained by suitably composing and coordinating available services. Services are impartial computational units. These services are distributed over a network. These services are obtained with the standard interaction mechanisms. We know that implementing transactions are the complex interaction pattern, so to handle these types of complex interaction patterns while nonfunctional requirements on the system behavior, composition of services may require peculiar mechanisms. For example, security, availability, performance, transactional, quality of service, etc are nonfunctional requirements. Our goal is to adopt the formal techniques for modeling, designing, and verifying SOC applications. So we should propose a SOC modeling framework, this SOC modeling framework supports history based security and call by contract.

The execution of program access security critical resources and these actions are logged into histories. We have the security mechanisms, these security mechanisms inspects these histories and also bans the execution that would violate the prescribed policies. Service composition can also depends on how those services that match the user's requirements and also depends on runtime behavior. Security makes service composition harder. Different providers' offers services and these different providers partially trust each other. In this system Providers should guarantee that the delivered service respects a given security policy. On the other hand, clients want to protect their sensitive data from the invoked services.

1.2 Scope of the project

Where both the parties trust each other partially we need to create new services and selling these services by a package base through a secured media.

1.3 Objectives

1. Design and as well as compose the services in a secured manner.
2. We need to model a system for the secure designing Using UML like graphical language.
3. Service Oriented Computing (SOC) applications are obtained by composing and coordinating available services.
4. The Software Engineering is used to facilitate the nature of the system for functional and non functional requirements by using Service Oriented Application as a framework.
5. We need to protect the sensitive data for the clients.
6. Based on service behavior, the call by contract selection mechanism implements a matchmaking algorithm.

1.4 Methodology

In proposed system, we introduced a UML like graphical language for designing and verifying the security policies of service oriented applications. And we have another feature, this feature is offered by SOC application framework and the feature is that mapping high level service descriptions into more concrete programs. With the help of simple model transformation tools we can do mapping. Here we are going to introduce a framework which is called Service Component Architecture (SCA). This Architecture is used to implement business logic while complying with existing standards. This implementation is done by allowing designers. Our approach is that providing a full fledged mathematical framework for designing and verifying properties of service. So it would be interesting to develop a (model transformation) mapping from our formal framework to SCA.

2. PROJECT DESCRIPTION

2.1 Modules

We have 4 modules in this project. They are

1. New User & Login
2. Admin
3. Service
4. User

New User and Login

Existing users can enter to site by their login information. Existing users need to provide sufficient username and password. This login information provides security authentication. And new users can create new account to use the site by giving their identity information.

Admin

Admin have the full control on the site, he can view the activities of users. Main role of the admin is to create and manage services. He should give the physical path and service package for the particular service.

Service

Service module is handling by admin. This module is the heart of website, because all the services are managed by this module. Here, admin should mention Service ID, Service Description, Path, Provider and Package.

User

In this module, user can login to their space. He can view personal information, and all the services. User can select any of the services and service package which are accessible to him.

3. SYSTEM STUDY

3.1 FEASIBLITY STUDY

A Feasibility Study is a process which defines exactly what a project is and what strategic issues need to be considered to assess its succeeding. In this phase, feasibility of the project is analyzed. In this feasibility study, business proposal presents with a very general plan for the project and we can also study the some cost estimates. The feasibility study of the proposed system is to be carried out during system analysis. This should be ensuring that the proposed system is not a trouble to the company. We need to understand the major requirements for the system and it is essential for feasibility analysis.

Three key considerations involved in the feasibility analysis are

• ECONOMICAL FEASIBILITY
• TECHNICAL FEASIBILITY
• SOCIAL FEASIBILITY

ECONOMICAL FEASIBILITY:

This study is carried out to check how the economic impact that the system will have on the organization. With the economical feasibility the amount of fund that the company can pour into the research and development of the system is limited. The expenditures must be reasonable. Thus the developed system is within the budget because most of the technologies used are freely available. The main thing is that only the customized products have to be purchased.

TECHNICAL FEASIBILITY:

This study is carried out to check the technical feasibility, that is, the technical requirements of the system. Any system developed must not have a high demand on the technical resources which is available. This will lead to high demands on the technical resources which is available. This will show the way to high demands being placed on the client. The developed system must have a reserved requirement and only minimal or null changes are required for implementing this system.

SOCIAL FEASIBILITY:

This study is used to check the level of acceptance of the system by the user. This feasibility includes the process of training the user to use the system capably. The user must accept the system as a necessity; he must not to feel threatened by the system. Methods are used to educate the user about the system and these methods make him familiar with system. So finally we conclude that the level of acceptance of the system by the users depends on the methods. His level of confidence must be raised so that he is also able to make some constructive analysis.

3.2. EXISTING SYSTEM

3.3. PROPOSED SYSTEM

4. SYSTEM SPECIFICATION

4.1. HARDWARE CONFIGURATION

The hardware used for the development of the project is:

PROCESSOR   :   PENTIUM III 766 MHz

RAM   :   128 MD SD RAM

MONITOR   :   15" COLOR

HARD DISK   :   20 GB

FLOPPY DRIVE   :   1.44 MB

CDDRIVE   :   LG 52X

4.2. SOFTWARE CONFIGURATION

The software used for the development of the project is:

OPERATING SYSTEM : Windows 2000 Professional

ENVIRONMENT : Visual Studio .NET 2005

.NET FRAMEWORK : Version 2.0

LANGUAGE : VB.NET

WEB TECHNOLOGY : Active Server Pages.NET

WEB SERVER : Internet Information Server 5.0

BACK END : SQL SERVER 2000

REPORTS : Web Form Data Grid control

5 LANGUAGE SPECIFICATIONS

5.1 FEATURES OF VISUAL BASIC .NET

5.1.1. Overview of the .NET Framework:

The .NET Framework is a newest computing platform which simplifies application development in the highly distributed environment of the Internet. The .NET Framework has the following objectives:

• .NET offers a reliable object oriented programming atmosphere whether object code is saved and run locally or remotely.
• When object code is saved and operated locally or remotely .Net offers a compatible object oriented programming atmosphere.
• .NET provides a code execution environment. This code execution environment minimizes software deployment, versioning conflicts and safe execution of code. This code execution environment also eliminates the performance problems of scripted or interpreted environments.
• .NET allows the developer experience compatible through a greater varying kinds of applications such as Web based or Windows based application.

The .NET Framework has 2 main components.

• Common language runtime and
• .NET Framework class library.

The common language runtime is the platform of the .NET skeleton. Runtime acts as an instrument that operates the code at execution time. Runtime also provides basic services such as memory management, thread management, and remoting. Runtime guards safety and solidity because of code precision. The idea of code management is a basic principle of the run time. Managed code is the code that targets run time, while unmanaged code is the code that does not target the run time. The other main part of the .NET skeleton is a class library which is extensive. The class library possesses object oriented accumulation of recyclable kinds that you can utilize to develop applications. These applications vary from graphical user interface (GUI) applications to applications formed on the newest creations offered by ASP.NET, such as Web Forms and XML Web services.

Unmanaged components host the .NET framework so this loads the common language runtime into their processes and also initiate the execution of managed code, thereby creating a software environment that can utilize both managed and unmanaged features.

For example, to provide a scalable, server side environment for managed code ASP.NET hosts the runtime. ASP.NET can work directly with the runtime to allow Web Forms applications and XML Web services.

Above figure shows the relationship of the common language runtime and the class library

5.1.2. Common Language Runtime features:

These features are built in to the managed code which runs on the common language runtime.

Memory, execution of thread, code security verification, code execution, compilation, and other system services are managed by the common language runtime.

In this system, Depending on a quantity of variables managed parts are given different levels of reliability. The factors here are the internet, enterprise network or local computer. This means that a managed part may or may not be capable to carry out file access executions, registry entry functions or other susceptive operations. The runtime put into effect code access security. For example, users can hope that an Executable fixed in a Web page can run a movie on screen or play a song, but cannot enter into their file system, personal data or network. Therefore the safety feature of the runtime allows Internet deployed software to current affluence. The runtime also has code rigidity by utilizing code verification framework called the common type system (CTS). The CTS ensures that all code that is managed is also describing itself. There are number of Microsoft and third party language compilers creating managed code that is CTS compliant. Which means that managed code can utilize managed kinds and instances.

In addition, the managed environment of the runtime reduces many common software issues. For example, the runtime automatically knobs object layout and manages references to objects, then releasing them when they are no longer being used. This automatic memory management determines the two most common application errors; they are memory leaks and invalid memory references. The runtime also supports developer productivity. For example, programmers can also write applications in their development language of preference. Therefore it offers greater advantage of the runtime, the class library and parts written in different languages by different developers. Whichever compiler dealer who chooses to target the runtime can do so.

The runtime is developed to boost performance. Although the common language runtime offers various fundamental runtime services, never is the managed code transformed. An attribute called just in time (JIT) compiling makes it possible for all managed code to run in a local machine language of the system on which it is operating. On the other side, the memory manager eliminated the chances of fragmented memory and increases locality of reference to further boost performance.

Lastly, the runtime could be hosted by server side applications, high performance such as Microsoft SQL Server and Internet Information Services (IIS). This framework it makes viable for you to use managed code to create your business logic, while still relishing the bigger performance of the industry's top enterprise servers that carry runtime hosting

5.1.3. .NET Framework Class Library…:

The .NET skeleton class library is a bunch or recyclable kinds that firmly packed together with the common language runtime. The class library is object oriented, given that kinds from which your own managed code can create utility. This makes the .NET skeleton kinds simple to utilize and also diminish the time required for learning fresh features of the .NET skeleton. More over, third party components can combine correctly with classes in the .NET skeleton. Taking an example, the .NET skeleton collection branches operate a bunch of interfaces that you can utilize to create your own collection branches. Your collection branches will combine correctly with the branches in the .NET skeleton.

As you would anticipate for from an object oriented class library, the .NET skeleton kinds let you gain a spectrum of common programming tasks, comprising tasks such as data collection, database connectivity, string management and file entry. More over, to these basic tasks, the class library has kinds that uphold a number of purposeful development scenarios. You can use .NET, for example.

Framework to build up the following types of applications and services:

• Console applications.
• Scripted or hosted applications.
• Windows GUI applications (Windows Forms).
• ASP.NET applications.
• XML Web services.
• Windows services.

For example, the Windows Forms branches are a broad ranging group of recyclable kinds that greatly simplify Windows GUI creation. If an ASP.NET Web Form application is put in writing, you can use the Web Form branches.

5.1.4. Client Application Development:

Client applications resemble the older form of application in Windows based programming. These are the forms of application that show windows or forms on the desktop, allowing a user to operate a task. Client applications hold applications such as spreadsheets and word processors, as well as custom business application such as reporting tools, data entry tools and so on. Clients applications often use windows, buttons, menus and other GUI features, and they often get local resources peripherals such as printers and such as file system.

Other kind of client application is the proven ActiveX control disposed onto the Internet as a Webpage. This application is in a great way similar to other client applications: it is operated natively, also has entry to local resources, and it also has graphical features.

5.1.5. Server Application Development:

In the organized environment Server side applications are utilized through runtime hosts. Applications which are not managed hosts the common language runtime, which permits your custom managed code to control the performance of the server. This model offers you with all the features of the common language runtime and class library while achieving the performance and scalability of the host server.

Fundamental network representation with managed code running in different server atmospheres is illustrated in the following diagram. Servers such as IIS and SQL can operate standard functions while your application logic operates through managed code.

5.1.6. Server side managed code

ASP.NET is the hosting environment that allows developers to use the .NET Framework to aim Web based applications. On the other hand, ASP.NET is not just a runtime host; it is a total structural model for constructing Web sites and Internet provided objects with managed code. Both Web Forms and XML Web utilities make use of IIS and ASP.NET as the publishing function for applications, and jointly have a class of supporting groups in the .NET Framework.

XML Web services, an important development in Web based technology, these are distributed, server side application components related to common Web sites. On the other hand, differing from Web based applications, XML Web utility parts have no UI and are not targeted for browsers such as Internet Explorer and Netscape Navigator. as an alternative, XML Web services includes of recyclable software parts modeled to be used by other applications, such as conventional client applications, Web based applications. As a result, XML Web services technology is fast passing application development and deployment into the largely distributed atmosphere of the Internet.

The .NET Framework also offers a group of classes and tools to support in development and utilization of XML Web services applications. XML Web services are created on basis such as SOAP (a remote procedure call protocol), XML (an extensible data format), and WSDL (the Web Services Description Language). The .NET skeleton is developed on these standards to support interoperability with non Microsoft solutions.

5.1.7. Active Server Pages.NET

ASP.NET is a programming framework developed on the common language runtime so that can be used on a server to develop powerful Web applications. ASP.NET offers numerous important advantages over former Web development models:

• Enhanced Performance. ASP.NET is compiled common language runtime code which is functioning on the server. ASP.NET can get benefit of early binding, native optimization, just in time compilation, and caching services right out of the box. This offers improved performance before you ever write a line of code.
• World Class Tool Support. The ASP.NET skeleton goes together by an intense toolbox and modeler in the Visual Studio added development atmosphere. This sophisticated tool offers Drag and drop server controls, WYSIWYG editing, and automatic deployment are just some of the features.
• Power and Flexibility. The power and flexibility of that whole base is available to Web application creators Because ASP.NET is based on the common language runtime. The .NET Framework class library, Messaging, Data Access solutions are all correctly accessible from the Web. ASP.NET is also language independent, so you can take the language that ideally suits to your application. More over, common language runtime interoperability assurances that your current investment in COM based development is saved when move around to ASP.NET.
• Simplicity. ASP.NET makes it simple to finish common tasks, from simple form submission and customer confirmation to deployment and site specification. For example, the ASP.NET page skeleton allows you to create user interfaces that clearly differentiate application logic from presentation code and to deal events in a simple, Visual Basic like forms processing model. More over, the common language runtime make things simple development, with the use of managed code services such as automatic reference counting and garbage collection.
• Manageability. ASP.NET utilizes of a text based, hierarchical configuration system, which make easier selecting settings to your server atmosphere and Web applications. Because configuration information is saved as plain text, new settings may be applied without the use of local administration tools. This "zero local administration" philosophy enlarges to deploying ASP.NET skeleton applications. By copying the needful files to the server an ASP.NET skeleton application is put into a server simply. Even to put in or replace running compiled code No server restart is necessary.
• Scalability and Availability. ASP.NET has been created with scalability to increase performance in clustered and multiprocessor atmosphere. Further, processes are closely observed and managed by the ASP.NET runtime, so that if one acts badly (leaks, deadlocks), a new process can be made in its position, which helps to keep your application always open to deal with requests.
• Customizability and Extensibility. ASP.NET offers a well factored architecture that permits creators to "plug in" their code at the correct state. In fact, it is viable to expand or alter any subpart of the ASP.NET runtime with your own custom written part. Utilizing state services or custom authentication has never been simpler.
• Security. With inbuilt Windows authentication and per application specification, you can be assured that your applications are safe.

5.1.8. Language Support

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

5.1.9. ASP.NET Web Forms

The ASP.NET Web Forms page skeleton is a standard language runtime programming model that can be utilized on the server to dynamically create Web pages.

The ASP.NET Web Forms skeleton has been specially modeled to show a number of important absences in the former model. In particular, it offers:

• The ability to produce and utilize reusable UI controls that can engulf common utility and thus reduce the amount of code that a page developer has to write.
• The capability for developers to form their page logic in an linear fashion
• The ability for development tools to present strong WYSIWYG design support for pages

ASP.NET Web Forms pages are given an .aspx file name extension. They can be entered into all over an IIS virtual root directory tree. When a browser client wants .aspx resources, the ASP.NET runtime compiles the required file into a .NET skeleton class. This class can then be utilized to operate incoming requests. An ASP.NET page can be developed by taking an existing HTML file and altering its file name extension to .aspx. For example, the following sample shows a simple HTML page that collects a user's name and category preference and then executes a form pushback to the originating page when a button is clicked:

ASP.NET presents syntax compatibility with existing ASP pages. This comprises support for <% %> code deliver blocks that can be intermixed with HTML content within an .aspx file. These code blocks are executing in a top down manner at page deliver time.

5.1.10. Code Behind Web Forms

ASP.NET maintains two methods of authoring dynamic pages. The first one is the method shown in the earlier samples. In this sample the page code is physically declared within the originating .aspx file. An another approach known as the code behind method, which enables the page code to be separated from the HTML content into an entirely separate file.

5.1.11. ASP.NET Server Controls:

Web pages are programmed by ASP.NET server controls which are used by ASP.NET page developers. Server controls are proclaimed inside an .aspx file with use of custom tags or intrinsic HTML tags which hold a runat = "server" credit value. One of the controls in the System.Web.UI.HtmlControls namespace can be used to deal HTML tags. Any tag that does not clearly refer to one of the controls is allocated the type of System.Web.UI.HtmlControls.HtmlGenericControl. Server controls periodically hold any client entered figures between round trips to the server. This control position will not be saved on the server.

ASP.NET enables developers to make use of richer custom controls on their pages. For example, the following sample shows how the control can be used to dynamically display rotating ads on a page.

1. ASP.NET Web Forms offers strong and a simple way to construct dynamic Web UI.
2. ASP.NET Web Forms pages aimed any browser customer.
3. ASP.NET Web Forms pages show syntax compatibility with current ASP pages.
4. ASP.NET server controls provide a simple method to engulf common functionality.
5. ASP.NET dispense with 45 built in server controls. Developers can also use controls made by third parties.
6. ASP.NET server controls by itself project both up level and down level HTML.
7. ASP.NET templates offer an easy method to customize the look and feel of list server controls.
8. ASP.NET validation controls offer an easy method to do declarative customer or server data validation.

5.2. ACTIVE X DATA OBJECTS.NET:

5.2.1. Overview of ADO.NET

ADO.NET is an improvement of the ADO data access exemplar that straight away deals with user needs for creating scalable applications. It was created specifically for the web with scalability, statelessness and XML taking into consideration.

ADO.NET utilizes some ADO objects, some of them are Connection and Command objects, and also introduces new objects. New ADO.NET objects comprise the DataSet, DataReader, and DataAdapter.

The main difference between ADO.NET and former data architectures is that there is an object, which is the DataSet which is separate and different from any data stores, as the DataSet functions are a standalone entity. Dataset is invariably cut off recordset that knows not about the origin or goal of the data that it holds. Tables, columns, relationships, constrains, views and so forth are within a Dataset like in a database.

A DataAdapter is the object which joins to the database to load the DataSet. Then, it joins back to the database so as to upgrade the data in database. In the earlier period, data processing has been mainly connection based. To make multi tiered apps more efficient, data processing is turning to a message based approach that rotates around large amount of information. The DataAdapter offers a connection to regain and store data between a DataSet and its source data store. It achieves this with the use of the correct SQL commands made against the data store.

The XML based DataSet object provides a stable programming exemplar that functions with all models of data storage: flat, hierarchical, and relational. It achieves this by referring the data that it contains as bunch and data types. The origin of the data inside the DataSet is altered through the same set of standard APIs surfaced through the DataSet and its primary objects.

As the DataSet has no information of the origin of its data, the managed provider has extensive and explicit knowledge. The job of the managed provider is to reach the dataset, load the dataset and carry on the DataSet to as well as from data stores. Four basic objects: the Command, Connection, DataReader and DataAdapter are provided by The OLE DB and SQL Server .NET Data Providers part of the .Net Framework.

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

• Connections. Connection is for conjoining to and controlling transactions against a database.
• Commands. Commands are for delivering SQL commands against a database.
• DataReaders. DataReaders are for verifying a forward only stream of data records from a SQL Server data origin.
• DataSets. Dataset is for saving, remoting and programming against flat data, XML data and relational data.
• DataAdapters. DataAdapter is for deploying data into a DataSet, and reuniting data against a database.

When managing with connections to a database, there are 2 separate options: SQL Server .NET Data Provider (System.Data.SqlClient) and OLE DB .NET Data Provider (System.Data.OleDb). In these samples we will use the SQL Server .NET Data Provider. These are written to handle directly to Microsoft SQL Server. The OLE DB .NET Data Provider is utilized to handle any OLE DB provider.

5.2.2. Connections

Connections are used to 'talk to' databases. These are illustrated by provider specific groups such as SQLConnection. Commands go through over connections and Resultsets are returned in the state of streams and it can be read by a DataReader object.

5.2.3. Commands

Commands carry the information that is given to a database, and these are referred by provider specific groups such as SQLCommand. A command will be a saved procedure call, an UPDATE statement or a statement that gives results. You can also utilize output and input parameters and return figures as piece of your command syntax.

5.2.4. Data Readers

Read only/forward only cursor over data is the Data Reader object. Hierarchical data as well as flat is supported by the DataReader API. After executing a command against a database, A DataReader object comes back. The structure of the returned DataReader object is varying from a recordset. As an example, you can use the DataReader to give the results of a search list in a web page.

5.2.5. Data Sets & DataAdapters

DataSets:

OleDbConnection objects.
The DataAdapter object uses commands to upgrade the data origin after alterations have been made to the DataSet. With the use of the Fill method of the DataAdapter calls the SELECT command and with the use of Update method calls the INSERT, UPDATE or DELETE command for every altered row.

You can set these commands in order to manage the statements used at runtime to determine changes, including the use of stored procedures. A CommandBuilder object can produce these at run time based upon a chosen statement. However, this run time production need an additional round trip to the server in order to gather necessary The DataSet object resembles the ADO Recordset object.

Another important difference is that the DataSet is always cut off. The DataSet object refers to a cache of data, with database like formation such as tables, columns, relationships, and constraints. A DataSet can and does behave similarly to a database, it is important to know that DataSet objects do not operate directly with databases, or other source data. This lets the creator to work with a programming structure that is always stable, irrespective of where the source data stays. Data coming from a database, an XML file, from code, or user input can all be put into DataSet objects. After, as alterations are made to the DataSet they can be traced and validated before updating the source data. The GetChanges is the method of the DataSet object, that it makes a second Dataset that holds just the alterations to the data. This DataSet is then utilised by a DataAdapter to upgrade the original data source.

The DataSet has numerous XML attributes and this including the capability to create and use up XML data and XML schemas. XML schemas can be utilized to show schemas exchanged via WebServices. DataAdapters (OLEDB/SQL)

The DataAdapter object acts like a bridge between the DataSet and the source data. Utilising the provider specific SqlDataAdapter can improve total performance when using Microsoft SQL Server databases. You would use the OleDbDataAdapter object for other OLE DB supported databases, and its associated OleDbCommand and metadata. So specifically offering the INSERT, UPDATE, and DELETE commands at design time will cause in improved run time performance.

1. ADO.NET is the further creation of ADO for the .Net Framework.
2. ADO.NET was developed with the use of n Tier, statelessness and XML in the foreground. Two new objects are the DataSet and DataAdapter, are offered for these scenarios.
3. ADO.NET can be used to retrive data from a stream, or to save data in a cache for upgrades.
4. There is a more larger information on ADO.NET in the documentation.
5. We can execute a command against the database in order to do operations like inserts, updates, and deletes. You do not need to first place data into a DataSet in order to insert, update, or delete it.
6. Also, you can make use of a DataSet to bind to the data, move through the data, and navigate data relationships

5.3 ADO.NET

ADO.NET offers consistent access to data sources such as Microsoft SQL Server, as well as data sources shown through OLE DB and XML. Data sharing user applications can make use of ADO.NET to join to the data sources and collect, alter, and upgrade data. ADO.NET clearly factors data access from data alteration into discrete parts that can be used independently. ADO.NET includes .NET data providers for joining to a database, running commands, and collecting results. Those results are either put in an ADO.NET DataSet object, or worked on directly in order to be shown to the user in an ad hoc manner which is combined with data from numerous sources, or remoted between levels. The ADO.NET DataSet object can also be used independently of a .NET data provider to manage data local to the application or sourced from XML.

The ADO.NET groups are created in System.Data.dll, and are added to the XML classes which are found in System.XML.dll. While compiling code that uses the System.Data namespace, reference both System.Data.dll and System.XML.dll. For an example, compiling an ADO.NET application utilizing a command line compiler, ADO.NET offers functionality to developers writing managed code similar to the functionality provided to local COM developers by ADO.

5.4. Design Goals for ADO.NET

As application creation has developed, new applications become loosely joined based on the Web application model. More and more of today's applications make use of XML to encode data to be carried over network connections. Web applications use HTTP as the medium for communication between levels to handle maintaining state between requests. This new design is very different from the connected, and this new one is closely coupled fashion of programming that attributed the customer/server period, where a connection was kept open for the period of the program's lifespan and no special handling of state was necessary.

ADO.NET was modeled for the requirements of this new programming design: close integration with XML, disconnected data architecture, common data representation to combine data from numerous and varied data origins, and optimized utilities for cooperating with a database which is all native to the .NET skeleton.

In developing ADO.NET, Microsoft holds the following model aims.

5.5. Leverage Current ADO Knowledge

The model for ADO.NET focuses on numerous of the requirements of current application development design. Current ADO creators do not have to begin from the starting in knowing a brand new data access technology. ADO.NET is an inbuilt component of the .NET skeleton without seeming totally different to the ADO programmer. ADO.NET exists together with the ADO. Even as most new .NET based applications will be written using ADO.NET, ADO still is accessible to the .NET programmer through .NET COM interoperability services.

5.6. Support the N Tier Programming Model

ADO.NET offers top class support for the n level programming atmosphere for which many new applications are written. The idea of working with a disconnected bunch of data has become a key point in the programming design. The ADO.NET key for n level programming is the DataSet.

5.7. Integrate XML Support

XML and data access are tightly joined — XML is all about encoding data, and as well data access is increasingly becoming all about XML. The .NET skeleton does not just support Web standards — it is constructed totally on top of them. XML support is constructed into ADO.NET at a ground level. ADO.NET and The XML groups in the .NET skeleton are fragments of the same architecture — they bind together at many various states. We no more have to select between the data access group of services and their XML counterparts because the ability to switch over from one to the other is ingrained in the design of both.

5.8. ADO.NET Architecture

Data processing has traditionally depended basically on a connection based, two level design. Since data processing increasingly utilizes multi level architectures, programmers are changing to a disconnected concept to show better scalability for their applications.

The model of the DataSet permits you to easily carry data to clients over the Web using XML Web services, as well as allowing you to marshal data between .NET parts using .NET Remoting services. DataTable objects can also be utilized with remoting services, but cannot be transported by way of an XML Web service.

5.9. XML and ADO.NET

ADO.NET balances the strength of XML to present cut off access to data. ADO.NET was designed hand in hand with the use of the XML groups in the .NET skeleton and these both are parts of a single architecture. ADO.NET and the XML groups in the .NET skeleton touch in the DataSet object. The DataSet can be filled with data from an XML origin, even if it is a file or an XML stream. The DataSet could be created as World Wide Web Consortium (W3C) compliant XML and together with its schema as XML Schema definition language (XSD) schema, apart from of the origin of the data in the DataSet. Because the inherent serialization structure of the DataSet is XML, it is a special platform for placing data between levels making the DataSet an ideal selection for remoting data and schema context to and from an XML Web service.

The DataSet can also be calibrated with an XMLDataDocument to present connection and hierarchical access to data in real time

5.9.1. Architectural Overview of XML in the .NET Framework:

This section presents an architectural overview of XML in the .NET Framework. The design targets for the XML classes in the .NET Framework are:

• Multilingual support.
• Standards based.
• High productivity.
• Extensible.
• Pluggable architecture.
• Integration with ADO.NET.
• Focused on performance, reliability, and scalability.

5.9.2. Design Goals for XML in the .NET Framework.

The goals of XML in .NET Framework are:

• Extensibility.
• Compliance with the W3C standards.
• Pluggable architecture.
• Tight integration with ADO.NET.
• Performance.

5.9.3. XML Integration with Relational Data and ADO.NET

While operating the older versions of ActiveX Data Objects (ADO), the code created while functioning relational data was different than the code created to work with hierarchical data. Presently, the .NET architecture fuses together numerous groups in XML with numerous groups in the ADO.NET architecture to join the two programming structures. This offers you an object structure to utilize irrespective of the structure of the data.

The XML in the .NET skeleton and ADO.NET offers a unified programming structure to get data referred as both XML data, text delimited by tags that form the data and relational data nothing but tables having rows, columns, and constraints. Where data can be looked into programmatically The XML sees XML data from any data stream into DOM node trees, as well as ADO.NET offers the means to access and change relational data within a DataSet object.

The XMLDocument uses the DOM in XML, and the XMLDataDocument conjoins the ADO.NET and XML by referring relational data from a DataSet and put into line it with the XML document structure. The XML integration with relational data takes place with the XMLDataDocument and a group obtained from the XMLDocument. The XMLDataDocument charts XML to relational data in an ADO.NET DataSet.

6. Web services

Web services offer a web enabled user interface with tools that have multiple web controls and hypertext markup language (HTML) controls. Web services also contain numerous web protocols, security. Managed code is called when code is aimed for .NET which means that the code by itself runs under a "contract of cooperation" with the CLR. Managed code offers the information useful for the runtime to give services like memory control, code access security, cross language integration, and the self functioning lifetime control of all of our objects.

6.1 Stateless / Stateful Services

A stateless service does not keep its history across distinct invocations. But a stateful service keeps track of the histories of all the past invocations. Stateless services can implement policies that inspect the history of the current invocation only. Let us take an example, resource usage control. Stateful services permit for more expressive security policies.

6.2 Local / Global Histories

Local histories record the events generated by a service locally on its site. Instead, a global history may span over multiple services. Local histories are the most sensible choice when services do not trust other services. In this case, a service only trusts its own history, but it cannot hold back the past history of its callers, for example, to avoid that its client has visited a malicious site. Global histories require some trust relation among services: If a service A trusts B, then the history of A may consist of that of B and, so, A may check policies on the behaviour of B.

7. SYSTEM DESIGN

Module Description

New User and Login

Existing users can enter to site by their login information. Existing users need to provide sufficient username and password. This login information provides security authentication. And new users can create new account to use the site by giving their identity information.

Admin

Admin have the full control on the site, he can view the activities of users. Main role of the admin is to create and manage services. He should give the physical path and service package for the particular service.

Service

Service module is handling by admin. This module is the heart of website, because all the services are managed by this module. Here, admin should mention Service ID, Service Description, Path, Provider and Package.

User

In this module, user can login to their space. He can view personal information, and all the services. User can select any of the services and service package which are accessible to him.

7.1 Module I/O

New User and Login

Given Input User details and login detail

Expected Output Enters into site.

Admin

Given Input Creates and provide service Expected Output Updation of service in database.

Service

Given Input Details of service like service id, service package etc.

Expected Output Shows all the services and its details.

User

Given Input User can view personal status and selects services Expected Output Services selected or bought may be stored in the users database in an encrypted format for future use.