OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

soa-rm-ra message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: Re: [soa-rm-ra] what is a generalized SOA RA?


My thoughts ...

Implementing SOA-based systems for a SOA ecosystem is
complex and there are certain architectural principles
at an abstraction layer lower than the RM that all
SOA-based systems will adhere to either in part or
whole.  An implementer can build a piece of pieces of
a SOA-based systems whether they realize the over
arching architectural principles or not, but we are
creating a document that spells them out. 

I would modify the part in the RM that states a
reference architecture is a design pattern to be a
reference architecture is a set of views and
viewpoints ...   The design pattern bit seems to be
the start of the argument questioning how we can
create an RA without an application specific problem
domain.

No one has to wait around for us to finish the RA to
build SOA-based systems, however, those who have built
SOA-based systems should be able to identify with the
material contained in the RA document.  The RA
document should be beneficial for many IT
professionals who are going to have to learn this
stuff in the future.

Danny
 
--- Ken Laskey <klaskey@mitre.org> wrote:

> I got the following well-stated email from someone
> at MITRE and I  
> think the answer is something that needs to be at
> the beginning of  
> the RA document but which isn't clearly tackled. 
> We've bumped around  
> this issue before but never put it to bed.  Rather
> than just  
> answering myself, I'd like to see something
> definitive from this group.
> 
> Read on.
> 
> Ken
> 
> Begin forwarded message:
> 
> > Ken, I'm trying to understand what the OASIS
> Reference Architecture  
> > effort is all about.
> >
> > I understand the OASIS definition of a reference
> model as:  "A  
> > reference model is an abstract framework for
> understanding  
> > significant relationships among the entities of
> some environment  
> > that enables the development of specific reference
> or concrete  
> > architectures using consistent standards or
> specifications  
> > supporting that environment."
> >
> > We use the OASIS SOA Reference Model as the basis
> for our  
> > development of a reference architecture for the
> Navy's application  
> > of SOA in its afloat environment.  So, to
> paraphrase the OASIS RM,  
> > we are using the RM to enable the development of a
> specific  
> > reference architecture using consistent standards
> or specifications  
> > supporting that environment.
> >
> > So, the RM goes on to define, "A reference
> architecture is an  
> > architectural design pattern that indicates how an
> abstract set of  
> > mechanisms and relationships realizes a
> predetermined set of  
> > requirements."  It also states: "The concepts and
> relationships  
> > defined by the reference model are intended to be
> the basis for  
> > describing references architectures and patterns
> that will define  
> > more specific categories of SOA designs."
> >
> > As a result of all this, we understood a reference
> architecture to  
> > be specific to a domain or an environment or a
> specific category of  
> > SOA design.  It is "an architectural design
> pattern ...[for  
> > realizing] a predetermined set of requirements." 
> We have  
> > interpreted "Navy application of SOA in its afloat
> environment" as  
> > a "specific category of SOA design" with "a
> predetermined set of  
> > requirements."
> >
> > By these definitions, how could one build a
> completely generalized  
> > SOA Reference Architecture irrespective of a
> domain or an  
> > environment or a category of SOA design or a
> predetermined set of  
> > requirements?
> >
> > Thanx in advance for your explanation!
> 
>
------------------------------------------------------------------------
> 
> -----
> Ken Laskey
> MITRE Corporation, M/S H305      phone: 703-983-7934
> 7151 Colshire Drive                         fax:    
>   703-983-1379
> McLean VA 22102-7508
> 
> 
> 
> 
> 


__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]