1 / 9

Integrating information towards Digital ATM

Integrating information towards Digital ATM. AIXM Modularity Considerations. Presented By: Katrina Wilson Date: August 29, 2013. Agenda. What is our Vision ? Information Service Reference Model What is Modularity? Why? Proposal. 1. What is our Vision?.

odelia
Download Presentation

Integrating information towards Digital ATM

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. Integrating information towards Digital ATM AIXM Modularity Considerations Presented By: Katrina Wilson Date: August 29, 2013

  2. Agenda • What is our Vision? • Information Service Reference Model • What is Modularity? • Why? • Proposal 1

  3. What is our Vision? • Practitioners at all levels of aviation share accurate, complete, timely and appropriately secured information to ensure public safety. • To produce “exchange schemas” which offer a high degree of clarity, interoperability and reusability while being agnostic to the actual deployment software tools. • Alignment to domain data model components dictionary – interoperability across domain applications. 2

  4. Information Service Reference Model 3

  5. What is Modularity? • From Wikipedia, “Modular design is an approach that subdivides a system into smaller parts (modules) that can be independently created and then used in different systems to drive multiple functionalities. Improve maintainability by enforcing logical boundaries between components”. 4

  6. Why? • Encourages reuse by creating well-defined modules that perform a particular task • Increases flexibility and maintainability because single modules can be upgraded or replaced independently of others • Eases development, testing, and maintenance by providing a logical, easy to understand, and consistent organization 5

  7. Proposal • Encapsulate Features and Usage • Generate XSD by Subject Area/Domain data model components • Evaluate Reorganizing Packages • Common XML features XML Schema are XML documents themselves and therefore share many aspects of the languages they define. 6

  8. 7

  9. Contact Information • Questions - Please contact us at 9-ATO-ATF-910-InfoDelivery@faa.gov • Katrina Wilson • FAA – Computer Specialist • Barbara Cordell • FAA – Manager - Data and Information Architecture Team 8

More Related