Literature Survey

Literature survey is the most important step in software development process. Before developing the tool it is necessary to determine the time factor, economy n company strength. Once these things r satisfied, ten next steps is to determine which operating system and language can be used for developing the tool. Once the programmers start building the tool the programmers need lot of external support. This support can be obtained from senior programmers, from book or from websites. Before building the system the above consideration r taken into account for developing the proposed system.
We have to analysis the Service Computing:

Web Services: Web Services can convert your application into a Web-application, which can publish its function or message to the rest of the world. The basic Web Services platform is XML + HTTP. A web service is a method of communication between two electronic devices. It a "solution logic" that can be exposed over worldwide web.

The W3C defines a "web service" as "a software system designed to support interoperable machine-to-machine interaction over a network. It has an interface described in a machine-processable format (specifically Web Services Description Language WSDL). Other systems interact with the web service in a manner prescribed by its description using SOAP messages, typically conveyed using HTTP with an XML serialization in conjunction with other Web-related standards."

REMOTE PROCEDURE CALLS:

RPC web services present a distributed function (or method) call interface that is familiar to many developers. Typically, the basic unit of RPC web services is the WSDL operation. The first web services tools were focused on RPC, and as a result this style is widely deployed and supported. However, it is sometimes

criticized for not being loosely coupled, because it was often implemented by mapping services directly to language-specific functions or method calls. Many vendors felt this approach to be a dead end, and pushed for RPC to be disallowed in the WS-I Basic Profile. Other approaches with nearly the same functionality as RPC are Object Management Group's (OMG) Common Object Request Broker Architecture (CORBA), Microsoft's Distributed Component Object Model (DCOM) or Sun Microsystems's Java/Remote Method Invocation (RMI).

Applied Computing: Although when considered from a purely technological point of view Service-Oriented Programming (SOP) is not an enormous novelty, when it comes to paradigmatic considerations SOP is quickly changing our vision of the Web. Originally, the Web was mainly seen as a means of presenting the information to a wide spectrum of people, but SOP is now triggering a radical shift to a vision of the Web as a computational fabric where loosely coupled

services interact publishing their interfaces inside dedicated repositories, where they can be searched by other services, retrieved and invoked, always abstracting from the actual implementation. In the context of this modern paradigm we have to cope with an old challenge, like in the early days of ObjectOriented Programming when, until key features like encapsulation, inheritance, and polymorphism, and proper design methodologies were defined, consistency in the programming model definition was not achieved. The complex scenario of Service Oriented Programming needs to be clarified on many aspects, both from the engineering and from the foundational point of view. From the engineering point of view, there are open issues at many levels. Among others, at the system design level, both traditional approaches based on UML and approaches taking inspiration from business process modeling, e.g. BPMN, are used. At the composition level, although WS-BPEL is a de-facto industrial standard, other approaches are appearing, and both the orchestration and choreography views have their supporters. At the description and discovery level there are two separate communities pushing respectively the semantic approach (ontologies, ...) and the syntactic one (WS-BPEL, ...). In particular, the role of discovery engines and protocols is not clear. In this respect we still lack

adopted standards: UDDI looked to be a good candidate, but it is no longer pushed by the main corporations, and its wide adoption seems difficult. Furthermore, a new different implementation platform, the so-called REST services, is emerging and competing with classic Web Services. Finally, features like Quality of Service, security, sustainability and dependability need to be taken seriously into account, and this investigation should lead to standard proposals. Conclusion: Web services are one of the key elements of the so-called programmable Web. They are extremely versatile software elements that really have the potential to open up a new era in sofware: the age of interoperability. Web services can be effectively used to participate in and set up business-to-business (B2B) transactions. They are great at exposing software functionality to customers and integrating heterogeneous platforms.