�糵����

ARB plays a critical role in centralizing information sharing and fostering strategic communication across the University's IM/IT landscape. By proactively engaging and involving the broader IM/IT community, ARB communicates and reviews projects that may impact various University units, processes, and policies. 

The board enables a collaborative approach that seeks out comments, recommendations, and questions from members representing different organizational units, thereby establishing a two-way communication and analysis strategy. Through this comprehensive approach, ARB contributes to the development of a well-defined framework that supports the University's long-term efficiency, productivity, and vision of building the University of Tomorrow.

Overall process of ARB is aligned with the Project Management LifeCycle, managed by the Project and Portfolio Management Office (PPMO), and is published and accessible to University staff. 

ARB conducts a comprehensive project presentation process with peer review and approval by the Architecture Working Group (AWG) at critical stages of the project lifecycle, including initiation, solution approach, and solution architecture review. 

These presentations are strategically aligned with the University's enterprise architecture principles, business capabilities models, and established IM/IT policies and standards, ensuring that IT initiatives directly support the organization's broader business strategy.

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.