Architecture Review Board (ARB) is the common ground for reviewing IT initiatives, ensuring that their outcome is aligned strategically and architecturally, utilizing best practices, in accordance with uOttawa’s policies and standards, with respect to business and technical capabilities, information management, security and privacy, integration, user experience, application design, and infrastructure.

Role & Responsibilities

Architecture Review Board (ARB) is the common ground for central IT project presentations.

ARB plays a significant role in centralizing information sharing on different topics related to Enterprise Architecture, ensuring overall alignment with the governance strategy. Different initiatives are being developed in order to reach a well defined framework, leading to a stabilized future state, even more reliable and evolved: all of that being part of building the University of Tomorrow.

Stats

Stats ARB 2024-25

Architecture Review Process

ARB process in English

Overall process of ARB is aligned with the Project Management LifeCycle, run by the Project and Portfolio Management Office (PPMO), ensuring that IT initiatives are aligned with the business strategy of the organization.

EA Artifacts

What is the purpose?

The Business Architecture Presentation (BAP) aims at providing a high-level description of the product from a business perspective. It may include a description of how the document relates to organizational goals and/or objectives.

The Technical Architecture Document (TAD) addresses architectural aspects like: solution design, infrastructure components, integration requirements, capacity, and security. It includes how the product will meet those goals and objectives.

Why is this important? 

  • Keeps track of all aspects of an application (or other IT products);
  • Plays the role of development, maintenance and knowledge transfer to developers;
  • Make information easily accessible and provide a limited number of user entry points;
  • Helps users learn quickly, simplify the product and help support costs.

The success of those documents depends on one important element: Reliable and up-to-date data. 

To enable this, the Product Manager must ensure the documents reflect current situation, however the collaboration of every member of the IT team is a must

As living documents, BAP and TAD evolve with the product. Suggestions and feedback are encouraged to continuously improve their clarity and usefulness.

Questions?

Contact the ARB Coordination Team:
[email protected]