AletschGueggisgratDavos Wiesner Alp

Invited Talks

Enterprise Architecture: The Issue of the Century

John A. Zachman, Chairman, Zachman International, Inc.


Wednesday, October 14, 2015 / 08:40 - 09:40

Enterprise Architecture tends to be a grossly mis-understood subject by General Management and the Information Technology community alike.  Enterprise Architecture has everything to do with managing Enterprise complexity and Enterprise change and relates to information technology only in so far as information technology may be one of the choices that an Enterprise can make with regard to Enterprise operations.  In my 1999 article, “Enterprise Architecture: The Issue of the Century”, I argued that the Enterprise that can accommodate the concepts of Enterprise Architecture will have the opportunity to stay in the game … and the Enterprise that cannot accommodate the concepts of Enterprise Architecture is not going to be in the game.  In recent history we have seen a lot of enterprises falling out of the game: small … and large;  private … and public.

  •  The Enterprise Ontology – Industry Standard Definitions of Architecture
  • Architecture IS Architecture IS Architecture – Enterprise Architecture is not arbitrary
  • Ontologies Versus Methodologies – “and,” NOT “either/or”

 

Agile Modelling Method Engineering

Prof. Dr. Dimitris Karagiannis, University of Vienna

 

Thursday, October 15, 2015 / 08:30 - 09:30

In this context, the foundations of a “conceptual-model”-awareness approach for next generation Enterprise Information Systems will be presented. This novel approach makes use of semantic networks to extend model-awareness towards arbitrary types of models that are developed for specialized communities aiming for domain-specificity (or even case-specificity) in their modeling language, therefore favoring productivity at the expense of reusability across domains. 

The technological space for capturing and bridging knowledge through model semantics is primarily based on diagrammatic models. Two categories of models are employed in this context: (1) Models of Concepts – for describing a common understanding of a domain through its concepts and relations; (2) Models that use Concepts – typically domain-specific models based on some already established understanding of the domain. The hereby introduced Agile Modeling Method Engineering –AMME- concept aims to apply the principle of agility established in Software Engineering (e.g., evolutionary development, flexible response to change) to the practice of Modeling Method Engineering. The main assumption is that a modeling method may evolve iteratively based on changing modeling requirements and feedback loops.

Within the context of AMME, a full methodological life cycle is established by the OMiLab Laboratory (www.omilab.org), with encompassing five phases: (1) create, (2) design, (3) formalize, (4), develop and (5) deploy/validate. The approach is supported, in its  prototyping stage, by the  meta modeling domain-specific language MM-DSL and within the academic version of the meta-modeling platform ADOxx (www.adoxx.org).