Versions Compared

Version Old Version 4 New Version 5
Changes made by

Marina Arseniev (Unlicensed)

Eric Puchalski

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

The purpose of an Architecture Review is to examine a proposed project to determine whether a practical solution can be based on existing resources, purchased components, or software developed in-house. In all cases when new systems are being considered, the emphasis should first be on reusing existing resources. If this is not practical then a third-party solution should be considered. In-house development should be proposed only as a last resort. Note that "third-party" simply means "not developed in-house." Third-party solutions may be commercial, open source, shareware, provided by another UC campus, etc.

The Architecture Review is conducted by the Architecture Review Board (ARB). The ARB will review the project and make recommendations based on what is known about existing resources and OIT's ability to support proposed solutions.

What To DoHow To Do It
Review existing Enterprise Architecture Documents
  1. Enterprise Architecture Standards, Guidelines, Tools.
  2. Architecture Design Worksheet
Are Campus Browser Standards supported?
  1. Justification must be provided if Campus Browser Standards are not met.
Submit your application for review by Architecture groupPlease speak with a Review Board
  1. Contact one of the Software Development Director in OIT to assemble a team of appropriate software engineers that can help do a peer review of the application architecture.
Architecture Recommendation of ARB reviewed and approved?
  1. An After considering the recommendations of the ARB, an application must be approved by Executive Management prior to release for general use.
  2. Please use the Project Sign-off / QualityControl Sheet for Developed Applications or Project Sign-off Sheet for Vendor/ASP Solutions as appropriate and schedule dates for the architecture review sign-off.