3: Map & Model

Associate local objects with types and elements in NIEM.

Other Information:

This process is called mapping a domain model to NIEM. Purpose: Create an exchange content model; associate local data objects with types and elements in NIEM Key Considerations: * Reusing NIEM elements increases consistency and promotes reuse * Each data object should be mapped to an element or type in NIEM, if possible; Do not force the mapping if it does not make sense * Implementers will create "extensions" to the NIEM data model for elements that do not directly map to NIEM data objects There are a number of tools currently available and being developed that support various stages of IEPD development. NIEM.gov Tools: Capability includes searching the NIEM data model, artifact generation, mapping to NIEM, and more. Available through NIEM.gov. NIEM Wayfarer: Capability includes advanced searching of the NIEM data model. Publically available online.* XML Software: Standard XML editing software can greatly aid the development of NIEM schemas. Free, open source XML software is available in addition to software distributed by vendors.

Stakeholder(s):

• Project Manager
  • Expectation Establishment (Performer): Establish expectations for exchange content model development, including how business requirements and rules are reflected in the model
  • Communication (Performer): Communicate with architects to discover how closely business needs map to the NIEM data model
  • Coordination (Performer): Coordinate review of the exchange content model and mapping document with multiple technical stakeholders

Objective(s):

3.1: Exchange Content Model

3.2: Mapping Document

Content