1 / 23

Agenda

Agenda. The NIEM Framework What common services , governance models, processes and tools are provided by NIEM? NIEM Specifications & Processes What is the NDR and MPD Specification? What is the IEPD Development Life Cycle?

yahto
Download Presentation

Agenda

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Agenda The NIEM FrameworkWhat common services, governance models, processes and tools are provided by NIEM? NIEM Specifications & ProcessesWhat is the NDR and MPD Specification? What is the IEPD Development Life Cycle? NIEM GovernanceHow is NIEM governed? How does the federated domain governance function? What are the different NIEM committees? Future OutlookWhat is NIEM 3.0? What is the scope and timeline for release? Where can I find more information? How does NIEM-UML relate? 2

  2. The NIEMFRAMEWORK What common services, governance models, processes and tools are provided by NIEM?

  3. The NIEM framework NIEM connects communities of people who share a common need to exchange information in order to advance their missions, and provides a foundation for seamless information exchange between federal, state, local, and tribal agencies. Much more than a data model, NIEM offers an active user community as well as a technical and support framework. Community Technical Framework Support Framework Tools for Development and Discovery Data Model Formal Governance Processes Established Training Program Online Repositories XML Design Rules Development Methodology Implementation Support Mission-Oriented Domains Help Desk & Knowledge Center Self-Managing Domain Stewards Predefined Deliverables (IEPD) 4

  4. Standardizing Data Moving Across Systems Scope-of-NIEM COMMONLY FORMATTED DATA INTERFACE INTERFACE LEGACY DATABASES LEGACY DATABASES Translation • NIEM intentionally does not address standardizing data inside legacy systems. NIEM serves as a translation layer (providing a common understanding) between and across disparate systems. 5

  5. The NIEM LIFECYCLES Common Language(Data Model Lifecycle) Repeatable, Reusable Process (Exchange Specification Lifecycle) Built and governed by the business users at Federal, State, Local, Tribal and Private Sectors 6

  6. NIEM Specifications & processes What is the NDR and MPD Specification? What is the IEPD Development Life Cycle?

  7. Normative NIEM Specifications Naming & Design Rules (NDR), Version 1.3 Specifies principles and enforceable rules for NIEM data components and schemas. Schemas and components that obey the rules are considered to be NIEM-conformant. URI: http://reference.niem.gov/niem/specification/naming-and-design-rules/1.3/niem-ndr-1.3.pdf Model Package Description (MPD) Specification, Version 1.1 Defines terminology, identifies required and optional artifacts and metadata, specifies normative rules, schemes, syntax, and provides non-normative guidance to support the creation of NIEM MPDs. MPDs include IEPDs, Business Information Exchange Components (BIEC), Enterprise Information Exchange Models (EIEM), Domain Updates, and Core Updates. URI: http://reference.niem.gov/niem/specification/naming-and-design-rules/1.3/niem-ndr-1.3.pdf

  8. MPD Classes Model Release:Contains a full set of harmonized reference schemas defining all content in a version of NIEM. Domain Update: Contains reference schemas that represent changes to NIEM domains. NIEM domains use these as the basis for incremental improvements, extensions, and proposed changes to future NIEM releases. Core Update: Contains reference schemas representing changes that apply to a specific NIEM Core version. A core update is not published to replace a NIEM Core; it adds new schemas, new data components, and new code values to a core without waiting for the next major release. Information Exchange Package Documentation (IEPD): Defines a reusable XML data exchange. A NIEM IEPD contains a set of valid XML schemas that may include portions of NIEM Core schemas, portions of domain schemas, enterprise-specific or IEPD-specific extension schemas, and at least one exchange schema that defines a document element. Enterprise Information Exchange Model (EIEM):A collection of business components organized into a subset and one or more extension schemas. Constraint schemas and non-NIEM-conforming external standards schemas with type adapters are optional in an EIEM. ​​​​​​​​​​​​

  9. The IEPD Lifecycle Scenario Planning Plan the project, establish the process, and identify information exchange business requirements Analyze Requirements Selected information exchange is further elaborated to understand and document the business context and data requirements Map & Model Associate local objects with types and elements in NIEM. This process is called mapping an exchange content model to NIEM Build & Validate Create a set of exchange-specific NIEM conformant XML schemas that implement the data model created for the exchange Assemble & Document Prepare and package all related files for this IEPD into a single self‐contained, self-documented, portable archive file Publish & Implement Publish IEPD for search, discovery, and reuse 10

  10. The IEPD Artifacts Scenario Planning • Business Processes • Use Cases • Sequence Diagrams IEPDs contain both required and recommended artifacts Required : Bold Recommended : Italic Note: Best practices for most organizations include many of the optional artifacts listed here Analyze Requirements • Business Rules • Business Requirements Map & Model • Exchange Content Model • Mapping Document Build & Validate • Subset Schema • Exchange Schema • XML Wantlist • Constraint Schema • Extension Schema • Main Document • Catalog • Sample XML Instances • XML Stylesheets Assemble & Document No required artifacts. Publish the IEPD to a repository and implement the exchange Publish & Implement 11

  11. NIEM Governance How is NIEM governed? How does the federated domain governance function? What are the different NIEM committees?

  12. NIEM Governing Structure NIEM’s governing structure is comprised of Federal, State, Local, Tribal and private organizations NIEM is jointly managed at an executive level by the Department of Homeland Security (DHS), Department of Justice (DOJ), and Department of Health and Human Services (HHS) ESC Executive Steering Council NIEM PMO Executive Director Deputy Director NC&OC NTAC NBAC NIEM Communications & Outreach Committee NIEM Technical Architecture Committee NIEM Business Architecture Committee 13

  13. Who steers NIEM currently? Voting Members • Dept of Justice • Dept of Homeland Security • Dept of Health and Human Services Ex-Officio Members • Global Justice Information Sharing Initiative • Office of Management and Budget • Program Manager, Information Sharing Environment • NASCIO Partners • Terrorist Screening Center • Dept of Defense / Dept of Navy • Dept of State, Consular Affairs (invited) 14

  14. Who governs NIEM Domains? 15

  15. Future Outlook What is NIEM 3.0? What is the scope and timeline for release? Where can I find more information? How does NIEM-UML relate?

  16. UML Profile for NIEM (v2.1 Alignment) Objective of the NIEM-UML Profile To allow modelers and developers to apply NIEM-UML with minimal effort in order to create new models or change existing models and ultimately to produce NIEM MPD artifacts. • NIEM-UML Implementations • MagicDraw NIEM-UML Plug-in • Open Source Implementation (Under Development) 17

  17. NIEM-UML What is NIEM-UML? Learning Requirements? ` ` • NIEM Logical Concepts Not the XSD and NIEM Naming & Design Rules Details • Platform Independent Model (PIM) Profile • Common Profile • Model Package Description Profile • UML Tooling/Development Environment • Subset of the Unified Modeling Language (UML) • Set of UML constructs & Stereotypes • Extends UML to represent NIEM concepts • NIEM concepts are augmented with NIEM-Platform mapping information • NIEM Naming & Design Rules enforced by leveraging the Object Constraint Language • A valid NIEM-UML model will produce a valid MPD 18

  18. NIEM-UML Goals Clarity: Ensure that a UML representation of a NIEM model produced by one developer can be interpreted as expected by another. Completeness: Ensure that a developer can produce a UML representation of any NIEM concept, including semantics, XML Schema structure, and metadata. Practicality: With minimal effort, a developer can employ the profile in current UML development tools to develop and use a NIEM model. • Represent the semantics of NIEM while being agnostic of its structural representation • To leverage standards and standards based tools • To reduce complexity and lower the barrier for entry • To facilitate reuse of NIEM models and as a result schemas • To embrace accepted UML modeling styles and constructs • To enable use of NIEM-PIM models for use with other standards, technologies and layers • To support deterministic mapping to and from the NIEM technology layers based on NIEM rules 19

  19. NIEM 3.0 High-Level BASELINE Scope * 1 Technical Architecture Enhancements and bug fixes 2 Harmonized Content, & Domain Content Change requests • Code List Decoupling & Updates • Optional Code List Complexity Solution • New Augmentation Solution • Integrate Latest Version of IC-ISM • Unify Reference & Content-Bearing Elements • Ability to Subset structures.xsd and appinfo.xsd • Conformance Target Declaration Attributes in appinfo.xsd • Local Terminology and Acronym Capability in appinfo.xsd • Resolved Architectural NIEM Configuration Control Tool (NCCT) Issues • Newly Identified Architectural NCCT Issues • Domain Content Change Requests • NCCT Content Harmonization Solutions • Newly Identified NCCT Content Issues NIEM.gov Tools UPDATES 3 • SSGT (Updates & NIEM-UML Alignment) • ConTesA • Code List Generator * Scope is subject to change 20

  20. NIEM 3.0 TIMELINE (13 months) Requirements & Preparation Phase Development & Execution Phase PRE-ALPHA (19 weeks) ALPHA 1(5 weeks) ALPHA 2(10 weeks) BETA(8.5 weeks) RC 1(9 weeks) 3.0(4 weeks) Domain Update Requirements& Harmonization (3 months) kickoffmeeting ReleaseAlpha 1 ReleaseAlpha 2 ReleaseBeta 90-day Deadline ReleaseRC 1 Release NIEM 3.0 Today RELEASEAUDIENCE 21

  21. Website/Public Communications NIEM 3.0 URL: https://www.niem.gov/technical/coming-soon/Pages/version-3.aspx 22

  22. Q&A

More Related