Conformance Validation Tool
- Assists developers by automatically identifying potential locations of non-conformance within IEPD artifacts.
The tool uses the latest published NIEM Naming and Design Rules (NDR) 1.3 and associated IEPD specifications.
NIEM schema developers can upload an IEPD, a set of schemas in a zip file, or an individual schema and receive a report identifying any NIEM NDR rules that have been violated.
NDR rules that auto-pass, auto-fail, or that require manual review are clearly labeled in the resulting spreadsheet validation report.
The current tool automatically checks 78 out of about 180 NDR rules.
Search - New specialized searches that can be turned on or off include:
Key word search - Searches the new key word field for components that contain common synonyms and slang for components (e.g. "cop" for EnforcementOfficial)
Usage description search - Searches the new usage description field that contains common uses for a given component.
Use example search - Searches the new use example field that may contain several common sample values or a description of such values for a given component.
Note that at present the key word, usage description, and use example fields are sparsely populated. As more data for these fields is harvested and inserted, these searches will become more effective.
Context search - Searches inherited components that may have more generic names than the search criteria entered by the user. For example, an arrest date may be the ActivityDate inherited by an ArrestType that is derived from ActivityType. Therefore ActivityDate is the appropriate element for arrest date in the context of Arrest.
Adding components to a subset is now faster and more efficient; requires only one click instead of two.
Easy access to pre-generated subsets including Universal, Common, domains, etc.
Support has been added for building a subset across multiple sessions without having to download and upload.
Map Data Requirements - Users can upload an XMI representation of a UML 1.4 or UML 2.1 metamodel.
Subsequently, a user can map his/her exchange model (with cardinality constraints) to NIEM, and:
Generate a detailed mapping report.
Create a subset schema.
Create a wantlist (for that subset schema).
Create a basic exchange schema template. This template can be downloaded and edited as required.
Create a basic extension schema template containing the components that could not be mapped to NIEM. This template can be downloaded and edited to add additional components and constraints as required.
Create a basic constraint schema template containing cardinality constraints captured from the XMI exchange exchange model. This template can be downloaded and edited to add additional constraints as required.
All artifacts generated can be downloaded separately or bundled in a conforming IEPD with the appropriate metadata and catalog files and documentation.
Work with IEPDs - Users can assemble and package NIEM conformant IEPDs by either uploading IEPD artifacts or adding those generated through the NIEM tool suite.
Users can save IEPDs in a personal workspace within the tool repository, and optionally share either full IEPDs or selected IEPD artifacts with others.
Users can search and reuse shared IEPDs.
Links are provided to other IEPD repositories (e.g., the
IEPD Clearinghouse).
Details for how to search for and register IEPDs with other repositories are provided.
NIEM Tools: New Capabilities and Features