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.
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. Reserved

Related to Software Development Life Cycle Policy

  • Design Development Phase Services 3.3.1 Based on the Owner’s approval of the Schematic Design Documents, and on the Owner’s authorization of any adjustments in the Project requirements and the budget for the Cost of the Work, the Architect shall prepare Design Development Documents for the Owner’s approval. The Design Development Documents shall illustrate and describe the development of the approved Schematic Design Documents and shall consist of drawings and other documents including plans, sections, elevations, typical construction details, and diagrammatic layouts of building systems to fix and describe the size and character of the Project as to architectural, structural, mechanical and electrical systems, and other appropriate elements. The Design Development Documents shall also include outline specifications that identify major materials and systems and establish, in general, their quality levels.

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

  • Purchase Order Flip via Ariba Network (AN) The online process allows suppliers to submit invoices via the AN for catalog and non- catalog goods and services. Contractors have the ability to create an invoice directly from their Inbox in their AN account by simply “flipping” the purchase order into an invoice. This option does not require any special software or technical capabilities. For the purposes of this section, the Contractor warrants and represents that it is authorized and empowered to and hereby grants the State and the third-party provider of MFMP the right and license to use, reproduce, transmit, distribute, and publicly display within the system the information outlined above. In addition, the Contractor warrants and represents that it is authorized and empowered to and hereby grants the State and the third-party provider the right and license to reproduce and display within the system the Contractor’s trademarks, system marks, logos, trade dress, or other branding designation that identifies the products made available by the Contractor under the Contract.

  • Creative Commons Attribution-Non-Commercial-NoDerivs License The Creative Commons Attribution Non-Commercial-NoDerivs License (CC-BY-NC-ND) permits use, distribution and reproduction in any medium, provided the original work is properly cited, is not used for commercial purposes and no modifications or adaptations are made. (see below) Use by commercial "for-profit" organizations Use of Wiley Open Access articles for commercial, promotional, or marketing purposes requires further explicit permission from Wiley and will be subject to a fee. Further details can be found on Wiley Online Library xxxx://xxxxxxx.xxxxx.xxx/WileyCDA/Section/id-410895.html Other Terms and Conditions:

  • Schematic Design Phase Services § 3.2.1 The Architect shall review the program and other information furnished by the Owner, and shall review laws, codes, and regulations applicable to the Architect’s services.

  • Additional Information for Product Development Projects Outcome of product development efforts, such copyrights and license agreements. • Units sold or projected to be sold in California and outside of California. • Total annual sales or projected annual sales (in dollars) of products developed under the Agreement. • Investment dollars/follow-on private funding as a result of Energy Commission funding. • Patent numbers and applications, along with dates and brief descriptions.  Additional Information for Product Demonstrations: • Outcome of demonstrations and status of technology. • Number of similar installations. • Jobs created/retained as a result of the Agreement.

  • Vendor Development Rights To the extent not inconsistent with Customer’s rights in the Work Product or as set forth herein, nothing in this Contract shall preclude Vendor from developing for itself, or for others, materials which are competitive with those produced as a result of the Services provided hereunder, provided that no Work Product is utilized, and no Intellectual Property Rights of Customer therein are infringed by such competitive materials. To the extent that Vendor wishes to use the Work Product, or acquire licensed rights in certain Intellectual Property Rights of Customer therein in order to offer competitive goods or services to third parties, Vendor and Customer agree to negotiate in good faith regarding an appropriate license and royalty agreement to allow for such.

  • 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.

  • Educator Plans: Improvement Plan A) An Improvement Plan is for those Educators with PTS whose overall rating is unsatisfactory.

  • 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).

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