Electronic Simple European Networked Services SGCC4 Conformance and Test kick off - WP6 Berlin, Germany Apr 10th 2013 Tuncay Namlı, PhD WP6 SGCC4 Manager SRDC, Turkey

Agenda 13:30-14:00 Project Setup 14:00-14:30 Administrative Issues Identify major contacts for SGCC4 from each contributing MS (Turkey, Sweden, Germany, Norway, Portugal) SGCC4 Overview, Objectives, Tasks, Deliverables General task assignments 14:00-14:30 Administrative Issues SGCC4 Internal process (Planning, meeting policy, collaboration with other SGCCs and WP5) Finalize mailing list Tools for administrative issues 14:30 -17:00 Start of work and short term plans Baseline for eSENS Conformance Testing Process and basic principles Comments and contributions from group members (expertise, experiences) Short term plans (4 months) How to monitor WP5 and WP6 results? (+ initial assignments) Open Issues and other discussions

SGCC4 Objective Provide an extensible, highly available and preferably Web accessible testing infrastructure in order to Support the sustainability of the e-SENS network by ensuring the conformance and interoperability of the participant systems to the developed e-SENS interoperability specifications, Facilitate and accelerate the adoption of the e-SENS system by the targeted organizations by providing an environment for an “extensible interoperability and conformance testing infrastructure” where they are able to test their applications and get detailed feedback, Ensure that the existing test applications and facilities used by specific domains in e-SENS will be utilized and ensure that ongoing standard development efforts on conformance and interoperability testing like CEN Global e-Business Interoperability Test Bed project and ISO DTR 28380-1, IHE Global Standards Adoption Part 1: Process will be followed to provide generic and reusable testing modules

Conformance and Interoperability Testing Conformance Testing "Process of verifying that an implementation of a specification fulfills the requirements of this specification, or of a subset of these in case of a particular conformance profile or level" Interoperability Testing "A process for verifying that several SUTs can interoperate at one or more layers of the interoperability stack while conforming to one or more specifications."

Why it is important? Only way to gurantee and certify correct information exchange among eBusiness/eGovernment implementations Quality of the specifications is directly related with whether conformance testing can easily be performed Missing conformance testing capabilities increase the implementation efforts and the risks for being non-interoperable

What is tested?

What will be tested in eSENS? WP6 will provide specifications for common building blocks eDelivery & eInteraction (ebMS3, ETSI TSL, ETSI REM, PEPPOL SML, ...) Semantics and Processes and Documents Identity, Security and Trust (SAML, WS-*, ...) Does WP5 produce any type of specification specific to domains?

SGCC4 Tasks Task T 6.4.1 (M1 to M36) Management Task T 6.4.2 (M1 to M4) Business Modeling Task T 6.4.3 (M5 to M10) Requirements Task T 6.4.4 (M11 to M16) Analysis and Design Task T 6.4.5 (M17 to M28) Implementation Task T 6.4.6 (M29 to M32) Test Task T 6.4.7 (M33 to M36) Deployment Task T 6.4.8 (M20 to M30) Evaluation

T6.4.2 Business Modeling eSENS Conformance Testing Process and business model for eSENS Conformance Testing Infrastructure Basic principles for conformance testing High level description of entities and workflow Definition of eSENS Conformance Testing Infrastructure Possible approaches for maintanance and governance (Collaborate with WP3 Sustainability) 9

T6.4.3 Requirements Collect conformance and interoperability testing requirements of the e-SENS Building Blocks Analyse the specifications and underlying standards Determine what should be tested Determine conformance levels and organize testing requirements accordingly Collect conformance and interoperability testing requirements of WP5 results (business processes?) Identify existing testing artifacts, tools, testbeds from related iniatives (LSPs, EC projects, SDOs, other)

T6.4.4 Analysis and Design Analyse the testing requirements and design test scenarios Describe the pre-configuration steps Describe the participating entities and SUTs Describe the workflow and test steps Describe the passing criteria Design testing tools if required

T6.4.5 Implementation Develop the testing scenarios which are designed in T6.4.4 Develop test scripts (to run on testbed) Develop test artifacts (ex: XML schemas, XPATH expressions, Schematrons, value sets, etc) or reuse existing ones Develop test tools when necessary or reuse existing ones (ex: an encryption utility, a simulator for a system, etc)

T6.4.6 Test Test your test scripts, artifacts and tools Check with a correct execution of scenario whether it decide as PASS Check with intentional incorrect executions whether it finds the errors

T6.4.7 & T6.4.8 Deployment Evaluation Deploy the test scenario into the testbed and make sure that it is available to end users Evaluation In general, evaluate the eSENS Conformance Testing Process and eSENS Conformance Testing Infrastructure for sustainability. (WP3 collaboration)

Deliverables WP6 Deliverable Due date Mapping to SGCC4 D6.1 Executable Baseline Architecture M6 - Business Model for eSENS Conformance Testing (T6.4.2) D6.2 Enterprise Interoperability Architecture n1 M15 eSENS Conformance Testing Requirements (T6.4.3) eSENS Conformance Testing Scenarios v1 (T6.4.4) D6.3 Enterprise Interoperability Architecture n2 M24 eSENS Conformance Testing Requirements eSENS Conformance Testing Scenarios v2 (T6.4.4) - eSENS Conformance Testing Infrastructure v1 (T6.4.5, T6.4.6, T6.4.7) D6.4 Architecture Evaluation M30 Evaluation of eSENS Conformance Testing Process Infrastructure (T6.4.8) D6.5 Transfer of Operation and Ownership M36 D6.6 Enterprise Interoperability Architecture n3 - eSENS Conformance Testing Infrastructure v2 (T6.4.5, T6.4.6, T6.4.7)

Milestones Milestones Month M6.1 Business Modelling Consolidated M4 Inception phase ended M6 M6.3 Elaboration phase ended M12 M6.4 Construction phase ended M27 M6.5 e-SENS Architecture Evaluation M32 M6.6 Transition phase ended M34 M6.7 Transition consolidated M36 M6.8 e-SENS Transfer of Operation and Ownership

SGCC4 Resources Participant Country PM 1 Turkey 55 2 Sweden 15 3 Norway 4 Germany 10 5 Portugal TOTAL 105

General Task Assignments Participant Country Tasks 1 Turkey All 2 Sweden T6.4.2, T6.4.4, T6.4.5 3 Norway T6.4.2, T6.4.3 (WP5.1 Public Procurement), T6.4.4 4 Germany T6.4.2, T6.4.3 (WP 6.2 Semantics, WP5.1 Public Procurement), T6.4.4, T6.4.6 5 Portugal T6.4.2, ?

Agenda 13:30-14:00 Project Setup 14:00-14:30 Administrative Issues Identify major contacts for SGCC4 from each contributing MS (Turkey, Sweden, Germany, Norway, Portugal) SGCC4 Overview, Objectives, Tasks, Deliverables General task assignments 14:00-14:30 Administrative Issues SGCC4 Internal process (Planning, meeting policy, collaboration with other SGCCs and WP5) Finalize mailing list Tools for administrative issues 14:30 -17:00 Start of work and short term plans Baseline for eSENS Conformance Testing Process and basic principles Comments and contributions from group members (expertise, experiences) Short term plans (4 months) How to monitor WP5 and WP6 results? (+ initial assignments) Open Issues and other discussions

SGCC4 Internal Process Work Planning Meetings 6 Monthly Action Plans Be ready for continous updates on plans as SGCC4 is heavily depending on results from other SGCCs and WP5. May work on partial results (ex: specifications) from WP6 and WP5 to be inline with general WP6 plan Meetings Face-to-face meetings Try to align with WP6 and WP5 meetings but they are also considering individual meetings (each SGCC and WP5 domain) Online meetings When necessary

SGCC4 Internal Process Collaboration with other SGCCs and WP5 I will attend WP6 Architectural Board Meetings regularly If we have group members that has expertise and contacts in those groups, they can also continously monitor the results

Agenda 13:30-14:00 Project Setup 14:00-14:30 Administrative Issues Identify major contacts for SGCC4 from each contributing MS (Turkey, Sweden, Germany, Norway, Portugal) SGCC4 Overview, Objectives, Tasks, Deliverables General task assignments 14:00-14:30 Administrative Issues SGCC4 Internal process (Planning, meeting policy, collaboration with other SGCCs and WP5) Finalize mailing list Tools for administrative issues 14:30 -17:00 Start of work and short term plans Baseline for eSENS Conformance Testing Process and basic principles Comments and contributions from group members (expertise, experiences) Short term plans (4 months) How to monitor WP5 and WP6 results? (+ initial assignments) Open Issues and other discussions

eSENS Conformance Testing Process Basic Principles Automate the testing process as much as possible Web accessible and extendible testing infrastructure Reuse the existing testing artifacts, tools, tesdbeds available from LSPs, SDOs and other initiatives Align with the existing works and standards on conformance testing (CEN Global e-Business Interoperability Test Bed, ISO DTR 28380-1, IHE Global Standards Adoption Part 1: Process)

eSENS Conformance Testing Process Basic Principles Sustainability of the eSENS Conformance Testing Infrastructure after the project, is a key requirement Be careful when reusing (e.g. licenses) Should serve to multi domain (eHealth, Public Procurement, eJustice) Support also interoperability testing and such testing events Consider also integrated testing scenarios (not only partial tests specific to single communication ) including multiple actors and building blocks

eSENS Conformance Testing Process Definition of eSENS Conformance Testing Infrastructure The approach: A single testbed or network of testbeds Related standards GITB and GITB Alternative Architectures ISO DTR 28380-1, IHE Global Standards Adoption Part 1: Process Entities, workflow, use cases for eSENS Conformance Testing Infrastructure Sustainability Maintenance, governance 25

What is a testbed? A test execution environment that provides a scripting language to define test scenarios an execution model (operational model) based on the scripting language interfaces or APIs to extend the testbed with new utilities or tools A user interface to report the results and enable the users to manage and monitor the execution

Global Interoperability Testbed (GITB) Project Hosted by the European Committee for Standardization (CEN) and supported by European, North American and Asian partners, such as NIST, KorBIT, OASIS, OAGI, ETSI and industry associations, such as AIAG (Automotive Industry Action Group). http://www.ebusiness-testbed.eu/ GITB aims at developing the required global Testing Framework, architecture and methodologies for stateof-the-art eBusiness Specifications and profiles covering all layers of the interoperability stack(business processes, business documents, transport and communication); supporting the realization of GITB as a network of multiple Test Beds, thereby leveraging existing and future testing capabilities from different stakeholders (for example standards development organizations and industry consortia, Test Bed Providers, and accreditation / certification authorities); establishing under EU support and guidance, a setup of a comprehensive and global eBusiness interoperability Test Bed infrastructure in a global collaboration of European, North American and Asian partners.

GITB 3-Phase project Phase I – Feasibility Study – CEN CWA 16093:2010 (ftp://ftp.cen.eu/CEN/Sectors/TCandWorkshops/Workshops/CWA16093TestBed.pdf ) Phase II – Development – CEN CWA 16408:2012 (ftp://ftp.cen.eu/CEN/Sectors/List/ICT/CWAs/CWA_16408.pdf ) Recommend an architecture for GITB (i.e. architectural specs) Phase III – Realization Not started yet – will finalize the specification for GITB Public Procurement and eHealth were major use cases analyzed in the first two phases (i.e. UBL, CEN/BII specs, HL7 as the underlying standards) SRDC is one of the major contributor of the project in both phases with the expertise gained from its conformance testing framework; TestBATN 28

GITB Alternative Architectures Single Test Bed Architecture with a single Test Description Language (TDL) and Execution Model Network of Multiple Test Beds and Test Services

IHE Global Standards Adoption Process

IHE Global Standards Adoption Process

TestBATN Conformance and interopability testing framework that we can provide for eSENS to automate the testing process and provide a web based conformance testing service We will provide it as open source and is full conformant with GITB specs (Phase I, II) When phase III is finalized, we will also align it

TestBATN It has already demonstrated the ability to perform conformance and interoperability tests for IHE Profiles, HL7, DICOM PEPPOL Specs (Start and Lime profiles), UBL, CEN/BII GITB Webinar: Testing a Sender Access Point In PEPPOL Network CEN BII04 Profile epSOS Specs Used by Turkish Ministry of Health to test the conformity of Hospital Information Systems (HIS) to the National Health Information System (NHIS) of Turkey (HL7 v3 CDA based) Used by some HIS Vendors in Turkey to prepare for IHE Connect-a-thons (IHE SWF) 33

Gazelle Gazelle provides a set of tools that allow testing the interoperability of medical systems as well as the compliance with standards of the messages exchanged by those systems. Developed by IHE Europe Used for IHE Connect-a-thons and its preparation phases Used by epSOS for conformance and interop testing (WP3c Validation) SRDC leads the WP, so we have also knowledge and expertise on Gazelle

So what is developed/reused in eSENS? Test Tools: Pluggable software components to selected testbed(s) which input, output, and configuration parameters are defined and perform a specific action required in testing scenarios. Ex: ebMS3 message handler, schematron validator, XML schema validator, Encrypter, ... Test Artifacts: Any structured or unstructured item that will be used as input or configuration parameter for test tools. Ex: sample message parts or documents (SAML Assertion, UBL document, DICOM image), schematron file, an XSD file, XPATH expressions, Regular expressions Test Scripts: Scripts that will run on the testbeds to execute the designed test scenario. 35

Comments & Contributions Any comment from group members regarding general architecture or process for eSENS Conformance Testing You can also share your expertise and experiences regarding conformance testing in other projects or initiatives

Short Term Plan (4 Months) T6.4.2 Business Modeling (M1-M4) D6.1 Executable Baseline Architecture Business Model and General Architecture for eSENS Conformance Testing T6.4.3 Requirements (M5-M10)

Short Term Plan (4 Months) Identify existing test artifacts, tools, and test beds used in LSP projects (PEPPOL, STORK, epSOS) or any other initiative and contact with them Who will deal with the collaboration from our team? (The assignee will investigate the following questions) Who are the contacts from those projects regarding conformance testing? What is the conformance testing approach they follow? What are the basic functionalities of the testbed they use? Is there any licensing, restrictions, legal issues regarding the resuse of them within eSENS? List of the target specifications (Hopefully, those specifications or standards will also be base specifications for eSENS) What type of test artifacts they provide?

Short Term Plan (4 Months) Define the Business Model and General Architecture for eSENS Conformance Testing Contact with WP3 Sustainability to gather input regarding the reuse of existing results from other projects Prepare draft version and send to the group for comments (M2) Comments and contributions from group members (M3) Finalize the deliverable (M4)

How to monitor WP5 and WP6 results? WP6 "SGCC1 e-Delivery and e-Interaction" WP6 "SGCC2 Semantics, Processes, Documents" WP6 "SGCC3 Identity, Security and Trust“ WP5.1 eProcurement WP5.2 eHealth WP5.3 eJustice

Further discussions ???