[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Public Comment
Comment from: jestefan@jpl.nasa.gov Name: Jeff A. Estefan Title: Systems & Software Division Technologist Organization: Jet Propulsion Laboratory, California Institute of Technology Regarding Specification: SOA-RM FAQ Errata: In item 6 of your FAQ (http://www.oasis-open.org/committees/soa-rm/faq.php) you have the reference "IBM's Rose Unified Process (RUP)...". This should read "IBM's Rational Unified Process (RUP)", i.e., the word "Rose" should be replaced by "Rational." In item 3, your definition of Software Architecture does not make reference to "principles." All architectures (software architectures or otherwise) should have a set of guiding principles. A good generic reference definition for architecture is the IEEE 1471-2000 (see http://standards.ieee.org/reading/ieee/std_public/description/se/1471-2000_desc.html). Candidate Reference Model: You should consider the candidate SOA reference model illustrated in Fig. 2-6 on page 25 of the IBM Redbooks entitled "Patterns: Service-Oriented Architecture and Web Services" available at the following URL: http://www.redbooks.ibm.com/redbooks/pdfs/sg246303.pdf Note that there is not tie to IBM implementation specific products. It is a generic reference model. For a mapping to emerging specifications/standards, see Fig. 5-1 on page 108. Of course, there are a myriad of other non-proprietary/implementation independent candidate reference models. Future Membership: We are JPL are very interested in this body of work and I am in the process of working through the chain to establish JPL as a Contributing member. Regards... - J.A.E.
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]