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

[Ken Laskey <klaskey@mitre.org>]

I just got out of a meeting with someone who advocates letting organizations build local SOA implementations and think of making these work together as a future challenge.  I said the pieces will never work together in the future if you don't at least consider the distributed ownership issues up front.  My local solution may be custom made for an ESB but will that make me a stovepipe for the future.

I raise this here because if our RA specifically decides not to sweep these under the rug, are those architectural principles ala the RM or requirements for a specific (our) RA?

Ken

P.S. Still looking for a definition of architectural design pattern so I know where I went awry.

On Nov 13, 2007, at 10:41 AM, Jeffrey A. Estefan wrote:

Rex,

Principles and Requirements are clearly not synonymous.  Principles are general rules and guidelines intended to be enduring and not often amended. Requirements, on the other hand, are obligatory statements, preferably testable or measurable and necessary for process or product acceptance. Principles and Tenets are more closely related terms than Principles and Requirements.

Cheers...

- Jeff E. 

---------------------------------------------------------------------

To unsubscribe from this mail list, you must leave the OASIS TC that

generates this mail.  You may a link to this group and all your TCs in OASIS

at:

https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php 

------------------------------------------------------------------------------------------

Ken Laskey

MITRE Corporation, M/S H305     phone:  703-983-7934

7515 Colshire Drive                        fax:        703-983-1379

McLean VA 22102-7508

smime.p7s