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

 


Help: OASIS Mailing Lists Help | MarkMail Help

soa-rm-editors message

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


Subject: Re: [soa-rm-editors] consolidated v11 issues and proposed dispositions



On Jan 30, 2006, at 5:56 PM, Ken Laskey wrote:

> Figure 1 shows how a reference model for SOA relates to other  
> distributed systems architectural inputs.  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.  Concrete  
> architectures will be derived from reference architectures and  
> other related models, such as [can't think of example right now],  
> will fulfill the needs for architectural work.  Architecture is not  
> done in isolation but must account for goals, motivation, and  
> requirements that define the actual problems being addressed.   
> While reference architectures can form the basis of classes of  
> solutions, concrete architectures will define specific solution  
> approaches.  Architecture also builds on other infrastructure work,  
> such as protocols, profiles, specifications, and standards.  SOA  
> implementations combine all of these, from the more generic  
> architectural principles and infrastructure to the specifics that  
> define the current needs, and represent specific implementations  
> that will be built and used in an operational environment.


Suggested wording:

Figure 1 shows how a reference model for SOA relates to other  
distributed systems architectural inputs.  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.  Concrete  
architectures arise from a combination of reference architectures,  
architectural patterns and additional requirements, including those  
imposed by technology environments.

Architecture is not done in isolation but must account for the goals,  
motivation, and requirements that define the actual problems being  
addressed.  While reference architectures can form the basis of  
classes of solutions, concrete architectures will define specific  
solution approaches.

Architecture is often in the context of a pre-defined environment,  
such as the protocols, profiles, specifications, and standards that  
are pertinent.

SOA implementations combine all of these elements, from the more  
generic architectural principles and infrastructure to the specifics  
that define the current needs, and represent specific implementations  
that will be built and used in an operational environment.


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