Requirements Based

Principle Name Requirements-Based Changes Statement Only in response to business needs are changes to applications and technology made. Rationale This principle will foster an atmosphere where the infor mation environment changes in response to the needs of the University, rather than having the business change in response to IT changes. This is to ensure that […]

Principle Name

Requirements-Based Changes

Statement

Only in response to business needs are changes to applications and technology made.

Rationale

This principle will foster an atmosphere where the infor mation environment changes in response to the needs of the University, rather than having the business change in response to IT changes. This is to ensure that the purpose of the information support — the transaction of business — is the basis for any proposed change. Unintended effects on University due to IT changes will be minimized. A change in technology may provide an opportunity to improve the business process and, hence, change business needs.

Implications

  1. Changes in implementation will follow full examination of the proposed changes using the University architecture.
  2. We do not fund a technical improvement or system development unless a documented business need exists.
  3. Change management processes conforming to this principle will be developed and implemented.
  4. This principle may bump up against the responsive change principle. We should ensure the requirements documentation process does not hinder responsive change to meet legitimate business needs. The purpose of this principle is to keep us focused on business, not technology needs — responsive change is also a business need.

Architecture Domains

  • Technology