[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Cogitating Descriptions for Reference Architecture and System
Chapter 1 of the latest RA doc is really shaping up. There are two issues for this section that we may be able to work through via email. 1) The first issue is our description of a reference architecture. Currently we state: "A reference architecture is an architectural design pattern that indicates how an abstract set of mechanisms and relationships realizes a predetermined set of requirements." If we state the reference architecture is an architectural design pattern, I would expect the document to contain design patterns in a common design pattern format. Also, I would associate "realizes" as it is used in the sentence with SOA implementation. The following is an alternative description for a reference architecture: A reference archicture is a design template that indicates how an abstract set of mechanisms and relationships may realize a predetermined set of goals and requirements. 2) The second issue is that we use the ANSI IEEE 1471-2000 definition for system: "A collection of components organized to accomplish a specific function or set of functions." I suggest dropping this direct quote from IEEE 1471 and stating something more appropriate for an SOA ecosystem. For example, For SOA, a system can be defined as a collection of services and components organized to accomplish specific goals and requirements. Other than these two issues, chapter one is a good read and resonates with me. Danny ____________________________________________________________________________________ Be a better Heartthrob. Get better relationship answers from someone who knows. Yahoo! Answers - Check it out. http://answers.yahoo.com/dir/?link=list&sid=396545433
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]