1. New Applications Modeled

2. Introduction Paul Heffley Contractor, L-3 Communications
FAA Air Traffic Organization (ATO) Information Technology
Engineering & Configuration Management

3. Discussion Points UML Package Structure UML Extensions
New Enumerations and Code List Extensions
Application Schemas (Data/Message Packages)

4. Information Exchange
The core AIXM structure provides the foundation of aeronautical features
Communities of Interest can exchange data using either:
Predefined web service (I.e. Web Feature Service)
Custom developed AIXM messages (Application Schemas)

5. Application Schemas
Designed to provide a custom developed AIXM message for a specific Community of Interest
Basic principles that regulate Application Schemas:
An extension of an existing AIXM Feature should remain valid against the definition of the core AIXM XSD element with the same name
An additional feature shall follow the core AIXM modeling conventions (stereotypes, naming, data types, etc.)
New stereotypes for collections and choices have been added for the message structure

6. UML Package Structure The ‘Core’ model VS.
Application Schemas and Extensions

7. XSD Specifications
The Community of Interest will define the Target Namespace and Prefix which are used when generating the XML Schema
Element and Attribute Form Defaults are set to qualified and unqualified respectfully
For ease of file naming, the Generate Filename property is overridden to provide a consistent file name

8. File Imports & Includes
Files within the same namespace should be ‘included’
Files external to the namespace should be ‘imported’
The path is configured to match the directory structure of the UML Model

9. Feature/Object Extensions
The extension class stereotype must be <<extension>>
The class name for the extension must match the class you are extending
The extension class must be a specialized class extending the matching base class
The extension class attributes are added to the extension class the same way they would be added to a core AIXM class

10. Extensions in the XML Schema
The <classname> ExtensionProperyGroup contains the properties (elements and relationships) of the Extension
The <classname> ExtensionType element is generated as a XMLSchema <complexType.> and extends base type aixm:AbstractExtensionType
The <classname> Extension element is generated as a XMLSchema <element>

11. New Enumerations
To add new enumerations create a second sub-package, the data types extension package, containing any new enumerations (or code lists) that are needed
It is not possible to extend <<enumerations>> or <<datatype>> classes. Only a <<codelist>> may be extended
Always use ‘OTHER’ as a value

12. Code List Extensions
Extend a code list by creating a class with the same name as the code list and giving it a stereotype of <<enumeration>>

13. Designated Point (Fix) Enumerations

14. Designated Point (Fix) Extensions

15. Fix Holding Data

16. Fix Holding Data Record

17. Application Schema
Modeling Demo

18. Questions
Paul