Define Measures of Performance Sample Clauses

Define Measures of Performance. Define MoPs for at least those system requirements that directly contribute to satisfying URD Measures of Effectiveness (MoE). Record how each requirement will be verified 3.1.4 Verify linkage between user requirements, system requirements and verification for completeness of coverage 3.1.5 Test the SRD to confirm that a system possessing the characteristics defined in the SRD would satisfy the URD within the effectiveness envelope. 3.1.6 Apply version control to all documents so that a change can be analysed for impact and appropriate action taken. Record changes in the SRD, including trade-off decisions and change of needs. Use formal configuration management 3.1.7 Create links between URD and SRD on KEYPAQ/DOORS including suitable Measures of Effectiveness (XXXx) and Measures of Performance (MOPs). 3.1.8 Baseline the SRD for IG. Structured in line with the AOF 5 part recommend structure. 3.2 Develop the SRD in line with the Assessment phase context and maturity in order to baseline the SRD for MG. 3.3 Organise, conduct and record Requirements Working Groups, including identifying appropriate stakeholders to maximise the value of the working group. 3.4
AutoNDA by SimpleDocs

Related to Define Measures of Performance

  • Review of Performance The Board of Directors shall periodically review and evaluate the performance of Employee under this Employment Agreement with Employee.

  • Evaluation of Performance School, in conjunction with Company personnel, is responsible for and shall make arrangements for evaluating Student’s performance during the clinical program.

  • Standards of Performance A. The standard of care for all professional and related services performed or furnished by Contractor under this Agreement will be the care and skill ordinarily used by members of Contractor’s profession practicing under similar conditions and circumstances and in a similar locality.

  • Time of Performance Time for performance of the Scope of Services under this Agreement shall begin with receipt of the Notice to Proceed and end no later than December 31, 2026. Consultant shall complete the tasks described in the Scope of Services, within this time or within such additional time as may be extended by the County.

  • Timeliness of Performance Contractor must provide the Services and Deliverables within the term and within the time limits required under this Contract, pursuant to Detailed Specifications or as specified in the applicable Task Order or Purchase Order. Further, Contractor acknowledges that TIME IS OF THE ESSENCE and that the failure of Contractor to comply with the time limits may result in economic or other losses to the City. Neither Contractor nor its agents, employees or Subcontractors are entitled to any damages from the City, nor is any party entitled to be reimbursed by the City, for damages, charges or other losses or expenses incurred by Contractor by reason of delays or hindrances in the performance of the Services, whether or not caused by the City.

  • Continuity of Performance In the event of a dispute between the Party and the State, each party will continue to perform its obligations under this Agreement during the resolution of the dispute until this Agreement is terminated in accordance with its terms.

  • Covenants of Performance Measurement No interference. Registry Operator shall not interfere with measurement Probes, including any form of preferential treatment of the requests for the monitored services. Registry Operator shall respond to the measurement tests described in this Specification as it would to any other request from an Internet user (for DNS and RDDS) or registrar (for EPP). ICANN testing registrar. Registry Operator agrees that ICANN will have a testing registrar used for purposes of measuring the SLRs described above. Registry Operator agrees to not provide any differentiated treatment for the testing registrar other than no billing of the transactions. ICANN shall not use the registrar for registering domain names (or other registry objects) for itself or others, except for the purposes of verifying contractual compliance with the conditions described in this Agreement. PUBLIC INTEREST COMMITMENTS Registry Operator will use only ICANN accredited registrars that are party to the Registrar Accreditation Agreement approved by the ICANN Board of Directors on 27 June 2013 in registering domain names. A list of such registrars shall be maintained by ICANN on ICANN’s website. (Intentionally omitted. Registry Operator has not included commitments, statements of intent or business plans provided for in its application to ICANN for the TLD.) Registry Operator agrees to perform the following specific public interest commitments, which commitments shall be enforceable by ICANN and through the Public Interest Commitment Dispute Resolution Process established by ICANN (posted at xxxx://xxx.xxxxx.xxx/en/resources/registries/picdrp), which may be revised in immaterial respects by ICANN from time to time (the “PICDRP”). Registry Operator shall comply with the PICDRP. Registry Operator agrees to implement and adhere to any remedies ICANN imposes (which may include any reasonable remedy, including for the avoidance of doubt, the termination of the Registry Agreement pursuant to Section 4.3(e) of the Agreement) following a determination by any PICDRP panel and to be bound by any such determination. Registry Operator will include a provision in its Registry-Registrar Agreement that requires Registrars to include in their Registration Agreements a provision prohibiting Registered Name Holders from distributing malware, abusively operating botnets, phishing, piracy, trademark or copyright infringement, fraudulent or deceptive practices, counterfeiting or otherwise engaging in activity contrary to applicable law, and providing (consistent with applicable law and any related procedures) consequences for such activities including suspension of the domain name. Registry Operator will periodically conduct a technical analysis to assess whether domains in the TLD are being used to perpetrate security threats, such as pharming, phishing, malware, and botnets. Registry Operator will maintain statistical reports on the number of security threats identified and the actions taken as a result of the periodic security checks. Registry Operator will maintain these reports for the term of the Agreement unless a shorter period is required by law or approved by ICANN, and will provide them to ICANN upon request. Registry Operator will operate the TLD in a transparent manner consistent with general principles of openness and non-discrimination by establishing, publishing and adhering to clear registration policies.

  • Resumption of Performance During the period that a Force Majeure Event is subsisting, the Affected Party shall, in consultation with the other Parties, make all reasonable efforts to limit or mitigate the effects of such Force Majeure Event on the performance of its obligations under the PPA. The Affected Party shall also make efforts to resume performance of its obligations under this Agreement as soon as possible and upon resumption, shall notify other Parties of the same in writing. The other Parties shall afford all reasonable assistance to the Affected Party in this regard.

  • Manner of Performance Subject to the provisions of Article XII hereof, the Contractor shall perform all of the Work described in the Statement of Work, or cause such Work to be performed in an efficient and expeditious manner and in accordance with all of the terms and provisions of this Agreement. The Contractor shall perform the Work in accordance with the current professional standards and with the diligence and skill expected for the performance of work of the type described in the Statement of Work. The Contractor shall furnish such personnel and shall procure such materials, machinery, supplies, tools, equipment and other items as may reasonably be necessary or appropriate to perform the Work in accordance with this Agreement.

  • Commencement of Performance This Agreement is of no force and effect until signed by both parties and all JBE-required approvals are secured. Any commencement of performance prior to Agreement approval shall be at Contractor's own risk.

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!