Checking the Programmer’s Code Sample Clauses

Checking the Programmer’s Code. For a given program, we first check that each template referred from the program is also mentioned in the contract directory, corresponding to §4. The remaining checks require the construction of summary graphs for each expression in show statements. These are obtained by constructing the dummy template directory T (C), as described in Section 4.3, and then running the JWIG analyzer on this structure. For every statement of the form: show H as P ; this provides a summary graph GH . To check §5, we inspect that P occurs as a page in the contract, construct a summary graph GP,C,T (C) as in Section 5.2 but using the dummy templates, and then check that GH ⊆ GP,C,T (C) Inclusion on summary graphs is determined on the set of edges, where po- tentially open gaps are viewed as edges to a special “ε” template, and nodes representing string sets are compared by set inclusion. Finally, the check of fields in receive expressions, §6, is simply performed by the JWIG analyzer using the algorithm described in [9].
Sample 1See All (4)
AutoNDA by SimpleDocs

Related to Checking the Programmer’s Code

  • Procedures for Providing NP Through Full NXX Code Migration Where a Party has activated an entire NXX for a single Customer, or activated at least eighty percent (80%) of an NXX for a single Customer, with the remaining numbers in that NXX either reserved for future use by that Customer or otherwise unused, if such Customer chooses to receive Telephone Exchange Service from the other Party, the first Party shall cooperate with the second Party to have the entire NXX reassigned in the LERG (and associated industry databases, routing tables, etc.) to an End Office operated by the second Party. Such transfer will be accomplished with appropriate coordination between the Parties and subject to appropriate industry lead times for movements of NXXs from one switch to another. Neither Party shall charge the other in connection with this coordinated transfer.

  • Compliance with Executive Orders Concerning Ethics The Contractor warrants that he and his firm have complied in all respects with the Governor’s Executive Orders concerning ethics matters, including, but not limited to, Executive Order dated January 13, 2003 (establishing Code of Ethics for Executive Branch Officers and Employees, including provisions governing former officers and employees); Executive Order dated October 1, 2003 (governing vendors to state agencies and disclosure and registration of lobbyists); and O.C.G.A. Sections 21-5-70(5), 21-5-71 and 21-5-73, all as amended effective January 9, 2006 (requiring registration and disclosure filings by state agency vendor lobbyists). In this regard, the Contractor certifies that any lobbyist employed or retained by the Contractor or his firm has both registered and made the required disclosures required by the Executive Orders, as amended.

  • Workstation/Laptop encryption All workstations and laptops that process and/or store DHCS PHI or PI must be encrypted using a FIPS 140-2 certified algorithm which is 128bit or higher, such as Advanced Encryption Standard (AES). The encryption solution must be full disk unless approved by the DHCS Information Security Office.

  • Monitoring and Management Information C10.1 The Contractor shall comply with the monitoring arrangements set out in the Monitoring Schedule including, but not limited to, providing such data and information as the Contractor may be required to produce under the Contract.

  • SERVICE MONITORING, ANALYSES AND ORACLE SOFTWARE 11.1 We continuously monitor the Services to facilitate Oracle’s operation of the Services; to help resolve Your service requests; to detect and address threats to the functionality, security, integrity, and availability of the Services as well as any content, data, or applications in the Services; and to detect and address illegal acts or violations of the Acceptable Use Policy. Oracle monitoring tools do not collect or store any of Your Content residing in the Services, except as needed for such purposes. Oracle does not monitor, and does not address issues with, non-Oracle software provided by You or any of Your Users that is stored in, or run on or through, the Services. Information collected by Oracle monitoring tools (excluding Your Content) may also be used to assist in managing Oracle’s product and service portfolio, to help Oracle address deficiencies in its product and service offerings, and for license management purposes.

  • LIMITATIONS ON REVERSE ENGINEERING, DECOMPILATION AND DISASSEMBLY You may not reverse engineer, decompile, or disassemble the Software, except and only to the extent that such activity is expressly permitted by applicable law notwithstanding this limitation.

  • HOW WE MAY USE YOUR PERSONAL INFORMATION 8.1 We will use the personal information You provide to Us to:

  • Malicious Use of Orphan Glue Records Registry Operator shall take action to remove orphan glue records (as defined at xxxx://xxx.xxxxx.xxx/en/committees/security/sac048.pdf) when provided with evidence in written form that such records are present in connection with malicious conduct.

  • Cooperation on Preventing End User Fraud The Parties agree to cooperate fully with one another to investigate, minimize, prevent, and take corrective action in cases of fraud.

  • Access Toll Connecting Trunk Group Architecture 9.2.1 If CBB chooses to subtend a Verizon access Tandem, CBB’s NPA/NXX must be assigned by CBB to subtend the same Verizon access Tandem that a Verizon NPA/NXX serving the same Rate Center Area subtends as identified in the LERG.

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