Modeling with the ECCF SS ● UML Profile for ECCF ● UML Redefinition Semantics ● Compliance ● Consistency ● Conformance ● Validation ● Transformation ● Construction ● ECCF Specification Stack

UML Profile for ECCF Services-Aware Interoperability Framework ECCF/SAIF/Framework Docs ESST Templates Behavioral Framework RM-ODP SoaML Profile ECCF MM ECCF Profile ● Semantic Enforcement ● Validation ● Conformance/compliance/consistency across ECCF Specification Stack traceability Grammar vocabulary UML compliance ECCF SS UML Domain Models ● Consistent, Formal, Verifiable, Computable Semantic Interoperability compliance

UML Redefinition Semantics Classifier ● Redefineable Element Classifier ● Redefineable Element redefinitionContext redefinedElement Redefinition Semantics are specific to type of Redefineable Element ● Property : (narrows) cardinality, type, OCL; implicit by name ● Operation: (narrows) cardinality, type of each parameter; behavior, OCL ● Behavior (e.g., Activity, StateMachine, Interaction): ● May redefine any other type of behavior ● Replaces redefined feature behavior; extends redefined classifier behavior ● (narrows) pre-conditions, post-conditions, etc.

Generic ECCF Compliance CIM Classifier ● Redefineable Element PIM Classifier ● Redefineable Element RedefinitionContext > redefinedElement > PSM Classifier ● Redefineable Element RedefinitionContext > redefinedElement > ● + ECCF-specific OCL Constraints a target/derived artifact (or artifact component, e.g., conformance statement) is compliant with its associated source artifact IF all conformant implementations of the target are also conformant with the source.

ECCF Consistency (Implicit/Enforced) > ● > <<ECCF. Domain Analysis Model>> implements uses > role Engineering ViewpointComputation ViewpointInformation Viewpoint type si Role binding > Consistency is a characterization of the logical coherence of the artifacts that are collected in a particular instance of a specification stack.

ECCF Conformance (Examples) > contract policy > > pre-condition post- condition body condition method > > > Conformance is a quantitative assessment of how completely and accurately a given implementation fulfills the requirements stated in the specification All s may be expressed in OCL for computable semantic interoperability

Validation (Conformance, Compliance and Consistency) UML Models ECCF Profile apply Stereotypes Constraints UML Meta Model Instance of Semantics Constraints OCL Execution Environment ● Extensions, as required for ECCF Validation Framework ● Tool Integration ● Validation Preferences ● Problem Navigation execute

Transformation (OMG Model to Model Transform) QVT Any MOF model Vanilla Model (UML, HL7, or other) QVT ECCF SS QVT PSM Models (XSD, WSDL, etc.) ECCF SS QVT ODM - OWL/RDF (SOAM, ECCF MM/Registry, etc.) In the context of evolution, a target artifact is said to be compliant with the source artifact if it has been derived from the source using a known, agreed-upon transformation

ECCF SS Construction (LSLR Example) EA Applicatio n Models 6+ EA to UML UML Information Viewpoint ECCF Specification Stack Per Service >20 LSLR Common ECCF SS (plugins) Model To Model (QVT) ECCF SS Templates Capability/ App Model Map App Common CIM Information Viewpoint (plugins) QVT import

ECCF Specification Stack Vanilla UML Model Vanilla +ECCF UML Model QV T ECCF Specification Stack CIM PIM PSM BICE B B I I C C E E Standard ECCF Specification Stack Standard ECCF Specification Stack reuse Multiple Modeling Tools Consistent Documents (ESST) Model Driven Technology Artifacts(PS M) ECCF Service Registry validation Conformanc e testing Computable semantic interoperability traceability

Backup Slides

Semantic Infrastructure 2.0 Service Development Process UML Service Model: an ECCF Specification Stack Standard ECCF Specification Stacks ● BRIDG ● LS-DAM ● ISO Data Types ● etc. HL7 MIF Models Scope Service Specifications and other Docs PSM and other Target Architecture Artifacts Analysis Technology Binding Refinement import ECCF Registry

Coherency:Enterprise Viewpoint ● Communities, Contracts, Policies, Obligations ● Identify roles in communities ● Contracts between roles ● Policies associated with contracts ● Enumeration of obligations, permission, prohibitions per policy ● All of these concepts may be refined ● Based on UML redefinition semantics ● Provides complete traceability across ECCF SS

Scope

Scope Contract/Policy

CIM Community

CIM Contract/Policies

PIM Community

PIM Contracts

Coherency:Computation Viewpoint ● Roles, Services, Interfaces, Operations ● Community Roles initially identified via Use Cases ● System Roles realize abstract (Actor) Roles ● System Roles define Services (via Ports) ● Services specify provided/used Interfaces ● Interfaces define operations ● All of these concepts may be refined ● Based on UML redefinition semantics ● Provides complete traceability across ECCF SS

Initial Roles

Role Refinement

CIM System Roles

PIM System Roles

Functional Profiles

Functional Profile-->PIM Interfaces

Role Assembly

Coherency:Information Viewpoint ● Models, Classifiers, Properties, Associations ● Information models package Classifiers ● Classifiers contain properties, typed as Classifiers ● Associations relate Classes ● Classifiers/Associations have inheritance ● Associations/Properties have cardinality,etc. ● All of these concepts may be refined ● Based on UML redefinition semantics ● Provides complete traceability across ECCF SS

More Backup Slides

Service Specifications and other Document Artifacts Enterprise Architect Eclipse EMF EA XMI EMF XMI XSLT DITA ARTIFACTS XSLT Model To Text Target Documents Consistent DITA Artifacts Based on caCIS conventions And specifications Consistent Target Documents Across Model Platforms Other EMF Models (MIF, WSDL, XSD, etc.) DITA Toolkit + caCIS Tooling

UML/MIF Composite: HL7 Profile MIF Models (an EMF Model) MTM (QVT) HL7 Profile UML Models ● 100% Isomorphic with MIF UML Native Models impor t ___________ MIF Schemas (an EMF Model) MTM (QVT) apply ___________ ECCF Profile ___________ HL7 Profile ● Complex data types for tag values ● OCL for Schema, Schematron, HL7 DT Constraints, etc. ___________ apply

ECCF Specification Stack as Model Composition CIM UML MIF PIM PSM WSDLXSD Other PSM Technol ogy Binding Model to Model Binding Conformance Model to Model (Transformation Conformance) __________ ___ ____________

caCIS/ECCF Convergence Semantic Infrastructure caCIS HL7 (mif) EA xslt Well- formed UML M2M Project- Specific M2M ECCF Profile Application And Model fixup UML (HL7 Profile) M2M ECCF Specification Stack Service Specificatio ns And Reports Validati on And analysis framew ork ECCF Registry feedback