Validating Requirements Sample Clauses

Validating Requirements. This section does not describe in detail how to create functional test cases from scenarios. Deliverables of task 6.2 will provide a close description of test cases. In eDIANA, the importance of this step is significant. Often the testers are given a printout of a scenario specification and then perform ad hoc manual testing. However, if we neglect formal creation of test cases in eDIANA, we may end up with poor universality of the eDIANA platform. Just as general information, we can mention that four steps are involved in test case creation: 1. Identify variables for each scenario step (input information, multiple selection options, etc.) 2. Identify significantly different options for each variable. Options are significantly different if they may trigger different system behaviour. These different options will trigger different processing flows. 3. Combine options to be tested into test cases. They must be combined in the sequence of test case steps. A technique is to use matrix mapping variables and test cases. For each variable, we must enter all the options that need to be tested for this variable.
AutoNDA by SimpleDocs

Related to Validating Requirements

  • Testing Requirements 12.1. Workplaces - 12.2. On workplaces where the value of the Commonwealth’s contribution to the project that includes the building work is at least $5,000,000, and represents at least 50% of the total construction project value or the Commonwealth’s contribution to the project that includes the building work is at least $10,000,000 (irrespective of its proportion of the total construction project value) the following minimum testing requirements must be adhered to.

  • Forecasting Requirements 19.5.1 The Parties shall exchange technical descriptions and forecasts of their Interconnection and traffic requirements in sufficient detail necessary to establish the Interconnections necessary for traffic completion to and from all Customers in their respective designated service areas.

  • Operating Requirements Any operating and technical requirements that may be applicable due to Regional Transmission Organization, Independent System Operator, control area, or the Connecting Transmission Owner’s requirements, including those set forth in the Small Generator Interconnection Agreement. Operating Requirements shall include Applicable Reliability Standards.

  • Posting Requirements Seller shall post the Development Security in accordance with the following terms and conditions: (i) Seller shall post one-half of the Development Security within thirty

  • Screening Requirements Practitioner shall ensure that all prospective and current Covered Persons are not Ineligible Persons, by implementing the following screening requirements. a. Practitioner shall screen all prospective Covered Persons against the Exclusion List prior to engaging their services and, as part of the hiring or contracting process, shall require such Covered Persons to disclose whether they are Ineligible Persons.‌ b. Practitioner shall screen all current Covered Persons against the Exclusion List within 30 days after the Effective Date and on a monthly basis thereafter.‌ c. Practitioner shall require all Covered Persons to disclose immediately if they become an Ineligible Person.‌ Practitioner shall maintain documentation in order to demonstrate that Practitioner: (1) has checked the Exclusion List (i.e., a print screen of the search results) and determined that its Covered Persons are not Ineligible Persons; and (2) has required its Covered Persons to disclose if they are an Ineligible Person. Nothing in this Section III.D affects Practitioner’s responsibility to refrain from (and liability for) billing Federal health care programs for items or services furnished, ordered, or prescribed by an excluded person. Practitioner understands that items or services furnished by excluded persons are not payable by Federal health care programs and that Practitioner may be liable for overpayments and/or criminal, civil, and administrative sanctions for employing or contracting with an excluded person regardless of whether Practitioner meets the requirements of Section III.D.

  • Staffing Requirements Licensee will be in full compliance with the main studio staff requirements as specified by the FCC.

  • Training Requirements Grantee shall: A. Authorize and require staff (including volunteers) to attend training, conferences, and meetings as directed by DSHS; B. Appropriately budget funds in order to meet training requirements in a timely manner, and ensure that staff and volunteers are trained as specified in the training requirements listed at xxxxx://xxx.xxxx.xxxxx.xxx/hivstd/training/ and as otherwise specified by DSHS. Grantee shall document that these training requirements are met; and C. Ensure that staff hired for HIV and syphilis testing are trained to perform blood draws within three (3) months of employment.

  • Monitoring Requirements This Schedule sets out the contract management requirements which are applicable to the delivery of the Services.

  • Bonding Requirements The Contractor is required to furnish a performance bond on the form in a form acceptable to the City, in a sum of not less than [insert bonding level] of the annual amount of the contract to guarantee the faithful performance of this contract. The bond must be approved as to sufficiency and qualifications of the surety by the Controller.

  • Reporting Requirements The Company, during the period when the Prospectus is required to be delivered under the 1933 Act or the 1934 Act, will file all documents required to be filed with the Commission pursuant to the 1934 Act within the time periods required by the 1934 Act and the 1934 Act Regulations.

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