Use Case views Sample Clauses

Use Case views. To illustrate how the architecture solves practical day-to-day situations which our target community may encounter, and to indicate the interaction between components, we identified 15 PICOS Use Cases (PUC) in D4.1. Use cases are used to show the most common interactions. Each use case has been selected because it satisfies an element of the scenarios previously described, and because from experience we know that the trust and privacy issues that PICOS will raise require a detailed level of understanding of user interactions. Of these 15 PUCs, in D4.1 we explored the first nine to better understand the interaction between components. These nine were considered higher priority PUCs because they cover the application of the core privacy and trust management components. Later, WP5 introduced a new use case (referred in D5.1 as PUC 10) to explain how privileges are managed. This is now included in this D4.2 as PUC 16, and described more fully in Appendix A. Further use cases (or refinements to existing use cases) arose from the trials, and these are also included and referenced as PUCs 17-23. They relate only to the online gaming community. (Note that the order of this list does not imply any priority.)
Sample 1
AutoNDA by SimpleDocs

Related to Use Case views

  • Use Cases Subscription Services are provided for Software only when used for its supported purpose (“Use Case”). The Use Case determines which Subscription is required and what fees are charged. If you use or deploy the Software in a manner contrary to a supported Use Case, you are responsible for purchasing the appropriate Subscription(s) to cover such usage. For example, if you are using a Red Hat Enterprise Linux Desktop Subscription as a server, you are obligated to purchase a Red Hat Enterprise Linux Server Subscription.

  • Supported Use Cases Subscription Services are provided for Red Hat Satellite Server, Red Hat Satellite Capsule and Red Hat Satellite Proxy Management Subscriptions only when used for their supported purposes (“Use Case”) in accordance with the terms of this Exhibit and Table 2 below.

  • Software Use Case Red Hat Enterprise Linux Developer Suite Subscription Services for Red Hat Enterprise Linux Developer Suite are available for Development Purposes only.

  • Early Construction of Base Case Facilities Developer may request Connecting Transmission Owner to construct, and Connecting Transmission Owner shall construct, subject to a binding cost allocation agreement reached in accordance with Attachment S to the ISO OATT, including Section 25.8.7 thereof, using Reasonable Efforts to accommodate Developer’s In-Service Date, all or any portion of any System Upgrade Facilities or System Deliverability Upgrades required for Developer to be interconnected to the New York State Transmission System which are included in the Base Case of the Class Year Study for the Developer, and which also are required to be constructed for another Developer, but where such construction is not scheduled to be completed in time to achieve Developer’s In-Service Date.

  • Case Management Prompt resolution of any dispute is important to both parties; and the parties agree that the arbitration of any dispute shall be conducted expeditiously. The arbitrators are instructed and directed to assume case management initiative and control over the arbitration process (including scheduling of events, pre-hearing discovery and activities, and the conduct of the hearing), in order to complete the arbitration as expeditiously as is reasonably practical for obtaining a just resolution of the dispute.

  • Skilled Nursing Facilities a. The following Health Care Services may be Covered Services when you are a patient in a Skilled Nursing Facility: i. room and board;

  • Meeting Space and Facilities The Employer’s offices and facilities may be used by the Union to hold meetings, subject to the agency’s policy, availability of the space and with prior authorization of the Employer.

  • ROAD DIMENSIONS Purchaser shall perform road work in accordance with the dimensions shown on the TYPICAL SECTION SHEET and the specifications within this road plan.

  • Utilization Scale STATE shall scale logs or portions of logs that are broken, wasted, or not removed by PURCHASER due to: (1) improper felling or bucking of the logs; (2) failure to remove the logs prior to deterioration; and (3) logs remaining on the timber sale area after completion of logging, provided the logs were merchantable prior to breakage or wastage. Material used to meet down material requirements in the section titled, "Reserved Timber," shall not be considered for utilization scale. PURCHASER shall pay for the logs at the contract price designated in Section 44. STATE shall notify PURCHASER of the volume of logs so scaled. Payment shall be considered due on such volume as if the logs were removed on the date of said notification. In the event PURCHASER disagrees with the findings made by STATE under this section, PURCHASER may furnish scaling by a third-party scaling organization acceptable to STATE. Costs and expenses of such third party shall be paid for by PURCHASER, and the findings of the third party shall be final.

  • Excellent Above Average Satisfactory Needs Improvement Unsatisfactory 5 4 3 2 1 5. The instructor demonstrates knowledge of the subject matter.

Time is Money Join Law Insider Premium to draft better contracts faster.