- Created by Piet Niederhausen, last modified on May 18, 2018
Principles
Highest level guidelines for governance of the enterprise architecture.
-
Page:EA Guiding Principles —
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
Shared vocabulary and concepts for describing and understanding the enterprise.
-
Page:Business Capability Reference —
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 —
As capability maps become available from units at the UW, they may be added to this directory for general reference.
-
Page:UW Strategy Reference —
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 —
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 —
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 —
Technical Solution designs SHOULD minimize the use of site-to-site VPNs and subnet-extensions.
-
Page:Private IP Addresses for Office Systems —
Use private IP addresses to reduce the attack surface for UW-IT office systems.
-
Page:Security and Privacy Policies —
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.
-
Page:
-
Page:
-
Page:
-
Page:
-
Page:Container-Based Applications Reference Architecture —
This reference architecture guides the use of containers and container orchestration technology at the UW.
-
Page:
-
Page:UX Design Guides —
This guide provides best practices for User Experience design.
Alpha order by topic.
Business Architecture
-
Page:Business Capability Reference —
High level UW-wide business capabilities defined by the EA team, with links to strategies, business processes, data models, and applications, where available.
-
Page:
-
Page:
-
Page:Capability Maps —
As capability maps become available from units at the UW, they may be added to this directory for general reference.
-
Page:
-
Page:
-
Page:UW Strategy Reference —
This reference links to IT and business strategies at the UW, as an aid to finding strategy information and linking IT and business strategy.
Data Architecture
-
Page:Delete Means Delete —
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:Security and Privacy Policies —
University policies and federal and state laws and regulations that UW teams must comply with.
Enterprise Architecture
-
Page:Architecture Value Scorecard v2 —
Helps initiatives and decision makers review and evaluate possible solutions to find those solutions that provide the highest architectural value where possible.
-
Page:EA Guiding Principles —
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.
Security and Privacy
-
Page:Private IP Addresses for Office Systems —
Use private IP addresses to reduce the attack surface for UW-IT office systems.
-
Page:Security and Privacy Policies —
University policies and federal and state laws and regulations that UW teams must comply with.
Solutions Architecture
-
Page:Minimize site-to-site VPNs —
Technical Solution designs SHOULD minimize the use of site-to-site VPNs and subnet-extensions.
-
Page:Private IP Addresses for Office Systems —
Use private IP addresses to reduce the attack surface for UW-IT office systems.
-
Page:Security and Privacy Policies —
University policies and federal and state laws and regulations that UW teams must comply with.
Strategy
-
Page:
-
Page:UW Strategy Reference —
This reference links to IT and business strategies at the UW, as an aid to finding strategy information and linking IT and business strategy.
Required
Applicable teams must follow this guidance, or obtain an exception from the authority shown.
-
Page:Security and Privacy Policies —
University policies and federal and state laws and regulations that UW teams must comply with.
Recommended
The EA team recommends that teams follow this guidance, or discuss and agree on why they will not.
-
Page:Architecture Value Scorecard v2 —
Helps initiatives and decision makers review and evaluate possible solutions to find those solutions that provide the highest architectural value where possible.
-
Page:Container-Based Applications Reference Architecture —
This reference architecture guides the use of containers and container orchestration technology at the UW.
-
Page:Delete Means Delete —
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 —
Technical Solution designs SHOULD minimize the use of site-to-site VPNs and subnet-extensions.
-
Page:Private IP Addresses for Office Systems —
Use private IP addresses to reduce the attack surface for UW-IT office systems.
-
Page:UX Design Guides —
This guide provides best practices for User Experience design.
Informational
Provides helpful guidance or background.
-
Page:
-
Page:Business Capability Reference —
High level UW-wide business capabilities defined by the EA team, with links to strategies, business processes, data models, and applications, where available.
-
Page:
-
Page:
-
Page:Capability Maps —
As capability maps become available from units at the UW, they may be added to this directory for general reference.
-
Page:
-
Page:EA Guiding Principles —
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.
-
Page:
-
Page:UW Strategy Reference —
This reference links to IT and business strategies at the UW, as an aid to finding strategy information and linking IT and business strategy.
To learn more, see EA Library Maintenance.
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, or have a question?
Required: Applicable teams must follow this guidance, or obtain an exception from the authority shown.
Recommended: The EA team recommends that teams follow this guidance, or discuss and agree on why they will not.
Informational: Provides helpful guidance or background.
- No labels