1 / 8

Accessing, Sharing, & Leveraging EA Information

a|EA International Committee on EA Standards. Accessing, Sharing, & Leveraging EA Information. Steve Hunter Chair – EA (Meta)Model  Representation and Interoperability Chair - EA Standardized Metamodels Steve@Agilense.com 703-878-2475.

priestj
Télécharger la présentation

Accessing, Sharing, & Leveraging EA Information

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. a|EA International Committee on EA Standards Accessing, Sharing, & Leveraging EA Information Steve Hunter Chair – EA (Meta)Model  Representation and Interoperability Chair - EA Standardized Metamodels Steve@Agilense.com 703-878-2475 * NOTE: The author’s affiliation with Agilense, Inc. is provided for identification purposes only, and is not intended to convey or imply Agilense concurrence with, or support for, the positions, opinions or viewpoints expressed by the author.

  2. Association of Enterprise Architecture (a|EA) The mission of the Association of Enterprise Architecture (a|EA) is to provide a global forum for the advancement of the profession and practice of enterprise architecture. “by Architects for Architects”

  3. Architecture Information Context Architects need a particular set of structured information to perform their role. In the ideal scenario an architect would have ready access to any and all information describing the enterprise. The Enterprise Template (Metamodel) (structured information used to blueprint an enterprise) “the kind of information of interest to the business” The Enterprise a subset necessary for the architect to perform the architects role. Architecture Management Tools structured and unstructured actual information conforming to the metamodel Information Source1 Information Source2 Information Source..n

  4. Implementation Issues Reality - enterprise information exists in many places, in many formats, with political and technical issues related to access and using the information. Metamodel – who defines it, who manages it, how is it modified, where is it stored, how is it shared ? How to establish an Information-Net™ Architecture Management Tools Architecture Repository What goes in it?, how to access, how to share ? How to access, how to ensure stewardship, how to ensure consistency with metamodel EA Information Source1 EA Information Source2 Information Source..n

  5. Within the EA community Unfortunately – even EA tools, significant sources for EA information, are unable to (easily) share information Architecture Management Tools Architecture Repository Metamodel Representation Differences Metamodel Concept Differences Data representation differences Input/Output exchange differences Architecture Repository

  6. Relationship to ONTACWG EA Tools are a Mix of ER, ORM, and OO models which use a “visual semantic” to express what is equivalent to predicates in knowledge representation languages. Axioms: A CAT MAY HAVE ZERO or more LEG(s) (where ----- is assumed to mean “hasedby---------has” LEG CAT 0..4 LEG A CAT MAY HAVE ZERO to FOUR LEG(s) (where ----- is assumed to mean “hasedby---------has” CAT Connected to 0..4 A CAT MAY HAVE ZERO to FOUR LEG(s). “If the cat dies, the legs go with it”. LEG(s) are connected to at most 1 cat LEG CAT 0..1 has Connected to 0..4 Connection CAT LEG 0..1 has Weight Ratio (Connection(CAT, 0..1, connectedTo, LEG, 0..4, has))

  7. Mission of this a|EA Standards Committee • Enable its members to adopt tools that can access and share the information they need to perform their work by: • Defining aEA standards for information representation and sharing between EA tools (“practice what we preach”) • Defining aEA standards for information representation and sharing between other information sources • Defining an infrastructure architecture for creating an Information-net, a means to establish the containment space for information used by the architect. • Identification, and possible recommendation of standard metamodels*

  8. a|EA International Committee on EA Standards Committee on EA (Meta)Model  Representation and Interoperability - Scope/Business Case/Charter - Content & Graphical Model Depiction Working Group - standard representation for content “models” - standard representation for visualization “diagrams” - standard format for information exchange - Exchange Infrastructure Working Group - information space containment solution - exchange service architecture Committee on EA Standardized Metamodels: - Scope/Business Case/Charter - Standardized initiative/program/project mgt metamodel

More Related