Minnesota § 16E.031 USER ACCEPTANCE TESTING

Minnesota Statutes

§ 16E.031 — USER ACCEPTANCE TESTING

Minnesota § 16E.031

PartADMINISTRATION AND FINANCE

Ch. 16EDEPARTMENT OF INFORMATION TECHNOLOGY SERVICES

This text of Minnesota § 16E.031 (USER ACCEPTANCE TESTING) is published on Counsel Stack Legal Research, covering Minnesota primary law. Counsel Stack provides free access to over 12 million legal documents including statutes, case law, regulations, and constitutions.

Bluebook

Minn. Stat. § 16E.031 (2026).

Text

Subdivision 1.Applicability. As used in this section:

(1)"primary user" means an employee or agent of a state agency or local unit of government who uses an information technology business software application to perform an official function; and

(2)"local unit of government" does not include a school district. Subd. 2.User acceptance testing.

(a)A state agency implementing a new information technology business software application or new business software application functionality that significantly impacts the operations of a primary user must provide opportunities for user acceptance testing, unless the testing is deemed not feasible or necessary by the relevant agency commissioner, in consultation with the chief information officer and representatives of the primary user.

(b)The

Free access — add to your briefcase to read the full text and ask questions with AI

Subdivision 1.Applicability.
As used in this section:
(1) "primary user" means an employee or agent of a state agency or local unit of government who uses an information technology business software application to perform an official function; and
(2) "local unit of government" does not include a school district.

Subd. 2.User acceptance testing.
(a) A state agency implementing a new information technology business software application or new business software application functionality that significantly impacts the operations of a primary user must provide opportunities for user acceptance testing, unless the testing is deemed not feasible or necessary by the relevant agency commissioner, in consultation with the chief information officer and representatives of the primary user.
(b) The requirements in paragraph (a) do not apply to routine software upgrades or application changes that are primarily intended to comply with federal law, rules, or regulations.