A Unifying Approach to COIs, Metadata, and SOA Dr. Marwan Sabbouh Jeff Higginson

Approved for Public Release; Distribution Unlimited; Case Number Copyright The MITRE Corp. All Rights Reserved 2 Background n Early in the struggle for interoperability, a “layered” approach to IT architecture was proposed to promote interoperability, modularization, and reuse –This approach held promise, but did not assure interoperability or drive common data standards n Since the layered architecture model does not specify data standards, multiple instantiations have developed n To manage these data standards, Community of Interests (COIs) formed to develop common vocabularies –COI process assures a well defined vocabulary will develop –Now the challenge becomes “how to optimize data shared across COIs”

Approved for Public Release; Distribution Unlimited; Case Number Copyright The MITRE Corp. All Rights Reserved 3 Integrating the Strategies

Approved for Public Release; Distribution Unlimited; Case Number Copyright The MITRE Corp. All Rights Reserved 4 In Principle, It Is Simple…But Too Many Artifacts and Actors, Results in Complex Processes

Approved for Public Release; Distribution Unlimited; Case Number Copyright The MITRE Corp. All Rights Reserved 5 Tie the Artifacts; Unite the Actors Metadata Mappings do for data interoperability what Mashup Editors have done for code

Approved for Public Release; Distribution Unlimited; Case Number Copyright The MITRE Corp. All Rights Reserved 6 UCORE to CoT Translator Shared Vocabulary Imports of schemas lines entities mappings or metadata 5 lines Workflow Mediation Common Data Model Web Page Automatic Generation of Shared Vocabulary and Common Data Model Tracking Service Universal CORE Display CoT Driver BFT UCORE  CoT Web Page Implements Workflow

Approved for Public Release; Distribution Unlimited; Case Number Copyright The MITRE Corp. All Rights Reserved 7 Sample WMSL Discovery Metadata Schema Import Mappings Code

Approved for Public Release; Distribution Unlimited; Case Number Copyright The MITRE Corp. All Rights Reserved 8 Mapping “When”

Approved for Public Release; Distribution Unlimited; Case Number Copyright The MITRE Corp. All Rights Reserved 9 Mapping “Where”

Approved for Public Release; Distribution Unlimited; Case Number Copyright The MITRE Corp. All Rights Reserved 10 Key Thoughts n This strategy that can accommodate multiple data standards –Shows preference for none n Supports process improvement –Process improvements to better streamline a manual (negotiation intensive) activity that works across COIs n Requires only the development of data mappings –That can be supported with automated tools n We suggest that this is a fundamental part of the way forward to manage the data interoperability –Migration from legacy standards, –Unifying the process for generating metadata and code - do for metadata what mashups is doing for code

Backup Charts

Approved for Public Release; Distribution Unlimited; Case Number Copyright The MITRE Corp. All Rights Reserved 12 Simplified View of the Enterprise (backup) How do we make these pieces work together ?

Approved for Public Release; Distribution Unlimited; Case Number Copyright The MITRE Corp. All Rights Reserved 13 Innovation vs. Integration

Approved for Public Release; Distribution Unlimited; Case Number Copyright The MITRE Corp. All Rights Reserved 14 A Structured Approach