1. Home
  2.  → 
  3. About OIT
  4.  → Enterprise Architecture

Enterprise Architecture

What is Enterprise Architecture?

Enterprise Architecture is the process by which organizations standardize and organize IT infrastructure to align with enterprise goals.

Enterprise Architecture Standards

The ARB defines the bar for OIT work by writing and disseminating standards. Our goal is to write standards that help teams work faster by making it easier to integrate with the campus’s technology environment.

ARB Standards are currently being updated to use a uniform template. (Access requires a campus network access or VPN).

  • All the updated standards can be found on ARB’s GitHub page. (Access requires a campus network access or VPN).
  • The older standards are still on ARB’s wiki (requires login) and will move as they get updated
ScopeStandardTypeLast review
UCIUCI Application Authentication and AuthorizationStandard2016-05
UCIUCI User Account NamesStandard2016-07
UCIUCI Use CampusID for Tracking IdentityStandard2017-02
UCIUCI DNS StandardStandard2018-02
UCIUCI @UCI.EDU Email Namespace StandardStandard2018-06
OITOIT Version ControlStandard2022-10
OITOIT Enterprise Server Baseline Standards and Checklist for Operating SystemsStandard2019-11
OITOIT Enterprise Baseline Standards and Checklist for MiddlewareStandard2016-09
OITOIT Database Server Standards and GuidelinesGuideline2017-07
OITOIT Data and Process Integration GuidelinesGuideline2017-10
OITOIT System Monitoring GuidelineGuideline2018-05
OITOIT Key Management StandardStandard2018-06
OITOIT Standard for Documentation Relating to ProjectsStandard2018-07
OITOIT Host Name GuidelineGuideline2018-09
OITOIT Disaster Recovery TiersReference2018-02
OITOIT Application Load Balancing GuidelineGuideline2019-01
OITInclusive IT Language GuideGuideline2021-04
OITSecret Storage GuidelineGuideline2024-02

ARB Recommendations

The ARB community keeps a regularly-updated list of recommendations (login required) documenting what tools OIT is currently using. This list can be helpful if you’re looking for a software solution for a particular problem, looking to connect with other teams using a tool, or researching the pros and cons of your options.

DomainDefinitionLast review
Development Language RecommendationsWhat people are using to talk to the computer2024-02
Identity, Authentication, and Authorization RecommendationsWhat people are using to know which people should be allowed in, and what they can do when they get there2024-03
Team Collaboration & Project Management RecommendationsWhat people are using to talk inside their teams2024-03
Editor and IDE RecommendationsWhat people are using to get ideas into the computer2023-04
Security RecommendationsWhat people are using to keep their systems safe2023-05
Business Intelligence RecommendationsWhat people are using to better understand their data2023-09
Application Infrastructure RecommendationsWhat people are using to let systems talk to each other2023-09
Frontend Web ToolsWhat people are using client side to make their applications more responsive2023-09
Backend Web FrameworksWhat people are using server side to make services and web apps2023-09
Operations Management RecommendationsWhat people are using to keep track of all this other stuff2023-12
Web Form RecommendationsWhat people are using to get feedback from lots of people2023-11
Database RecommendationsWhat people are using for SQL data2023-11
Platform RecommendationsWhat people are using to run all this other stuff on2022-09
JDK (Java Development Kit) RecommendationsWhat people are using to get Java running2023-09

The Architecture Review Board (ARB)

At UCI, Enterprise Architecture is coordinated by the Architecture Review Board (ARB), which brings together technology leaders from across the Office of Information Technology (OIT) and the campus community.

The heterogeneous technology environment at UCI has grown organically over decades, with different parts of the organization using wholly different technologies, toolsets, and development methodologies. The ARB meets monthly to bring these diverse groups together and develop an institutional perspective, identify areas of possible change, and work toward more unified practices.

The Architecture Review Board Charge

The ARB charge helps inform where we spend our time and attention. There are three pillars that define what ARB tries to accomplish, each with three supporting practices that make those goals concrete.

  1. Define the bar for OIT work
    1. Set practices as Standards and Guidelines, demarcating the hard and soft expectations of the OIT community
    2. Provide Recommendations and Standards of Practice to foster community and share knowledge
    3. Make clear when exceptions are available and how to obtain them
  2. Promote standards and best practices
    1. Host conversations that will lead to new collaborations, new solutions, and new documentation
    2. Bridge teams and divisions to connect people who might otherwise duplicate effort
    3. Champion good ideas to broaden their reach
  3. Explore new products, technologies, and practices
    1. Offer expert opinion to evaluate what’s novel
    2. Research and understand industry trends and work to integrate them into our environment
    3. Streamline adoptions that will help UCI fulfill its mission

ARB Leadership

Co-Chairs: Dana Watanabe & Seth A. Roby (email the chairs)
Executive Sponsor: Henry Jenkins
Voting members: the current voting members, as well as their responsibilities, are listed here (login required).

ARB Meetings

Meetings are held on the third Tuesday of the month at 2 pm. Additional meetings for subgroups and follow-ups are scheduled as needed.

The meeting agenda is posted two weeks before each call. See the meeting notes on the OIT Wiki (login required).

ARB Subgroups

Between our monthly meetings, other subgroups meet to define, promote, and explore. The following groups are currently active or being formed:

Current work

  • Maintaining the Recommendations Lists
  • Defining and refining how OS versions are approved for use and how teams can track that process
  • Updating all our standards to be more actionable, with current focus on these standards:
    • System monitoring
    • Authentication & Authorization
    • Key management
    • System logging
  • Ongoing AWS Migrations

Recent Work

Updated on
April 16, 2024