Introduction
Excerpt A reference model is a standard, template or pattern that can be redeployed in a number of different ways. They can be organisational specific, industry standards or open standards cutting across a number of industries.
Reference models come in many forms and sizes, there may be
- reference data models such as the Data Reference Model (DRM) in the Federal Enterprise Architecture (FEA), or SID from eTOM
- reference business operating models such those found in eTOM, called the Business Process Framework
- application reference models as those found in JEE, known as the JEE Reference Architecture
- technical reference models such as Androids TRM, the technical specification for and any PC or laptop and the technical specification for Symbian
Collateral
TOGAF defines two reference models. They are just examples and nothing more. You can use them as they are or define your own. In actual fact you will need to define your own.
...
- Electronic Data Interchange - using EDIFACT, ASC x12, or TRADACOMS
- Remote Procedure Calls (middleware) - using DCE RPC, ONC RPC, MS-RPC, JSON-RPC, or XML-RPC
- Object Remote Procedure Calls (middleware) - using Java RMI, MS COM and DCOM, or OMG CORBA
- Application Servers - would make use of the technologies listed above but perform the exchange of information through transformation rules between clients and corporate data sources
- Service Oriented Architecture - sometimes referred to by some vendors as CORBA on steroids, adds to the ORPC middleware services such things as routing, message transformation, security, service location and registration. All of these services would be built into what is typically referred to as an ESB (Enterprise Service Bus).
...