a unifying approach to cois metadata and soa n.
Skip this Video
Loading SlideShow in 5 Seconds..
A Unifying Approach to COIs, Metadata, and SOA PowerPoint Presentation
Download Presentation
A Unifying Approach to COIs, Metadata, and SOA

A Unifying Approach to COIs, Metadata, and SOA

80 Views Download Presentation
Download Presentation

A Unifying Approach to COIs, Metadata, and SOA

- - - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript

  1. A Unifying Approach to COIs, Metadata, and SOA Dr. Marwan SabbouhJeff Higginson

  2. Background • 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 • Since the layered architecture model does not specify data standards, multiple instantiations have developed • CoT, UCORE, VMF, Link 16, etc. • To manage these data standards, 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”

  3. Objective • Provide a simpler alternate method to allow vocabularies within domains (or COIs), while allowing for sharing across domains (or COIs) • Based on idea of loose couplers • Not focused on a single solution • The UCORE will influence multiple Common Cores • Recognize that legacy systems dominate and that today’s systems are tomorrow’s legacy systems • And that technology will continue to present better alternatives • This briefing outlines the result of interoperability work at ESC, and our approach for demonstrating the results of these efforts

  4. Integrating the Strategies

  5. In Principle, It Is Simple…But Too Many Artifacts and Actors, Results in Complex Processes

  6. Recommended COI Pilot Process

  7. Tie the Artifacts; Unite the Actors Metadata Mappings do for data interoperability what Mashup Editors have done for code

  8. Resulting Changes to the Recommended COI Pilot Process

  9. Demonstration – UCORE to CoT • Tasking began with leveraging COI work to meet operational needs, specifically showing Blue-Force tracks in cockpit (situation awareness for fratricide avoidance) • Leveraging CoT enabled platforms (cockpits) to illustrate data interoperability • Activity took a basic look at evolving Strike, UCORE activities, and mapping into CoT focused tactical data network updates • This mapping has been accomplished • Will be supported with automation in future spirals

  10. UCORE to CoT Translator

  11. Sample WMSL Discovery Metadata Schema Import Mappings Code

  12. Mapping “What”

  13. Mapping “When”

  14. Mapping “Where”

  15. Key Thoughts • This strategy that can accommodate multiple data standards • Shows preference for none • Supports process improvement • Process improvements to better streamline a manual (negotiation intensive) activity that works across COIs • Requires only the development of data mappings • That can be supported with automated tools • We suggest that this is a fundamental part of the way forward to manage the data interoperability • Migration from legacy standards, i.e. executing the DoD data strategy • Unifying the process for generating metadata and code - do for metadata what mashups is doing for code

  16. Backup Charts

  17. Simplified View of the Enterprise (backup) How do we make these pieces work together?

  18. Mapping Table (backup)

  19. Innovation vs. Integration

  20. A Structured Approach

  21. Can Mappings be Integrated into the COI Process?