Version 2 of what is a Reference Architecture

[Francis McCabe <frankmccabe@mac.com>]

Please note: this is trying to explain what we mean by Reference  
Architecture, not nec. what our RA is or is intended to do...

I have cleaned it up some; copy and paste from word apparently is a  
hit or miss affair.

Frank

----

The SOA Reference Model defines reference architecture as “an  
architectural design pattern that indicates how an abstract set of  
mechanisms and relationships realizes a predetermined set of  
requirements.” More precisely, a reference architecture can be  
described as an architectural pattern that provides a set of  
predefined subsystems, specifies their responsibilities, and includes  
rules and guidelines for organizing the relationships between them  
[TOGAF v8.1].

It is possible to define reference architectures at many levels of  
detail or abstraction, and for many different purposes. In particular,  
a reference architecture need not be a concrete architecture.

Our approach is to be as high-level and as technology-neutral as  
possible; while at the same time being fully aware of the dominant  
technologies likely to be employed. The detail necessary in concrete  
architectures typically requires technology choices that are not  
directly implied by the requirements of SOA-based systems per se, but  
by the technology choices available at the time.

We believe that out our approach will serve two purposes: ensuring  
that the true value of the SOA approach can be realized on any  
appropriate technology; while permitting our audience to focus on the  
important issues without becoming over-burdened with the details.