RE: [soa-rm] Reference Architecture - Definition

["Beack, Theo" <Theo.Beack@softwareagusa.com>]

Frank,

 

At first when I read your definition of Reference Architecture I found it a bit vague. The key phrases

that made it seem vague were "set of mechanisms" and "predetermined set of requirements".

 

I tried different alternative variations of the RA definition in an attempt to come up

with a clear an concise definition. It has been a bit of a frustrating exercise.

 

Below are the best variations I could come up with.

 

Variation #1: A reference architecture is an abstract design consisting of a high-level description of it's

design components, services and their relationships, while being devoid of any implementation details.

 

Variation #2: A reference architecture is an abstract design that is modeled after a reference model.

This reference architecture consists of a high-level description of it's design components, services

and their relationships, while being devoid of any implementation details.

 

Variation #3: A reference architecture is an abstract design that is based upon a reference model.

The reference architecture consists of a high-level description of it's design components, services

and their relationships, while being devoid of any implementation details.

 

Now when I re-read your definition it makes more sense and I interpret

"set of mechanisms" as "design components, services and relationships"; and

"predetermined set of requirements" as "reference model".

 

However, I think that many readers might have the same initial reaction that I did. Does anyone else have any

thoughts on the RA definition?

 

Regards

Theo

Ps. Below is a minor edit of the RA purpose description you included in your post:

"A reference architecture can be used to guide the realization of implementations where specific properties are desired of the concrete system."

 

-----Original Message-----

From: Francis McCabe [mailto:frankmccabe@mac.com]

Sent: Saturday, January 14, 2006 00:33

To: SOA-RM

Subject: [soa-rm] Reference Architecture

The time has come to start considering the development of a Reference Architecture.

The TC agreed to establish a sub-committee to pursue this, so we will be called the SOA RM TC RA SC !

The first item of business is to develop a statement of purpose.

One suggestion is:

To develop, in accordance with the SOA RM TC Charter, a reference Service Oriented Architecture.

Definition: A reference model that is mapped onto software elements that implements the functionality defined in the reference model.

www.sei.cmu.edu/architecture/glossary.html

 

Definition: A reference architecture is an abstract set of mechanisms and relationships that models a predetermined set of requirements.

McCabe 2006

Keywords: abstract, mechanisms, model, requirements.

A reference architecture can be to guide the realization of implementations where specific properties are desired of the concrete system.

To initiate the discussion, some questions suggest themselves:

1. What requirements should be captured in a reference architecture 2. What mechanisms are required to realize those requirements 3. What is the relationship between the Reference Model and the Reference Architecture 4. What additional concepts (if any) to those captured in the Reference Model are necessary to develop an RA.

Immediate steps

1. To agree on a statement of purpose

2. To collect requirements

Let the fur fly!

Frank McCabe