Technical Reference Model

Intro

A Technical Reference Model (TRM) categorizes standards, specifications, and technologies for constructing and integrating components. It supports component‑based and service‑oriented architectures.

Key points:

• Provides a common technical vocabulary.
• Guides technology selection and interoperability.
• Common use cases across EA/BPM/Data/App/Tech include standard stacks, integration protocols, and security controls.
• Pitfall: outdated TRMs that misguide solution choices.

Examples:

• Approved API, data, and messaging standards.
• Reference stacks for web, data, and integration layers.
• Security standards for identity and encryption.

In practice:

Maintain and govern the TRM as a living standard; align solution designs and waivers to it.

Related terms: Standards Information Base; Service Oriented Architecture; Reference Architecture

FAQs:

Q: Who owns the TRM?
A: Architecture governance with domain SMEs.

Q: How often is it updated?
A: On a cadence aligned to technology lifecycle.

‍