|
<br />product(s), or any part thereof, infringes any patent, trademark or copyright, or if the sub -
<br />license or use of the product(s), or any part thereof, is enjoined, contractor, after consultation
<br />with the State, shall do one of the f ollowing at contractor's expense: (i) produce for the State
<br />the right under such patent, trademark or copyright to use or sub - license, as appropriate, the
<br />product or such part thereof: or (ii) replace the product(s), or part thereof, with other suitable
<br />pr oducts or parts conforming to the original license and State specifications; or (iii) suitably
<br />modify the products, or part thereof. Except as otherwise expressly provided herein,
<br />contractor shall not be liable for any costs or expenses incurred without it s prior written
<br />authorization.
<br />ARTICLE 19. GOVERNMENTAL IMMUNITY
<br />Notwithstanding any other provision of this [contract] to the contrary, no term or condition of this
<br />contract shall be construed or interpreted as a waiver, express or implied, of any of the
<br />immunities, rights, benefits, protection, or other provisions of the Colorado Governmental
<br />Immunity Act, Section 24 - 10 - 101, et.seq ., CRS, as now or hereafter amended. The parties
<br />understand and agree that liability for claims for injuries to persons or property arising out of
<br />negligence of the State of Colorado, its departments, institutions, agencies, boards, officials and
<br />employees is controlled and limited by the provisions of Section 24 - 10 - 101, et. seq ., CRS, as now
<br />or hereafter amended and the risk management statutes, Section 24 - 30 - 1501, et. seq ., CRS, as
<br />now or hereafter amended.
<br />ARTICLE 20 . DATA AND DOCUMENT DELIVERABLES
<br />Unless otherwise specified, software documentation shall be delivered that meets the following
<br />standards:
<br />A. The documentation shall be in paper, human readable format, which clearly identifies the
<br />programming language and version used, and when different programming languages are
<br />incorporated, identifies the interfaces between code programmed in different programming
<br />languages.
<br />B. The documentation shall contain source code in a paper, human readable format, which
<br />describes the program logic, relationship between any internal functions, and identifies the disk
<br />files which contain the various parts of the code.
<br />C. Detailed "commenting" of source code may be used to partially satisfy the documentation
<br />requirements, although documentation shall also include a flow chart which identifies the
<br />program flow between files and functions. Comments may be used to document internal flow
<br />control in functions.
<br />D. Files containing the source code shall be delivered, or may be left on the host machine so long
<br />as the files and their location are identified, and their significance to the program described, in
<br />the documentation.
<br />E. Documentation shall describe e rror messages and the location in the source code, by page, line
<br />number, or other suitable identifier, where the error message is generated. It is the intent of the
<br />parties that documentation be written so persons reasonably proficient in the use of the
<br />p rogram language involved can efficiently use the documentation to understand the program
<br />structure, iterative and other control techniques, and decipher error messages should they
<br />occur. Within the rights granted elsewhere in this contract, the contractor warrants that the
<br />delivered software will be sufficiently descriptive to enable maintenance and modification of the
<br />software to permit change to addresses and telephone numbers in computer generated
<br />documentation, addition of fields to the database, revisi ons of report formats, including
<br />breakpoints and summary computations.
<br />Page 6 of 16 Pages
<br />
|