Once the Technology Strategy is clearly defined and communicated and the High Level Requirements have been agreed it is time to produce a Reference Architecture that will guide the selection of technologies that are required to be implemented.

The Reference Architecture will define the software components, patterns and integrations that will deliver an efficient and operational technology platform for the customers, partners, staff, suppliers and auditors to interact with.

Here are the topics that will be covered in the Reference Architecture:

  • Executive Summary
  • Architectural Principles and Approach
  • Key Use Cases
  • Key Outcomes
  • End-to-end Architecture Diagram (Logical Enterprise view)
  • Breakdown of Components
  • Architectural Patterns for Integration
  • Cyber Security Concerns
  • Action Plan (Next steps)

Key Focus: Technology agnostic and interoperable with the digital age

A typical strategic engagement for a Reference Architecture is:

AOTC Service

Definition and Description

Duration

Reference Architecture

The Reference Architecture will guide all future Application and Integration investment and will seek to re-use, sweat and contain your existing business assets while adding powerful digital and business platforms where Cloud adoption makes sense.

  • Reference Architecture (VISIO A3 - High Impact),
  • RA Specification (DOC 20-50 Pages)
  • Presentation Slide Deck for MGMT (PPT 5-10 Slides)

8 Weeks