Software Development Life Cycle Policy Sample Clauses

Software Development Life Cycle Policy. The Software Development Life Cycle Policy requires any Contractor developing software for the State to work with DTS in implementing a Software Development Lifecycle (SDLC) that addresses key issues of security, accessibility, mobile device access, and standards compliance. DTS Policy 4000-0004, Change Management Policy: Per the Change Management Policy, any Goods or Custom Deliverables furnished or Services performed by Contractor which have the potential to cause any form of outage or to modify DTS’s or the State of Utah’s infrastructure must be reviewed by the DTS Change Management Committee. Following this notification, any outages or Data Breaches which are a direct result of Contractor’s failure to comply with DTS instructions and policies following notification will result in Contractor’s liability for any and all damages resulting from or associated with the outage or Data Breach.
Sample 1Sample 2Sample 3See All (10)
AutoNDA by SimpleDocs
Software Development Life Cycle Policy. A Contractor developing software for the State shall work with DTS in implementing a Software Development Lifecycle (SDLC) that addresses key issues of security, accessibility, mobile device access, and standards compliance. DTS Policy 4000-0004, Change Management Policy: Goods or Custom Deliverables furnished or Services performed by Contractor which have the potential to cause any form of outage or to modify DTS’s or the State of Utah’s infrastructure must be reviewed by the DTS Change Management Committee. Any outages or Data Breaches which are a result of Contractor’s failure to comply with DTS instructions and policies will result in Contractor’s liability for all damages resulting from or associated with the outage or Data Breach. CONFIDENTIALITY: This section does not apply to records where disclosure is regulated under Federal or State laws. GRAMA applies only to records, therefore if information (other than Non-Public Data, Public Health Information, or State Data) is disclosed orally by either party which either party wishes to remain confidential, then each party shall adhere to the following: Each party will: (a) limit disclosure of any such information to Authorized Persons who have a need to know such information in connection with the current or contemplated business relationship between the parties to which this Contract relates, and only for that purpose; (b) advise its Authorized Persons of the proprietary nature of the information and of the obligations set forth in this Contract and require such Authorized Persons to keep the information confidential; (c) shall keep all information strictly confidential by using a reasonable degree of care, but not less than the degree of care used by it in safeguarding its own confidential information; and (d) not disclose any such information received by it to any third parties, except as otherwise agreed to in writing by the disclosing party. Each party will notify the other of any misuse or misappropriation of such information that comes to said party’s attention. This duty of confidentiality shall be ongoing and survive the Contract Period.
Sample 1Sample 2Sample 3See All (5)

Related to Software Development Life Cycle Policy

  • Software Development Software designs, prototypes, and all documentation for the final designs developed under this agreement must be made fully transferable upon direction of NSF. NSF may make the software design, prototype, and documentation for the final design available to competitors for review during any anticipated re-competition of the project.

  • Programming Phase Schematic Design Phase: 2.2.1.3. Design Development Phase:

  • Flexible Work Schedule A flexible work schedule is any schedule that is not a regular, alternate, 9/80, or 4/10 work schedule and where the employee is not scheduled to work more than 40 hours in the "workweek" as defined in Subsections F. and H., below.

  • Software License Terms (a) Software that is made available by a Provider to Recipient in connection with any Service (any such Software being referred to herein as “TSA-Licensed Software”) provided hereunder will be subject to the terms set forth in this Section 3.5 except as otherwise provided in the applicable Service Schedule. The Provider hereby grants to the Recipient a non-exclusive, non-transferable license to use, in object code form, any TSA-Licensed Software that is made available by the Provider pursuant to a Service Schedule. For the avoidance of doubt, the Provider that makes available any TSA-Licensed Software in connection with the provision of any Service retains the unrestricted right to enhance or otherwise modify such TSA-Licensed Software at any time, provided that such enhancements or other modifications do not disrupt the provision of such Service to the Recipient. (b) The Recipient may not exceed the number of licenses, agents, tiers, nodes, seats, or other use restrictions or authorizations, if any, specified in the applicable Service Schedule. Some TSA-Licensed Software may require license keys or contain other technical protection measures. The Recipient acknowledges that the Provider may monitor the Recipient’s compliance with use restrictions and authorizations remotely, or otherwise. If the Provider makes a license management program available which records and reports license usage information, the Recipient agrees to appropriately install, configure and execute such license management program. (c) Unless otherwise permitted by the Provider, the Recipient may only make copies or adaptations of the TSA-Licensed Software for archival purposes or when copying or adaptation is an essential step in the authorized use of TSA-Licensed Software. If the Recipient makes a copy for backup purposes and installs such copy on a backup device, the Recipient may not operate such backup installation of the TSA-Licensed Software without paying an additional license fee, except in cases where the original device becomes inoperable. If a copy is activated on a backup device in response to failure of the original device, the use on the backup device must be discontinued when the original or replacement device becomes operable. The Recipient may not copy the TSA-Licensed Software onto or otherwise use or make it available on, to, or through any public or external distributed network. Licenses that allow use over the Recipient’s intranet require restricted access by authorized users only. (d) The Recipient must reproduce all copyright notices that appear in or on the TSA-Licensed Software (including documentation) on all permitted copies or adaptations. Copies of documentation are limited to internal use. (e) Notwithstanding anything to the contrary herein, certain TSA-Licensed Software may be licensed under the applicable Service Schedule for use only on a computer system owned, controlled, or operated by or solely on behalf of the Recipient and may be further identified by the Provider by the combination of a unique number and a specific system type (“Designated System”) and such license will terminate in the event of a change in either the system number or system type, an unauthorized relocation, or if the Designated System ceases to be within the possession or control of the Recipient. (f) The Recipient will not modify, reverse engineer, disassemble, decrypt, decompile, or make derivative works of the TSA-Licensed Software. Where the Recipient has other rights mandated under statute, the Recipient will provide the Provider with reasonably detailed information regarding any intended modifications, reverse engineering, disassembly, decryption, or decompilation and the purposes therefor. (g) The Recipient may permit a consultant or subcontractor to use TSA-Licensed Software at the licensed location for the sole purpose of providing services to the Recipient. (h) Upon expiration or termination of the Service Schedule under which TSA-Licensed Software is made available, the Recipient will destroy the TSA-Licensed Software. The Recipient will remove and destroy or return to the Provider any copies of the TSA-Licensed Software that are merged into adaptations, except for individual pieces of data in the Recipient’s database. The Recipient will provide certification of the destruction of TSA-Licensed Software, and copies thereof, to the Provider. The Recipient may retain one copy of the TSA-Licensed Software subsequent to expiration or termination solely for archival purposes. (i) The Recipient may not sublicense, assign, transfer, rent, or lease the TSA-Licensed Software to any other person except as permitted in this Section 3.5. (j) The Recipient agrees that the Provider may engage a third party designated by the Provider and approved by the Recipient (such approval not to be unreasonably withheld) to audit the Recipient’s compliance with the Software License terms. Any such audit will be at the Provider’s expense, require reasonable notice, and will be performed during normal business hours. Such third party will be required to execute a non-disclosure agreement that restricts such third party from disclosing confidential information of the Recipient to the Provider, except to the extent required to report on the extent to which the Recipient is not in compliance with the Software License terms.

  • COMMERCIAL COMPUTER SOFTWARE If performance involves acquisition of existing computer software, the following Company Exhibit is incorporated by reference: CCS Commercial Computer Software License (Company – July 2010).

  • Computer Equipment Recycling Program If this Contract is for the purchase or lease of computer equipment, then Contractor certifies that it is in compliance with Subchapter Y, Chapter 361 of the Texas Health and Safety Code related to the Computer Equipment Recycling Program and the Texas Commission on Environmental Quality rules in 30 TAC Chapter 328.

  • Software License Agreement 1) Customers acquiring software licenses under the Contract shall hold, use and operate such software subject to compliance with the Software License Agreement set forth in Appendix D of this Contract. No changes to the Software License Agreement terms and conditions may be made unless previously agreed to between Vendor and DIR. Customers may not add, delete or alter any of the language in Appendix D; provided however, that a Customer and Vendor may agree to additional terms and conditions that do not diminish a term or condition in the Software License Agreement, or in any manner lessen the rights or protections of Customer or the responsibilities or liabilities of Vendor. Order Fulfiller shall make the Software License Agreement terms and conditions available to all Customers at all times. 2) Compliance with the Software License Agreement is the responsibility of the Customer. DIR shall not be responsible for any Customer’s compliance with the Software License Agreement. If DIR purchases software licenses for its own use under this Contract, it shall be responsible for its compliance with the Software License Agreement terms and conditions.

  • First Source Hiring Program Contractor must comply with all of the provisions of the First Source Hiring Program, Chapter 83 of the San Francisco Administrative Code, that apply to this Agreement, and Contractor is subject to the enforcement and penalty provisions in Chapter 83.

  • Technology Research Analyst Job# 1810 General Characteristics

  • Drug-Free Workplace Policy Consultant shall provide a drug-free workplace by complying with all provisions set forth in City’s Council Policy 100-5, attached hereto as Exhibit “D” and incorporated herein by reference. Consultant’s failure to conform to the requirements set forth in Council Policy 100-5 shall constitute a material breach of this Agreement and shall be cause for immediate termination of this Agreement by City.

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