Req UR - User Requirement Sample Clauses

Req UR - User Requirement. ‌ These are the “user requirements”, which are sets of features that the CMF should support in order to help the user in the experiment accomplishment. Requirement XXXXXX FOAM OMF ProtoGENI I&M XXXXXX I&M OMF I&M ProtoGENI Req UR01 Req UR02 Req UR03 Req UR04 Req UR05 Req UR06 Req UR07 Req UR08 Req UR09 Req UR10 Req UR11 Req UR12 Req UR13 Req UR14 It follows a brief discussion about user requirements not supported by specific CMFs. UR8 - This requirement is about the need of experiment snapshots (pause and resume for later use). Currently, from the point of view of XXXXXX, the VT_Manager sends commands to a Xen daemon. Being so, it is intrinsically supportable but this is not in the interface neither it is automatized. Since the experimenter could do it manually, we review the requirement lowering the need from MUST to SHOULD and we will incorporate changes in the VT_Manager or either other CMF tools that evolve. UR9 - In XXXXXX, growing or shrinking resources can be done at any time, for example, one can redefine the flowspace or network resources. Regarding VMs, it is always possible to add/delete VMs, although, it could be not possible to change the VM configuration (HD size, RAM, once created). However, restarting the slice is not the same as restarting the experiment. UR10 - In XXXXXX 0.1, there exist the possibility of storing the experiment data through a remote access by the experimenter. However, since the virtual machine (end-host) is based on a template, at every new experiment it generates a VM zeroed from the template. Thus, at every new restart tools and results could be lost. This functionality is planned to be incorporated in next releases of VT_Manager where each user could have his own VM and storage block. Other possibility is to document that the transfer of results should be done by the experimenter as the part of the experiment cycle. UR12 - XXXXXX supports this requirement partially (high level description of projects, slices and flowspaces). As such, a more detailed documentation could be done manually, since XXXXXX system differently than OMF and ProtoGENI has no formal configuration of topology and order of events as it is done in ns-2 format (protoGENI) and OEDL format (OMF).
Sample 1
AutoNDA by SimpleDocs

Related to Req UR - User Requirement

  • Customer Requirements ▪ Seller shall comply with the applicable terms and conditions of any agreements between Buyer and Xxxxx’s Customer (the “Customer Purchase Orders”) pursuant to which Buyer agreed to sell to Buyer’s Customer products or assemblies which incorporate the goods provided by Seller hereunder. This provision specifically includes costs and obligations imposed by warranty programs instituted by the original equipment manufacturer that ultimately purchases Buyer’s products that incorporate the goods sold by Seller if applicable to Buyer under the terms of the Customer Purchase Order. ▪ If Buyer is not acting as a Tier One supplier, the defined term “Customer Purchase Order” shall also include the terms and conditions of the original equipment manufacturer that ultimately purchases Buyer’s product that incorporates the goods or services sold by Seller. ▪ Seller will be responsible to ascertain how the disclosed terms affect Seller’s performance under the Purchase Order. ▪ By written notice to Seller, Buyer may elect to disclose and have the provisions of the Customer’s Purchase Orders prevail over any term of the Purchase Order at any time.

  • W-9 Requirement Alongside a signed copy of this Agreement, Grantee will provide Florida Housing with a properly completed Internal Revenue Service (“IRS”) Form W-9. The purpose of the W-9 form is to document the SS# or FEIN# per the IRS. Note: W-9s submitted for any other entity name other than the Grantee’s will not be accepted.

  • Computer Requirements You are responsible for obtaining, installing, maintaining and operating all software, hardware, or other equipment necessary (collectively, “Access Device Systems”) necessary for you to access and use the Service. This responsibility includes, without limitation, your utilizing up to date web-browsers and Access Devices and the best commercially available encryption, antivirus, anti-spyware, and Internet security software. You are additionally responsible for obtaining Internet service via an Internet service provider of your choice, for any and all fees imposed by such Internet service provider, and any associated communications service provider charges. You acknowledge that there are certain security, corruption, transmission error and access availability risks associated with using open networks such as the Internet and you hereby expressly assume such risk, including, but not limited to those we may disclose in our educational materials. You acknowledge that you are responsible for data security of the Systems used to access the Service, and for the transmission and receipt of information using such System. You acknowledge that you have requested the Service for your convenience, have made your own independent assessment of the adequacy of the Internet and Systems and that you are satisfied with that assessment. The Bank shall have no responsibility for failures, interruption or other defects in the Services, which arise from the malfunction or failure of the Internet or your Systems nor are we responsible for notifying you of any upgrades, fixes, or enhancements to, or for providing technical or other support for your Systems. The Bank may add to, modify, or replace software programs used in conjunction with providing the Services under this Agreement at its sole discretion and without notice, provided Services rendered to you are not substantially negatively affected or obligations altered.

  • Child Abuse Reporting Requirement Grantee will:

  • System Requirements Apple Software is supported only on Apple-branded hardware that meets specified system requirements as indicated by Apple.

  • Minimum System Requirements The following summarizes the minimum office system requirements for all Contractors and Architect/Engineer to possess in order to participate. It is the responsibility of all Contractors and Architect/Engineer to possess these minimum requirements at no additional cost to Princeton University.

  • Accessibility Requirements Under Tex. Gov’t Code Chapter 2054, Subchapter M, and implementing rules of the Texas Department of Information Resources, the System Agency must procure Products and services that comply with the Accessibility Standards when those Products are available in the commercial marketplace or when those Products are developed in response to a procurement solicitation. Accordingly, Grantee must provide electronic and information resources and associated Product documentation and technical support that comply with the Accessibility Standards.

  • Federal Medicaid System Security Requirements Compliance Party shall provide a security plan, risk assessment, and security controls review document within three months of the start date of this Agreement (and update it annually thereafter) in order to support audit compliance with 45 CFR 95.621 subpart F, ADP System Security Requirements and Review Process.

  • Power Factor Requirement Consistent with Section 4.7 of Appendix 2 to this ISA, the power factor requirement is as follows: The Generation Interconnection Customer shall design its non-synchronous Customer Facility with the ability to maintain a power factor of at least 0.95 leading to 0.95 lagging measured at the high-side of the facility substation transformers.

  • Data Universal Number System (DUNS) number Requirement Grantee will provide their valid DUNS number contemporaneous with execution of this Agreement.

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