Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 17 Next »

The Enterprise Architecture library provides best practices and information to help leaders and teams make choices that are consistent with UW enterprise goals.

Don't see what you're looking for? Contact the EA team and we may be able to help.



Highest level guidelines for governance of the enterprise architecture.

  • Page:
    EA Guiding Principles (info) Enterprise Architecture Guiding Principles help define the criteria by which technology and services that span or impact the enterprise are managed, acquired, designed and configured.

Reference Models

A common vocabulary and taxonomy of accepted concepts used to describe an organization’s capabilities.

  • Page:
    Business Capability Reference (info) High level UW-wide business capabilities defined by the EA team, with links to strategies, business processes, data models, and applications, where available.
  • Page:
    Capability Maps (info) As capability maps become available from units at the UW, they may be added to this directory for general reference.
  • Page:
    UW Strategy Reference (info) This reference links to IT and business strategies at the UW, as an aid to finding strategy information and linking IT and business strategy.

Standards and Guidelines

Prescribed or preferred technology, design, data, and process elements that help projects conform to architectural principles.

  • Page:
    Architecture Value Scorecard v2 (tick) Helps initiatives and decision makers review and evaluate possible solutions to find those solutions that provide the highest architectural value where possible.  
  • Page:
    Delete Means Delete (tick) When a file (or other data object) is deleted by a system or user action, no copy of the deleted data SHOULD be kept longer than 90 days.
  • Page:
    Minimize site-to-site VPNs (tick) Technical Solution designs SHOULD minimize the use of site-to-site VPNs and subnet-extensions.
  • Page:
    Private IP Addresses for Office Systems (tick) Use private IP addresses to reduce the attack surface for UW-IT office systems.
  • Page:
    Security and Privacy Policies (warning) University policies and federal and state laws and regulations that UW teams must comply with.  

Implementation Guides and Methods

Patterns, prototypes, use cases, or analytical methods that help teams apply principles, standards, and guidelines.

Capability Mapping

There is no content with the specified labels


Security and Privacy


Resources in this library may be Required, Recommended, or just Informational. To learn more, see About Reference Architectures.

Required Reference Architectures

Marked with a (warning) symbol

Recommended Reference Architectures

Marked with a (tick) symbol

Informational Reference Architectures

Marked with a (info) symbol.

  • No labels