| Thread Links | Date Links | ||||
|---|---|---|---|---|---|
| Thread Prev | Thread Next | Thread Index | Date Prev | Date Next | Date Index |
|
Jim,
I would agree that IEEE 1471 is the standard for enterprise architecture descriptions. However, I would question its relevance for describing Enterprise Architecture Ontologies. IMHO, IEE 1471, FEA, TOGAF and C4ISR are frameworks. The problem with a framework is that it does not provide explicit set of guidelines for creating definitions. It has been my experience that EA projects rise and fall on the ability to reach consensus on definitions (e.g. objective, function, IS-A relationships, IS-Part-Of). Ontology Engineering principles and the underlying logic systems would provide a better tool for evaluating definitions than the current EA frameworks and give EA architects a more robust platform for performing trade-off analysis.
Zachary Alexander The IT Investment Architect ebTDesign LLC, (703) 283-4325 http://www.ebTDesign.com | http://www.semanticviewpoint.com | http://www.p2peconomy.com
-----Original Message-----
Jim,
I have not seen any announcements of Enterprise Architecture Ontology Work.
However, using ontology engineering practices should really help in standardizing Enterprise Architecture Descriptions. If you are thinking about developing an EA ontology, I would look at the presentation Leo Orbst gave to the Ontoforum. The presentation really outlines the differences in ontology representation. The ontology representation will have a huge impact on the Enterprise Architecture description and the potential to do automated reasoning about the resources. I would also look at some of the old semantic modeling discussions, circa 1980, early 1990.
[1] http://ontolog.cim3.net/file/resource/tutorial/OntologiesForSemanticallyInteroperableSystems-ONTOLOG--LeoObrst_20040115b_files/frame.htm
Zachary Alexander The IT Investment Architect ebTDesign LLC, (703) 283-4325 http://www.ebTDesign.com | http://www.semanticviewpoint..com | http://www.p2peconomy.com
-----Original Message-----
Folks,
'Enterprise Architectures' are in vogue, but when a large organization has multiple subordinant organizations independently developing their own enterprise architectures, there barely relate.
Is anyone aware of the use of an ontology for describing an Enterprise Architecture? Or better yet, use of a common domain ontology for describing multiple architectures?
As an example, the U.S. Federal Enterprise Architecture is at http://www.feapmo.gov/fea.asp.
Jim Schoening
|