[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [soa-rm] Changes to "What is a Reference Model"
While not in a formal pattern template, I would assert that the
RM is
essentially a set of patterns. My favorite patterns template is
obvious:
http://www.google.com/search?hl=en&q=architectural+patterns+metamodel&btnG=G
oogle+Search
;-)
Duane
On
9/21/06 7:36 PM, "Danny Thornton" <danny_thornton2@yahoo.com>
wrote:
> Being a software technical person, I am biased about
>
the use of the term pattern. If I see an unqualified
> usage of
pattern in the context of a technical
> reference model for computing, my
first expectation
> will be to see things like Pattern Name,
Problem,
> Forces, Solution ... (pick your favorite pattern
>
template). The broader audience for a reference model
> may not have
the same bias.
>
> Danny
>
> --- Duane Nickull
<dnickull@adobe.com> wrote:
>
>> This is actually not
specific to SOA systems and is
>> intended to be a stop
>> gap
to define "Reference Model" until the Wikipedia
>> page that should do
such
>> gets built. The motivation is to help people
>>
understand the abstract nature
>> and use of the RM. Points well
taken however.
>>
>> How
about:
>>
>>
>> "A Reference Model is an abstract
artifact for
>> documenting patterns and
>> significant
relationships among the entities of an
>> environment. It is
used
>> to guide architects in the development of specific
>>
reference or concrete
>> architectures. It also facilitates the
creation of
>> consistent standards or
>> specifications
supporting that environment. A
>> reference model consists of
a
>> minimal set of unifying concepts, axioms and
>>
relationships within a domain,
>> and is abstract (independent of
specific standards,
>> technologies,
>> implementations, or
other concrete details). The
>> Reference Model for SOA is
>>
the set of concepts and patterns for understanding
>> significant
relationships
>> among the entities within a SOA
environment."
>>
>> The last sentence is purely an
example.
>>
>> Duane
>>
>>
>> On
9/21/06 2:52 PM, "Michael Stiefel"
>>
<development@reliablesoftware.com>
>>
wrote:
>>
>>> +1
>>>
>>>
Michael
>>>
>>> At 05:48 PM 9/21/2006, Danny Thornton
wrote:
>>>> Where is the boundary between pattern and
>>
concept?
>>>> When putting together SOA systems, I do not
think
>> of
>>>> the SOA RM as a set of patterns that I
would use
>> for
>>>> constructing an enterprise
system. I do think of
>> the
>>>> SOA RM as a set
of concepts that help in
>> understanding
>>>> a
SOA. From a formal software perspective, I
>>
would
>>>> not be inclined to use "pattern" in this part
of
>> the
>>>> introduction. On the other hand, it
is not a
>> false
>>>> statement to say that the SOA RM
contains
>> patterns
>>>> that will be seen in
SOAs.
>>>>
>>>>
Danny
>>>>
>>>> --- Duane Nickull
<dnickull@adobe.com> wrote:
>>>>
>>>>>
Replace:
>>>>>
>>>>> "According to the
SOA-RM specification, a
>> reference
>>>>> model is
an abstract
>>>>> framework for understanding
significant
>>>>> relationships among the entities
of
>>>>> some environment. It enables the development
of
>>>>> specific reference or
>>>>>
concrete architectures using consistent
>> standards
or
>>>>> specifications
>>>>> supporting
that environment. A reference model
>>>>> consists of a
minimal set of
>>>>> unifying concepts, axioms and
relationships
>> within a
>>>>> particular
problem
>>>>> domain, and is independent of
specific
>> standards,
>>>>>
technologies,
>>>>> implementations, or other concrete
details. A
>>>>> reference model for
SOA,
>>>>> therefore, is an abstract framework
for
>>>>> understanding significant
>>>>>
relationships among the entities of
SOA."
>>>>>
>>>>>
With
>>>>>
>>>>> "A Reference Model is an
abstract artifact for
>>>>> documenting patterns
and
>>>>> significant relationships among the entities
of
>> an
>>>>> environment. It is
used
>>>>> to guide architects in the development
of
>> specific
>>>>> reference or
concrete
>>>>> architectures using the model as a template
or
>>>>> pattern. It also
facilitates
>>>>> the creation of consistent standards
or
>>>>> specifications supporting
that
>>>>> environment. A reference model consists of
a
>> minimal
>>>>> set of
unifying
>>>>> concepts, axioms and relationships within
a
>> domain,
>>>>> and is
abstract
>>>>> (independent of specific standards,
>>
technologies,
>>>>> implementations, or
other
>>>>> concrete details). The Reference Model for
SOA
>> is a
>>>>> set of patterns
for
>>>>> understanding significant relationships
among
>> the
>>>>> entities within a
SOA
>>>>>
environment."
>>>>>
>>>>>
Comments?
>>>>>
>>>>>
Duane
>>>>>
>>>>>
>>>>>
--
>>>>>
>>>>
>>
>
******************************************************
>>>>>
Sr. Technical Evangelist - Adobe Systems, Inc.
>>>>>
*
>>>>> Chair - OASIS SOA Reference Model
Technical
>>>>> Committee*
>>>>> Blog: http://technoracle.blogspot.com
>>>>>
*
>>>>>
>>>>
>>
>
******************************************************
>>>>>
>>>>>
>>>>
>>>>
>>>>
>>
__________________________________________________
>>>> Do You
Yahoo!?
>>>> Tired of spam? Yahoo! Mail has the best
spam
>> protection around
>>>> http://mail.yahoo.com
>>>
>>>
>>>
>>
>>
--
>>
>
******************************************************
>> Sr. Technical
Evangelist - Adobe Systems, Inc.
>> *
>> Chair - OASIS SOA
Reference Model Technical
>> Committee*
>> Blog: http://technoracle.blogspot.com
>>
*
>>
>
******************************************************
>>
>>
>
>
>
__________________________________________________
> Do You
Yahoo!?
> Tired of spam? Yahoo! Mail has the best spam protection
around
> http://mail.yahoo.com
--
******************************************************
Sr.
Technical Evangelist - Adobe Systems, Inc.
*
Chair - OASIS SOA Reference Model Technical Committee*
Blog: http://technoracle.blogspot.com
*
******************************************************
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]