How can various government departments and organizations communicate in a cost effective and reliable manner?
How can different organizations exchange information when they use different terminology and employ a different database structure?
The National Information Exchange Model (NIEM) is a robust XML-based framework for the exchange of information between people, organizations and communities. This webinar will examine the benefits of using Enterprise Architect to model and define how information can be shared using the NIEM standard.
In this webinar you will learn how to:
Don't miss this opportunity to learn more about Enterprise Architect
Enterprise Architect 12.1 is required to model and implement NIEM.
Enterprise Architect's MDG Technology for NIEM helps you to:
The National Information Exchange Model (NIEM) provides a common framework that is used to define how information can be shared between systems, government agencies and organizations.
To learn more about NIEM, visit the NIEM.Gov website.
The Enterprise Architect User Guide also contains a detailed description and a number of examples that can help you to learn more.
A step by step tutorial on NIEM has been published that implements techniques similar to what was demonstrated throughout the webinar.
To learn more about NIEM, complete the following tutorial.
NIEM helps connect communities in order to share and exchange information. The Enterprise Architect platform comprehensively supports the National Information Exchange Model (NIEM), which provides a common framework used to define how information can be shared between systems, government agencies and organizations. NIEM originated in 2005 and has been used successfully in a large number of information exchange projects. The Best of NIEM page showcases some winning examples.
The demonstration was conducted using Enterprise Architect 12.1, build 1230. Build 1230 introduced a number of improvements to our NIEM implemetation, based on feedback from customers and partners.
To use NIEM and Enterprise Architect, you need to install Enterprise Architect 12.1. The model wizard will automatically build the NIEM reference model and starter model.
Yes. Launch the importer with "Extensions | NIEM 3.0 | Import NIEM 3.0 Schema".
The importer does a very good job of importing. However, if you just specify a set of schema files, then you won't have the model framework that is provided by the NIEM 3.0 Starter Model - the things like the MPD object instance, the conformance targets and the "Model Description" part of the model that is represented on the MPD diagram.So you won't be able to generate the schema files back out again, unless you do the work to create the MPD diagram.
You can model all of these elements within Enterprise Architect and all of the NIEM UML tools
The specification contains a rather rigid outline about what an IEPD should look like.
It is up to the user to create the change log file and to save it to the appropriate location for their IEPD.
Using Enterprise Architect, you can model the relationship between the MPD instance and the ChangeLog artifact.This allows you to specify the URI for the change log, as a tag value on the <<ChangeLog>> usage connector.
That information is subsequently generated into the file "mpd-catalog.xml".
The following link provides additional details.
IEPD stands for Information Exchange Package Documentation. An IEPD is a collection of artifacts that define and describe the structure and content of an information exchange.? In the webinar I opened an IEPD and navigated through the directory structure, trying to highlight what an IEPD might look like.
Enterprise Architect does NOT generate or create Conformance Targets or ChangeLogs for you.
Conformance Targets (and also ChangeLogs) are defined and described in the document:
There are a number of MPD artifacts that can be modelled on the NIEM MDP diagram. Amongst these are IEPConformanceTargets and the artifacts that they reference. An example of this is provided in the NIEM 3 Starter Model.
Stereotyped Usage connectors are used to specify relationships between ConformanceTargets and artifacts that they use. The usage stereotypes include such things as IEPSampleXMLDocument, XMLCatalog, SchematronSchema and XMLSchemaDocument, as well as ReadMe, MPDChangeLog, ConformanceAssertion and ConformanceReport.
URI's for the artifacts are specified as Tag Values on the Usage connectors to link to them.
The MPD diagram is basically a visual representation of the contents of the IEPD you are modelling.
When you generate the IEPD, the information depicted by the MPD diagram is generated into the file "mpd-catalog.xml", which is essentially a "table of contents" for the IEPD.
In the webinar I used the search feature in the Project Browser to rapidly find classes that I wanted to use. Once you become familiar with NIEM, it becomes much easier to find the Classes and Attribute you need in a timely manner.
Please refer to the to learn more about searching NIEM User Guide on Model Search to find what you need quicker.