This site employs JavaScript, but your browser does not support JavaScript. Please enable JavaScript on your browser, or if your browser does not support JavaScript, access this site with a browser that does support Javascript.



          Help and Features: Mapping Information Exchanges

Overview
  • With this tool, you will create an exchange, associate a exchange model with that exchange, map the exchange model to NIEM, and generate artifacts - such as mapping reports, wantlists, and schemas - based on that mapping.
  • You may use the tool without an account; however, if you do not have an account, no exchanges you create, no exchange models you upload, no mappings you create, and no artifacts you generate will persist after your session ends. To save your exchanges, exchange models, mappings, and artifacts, you must create an account.


Create a Exchange Model
  • Before you begin, you will need a exchange model. A exchange model represents your local data, which you will map to NIEM.
  • The exchange model must be an XMI representation of a UML 1.4 or UML 2.1 metamodel. Such exchange models may be created in a tool like ArgoUML or Eclipse.
  • When you have a exchange model, you may begin to create an exchange.


Create an Exchange
  • To create an exchange, click create an exchange under the list of exchanges.
  • You may rename your exchange. To rename the exchange, type a new name into the text box below the "Currently Selected" label.
  • To save your changes, click "save."


Upload a Exchange Model
  • To upload a exchange model, click the "browse" button below the "Exchange Models" label. The browser will prompt you to upload a exchange model file; select the file and click the "open" button. The browser will upload the file, then the tool will parse the file. If the parse is successful, the name of the exchange model will appear below "Exchange Models."
  • On upload, the system parses UML Classes, DataTypes, Attributes, and Associations; at present, other UML is ignored.
  • After parsing, the system attempts to organize the parsed UML as a tree. The root of the tree is the Class with either Attributes or outgoing Associations but without incoming Associations. If this describes more than one Class in the exchange model, each such Class will appear as the root of a separate tree.
  • To save your changes, click "save."
  • After you have saved your changes, you will have an exchange and a exchange model that you may map to NIEM.


Map a Data Model
  • In this step, you will map a exchange model to NIEM.
  • To map a exchange model in an exchange to NIEM, click "map" under the name of the exchange in the list of exchanges. The tool will forward you to the next step, where you may select a exchange model to map.
  • To select the exchange model to map, click the name of the exchange model below the label "Exchange Models." The tool will forward you to the next step, where you may select a data element to map or note.
  • If you wish to search NIEM for a component with a similar name to a data element, click "search" adjacent to the name of the data element. The tool will foward you to the next step, where you may map to a NIEM component.
    • To map a NIEM component to a data element, click "map" beside the name of the NIEM component. The tool will forward you to the next step, where you may make a note about the selected data element.
    • If you wish to search NIEM for a phrase of your choice, type the phrase into the text box below the label "Search," then click "search."
  • If you wish to make a note about a data element, click "note" adjacent to the name of the data element. The tool will foward you to the final step, where you may make a note about the data element.
    • If you wish to note the type of mapping, click a radio button below the label "Mapping Category."
      • Equivalent - Semantics and structure map appropriately. The NIEM element name and definition do not have to be the same as the source element name and definition, but they should have exactly the same meaning.
      • Partial Match - The elements/semantics partially match. Otherwise, there are no mismatch or conflict.
      • Semantic Conflict - The type/structure maps appropriately; the element/semantics do not.
      • Structural Conflict - The element/semantics map appropriately; the type/structure does not. The NIEM element name and definition do not have to be the same as the source element name and definition, but they should be similar in meaning.
      • No Match - No NIEM element or type maps to the source requirement.
    • If you wish to note other information, type the information into the text box below the label "Mapping Notes," then click "search."
    • After you have note the type of mapping or other information, click "save."
  • After you have mapped a data element, you may generate mapping reports, wantlists, and schemas.


Generate Artifacts
  • In this step, you may generate and download artifacts for an exchange. You may use the generated artifacts as templates to write your final artifacts.
  • To generate an artifact, click "generate" below the section for that artifact.
  • To download an artifact, click the name of the artifact.
  • To delete an artifact, click "delete" beside the name of the artifact.