NIEM, CAM and the 7 “D’s”

<Insert Picture Here>

NIEM, CAM and the 7 “D’s”

David Webber - Public Sector NIEM Team, November 2011

NIEMTest Model Data

Deploy Requirements

Build Exchange

GenerateDictionary

XML Exchange Development

NationalInformationExchangeModel

Copyright ©2011, Oracle. All rights reserved. Oracle Draft Materials – Limited Circulation

The following is intended to outline Oracle general product direction. It is intended for information purposes only, and may not be incorporated into any contract. It is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decisions.

The development, release, and timing of any features or functionality described for Oracle’s products remains at the sole discretion of Oracle.

Disclaimer Notice

Slide 2


Why CAM and NIEM?

“Can you give us a brief overview of how you expect IT professionals and line of business managers to use CAM*?”

– Van Ristau, CTO DLT Inc.

*CAM editor toolkit – http://www.cameditor.org and OASIS Content Assembly Mechanism standard – http://docs.oasis-open.org/cam

http://www.cameditor.org/

http://docs.oasis-open.org/cam


Response

• Line of business managers can use CAM to drive better alignment to NIEM and faster more consistent delivery of NIEM information exchanges enabling projects to be performed more timely and predictably

• CAM provides tools that allow business analysts to work collaboratively with software developers to build exchanges

• Teams use CAM to perform the 7 “D’s” tasks when implementing NIEM exchanges

• CAM automates the delivery of key XML artifacts for NIEM exchange services

• CAM can be deployed using the CAMV engine


OASIS CAM standard and approach• CAM is about content assembly for information

exchanges using a visual XML paradigm with the components managed in dictionary collections

• NIEM provides the basis for domain dictionaries and the naming and design rules for creation of components

• NIEM aligns well with CAM because they share a common heritage in core component standards work

• CAM is designed for standards based business exchange development and simplifying that process

• CAM works for both top down new exchanges or bottom up customizing and tailoring of existing exchanges


Introducing the 7 “D”s

• Design• Develop• Deploy• Document• Dictionaries• Discovery• Delimit

Tasks in implementing NIEM


The 7 “D”s and NIEM

• Design• Develop• Deploy• Document• Dictionaries• Discovery• Delimit

Repeatable, Reusable Process(Exchange Specification Lifecycle)

NIEM IEPD Process

*IEPD - Information Exchange Package Documentation


NIEM IEPD Reports

DictionariesDiscovery

Exchange Delivery Lifecycle

Supervise

Delimit

Design

Develop

ValidatedTemplates /

Schema

XSD Schema

XML Samples

XMI / UML Models

ProductionResults

RequirementsUpdates

Documentation

Drag and Drop Visual

Designer

DocumentDeploy

ExchangeTemplates


CAM: Top Down Exchange AssemblyCanonical XML Components Dictionary1

Component Associations and Couplings2

Exchange Templates and Rules3

W3C Schema and Model Representations4

Delivery Control, Messaging, Security5

Presentation

Collaboration Services

Artefact relationships

Implementation Artifacts and Examples6

Navigation and Query

Tools

Domains Reuse Library

Components

Automatic Rendering Tools

Deployment Environments and Middleware

XML

User Inserts

Relationship Lookups

Template Catalog

Testing Workbench, Rules Engine, Data Samples, Integration ETL

SchemaXML

Models Components

Canonical Dictionary Collections


Design• Create information exchange conceptual work flows

including the information exchanges needed to match business process needs

• Determine conceptual information exchanges• Understand security and information privacy needs• Determine the information components for each

exchange• Organize the components in each exchange structure

to an overall hierarchy to align with the business process needs

• CAM provides visual editor for prototyping of exchange structures along with Mind map modelling to allow conceptual reviews


Discovery• CAM provides a variety of tools to assist in discovery

of existing components from dictionary collections• Automatic comparison tool between exchange and

dictionaries – creates mapping spreadsheet• Search tools within dictionary interface• Visual dictionary structure viewer• Mind map models of dictionary components to allow further

visual inspection and analysis


Develop• Using the CAM exchange structure outlines complete

the actual exchange details• Select actual components either from existing NIEM

dictionaries or from the enterprise dictionaries• Create new components or extend existing components to

meet additional design needs• Add validation rules for structure and content as needed by

the business process• Build working exchanges using actual simulated data

with realistic XML instances• Test each exchange to verify validation and operation• Integrate the information exchange handling with the

business processes and applications


Visual Designer with Dictionary Collection

Drag n’ Drop Tool

Industry dictionaryDomain dictionary

Component Definitions

4

Component Definitions

Search Tools

2

ExchangeDesigner

1

InsertDictionary

ParentComponents

3

Completed Exchange Template

5

Collection


Example - Suspicious Activity Report V2.0

dictionaries

XMLXML

XML

• SAR v1.5 components• NIEM core dictionary• LEXS 3.1.4 dictionary

LEXS components referenced

New structure componentsbased on NIEM + SAR + new

SAR conceptual components

Definitions stored as syntax neutral canonical XML

NIEM core components

Dictionary Collection

Namespaces of dictionary components

DRAFT


Document

• CAM generates NIEM IEPD documentation artifacts including• Business component usage report with rules and definitions• Code list details and content checks• UML physical models• Mind map model of exchange structure and components• Comparison mapping spreadsheets to NIEM dictionaries and

components• NIEM “want list” XML for use with NIEM subset generator tool• Example XML instances


Delimit

• This step includes building in deployment specific details and rules and usage policy determinations• Add additional XPath rules for local integration needs• Constrain code lists to local use • Limit and restrict content based on policy and role of exchange

partners• Contextually exclude structure components based on rules

• Create other integration artifacts for middleware such as policy control, partner certificates and security configuration

• Can configure these aspects through the CAM template and using middleware tools


Deploy

• Once structure information exchange is complete

need to test and verify it by generating realistic XML

examples• Validate those against the exchange template

• Share working examples with exchange partners

• Share documentation (IEPD)

• Deploy with CAMV and distribute test suite module• CAMV is Spring aware and supports Java API

• Tutorial and examples availableCAM Editor resources site: http://www.cameditor.org

http://www.cameditor.org/


CAM Validation Framework

CAMVXML instance

Template (compiled)

Database Lookup

(optional)

Results XML

Java Handler Errors and Warnings

Structure

Rules

Code Lists

SQL Query


CAMV / ANT Test Suites Environment

XML TestInstances

ANT

CAMV XML ValidationResults

XSLT

Reports

CAM template

CAMV Control Script XML

2

1

Examples and instructions:http://www.cameditor.org/#CAMV_Testing


Dictionaries

• Sets of NIEM domain dictionaries available• Dictionaries can be grouped into collections• Tools allow comparisons with existing dictionaries for

reuse analysis and mapping spreadsheet generation• New dictionaries can be created by

• Harvesting existing schema collections• Export and generation from Enterprise Data Models (ERwin)• Automatic Renaming tool can be used to generate NIEM

consistent dictionary components for a domain• Naming and Design evaluation tool provides alignment

to NIEM and interoperability reporting and spell checks• Dictionaries can be viewed as spreadsheets or models

CAM Toolkit provides suite of tools for dictionary handling


Developing domain dictionaries (EIEM)

• Allows domains to manage their components libraries• Provides consistency for project development teams

• Sets of NIEM consistent XML exchange components• Aligned to enterprise data stores• Optimized for reuse and interoperability

• Save time and effort across the enterprise• Perennial question for developers – when should I use NIEM

components, and when our own local ones?• Are there components already available for that purpose?

• Provide formal mechanisms and procedures to share components and collaborate through project lifecycle

• Provide external parties consistent data views

*EIEM – Enterprise Information Exchange ModelCAM Toolkit for EIEM generation


CAM Toolkit capabilities review


SUMMARY AND REVIEWReviewing NIEM technologies


Summary of NIEM and CAM Technologies

Rapid NIEM solution development – IEPDs• NIEM and CAM editor toolkit

• Ability to use rules, code lists and SQL lookups

Dictionaries and Exchange development• Simplifying and accelerating effective exchanges

• NIEM – canonical component management

• Tools for building EIEM dictionaries

• Drag and Drop designer using dictionary collections

Deployment• CAMV validation XML framework and test suite toolkit


Q & A

Download the CAM editor toolkit from:

http://www.cameditor.org

Resource Center linkhttp://www.oracle.com/goto/niem

Documents

NIEM, CAM and the 7 “D’s”