The term Web services describes a standardized way of integrating Web-based applications using the XML, SOAP, WSDL and UDDI open standards over an Internet protocol backbone. XML is used to tag the data, SOAP is used to transfer the data, WSDL is used for describing the services available and UDDI is used for listing what services are available. Used primarily as a means for businesses to communicate with each other and with clients, Web services allow organizations to communicate data without intimate knowledge of each other's IT systems behind the firewall.
It is unwise to attempt to transfer a domain immediately before it expires. In some cases, a transfer can take up to 14 days, meaning that the transfer may not complete before the registration expires. This could result in loss of the domain name registration and failure of the transfer. To avoid this, end users should either transfer well before the expiration date, or renew the registration before attempting the transfer.
In 1993 the U.S. Department of Commerce, in conjunction with several public and private entities, created InterNIC to maintain a central database that contains all the registered domain names and the associated IP addresses in the U.S. (other countries maintain their own NICs (Network Information Centers) -- there's a link below that discusses Canada's system, for example). Network Solutions, a member of InterNIC, was chosen to administer and maintain the growing number of Internet domain names and IP addresses. This central database is copied to Top Level Domain (TLD) servers around the world and creates the primary routing tables used by every computer that connects to the Internet.
Functional and non-functional testing of Web services is done with the help of WSDL parsing. Regression testing is performed by identifying the changes made to upgrade software. Web service regression testing needs can be categorized in three different ways, namely, changes in WSDL, changes in the code, and selective re-testing of operations. We can capture the above three needs in three intermediate forms of Subset WSDL, namely, Difference WSDL (DWSDL), Unit WSDL (UWSDL), and Reduced WSDL (RWSDL), respectively. These three Subset WSDLs are then combined to form Combined WSDL (CWSDL) that is further used for regression testing of the Web service. This will help in Automated Web Service Change Management (AWSCM), by performing the selection of the relevant test cases to construct a reduced test suite from the old test suite. 
Web services are almost like normal a web page. The difference is that they are formatted to make it very easy for a program to pull data from the page, to the point of probably not using any HTML. They generally also are more reliable as to the consistency of the format, may use a different formal process to define the content such soap or raw xml, and there is often also a descriptor document that formally defines the structure for the data.
A developer using a top-down model writes the WSDL document first and then uses a code generating tool to produce the class skeleton, to be completed as necessary. This model is generally considered more difficult but can produce cleaner designs and is generally more resistant to change. As long as the message formats between the sender and receiver do not change, changes in the sender and receiver themselves do not affect the Web service. The technique is also referred to as contract first since the WSDL (or contract between sender and receiver) is the starting point.
"All the standard Web Services works using following components:" ... the problem with this answer is that it suggests that web services do or must operate within the SOAP/WSDL mechanism. This is inaccurate. Representational State Transfer (REST) is another very popular paradigm for implementing web services. Some major websites have deprecated their SOAP services in favor of REST web services. – scottb Jul 7 '15 at 15:50