Use Cases definition

Use Cases means the sub-processes or sub-services set forth in Annex 2 to Exhibit A, the purpose of which is to assist the Parties to analyze the demarcation lines of the Services (as defined in Annex 1 to Exhibit A). Each Use Case is a subset of a Service describing a sequence of actions that represents a business process.

Use Cases three use case scenarios.

Use Cases means specific uses of the CRISP Health Information Exchange identified from time-to-time in accordance with this Participation Agreement and this Addendum and listed on Exhibit D (each, a “Use Case”). A defined term, indicated by capitalization of the first letter(s), not otherwise set forth above or elsewhere in the Agreement shall have the meaning stated in HIPAA or, if not defined in HIPAA, assigned by other Applicable Law.

Use Cases. This sub-section presents use cases that used the data contained in the portal for a valuable purpose (e.g., a study on how the performance of the small ports of a region have improved through time thanks to the data provided by the portal). Pilot Projects This section is containing the info about the various pilot projects (or pilots). It is going to be organised in two tiers. The former one is presenting the macro-themes of the various pilots. The projects are divided into macro-themes according to their features and purposes (i.e. Planning&Management, E&E aspects, T&K aspects, ICT&Services, Business Aspects). While the latter is the tier where the various pilots are presented. In particular, it is going to contain a brief description of the project, its expected and actual output, the work progress, and the experiences and know-how developed. Regulations Present the regulation that the various stakeholders need to follow and recommendations on how to conform to it. This section is presenting the territory of the Adriatic basing. It is going to composed of two tools. The former is a map with different layers that gives to possibility to switch from one player to another and to show different data. The latter is a tool that allows to run queries and find specific data according to the one contained in the various layers of the map. Map The map of the territory is composed of different layers that presents the various features of the sea. It is possible to open multiple layers at the same time and see how the various data displayed are related to each other. The map is going to initially show the entire Adriatic basin with a satellite view, according to the layer(s) chosen various info are going to appear. There is the possibility to zoom and see the features of a specific location. The layers are presented below: This layer is a map with the location of the various small ports. Each port is going to be identified with a coloured dot. When the user clicks on the small port, the user gets access to its information that are showed on a window that is going to open on the side (Figure 3).

Use Cases. Means the use case or cases which are specifically agreed in writing between Boomerang and the Customer which identify the specific scope and nature of the use of the Services and Documentation that can be made by the Customer and which are set out in the Service Profile.

Use Cases. In this section, we present SLA-Oriented projects and algorithms as academy use cases. SLA-Oriented Resource Allocation for Data Centers and Cloud Computing Systems: The Cloud Computing and Distributed Systems (CLOUDS) Laboratory, at the University of Melbourne has proposed the use of market-based resource management to support utility-based resource management for cluster computing (▇▇▇ ▇. ▇. et. al. 2005) (▇▇▇ ▇. ▇. et. al. 2007). The initial work successfully demonstrated that market-based resource allocation strategies are able to deliver better utility for users than traditional system-centric strategies. However, early research focused on satisfying only two static Quality of Ser- vice (QoS) parameters: the deadline for completing a service request and the budget that the consumer is willing to pay for completing the request before the deadline. In the commercial computing environment, there are other critical QoS parameters to consider in a service request, such as reliability and trust/security. In particular, QoS requirements cannot be static and need to be dynamically updated over time due to continuing changes in business operations and operating environments. SLA@SOI: A European Union funded Framework 7 research project, SLA@SOI (SLA@SOI project), is researching aspects of multi-level, multi-provider SLAs within service-oriented infrastructure and cloud computing. Currently, this project aims to build an ad-hoc architecture and integration approach for a ba- sic SLA management framework. It provides a major milestone for the further evolution towards a ser- SLA based Management and Scheduling: ▇▇▇ et. al. (2010) propose profit-driven SLA based schedul- ing algorithms in Clouds to maximize the profit for service providers. The application model used in this work can be classified as SaaS and PaaS. The service types supported by their algorithm are dependent services, which mean one sub-service can not start until the prerequisite services are completed. However, their work does not support multiple providers and full simulation configuration is not available. We rec- ommend possible future research direction is SLA management with multiple providers, since it is re- quired for emerging research in InterCloud.We define InterCloud as multiple Cloud providers with peer agreement to support collaborative activities.

Use Cases means how the DER technology is applied in the customer and/or market setting to deliver value to the customer, market participant, and/or electricity system

Use Cases means the Test Drive Analysis objectives in the Scope of Work

Use Cases means the use cases as set out in Clause A.9.5 of Part 2, Section B.