A Study on Testing of Service Oriented Architecture

Abstract services are combined via orchestration engines and are controlled to implement business processes. These services may be internal to the organization or COTS, which raises the problem of verifying the quality of the service. The problem currently faced by SOA developers is the lack of a system to guarantee third party services. Service providers can provide explanations about services, but they need to be verified. Due to an increase in traffic, data or other factors, even service providers may not know that their services have been downgraded over time.

According to IBM, Service Oriented Architecture (SOA) is "a business-centric IT architecture approach that supports business integration into linked repetitive business tasks or services." Service-oriented architecture is basically a collection of services. . These services are loosely coupled and implemented in a standard way. In other words, callers do not need to know the service provider's technology or location. For example, if you need to create an invoice, another department or business application can call Create Invoice as a service.

The service-oriented architecture (SOA) can be categorized as follows; the architecture style as a combination of unique functions of the executive architecture supports service-oriented. SOA services are reusable components used in business processes. This is a logical representation of repeatable business activities with specified results and in some cases consists of other services. (Mark Colan, 2004; Barbara Reed, 2008)

Service Oriented Architecture (SOA): A computer system that describes the concept of software architecture that defines the use of services that support business needs. With SOA, resources can be used as an independent service accessed in a standardized way for other participants in the network to use. Most SOA definitions identify implementation of Web services (using SOAP and WSDL), but you can use any service-based technology to implement SOA. Seven Waste: For many years, developed by Toyota's chief engineer, Ohno Taichi, he is a central innovator in Toyota's quality system. They are: 1) excessive waste, 2) waste of waste, 3) waste of transport, 4) waste of inappropriate handling, 5) waste of unnecessary stock, 6) waste of unnecessary movement, 7) waste of faults .