- From: Austin, Daniel <Austin.D@ic.grainger.com>
- Date: Tue, 5 Mar 2002 14:52:39 -0600
- To: "'Alan Davies'" <ADavies@SeeBeyond.com>
- cc: "'www-ws-arch@w3.org'" <www-ws-arch@w3.org>
- Message-ID: <E0995D588DC3D211BB8D00805FFE353907358B3A@ic.ic.grainger.com>
Hi Alan, I posted in my original email to the group on goals and requirements a definition of architecture. I'll repost it again here: "The software architecture of a program or computing system is the structure or structures of the system, which comprise software components, the externally visible properties of those components, and the relationships among them." [1] I also posted a definition of a reference architecture: "A reference architecture is the generalized architecture of several end systems that share one or more common domains. The reference architecture defines the infrastructure common to the end systems and the interfaces of components that will be included in the end systems. The reference architecture is then instantiated to create a software architecture of a specific system. The definition of the reference architecture facilitates deriving and extending new software architectures for classes of systems. A reference architecture, therefore, plays a dual role with regard to specific target software architectures. First, it generalizes and extracts common functions and configurations. Second, it provides a base for instantiating target systems that use that common base more reliably and cost effectively." [2] In addition I posted a note about an existing proposal for a reference architecture for Web Services [3]. Comments? Regards, D- [1] Bass, L., Clements, P., and Kazman, R. Software Architecture in Practice. Reading, Mass.: Addison Wesley, 1998. [2] Gallagher, Brian P. "using the Architecture Tradeoff Analysis Method to Evaluate a Reference Architecture: A Case Study" CMU/SEI-2000-TN-007 June 2000 http://www.sei.cmu.edu/publications/documents/00.reports/00tn007/00tn007.htm <http://www.sei.cmu.edu/publications/documents/00.reports/00tn007/00tn007.ht m> [3] Yin, Kevin "A Refrence Architecture for Smart Web Services" Sun Developer Connection, August 2001 http://dcb.sun.com/practices/devnotebook/webserv_refarch.jsp <http://dcb.sun.com/practices/devnotebook/webserv_refarch.jsp> -----Original Message----- From: Alan Davies [mailto:ADavies@SeeBeyond.com] Sent: Tuesday, March 05, 2002 1:39 PM To: www-ws-arch@w3.org Subject: Web Services Architecture Morning all, For a little light relief, why don't we spend a little time deciding what "Architecture" means? ;-) Seriously, it is relevant to the current debate - a good architecture will support many and varied implementations without creaking. Regards, Alan. <http://www.seebeyond.com/> Go to SeeBeyond website >" hspace=0 src="http://www.seebeyond.com/images/i_seebeyodlogoSmallnotag.gif" width=180 align=absMiddle border=0 NOSEND="1"> _____ Alan Davies VP Standards ph: +1-626-471-6050 cell: +1-626-437-0272 adavies@SeeBeyond.com <mailto:adavies@SeeBeyond.com>
Received on Tuesday, 5 March 2002 15:54:34 UTC