Ontologies are the Esperanto for the Babel Fish of the 21st Century (part 10)


Pulling it all together

Business and end users require ontologies to trade and communicate, ontologies provide the single taxonographic (language) interface (syntax & semantics) for service (business and system) interaction (consumption and provision) both internally and externally in the enterprise.Ontologies are expressed as Canonical Data Models (CDM) (amongst other things), CDM’s are implemented in Master Data Management (MDM) enterprise capability providing an Enterprise CDM (ECDM).

MDM is implemented in Event Driven Architecture (EDA) and Services Oriented Architecture (SOA) and provides services (ECDM and others) which expose enterprise ontology(ies)  (and other services) internally to enterprise and externally through enterprise services.

EDA/SOA are implemented on ESB. 7 layer model technologies (IS & TI) required to build an ESB ( EDA/SOA, BPM, Rules, MDM, CEP, MOM, others) require ontologies specific to them (as does ESB itself for autonomic – reporting and self healing – capabilities), these are harnessed by CEP and integrated into MDM for business intelligence over 7 layers of technology stack.

All these technology initiatives; Ontologies, MDM, EDA, SOA, CEP, ESB, BPM, Rules, MOM, MDA, ODM, etal, require a, common, mature, stable, standards base.

Model Driven Architecture (MDA) through Ontology Definition Metamodel (ODM), OMG EDA/SOA standards and OMG base standards (and dependent third party standards from OASIS, W3C, etal) provide rigour in ontological design, implementation, management and integration for tool support into the enterprise systems horizontally and vertically across the 7 layer model technology stack and across all rows and columns of the Zackman Enterprise Framework and all aspects of the IAF.

Ontologcial implementation in the enterprise is complex, time consuming and expensive. Requires strong business buy in and governance framework to implement successfully. Application to enterprise and business should be approached as a strategic initiative and requires lots of planning, governance, oversight. However should be implemented in tactical small scale initiatives when the opportunity presents itself in Enterprise Architecture (EA) cycle. Should avoid big bang approach to implementation. Should be integrated into EA cycle as per best practice and TOGAF recommendations as it has touch points through out enterprise and business at all levels.



Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

%d bloggers like this: