1. OMG’s Model Driven Architecture® (MDA®) Standards for Information Sharing Lightning Talks OMG’s Model Driven Architecture® (MDA®) Standards for Information Sharing Lightning Talks Or, how to share information without really trying (so hard)

2. Session Purpose Provide an overview of OMG Model Driven Architecture (MDA) standards – As a basis for information sharing – As a base line for future work and our roadmap – To motivate use of a model driven approach to information sharing These talks are short, 10 minutes each, to provide an overview of the available capabilities

3. Agenda Introduction to the session MDA across the full lifecycle of information sharing – Cory Casanave, Model Driven Solutions NIEM-UML for information exchange – Justin Stekervetz, NIEM- PMO Information Sharing Services with SoaML – John Butler, Everware- cbdi BPMN & UML for Business Processes - Lonnie VanZandt, Nomagic Business Rules with OCL - Tricia Balfe, Nomos Software Policies for privacy and security – Mike Abramson, Asmg-ltd Metadata & Model Management with the Meta Object Facility - Pete Rivett, Adaptive

4. MDA ACROSS THE FULL LIFECYCLE OF INFORMATION SHARING Cory Casanave, Model Driven Solutions – cory-c@modeldriven.com

5. Complex Systems Data About Systems Organizations Communities I.T. Systems Systems of Systems Data About Systems Understood Described Simulated Optimized Implemented Federated Models

6. Models for Model Driven Architecture Are based on standards Have well defined structure, semantics and notations Separate concerns like business needs and technology implementation Can be processed as data to produce derivative value: – Analytics – Simulations – Documentation – Acquisition requirements – Executable processes, services and information exchanges – Source code, schema, configurations – Tests

7. Business Concerns Goals Policy Customers Costs Agility Technology Specification JMS, JEE, Web Services,.NET WS*, BPEL, XML Schema, NIEM-XML Technology Specification JMS, JEE, Web Services,.NET WS*, BPEL, XML Schema, NIEM-XML Logical System Model Technology Services (t-SOA), Components, BPM, Interfaces, Messages, NIEM-UML & Data Logical System Model Technology Services (t-SOA), Components, BPM, Interfaces, Messages, NIEM-UML & Data Describing Systems in Models Business Model Enterprise Services (e-SOA) Roles, Collaborations & Interactions Process, Information & Rules Business Model Enterprise Services (e-SOA) Roles, Collaborations & Interactions Process, Information & Rules Refinement & Automation Line-Of-Sight Computation Independent Model Platform Independent Model Platform Specific Model MDA Terms

8. Value derived from architectures with MDA Component Acquisition Specification Web Services Test & Simulation OMB 300 FEA/FTF BRM SRM DRM* Value derived from models Adapters Components Schema Deployment NIEM-XML

9. Business Architecture Automated Model Driven Architecture Framework & Infrastructure (E.G. -J2EE-WS) Platform InfrastructureMapping (E.G. J2EE-WS) Mapping is tuned to the infrastructure Tools Produce & Integrate SystemsComponents SystemsArchitecture Model (PIM) Minimize and structure manual implementation C Technical Architecture

10. Business Architecture Simulated Model Driven Architecture Simulator SystemsArchitectureModel(PIM) Live Process Simulation Refine/Iterate

11. UML/MDA Information Sharing Framework ContentServicePolicyProcess Representation Standards Process Representation Content Representation Services Representation Policy Representation UML Framework NIEM-UML UML SoaML GRA TBD (IEPV?) Activity Diagrams UML-BPMN Requirements Definition Process Specification Content Specification Services Specification Policies Specification Requirements Represents XML / Web Services Framework NIEM-XML WS* GRA GFIPM XACML WS Security Encryption IEPV BPEL Generates

12. Information Sharing Architecture Implementing Information Sharing Content Process Services Security/Privacy Policies Back-end Stakeholders & Systems (Consume and/or supply information) Adapters Information Sharing Specifications Implement Adapt NIEM-XML / Other XML RDF / JASON / EDI WS*/REST/PubSub XACML, GFIPM Etc… Code XSLT OWL/Sparql Brokers Anything Enable the full life- cycle of information sharing Across diverse technologies, standards, communities and systems

13. Model Driven Architecture for Information Sharing 13 Models are easier for both business and technical stakeholders to understand MDA helps reduce the time and cost to develop and maintain information sharing solutions Complex technologies like XML & NIEM Naming, design and packaging rules are automatically applied and validated Processes, services and information can be part of a coherent system and system of systems architecture across the full life-cycle of solutions Multiple technologies can be supported using different MDA generation patterns, such as Java,.NET, JSON or the Semantic Web

14. 14 Using Semantic Technologies Unified Modeling Language NIEM-UML Business Process Modeling Notation Service Oriented Architecture Model Driven Architecture Industry Standards Open Source & Commercial Products Providing Enterprise Architecture Business Architecture Information Architecture Information Sharing Services Architecture Systems Architecture Executable Systems Automated Federation Open Source Tooling A division of Data Access Technologies, Inc. Cory-c@modeldriven.com

15. NIEM-UML for Information Exchange Justin Stekervetz NIEM-PMO

16. COLLABORATIVE INNOVATION

17. Automatic Generation w/ NIEM- UML INFORMATION EXCHANGE BASED ON NIEM-UML XML data “on the wire”

18. TO SUMMARIZE… NIEM-UML is a new NIEM specification that provides for modeling NIEM in UML and producing or reverse engineering information exchange technical specifications using Model Driven Architecture This reduces the time, cost and learning curve of information exchange using NIEM MDA also provides for other aspects of the information sharing solution, such as: business processes, SOA services and back-end system integration NIEM-UML can be extended to support other technologies, such as JSON and the semantic web NIEM-UML is in the final stages of the standards process, tools are available now and more are being built

19. WEBINARS - LEARN MORE!!! NIEM-UML High-Level Introduction NIEM-UML Specification Overview Creating a NIEM IEPD with NIEM-UML Modeling Properties and Associations in NIEM-UML NIEM-UML Subsetting and Extension https://www.niem.gov/training/Pages/webinars.aspx

20. SoaML: A UML Standard for Modeling the Services that Enable Information Sharing John Butler, Chief Architect Everware-CBDI Co-Chair, Government Info Sharing DTF

21. Quick History 2006: UPMS RFP release by the OMG 2007: Initial submissions returned 2008: SoaML revised submission 2008: SoaML recommended for adoption Current Version 1.0.1 released 2012

22. What is SoaML? Extension to UML for modeling services… …and the people, organizations, and systems that provide them Provides the hooks necessary to specify information being shared in a particular context or exchange

23. Key Features – Services Architecture A services architecture describes how participants work together for a purpose by providing and using services expressed as service contracts. It is modeled as a UML collaboration. A participant represents some party that provides and/or consumes services. Participants may represent people, organizations or systems. A service contract is the specification of the agreement between providers and consumers of a service as to what information, products, assets, value and obligations will flow between them. It specifies the service without regard for realization, capabilities or implementation.

24. Copyright © 2009 Data Access Technologies, Inc. Model Driven Solutions May 2009 Service Interaction Provides Context for Information Exchange The roles of the consumer and provider and their interfaces Information exchanges captured as part of the Contract Message Types detail the information being exchanged

25. Capabilities and Services Services provide access to capabilities or… Capabilities realize Services or… Participants expose Capabilities through Services

26. Lots of Other Features Multi-party Service Contracts Service Channels Agents Milestones Value Specifications

27. Standards Interoperability Business Motivation Metamodel (BMM): Motivation behind providing or using the service Business Process Definition Metamodel (BPDM): Mapping to allow business process to use services and services to be realized by business processes UML Profile for DoDAF and MoDAF (UPDM): Capability modeling and how that is exposed through services NIEM-UML: Specification of Message Types

28. Why Use SoaML? Standard language for modeling services “Plug-in” for any UML tool Interoperable with other useful standards – UML – BPMN/BPDM – BMM – UPDM Provides context for information exchanges

29. OMG’s Model Driven Architecture® Standards for Information Sharing Business Process Modeling Notation

30. Visualization Graphic courtesy of Cameo Enterprise Architecture v17.0.3 with the Cameo Business Modeler Plugin available from No Magic, Inc.

31. Foundation: Shared Concepts Business Motivation Concepts – What is the Mission, Vision, Goal of a Business—or any Endeavor Business Organization Concepts – Participants, Pools, and Choreography Process Concepts – Tasks, Events, Decisions, Interruptions, Compensations, Sequence and Message Flows Shared Language enables Architects from differing domains to understand each other’s concerns.

32. History: OMG BPMN 2004 May: Version 1.0 (from BPMI) 2008 January: Version 1.1 (OMG) 2009 January: Version 1.2 (OMG) 2011 January: Version 2.0 (OMG) – formal/2011-01-03 Crucial Enhancements in v2.0 are formalisms to support Semantic Consistency, Automated Execution, and Interchange

33. Standardization Benefits Portability – Of Intellectual Property and of Intellectuals Modularity – Integration of Tools from various Service Providers Execution Automation – No longer just Pictures, tools can execute Models Inferences – One day soon: Semantic Quality

34. OMG Activities OMG Certification Exam for BPMN – Being revised for BPMN 2 – Offers an objective standard for Practitioners BPMN Interchange Working Group – Collaboration of Vendors to foster BPMN Interchange BPMN UML Profile

35. Exchange Languages XMI – XML Metadata Interchange – Standardized by the OMG XPDL – XML Process Definition Language – Standardized by Workflow Management Coalition

36. BPMN to XPDL

37. BPMN Summary Provides a Common Notation For Business (or Endeavor) Concerns That Aids Humans in Collaboration And is Sufficiently Formal for Simulations By Credentialed Architects Can Interchange via Standard Format

38. Business Rules with OCL tricia.balfe@nomos-software.com nomos-software.com OCL rules vendor

39. Information Sharing Requires Data Model + Business Rules Developers are usually given + XML Schema Documentation listing the business rules

40. Example Schema and Documentation Example IEPD Document Example NIEM Schema

41. Can implement improved rules process using OCL OCL = rules standard from OMG

42. About OCL OCL = Object Constraint Language Most recent specification from the OMG – http://www.omg.org/spec/OCL/2.3.1/ http://www.omg.org/spec/OCL/2.3.1/ Adopted as an ISO standard in 2012: – ISO/IEC 19507 Originated at IBM Every person must be over 12 self.person->forAll(p | p.age > 12) Every person with a driving license must be over 16 self.person->forAll(p | p.hasDrivingLicense implies p.age > 16) Example OCL

43. OCL Implementations Eclipse OCL – Open source, used in IBM Rational Software Architect, Borland Together, Topcased, Acceleo, Eclipse EMF Dresden OCL – Open source, from Technical University of Dresden, used in MagicDraw NIST Implementation – For testing XMI Nomos Software – Java code generation from OCL

44. MDA for NIEM NIEM Conformant XML Schema + Documentation - IEPDs UML Model NIEM-UML supports a model-driven process Use OCL: follow a model-driven process for business rules automatically generate

45. MDA for NIEM Business Rules NIEM Conformant XML Schema + Documentation - IEPDs UML Model + OCL Business Rules Executable Rules + Can include rules in the generated documentation Nomos Software product generates java from OCL. MagicDraw and IBM RSA support OCL currently.

46. Example Model : NIEM Search Warrant OCL self.Judge.Signature.SignatureDate.befor e(self.SearchWrntIssueDate) The date of the judge's signature must be before the search warrant issue date. UML Model for a NIEM Search Warrant OCL Business Rule

47. Example: OCL Rules in MagicDraw OCL Rules in MagicDraw – NIEM IncidentArrest example

48. Advantages of OCL for Business Rules Can write, run and test rules in the model Automatically generate – Rules documentation – Test Services that check compliance with business rules – Executable rules for production systems

49. OCL and Access Control Policy Rules User Profile Model Executable Policy Rules in Java OR No OCL to XACML implementation available currently, but practical Information Sharing Model OCL Rules defining Content-Based Access Control Rules across User Profile and Information Models XACML Policy Rules XACML =XML-based access control Includes access control policy language Policy = set of rules

50. Summary Business rules are needed for information sharing Can use OMG OCL standard – get improved process for managing the business rules Find out more : tricia.balfe@nomos-software.comtricia.balfe@nomos-software.com nomossoftware http://www.linkedin.com/company/nomos-software/ http://www.linkedin.com/company/nomos-software/ nomos-software.com

51. OMG’s Model Driven Architecture® Standards for Information Sharing ISS Policy

52. Information Exchange Policy Vocabulary (IEPV) As illustrated: the IE Packaging Policy Vocabulary (IEPPV) is the first in a series of IEPV specifications that will be needed to address the growing number of IEF Service Specifications.

53. ISS Objectives Semantic Interoperability: the ability of information systems to exchange information in a manner; enabling automatic processing, classification and analysis of the content to infer the implicit meaning; and then provide relevant elements to decision makers in a timely, accurate and digestible manner. To achieve semantic interoperability, both sides of the exchange must infer common meaning and intent based on agreed domain, semantic or ontological models. – Information Sharing: refers to the combination of policies, governance, procedures, and technologies that allow different organizations to share relevant/important data with each other. – Information Safeguarding: refers the combination of policy, governance, procedures and technologies that assure that the information (content) is not released to those not authorized or credentialed to receive it. Policy-Driven: the ability to translate policy into machine enforceable instructions in a manner that is traceable and auditable. (resulting in Policy Automation) Policy Management: the ability to configured and tailor run-time policies to accommodate changes in operational context. Overcome current operational, architecture and design challenges: the ability to evelop or align specifications that enable tool vendors to deliver the tools required to deliver and sustain Flexible, Agile and Adaptive information Sharing and Safeguarding Solutions. Policy Automation: the ability of information systems, intelligent agents and appliances to enforce policy without the requirement of human interaction.

54. Shared Understanding Shared Knowledge Situational Awareness Data and Information Fusion Machine Analytics and Reasoning Semantic Interoperability Goals Asymmetric Sharing: The ability to share content with different communities, agencies or individuals conforming to legislative, regulatory, policy, contractual of service level requirements – while leveraging standard protocols, interfaces and infrastructure. Adaptive Sharing: The ability to selectively share information content based on operational or business context: roles, relationship, risks, threats, trust, … Safeguard: The ability to appropriately protect the content, storage and exchange if information and data elements. Automation: The ability deliver machine computable ISS decision and enforcements points. Auditable: The ability to trace the sharing of information implementations to Legislative, regulatory, policy, … mandates. “ilities”: The ability to deliver and deploy computable ISS decision and enforcements points that provide adaptability, flexibility, agility, supportability, … IEF FOCUS

55. Addressing Operational Challenges Data rich and Information poor: enable the selective sharing of information based on established policies and semantics and enhance the quality of information (timely, accurate, relevant, digestible, …) available to the decision makers. Expanding legislative, regulatory and policy required to responsibility share relevant information: enable the translation regulations and policies into machine enforceable rules. Balancing information sharing and information protection: enable selective release of information content based on sensitivity, level of trust or recipient and operational context. Adapting to increasing complexity of the information domain: enable timely and cost effective development, testing and certification of ISS capability. Balancing information and data overload: deliver integrated/fused information tailored to the policies and semantics of the decision maker. Adapting to highly dynamic and fluid operational environments: enable management (activate, deactivate, modify, append) policies and semantics at runtime. Perception the IM and SA system do not provide quality Information: provide direct traceability and auditability of decision makers requirements for accurate, relevant, timely, digestible, usable, complete, trustworthy, secure/protected – enabling analytics and reasoning.

56. Addressing Architecture and Design Challenges Specifications for the development of tools that will enable the translation of ISS Policies into machine enforceable rules, instructions and constraints. Specifications for the development of Policy Decision and Enforcement Points/Services (e.g., IEPPS) Practices that enable users with the ability and capacity to keep pace with: – New Legislation, Policy, and Operating Procedures – Evolving threats and risks – Asymmetric operations – New Techniques and Technologies – Real-world operational context and coalitions Practices that enables users to retain institutional knowledge and memory Practices that increase capacity while reducing IM/IS/IT life-cycle costs

57. Where is the challenge? Data in Use Data in Transit Data at Rest Addressed by Extract, Transform Load; or Application Code Rigid and Brittle Costly to Maintain and Adapt Not Responsive to Changes in Operations Typically Pier-to-Pier Task/Organization Specific Stove-piped Organizations have lost, the institutional knowledge and memory needed to manage and maintain Business Rules related to information usage and exchange Community Specifications Community / User Applications

58. How it is typically Handled Custom Application ETL Mediation Middleware Other User Application Custom or Tool Specific Code or Script Minimal alignment with other architectural elements. Data Interface

59. Policy/Rule Life-cycle (Policy-based Packaging) Source Requirement Legislation/International Agreement Government Policy Regulation Agency Policy Operating Procedures Service Level Agreements Architecture Driven Transformation Testing, Validation and Certification Policy Management Governance Change Recommendations Post Mission Analysis Architecture Policy Decision/Enforcement Point Policy Enforcement Point 1 1 2 2 Architecture Framework (AF) DODAF/UPDM/IEPPV/NIEM-UML AF Domain Model Executable Policy