The document discusses the evolution of web services and their life cycles. It describes how web services allow for program-to-program interactions and how standards like SOAP, WSDL, and UDDI facilitate web service discovery, description, and composition. The key activities in a web service life cycle include service wrapping, specification, planning, advertisement, discovery, scheduling, negotiation, construction, execution, and monitoring.

1. 1
1. Introduction:
Web Services are involved in all aspects of life as millions of users use Internet. Web service
Pervious environment used only the format, transport and interface standards, not be meaning of
the data to be exchanged see SOA, SOAP, UDDI, Web Services protocols and XML.
UDDI is used to register and discover Web Services, typically described in WSDL.
Web service composition is a promising area of research and development. From a research
point of view, the key issues that need to be investigated relate to the facilitation of Web service
composition in large, autonomous, heterogeneous, and dynamic environments. For Business-to-
Business (B2B) E-commerce to really take off, there is a need for effective and efficient means
to search, abstract, compose, analyze, execute evolve Web Services in appropriate time-frames.,
and Users appeal for high scalability, availability, readability of hosts (nodes) to provide rapid
response and high throughput for their applications running at any time.
2. Introduction of Web
The Web is a repository of information which resides on the servers. To access Web, the user
need a computer machine or related device, a browser on the machine and an Internet
connection. The users normally begins either by typing the URL of the page into the address bar
of browser or by following a hypertext link to that page or resource. Browser finds and displays
pages of information. The function of a Web Browser is to interpret the programming language
of the Web pages and transform it into the words and graphics that you see on your screen [20].
2.1 Evolution of Web
The World Wide Web was developed in 1989 by English computer scientist Timothy Berners-
Lee to enable information to be shared among internationally dispersed teams of researchers at
the European Laboratory for Particle Physics and further refined by him and Robert Cailliau in
1990. The idea behind WWW was to merge and share the technologies of computers, networking
and hyperlinks.
In 1991, an early www system was released with the help of CERN to the high energy physics
community. They use simple browser, Web server and a library, implementing the essential
functions for developers to build their own software. International World-Wide Web
Consortium was founded in January 1995 to guide the World Wide Web by rising common
protocols that support its evolution and ensure its interoperability.

2. 2
Since 1989 Web has grown initially as a medium for the broadcast of read-only material from
heavily loaded corporate servers to the mass of Internet connected consumers. As the use of
Internet is increased the style, demands of people are also increased. Now a day, the Web users
want all information on the Web.
2.2 Basic Process
Whenever a user wants to access a Web page the first step is for the server-name part of the URL
to be resolved. The next step is for an HTTP request to be sent to the Web server at that IP
address. Then Web browser displays the page. Web pages contain the links of other related
pages, or download and Web resources etc. Now for example, let's say that a user is sitting with
his/her computer and surfing the Web. Suddenly you get information from your friend about a
university. For example the link is mmumullana.org. Then you type the link in the address bar or
you may click on the URL. And magically, no matter where in the world that URL stored, the
page pops up on your screen. At the most basic level possible, the following Figure 1.1 shows
the steps that brought that page to your screen:
Figure 1.1

3. 3
2.3 Web Documents
Since 1989 Web has grown initially as a medium for the broadcast of read-only material from
heavily loaded corporate servers to the mass of Internet connected consumers. As the use of
Internet is increased the style, demands of people are also increased. Now a day, the Web users
want all information on the Web. Then the scientists categorize Web application in three
categories named as static, dynamic and active. Now, the Web developer had to choose different
techniques for different type of Web document. These are as follows:
2.3.1 Static document: - In the evolution of the Web the basic requirement was to
transfer the text data. Static documents are the read only documents the user can access and read
these pages but he/she cannot give his/her input. Simple HTML/DHTML is used for these types
of documents.
2.3.2 Dynamic Document: - As the use of Web Services increased, the user’s
requirements were increased. After few years, Web users feel the need to interact online. They
want to input their data and wants response online. Then the scientists developed dynamic
documents. In these types of documents user can interact with the Web page. These types of
documents are processed at the client side which is helpful to reduce the network traffic. He/she
can give his/her inputs. For example they can fill a form and after processing an appropriate
message can be displayed. The processing will be done on client side and the final data will be
stored on the server. For these types of documents the Web scientists provide scripting
languages, i e., JavaScript and VBScript.
2.3.3 Active Document: - After using dynamic documents the security and accuracy
problem came into existence. Then scientists proposed active documents. These documents are
similar to Dynamic Documents. User can directly interact with the Web page. The basic
difference between both is that the Active Documents are processed at Server side not on the
Client side. This method increased the network traffic but increase accuracy, reliability and Web
security. The applications of active documents are all online transactions e. g., Railway
Reservation, Stock Market, Internet banking etc. The scientists proposed server side

4. 4
programming languages for active documents e. g, CGI, Servlets, ASP, JSP, ColdFusion, PHP,
.net etc.
3. Web Services
The Web has become the means for organizations to deliver goods and services and for
customers to search and retrieve services that match their needs. What the Web did for program-
to-user interactions, Web Services are poised to do for program-to-program interactions. Web
Services allow companies to reduce the cost of doing e-business, to deploy solutions faster and to
open up new opportunities. The key to reaching this new horizon is a common program-to
program communications model, built on existing and emerging standards such as HTTP,
Extensible Markup Language (XML), Simple Object Access Protocol (SOAP), Web Services
Description Language (WSDL) and Universal Description, Discovery and Integration (UDDI).
Web Services are self-contained, Internet enabled applications capable not only of
performing business activities on their own, but also possessing the ability to engage other Web
Services in order to complete higher-order business transactions. Simple Web Services may
provide simple functions such as credit checking and authorization, inventory status checking, or
weather reporting, while complex services may appropriately unify disparate business
functionality to provide a whole range of automated processes such as insurance brokering,
travel planning, insurance liability services or package tracking. Several software vendors and
consortia are providing platforms (such as IBM’s Web Sphere, or Microsoft’s .NET), languages
and description models for service representation and discovery such as WSDL and UDDI,
which offer uniform representation of and access to Web Services, respectively.
The Web Service Model
This section will look at the parties involved in Web Services and corresponding
architectures. There are mainly three roles related to Web Services: Web Service
requesters, Web service brokers, and Web service providers, as shown in Figure 2.
Web service requesters denote Web service users, buyers, customers, consumers,
receivers, and their intelligent agents. Web service brokers denote Web service
intermediaries, middle agents and their intelligent agents. Web service providers denote
Web service owners, sellers, senders and their intelligent agents. In this architecture,
Web service providers create Web Services and advertise them to combine Web

5. 5
service requesters by registering the Web Services with Web service brokers, or simply
offers Web Services. The Web service provider also needs to describe the Web service
in a standard format, and publish it in a central service registry. The service registry
contains additional information about the service provider, such as address and contact
of the providing company, and technical details about the service. Web service
providers may integrate or compose existing services using intelligent techniques such
as Case-Based Reasoning (CBR). They may also register descriptions of services they
offer, monitor and manage service execution. Web service requesters retrieve the
information from the registry and use the service description obtained to bind to and
invoke the Web service. Web service brokers maintain a registry of published Web
Services and might introduce Web service providers to Web service requesters. They
also provide a searchable repository of service descriptions where service providers
publish their services, service requesters find services and obtain binding information
for these services.
 The Web Services architecture is based upon the interactions between three roles:
 Service provider
 Service registry
 Service requestor
 The interactions involve the:
 Publish operations
 Find operation
 Bind operations.
The Web Services model follows publish, find, and bind paradigm.

6. 6
Figure 2: Web Services Model
This architecture is simple because it only includes three parties and three basic
operations: publish, find and bind. In fact, some behaviors of Web service agents are
also fundamentally important in order to make Web Services successful. These
fundamental behaviors at least include communication, interaction, collaboration,
cooperation, coordination, negotiation, trust and deception [4 & 5].
The platform neutral nature of Web Services creates the opportunity for building
composite services by combining existing elementary or complex services, possibly offered by
different enterprises. For example, a travel plan service can be developed by combining several
elementary services such as hotel reservation, ticket booking, car rental, sightseeing package,
etc., based on their WSDL description [6]. The services that are used in the context of a
composite service are called its constituent services.
An atomic Web service is a basic unit of operation in a Service-oriented Architecture
(SOA). However, in general, an atomic Web service is not able to satisfy the functional
requirements of complex tasks. Therefore, it is desirable to logically connect several atomic Web
Services to satisfy complex functional requirements, leveraging the loose coupling
characteristics of SOA. For example, an atomic Web service may be sufficient to retrieve a map
of a location or obtain the weather conditions of a region. However, such piecemeal information
by itself is not very useful. For example, in geospatial domain, one example application is the
construction of a landing plan that takes location, time and equipment as inputs, and provides a
map of the landing area annotated with weather, meteorology, and tidal conditions.

7. 7
Web Services technology is the most promising choice to implement service oriented
architecture and its strategic objectives. A Web service could be described, advertised and
discovered using standard-based languages, and interacted through Internet based protocols.
Today, two types of Web Services are most popular and widely used: SOAP-based Web Services
and RESTful Web Services [7]. The former is based on Web Services Description Language
(WSDL) and Simple Object Access Protocol (SOAP), while the latter conforms to the REST
architectural principles [8]. With the technology with the technology of Web Services,
enterprises are able to expose their internal business processes as services and make them
accessible via the Internet. Nowadays, companies such as Google, Amazon, Twitter, and
Facebook have Web Services to provide simple access to some of their resources, enabling third-
parties to combine and reuse their services.
4. Life cycle Activities on Web Services
As the use and purpose of the Web is changing from its beginning the Web lifecycle and
Web service lifecycles has been affected and changed accordingly. It describes the life
of a software product from its conception to its implementation, delivery, use, and
maintenance [2]. A traditional software development lifecycle mainly consists of seven
phases: planning, requirements analysis, systems design, coding, testing, delivery and
maintenance. Based on this, a Web service lifecycle consists of the start of a Web
service, the end of Web service and its evolutionary stages that transform the Web
service from the start to the end.
A lifecycle for Web service solutions that consists of Web service modeling,
development, publishing, discovery, composition, collaboration, monitoring and
analytical control from a perspective of Web service developers [3]. The researchers
also explore technical challenges related to each activity in the Web service lifecycle.
The life cycle of activities related to Web Services. It begins by distinguishing between
three kinds of life cycle: The operational life cycle, The B2B trading life cycle and the business
networking life cycle. In the past, most B2B integration solutions have been designed to support
the operational life cycle by specifying a set of pre-defined B2B conversations.

8. 8
Motivation
The process of composition of Web Services is for reusability, specializing and extending the
available constituent Web Services to fulfil the request by the client that cannot be handled by a
single atomic Web service. It provides a great of flexibility and reusability of service
compositions.
 The ability to program the Web.
 Example: Consider an Excel spreadsheet that summarizes your whole financial picture :
stocks, bank accounts, loans, etc. If some of this information is available through XML
Web Services, Excel can update it and present the update information to the user.
5. Life cycle activities
There are various phases or activities involved in the life cycle of composite Web service (as
shown in Figure 3).

9. 9
Figure 3: Life Cycle Activities composite Web service
Several technologies have been developed to support the various activities of the service
composition life cycle. The problem is that (mostly for historical reasons) these technologies
tend to provide overlapping features. In addition, they require intimate knowledge of several
low-level features associated with the supporting infrastructure (e.g. operating systems,
networks, and programming languages). As the infrastructure is modeled or upgraded, software
maintenance becomes an issue. It is believed that the analysis and design activities related to
service composition should be rest conducted at a high level of abstraction, primarily addressing
the business requirements, and design issues at the architectural level.
In accordance with standard software engineering practice, lower level design issues and
the choice of adequate technology should be treated separately (at the implementation stage).
Accordingly, the researchers[ ] propose seven analysis/design patterns corresponding to the
above activities: Service Wrapper, Composite Service Specification, Service Discovery, Service
SERVICE
WRAPPING
COMPOSITE
SERVICE
SPECIFICATION
SERVICE PLANNING
AND
VALIDATION
SERVICE
ADVERTISEMENT/
DISCOVERY
SERVICE
SCHEDULING
SERVICE
NEGOTIATION
SERVICE
CONSTRUCTION
COMPOSITE
SERVICE
EXECUTION
SERVICE
MONITORING
SERVICE
EVOLUTION

10. 10
Negotiation, Composite Service Execution, Service Monitoring and Service Evolution. Due to
the emerging nature of the topic, these patterns are in early stages of development and validation,
and should rather be called proto-patterns.
6. Literature Review
A Web Service supports direct interactions with other software agents using XML-based
messages exchanged via Internet-based protocols. Examples of Web Services include online
reservation, ticket purchase, stock trading, and auction. Standards are key enablers of Web
Services [14]. Major industry players took a lead to set up crucial standards. This has greatly
facilitated the adoption and deployment of Web Services [15]. Three key XML-based standards
have been defined to support Web service deployment: SOAP [16], WSDL [17], and UDDI [18].
SOAP defines a communication protocol for Web Services. WSDL enables service providers to
describe their applications. UDDI offers a registry service that allows advertisement and
discovery of Web Services.
The Web Services paradigm promises to enable rich, flexible, and dynamic interoperation
of highly distributed and heterogeneous Web-hosted services. Substantial progress has already
been made towards this goal (e.g., emerging standards such as SOAP, WSDL, BPEL) and
industrial technology (e.g., IBM's Web Sphere Toolkit, Sun's Open Net Environment and Jini
TM Network technology, Microsoft's .Net and Novell's One Net initiatives, HP's e-speak, BEA's
Web Logic Integration). Several research efforts are already underway that build on or take
advantage of the paradigm, including the DAML-S/OWL-S program [9, 10 & 11] and automata-
based models for Web Services [13 & 12]. But there is still a long way to go, especially given
the ostensible long term goal of enabling the automated discovery, composition, enactment, and
monitoring of collections of Web Services working to achieve a specified objective.
A kind of middle ground is also emerging, which provides abstract signatures" of Web
Services that are richer than WSDL but retain a declarative avor. Most popular here is the use of
automata-based descriptions of permitted sequencing patterns of the Web Services, with a focus
on either activities performed [19] or messages passed [20].

11. 11
MAIS (Multichannel Adaptive Information Systems) The MAIS [21] project aims at
creating a platform, a methodology, and a set of design tools to develop distributed information
system based one-services. MAIS fullls QoS-aware dynamic services composition using
contextual information. In MAIS, a service is described by a name, a short description, a service
category, and an aggregation of three types of elements: a Channel (containing contextual
information), one or more Service Providers and a Functional Description. When requesting a
composite service, a user species the composition requirement and desired QoS constraints,
while services are selected based on QoS constraints and their contexts.
Although Web Services composition has been extensively studied in the past decade,
techniques are still not fully mature yet with several open issues remaining. Moreover, the rapid
rise and adoption of new computing paradigms such as Cloud computing, social computing, and
Web of Things in recent years also presents compounded challenges in this area [22]. The
authors[22] identify several directions for future research on services composition.
Quality of service (QoS) has been widely used in middleware and networking
communities [23 &14]. Research efforts in these communities main focus on the performance of
network and devices. There has been a surge in adapting the QoS concept to Web Services in
line with their fast growth. Quality of Service or Quality of Web Service (QoWS) could
encompass a number of quantitative and qualitative parameter (non-functional properties) that
measure the Web service performance in delivering its functionalities. The researchers [23 &14]
present taxonomy of QoWS parameters to clearly identify the different quality aspects of Web
Services.
Efficient access to Web Services As the Web is moving from a data Web to a service
Web, it is expected that tomorrow’s Web will be the repository of a large number of Web
Services provided by third-party providers. In that context, the ability to efficiently access Web
Services is poised to become of prime importance [24]. In the simplest scenarios, accessing Web
Services would consist of invoking their operations by sending and receiving messages.
As a step further in this direction, our ongoing work in the context of the SELF-SERV
project aims at providing high-level modelling constructs and supporting tools to search,
compose, execute, monitor, an evolve Web Services. SELF-SERV provides a framework in
which services can be declaratively composed and the resulting composite services can be
executed in a peer to-peer way within a dynamic environment. One of the main objectives of the

12. 12
project is to devise novel integration techniques that allow fast development of new services
from existing ones.
7. Challenges
Various theories and techniques are developed to improve the Web Services. But with the
growth of Internet usage the challenges listed below need to be resolved efficiently.
Optimised Web Services: The variation in different Web Services response used in Internet is
an important growing issue.
Web Service Composite correctness: Correct Web pages and services must be add during
composition of Web Services.
Time Limit: The Web service composition takes much time during composition. So, it reduces
the performance.
Transaction failures: The Web Services in case to online money transaction systems are getting
heavier due to exponential growth of Internet Banking that leads to failure of lot many
transactions on Internet.
8. Aim of the Work
The current era is the time of communication. Now a day, every person knows about mobile and
Internet. Due to the revolution of wireless communication, the circumstances surrounding Web
users are constantly changing realistically and their requirements are also changing with the
situation. People from various fields, are not depending on computers they can access
information services with a mobile terminal anytime, anywhere.
The changes in the development, life cycle activates, services of Web were done from time to
time as per the requirements were increased. In the modern era, there are many problems like
security, access time, numbers and type of users, heterogeneous data on the Web. In this
research, the focus is on how the life cycle and Web Services are affected as the requirements
and use of the Web is increased.
9. Objectives of Research

13. 13
 To compare various activities of Web life cycle activities in Composite Web Services
from evolution of web to this era.
 To analysis and propose the improved Web life cycle activities framework for Web
Services.
10. Research Methodologies
The fundamental idea behind this research is to increase the efficiency of Web technology by
learning process through concepts of ANN. The tools and techniques used in the study will be:
• Study of Literature
• Analysis of different types of Web Services used
• On line Interpretation of Optimized results
• Research Paper publication
• Change order upon interrupts in form of feedback and publications
• Overall outcome processing, development of related facts
11. References
[1] R.S. Pressman, Software Engineering: A Practitioner’s Approach (5th edn). Boston:
McGraw-Hill, 2001.
[2] S.L. Pfleeger, and J.M. Atlee, Software Engineering: Theory and Practice (3rd Edn), Pearson
Education, Inc. 2006.
[3] L.J. Zhang, and M. Jeckle, “The next big thing: Web Services composition,” In Jeckle, and
Zhang, Eds, ICWS-Europe, LNCS 2853, Berlin: Springer, 2003, pp. 1-10.
[4] M.P. Singh, and M.N. Huhn , “Service-oriented computing Semantics, Processes,
and
Agents” ,Chichester: John Wiley & Sons, Ltd, 2005.
[5] Z. Sun, and G. Finnie, “Intelligent Techniques in E-Commerce”, A Case-based
Reasoning
Perspective. Berlin, Heidelberg: Springer-Verlag, 2004.
[6] Roy Thomas Fielding, “Architectural styles and the design of network-based software
architectures”,PhD thesis, 2000.
[7] “Web Service Definition Language”. http://www.w3.org/TR/wsdl.

14. 14
[8] C.Pautasso, O. Zimmermann, and F. Leymann. Restful Web Services vs. Big, “Web World
Services: Making the Right Architectural Decision” ,In Proceedings of the 17th International
Wide Web Conference (WWW 2008), Beijing, China, 2008.
[9] OWL Services Coalition. OWL-S: Semantic markup for Web Services, November 2003.
[10] S. A. McIlraith, T. C. Son, and H. Zeng, “Semantic Web Services. In IEEE Intelligent
Systems”, March/April 2001.
[11] M. Gruninger, “ Applications of PSL to semantic Web Services”,In Proceedings of
SWDB'03, The first International Workshop on Semantic Web and Databases, 2003.
[12] R. Hull, M. Benedikt, V. Christophides, and J. Su, “ E-services: A look behind the
curtain”,In Proc. ACM Symp. on Principles of Database Systems, 2003.
[13] D. Berardi, D. Calvanese, G. De Giacomo, M. Lenzerini, and M. Mecella, “Automatic
composition of e-services that export their behaviour”, In Proc. 1st Int. Conf. on Service
Oriented Computing (ICSOC), volume 2910 of LNCS,pages 43{58, 2003. [10]. Vaughan-
Nichols, S.J, “Web Services: beyond the hype”, IEE Comput. 35(2), 18–21 (2002)
[14]. Langdon, C.S, “The state of Web Services” ,IEEE Comput. 36(7), 93–94 (2003)
[15]. W3C:“Simple Object Access Protocol (SOAP)” ,http://www.w3.org/TR/SOAP/ (2003)
[16]. W3C: “Web Services Description Language (WSDL)”, http://www.w3.org/TR/wsdl (2003)
[17]. W3C: “Universal Description, Discovery, and Integration (UDDI)”,http://www.uddi.org
(2003)
[18] D. Berardi, D. Calvanese, G. De Giacomo, M. Lenzerini, and M. Mecella, “Automatic
composition of e-services that export their behavior”, In Proc. 1st Int. Conf. on Service
Oriented Computing (ICSOC), volume 2910 of LNCS,pages 43{58, 2003.
[19] R. Hull, M. Benedikt, V. Christophides, and J. Su. E-services: A look behind the curtain. In
Proc. ACM Symp, on Principles of Database Systems, 2003.
[20] Andrea Maurino, Enrico Mussi , Stefano Modaeri , and Barbara Pernici, “The MAIS
framework for Composite Web Services”, International Journal of Interoperability in
Business Information Systems, 6:32{64, 2007.
[21] Athman Bouguettaya, Quan Z. Sheng, and Florian Daniel, editors, “ Advanced Web
Services”, Springer, 2013.
[22] Aurrecoechea, C., Campbell, A., Hauw, L.: A Survey of QoS Architectures. ACM/Springer
Verlag Multimedia Syst. J. 6(3), 138–151 (1998)
[23] Marchetti, C., Pernici, B., Plebani, P., “A quality model for multichannel adaptive

15. 15
information”, In: WWW04. NewYork,USA (2004)
[24]. Ouzzani, M., Bouguettaya, A.: Efficient access to Web Services IEEE Internet Comput.
8(2), 34–44 (2004)