[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?
Frank, Danny, Rex, and everyone else, I looked at the email traffic and then went back to the beginning of the RA draft. In an effort to get to the point quicker and answer the MITRE questions, I'm submitting the attached edits (some wordsmithing and the added section 1.x.) for your consideration. (The Word doc tracks changes; the following paste just shows the net results.) This would also serve as the response to the MITRE question. 1 Introduction Service Oriented Architecture is an architectural paradigm that has gained significant attention within the information technology (IT) and business communities. The OASIS Reference Model for SOA provides a common language for understanding the important features of SOA but does not address the issues involved in constructing, using, or owning a SOA-based system. This document focuses on these aspects of SOA. 1.1 What is a Reference Architecture A reference architecture models the abstract architectural elements in the domain independent of the technologies, protocols, and products that are used to implement the domain. It differs from a Reference Model in that a Reference Model describes the important concepts and relationships in the domain focusing on what distinguishes the elements of the domain; a Reference Architecture elaborates further on the model to show a more complete picture that includes what is involved in realizing the modeled entities. While still remaining abstract, a reference architecture is more concrete than a Reference Model in that it identifies and provides a high level description of architectural components and artifacts. 1.x What is this Reference Architecture The SOA Reference Model defines reference architecture as “an architectural design pattern that indicates how an abstract set of mechanisms and relationships realizes a predetermined set of requirements.” It is possible to define Reference Architectures at many levels of detail or abstraction, and for many different purposes. In fact, the reference architecture for one domain may represent a further specialization of another reference architecture, with additional requirements over those for which the more general reference architecture was defined. While requirements for this reference architecture are discussed in Section 2, an overview of those requirements specifies a SOA for which:
Below, we talk about such an environment as a SOA ecosystem. Informally, our goal in this Reference Architecture is to show how Service Oriented Architecture fits into the life of users and stakeholders in a SOA ecosystem, how SOA-based systems may be realized effectively, and what is involved in owning such a SOA-based system. We believe that this approach will serve two purposes: ensuring that the true value of a SOA meeting the stated requirements can be realized using appropriate technology, and permitting the audience to focus on the important issues without becoming over-burdened with the details of a particular implementation technology. 1.2 Service Oriented Architecture – An Ecosystems perspective Many systems cannot be understood by a simple decomposition into parts and subsystems. There are... Note, the RA we are writing would be relevant to the Navy SOA but the Navy one will likely have more requirements, e.g. for supporting disconnected ops. This is an example of the Navy RA being a further specialization of a more general one. Ken |
On Nov 10, 2007, at 5:21 PM, Francis McCabe wrote:
------------------------------------------------------------------------------------------ Ken Laskey MITRE Corporation, M/S H305 phone: 703-983-7934 7515 Colshire Drive fax: 703-983-1379 McLean VA 22102-7508 |
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]