NIEM-UML

Report
AGENDA
1.
The NIEM Framework
What common services, governance models, processes and tools are
provided by NIEM?
2.
NIEM Specifications & Processes
What is the NDR and MPD Specification? What is the IEPD
Development Life Cycle?
3.
NIEM Governance
How is NIEM governed? How does the federated domain governance
function? What are the different NIEM committees?
4.
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?
2
THE NIEM
FRAMEWORK
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
Formal Governance
Processes
Data Model
Tools for Development
and Discovery
Online Repositories
XML Design Rules
Established
Training Program
Mission-Oriented Domains
Development Methodology
Implementation Support
Self-Managing
Domain Stewards
Predefined
Deliverables (IEPD)
Help Desk &
Knowledge Center
4
STANDARDIZING DATA MOVING ACROSS
SYSTEMS
COMMONLY
FORMATTED
DATA
I N T E R FA C E
LEGACY
DATABASES
I N T E R FA C E
Scope-of-NIEM
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
THE NIEM LIFECYCLES
Common Language
Repeatable, Reusable Process
(Data Model Lifecycle)
(Exchange Specification Lifecycle)
Built and governed by the business users at
Federal, State, Local, Tribal and Private Sectors
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-ndr1.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-ndr1.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, selfdocumented, portable archive file
Publish &
Implement
Publish IEPD for search, discovery, and reuse
10
THE IEPD ARTIFACTS
IEPDs contain
both required and
recommended
artifacts
Scenario
Planning
Analyze
Requirements
Required : Bold
Recommended : Italic
Map & Model
Note: Best
practices for most
organizations
include many of
the optional
artifacts listed
here
Build &
Validate
Assemble &
Document
• Business
Processes
• Use Cases
• Sequence
Diagrams
• Business Rules
• Business
Requirements
• Exchange Content
Model
• Mapping
Document
• Subset Schema
• Exchange
Schema
• XML Wantlist
• Constraint Schema
• Extension Schema
• Main Document
• Catalog
• Sample XML
Instances
• XML Stylesheets
No required artifacts. Publish the IEPD
to a repository and implement the
exchange
Publish &
Implement
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
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
WHO GOVERNS NIEM DOMAINS?
Domain
Executive Steward
Justice
Global Justice (State & Local)
Screening
DHS/Screening Coordination Office
Immigration
DHS/Immigration & Customs Enforcement (ICE), US Citizenship and
Immigration Services (USCIS)
Chem/Bio/Rad/Nuc
DHS/Domestic Nuclear Detection Office (DNDO)
Maritime
DOD/Maritime Domain Awareness (MDA)
Cyber
DHS/National Protection and Programs Directorate (NPPD)/Cyber Security &
Communications (CS&C)
Children, Youth & Family Services
HHS/Administration for Children and Families (ACF) & DOJ (State & Local)
Emergency Management
DHS/FEMA, DHS/Science & Technology (S&T)
Infrastructure Protection
DHS/NPPD
International Trade
DHS/Customs and Border Protection (CBP)
Biometrics
DHS/NPPD, National Institute of Standards & Technology (NIST)
Health
HHS/Office of the National Coordinator (ONC) & HHS/Office of the Chief
Information Officer (OCIO)
Human Services
HHS/ACF & HHS/ONC
Government Resource Management
General Services Administration (GSA)
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
NIEM-UML
WHAT IS NIEM-UML?
LEARNING REQUIREMENTS?
• Subset of the Unified Modeling
Language (UML)
• NIEM Logical Concepts Not
the XSD and NIEM Naming &
Design Rules Details
• Set of UML constructs &
Stereotypes
– Platform Independent Model (PIM)
Profile
– Extends UML to represent NIEM
concepts
– Common Profile
`
` are augmented
– NIEM concepts
with NIEM-Platform mapping
information
– Model Package Description Profile
• UML Tooling/Development
Environment
– NIEM Naming & Design Rules
enforced by leveraging the Object
Constraint Language
• A valid NIEM-UML model will
produce a valid MPD
18
NIEM-UML GOALS
•
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
•
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.
To support deterministic mapping to and
from the NIEM technology layers based on
NIEM rules
19
NIEM 3.0 HIGH-LEVEL BASELINE SCOPE *
1
•
•
•
•
•
•
•
TECHNICAL ARCHITECTURE
ENHANCEMENTS AND BUG FIXES
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
•
2
•
•
•
3
•
•
•
HARMONIZED CONTENT, & DOMAIN
CONTENT CHANGE REQUESTS
Domain Content Change Requests
NCCT Content Harmonization
Solutions
Newly Identified NCCT Content
Issues
NIEM.GOV TOOLS UPDATES
SSGT (Updates & NIEM-UML Alignment)
ConTesA
Code List Generator
* Scope is subject to change
20
NIEM 3.0 TIMELINE (13 MONTHS)
REQUIREMENTS & PREPARATION PHASE
Sep
Oct
Nov
Dec
PRE-ALPHA (19 weeks)
Domain Update Requirements
& Harmonization (3 months)
Jan
DEVELOPMENT & EXECUTION PHASE
Feb
MEETING
Apr
May
Jun
Aug
Sep
ALPHA 2
BETA
RC 1
3.0
(5 weeks)
(10 weeks)
(8.5 weeks)
(9 weeks)
(4 weeks)
RELEASE
ALPHA 2
RELEASE
BETA
90-DAY
DEADLINE
RELEASE
RC 1
RELEASE
NIEM 3.0
Today
RELEASE AUDIENCE
PMO
Jul
ALPHA 1
RELEASE
ALPHA 1
KICKOFF
Mar
NBAC
NTAC
GTRI
Alpha 1
Alpha 2
Beta
RC 1
21
Community
WEBSITE/PUBLIC COMMUNICATIONS
NIEM 3.0 URL:
https://www.niem.gov/technical/comingsoon/Pages/version-3.aspx
22
Q&A
23

similar documents