InfoQ has gathered a virtual panel of Enterprise Architects who have lived and implemented SOA for most of this decade to better understand what SOA means to IT in 2009.
The Open Group's SOA Source Book is a collection of source material for use by enterprise architects working with Service-Oriented Architecture.
It consists of material that has been considered and in part developed by The Open Group's SOA Working Group. The SOA Working Group is engaged in a work program to produce definitions, analyses, recommendations, reference models, and standards to assist business and information technology professionals within and outside of the Open Group to understand and adopt SOA. The source book does not represent the final output of that work program, which will be published as a collection of Open Group Standards and Guides. It is an interim publication, and its content will not necessarily be reflected in the final output.
The material reflects input from a large number of people from a wide range of Open Group member companies, including product vendors, consultancies, and users of SOA. In some cases, these people have brought concepts developed, not just by themselves, but by groups of people within their organizations. The input has been refined and further developed through discussion within the Working Group. The value in the result is due to the ideas and efforts of the Working Group members.
The material is now published in its current form to make that value available to the wider architecture community.
In the book The Art of War for Executives, Donald G. Krause interprets the following: “Sun Tsu notes, superior commanders succeed in situations where ordinary people fail because they obtain more timely information and use it more quickly.” For metadata professionals, this observation is increasingly relevant as more and more of the business seeks integration and federation, alignment with business goals and strategies, and agility - the ability to respond both quickly and accurately to change. Industry analysts and IT professionals are less focused on solutions to problems where metadata management plays a role but rather look more to metadata management as an overall strategy for the benefits it provides to multiple aspects of the whole organization.
IAwiki is a collaborative knowledge base for the topic of InformationArchitecture. Anyone can contribute, and there are no pre-registration hoops to jump thru ... just click the "Edit This Page" link at the bottom of any page.
I'm a big believer in Information Architecture as a community of practice, and I also believe it's good for such a community to have a "home base," especially if they're a virtual organization spread all over the globe like ours.
Consider an [arbitrary] piece of code. It's indoors, it's well behaved, and you can be proud of it. What is it about that code that you like? Is it elegant? Is it clever? Does it enable something? How would you measure the value of code?
B. Wang, C. Wen, W. Zhu, and J. Sheng. International Symposium on Computer Science and Computational Technology, 2008. ISCSCT '08, 2, page 383--386. IEEE, (December 2008)
Y. Oh, D. Lee, S. Kang, and J. Lee. 5th IEEE/ACM International Conference on Formal Methods and Models for Codesign, 2007. MEMOCODE 2007, page 87--88. IEEE, (June 2007)
S. Giesecke, J. Bornhold, and W. Hasselbring. The Working IEEE/IFIP Conference on Software Architecture, 2007. WICSA '07, page 21--21. IEEE, (January 2007)
S. Angelov, P. Grefen, and D. Greefhorst. Joint Working IEEE/IFIP Conference on Software Architecture, 2009 & European Conference on Software Architecture. WICSA/ECSA 2009, page 141--150. IEEE, (September 2009)
R. Kent. (2011)cite arxiv:1109.0983Comment: Presented at the International Category Theory Conference (CT 2006) June 25 - July 1, 2006 at White Point, Nova Scotia.