Service request scenario

Figure 1 depicts the basic scenario we consider. We are given different parties that interact with each other to offer services. A party can act both as a server and a client and each party has i) a set of services it provides and ii) a portfolio of properties (attributes) that the party enjoys. Access restrictions to the services are expressed by policies that specified the properties that a requester should enjoy to gain access to the services. The services are meant to offer certain functionalities that depend on the input parameters supplied by its users. Often input parameters must fulfill certain conditions to assure correct behavior of a... 

To compare these strategies the following scenario was set up. A client requests a service from a server, which in turn needs information from three other system components to provide this service. This information is transmitted as a sequence of strings, using polling and caching. 

Thus, a method for assessing and choosing tools and services with respect to their quality was developed [265]. The term quality, or Quality of Service, refers to non-functional properties of a service, for instance cost, performance, or availability. Suitable services must be found by the management layer upon request. It is of further substantial benefit if applications and services, such as simulators or communication tools, can be selected from a set of interchangeable instances. This is very likely to be the case in collaborative distributed scenarios. 

With our Supply Chain Simulation software (Fig. 13) you pretend to produce the desired services and products requested by your customers. In doing so, you simulate the future order and material flows in your enterprise. But, you only do it in the form of a what if scenario. 

---