V-Con TS - Test Cases “The Mini Cases” To be used by Contractors in Phase 2 of the V-Con PCP process to validate their prototype V-Con Solutions Progress Update 26-28 May 2015 Sander van Nederveen, TNO

Systems Engineering / Requirements Management Objectives for today Agreement on the Mini Case way of working, based on elaboration of Mini Case #1; More specific: identify and solve issues on the use of Olle’s Test Plan template for the Mini Cases Context ontology Common ontology V-Con Solution mapping Dataset Context BIM application W3C Linked Data application Common VCS V-Con ontologies Systems Engineering / Requirements Management

Mini Cases Strategy To show Software Vendors what we (=the V-Con Consortium) mean with the Tech Specs, by elaborating simple examples, To develop a Test Approach, and find out whether we can use this approach for the Business Specs, To identify gaps and issues. Strategy is further described in TS Phase 2 Report

Mini Cases - Approach Step by step: Common dataset only Common & Context, Turtle only Common & Context, Turtle & STEP-file

2. Common & Context, Turtle only Context ontology Common ontology V-Con Solution mapping Common Dataset Context BIM application W3C Linked Data application Context ontology Common ontology V-Con Solution mapping Context Dataset BIM application W3C Linked Data application Common Context ontology Common ontology V-Con Solution mapping Common Dataset Context ANDA application W3C Linked Data application 1. Common dataset only 2. Common & Context, Turtle only 3. Common & Context, Turtle & STEP-file

Approach (2) HESMOS/IDM project a): Identify Processes and Actors Identify Exchanges The data between the actors (files or query data) Create Exchange Requirements Datasets, Ontologies, Conversions, Mappings Plus: Specify who provides datasets/ontologies/conversions/ mappings V-Con Consortium / Vendor / External Party Identify steps of Testing Procedure, based on template Olle Liebich et al., “IDM Work within HESMOS, A descriptive approach to defining Information Delivery Manuals” Question for today: do we agree upon this “combined” approach?

Mini case 1 Common only Application works with Common Ontology Application “understands Turtle” no common <-> context conversion 1 Actor: System Engineer/Requirements Manager Import, export data in Turtle V-Con Solution Common Dataset in Turtle Export, import data in Turtle An ontology prescribed by V-Con A Software Application that knows the ontology prescribed by V-Con

Read ontologies and create database Mini case 1 Common only Application works with Common Ontology Application “understands Turtle” no common <-> context conversion 1 Actor: System Engineer/Requirements Manager An ontology prescribed by V-Con Export data in Turtle 4 Read ontologies and create database SE Application that knows the ontology prescribed by V-Con 1 Import data in Turtle 2 3 Common Dataset in Turtle 5 6 V-Con Solution

Mini Case 1 – the objects RoadNode_2 RoadNode_1 RoadSegment_1

Mini case 1 Common only Actor: System Engineer/Requirements Manager Import, export data in Turtle V-Con Solution Common Dataset in Turtle Export, import data in Turtle An ontology prescribed by V-Con A Software Application that knows the ontology prescribed by V-Con Actor: System Engineer/Requirements Manager Process & Exchange: Read data: objects: 2 existing Roads, 1 new Road, 5 RoadSegments, 6 RoadNodes Add data: property “RoadSegment#31.min_vehicle_capacity := 1500 (amount per hour) ” b) Store data. b) This is one way to model this property; other ways are possible too! Road 1 Road 2 Road 3 Road Node5 Node6 RoadSegment 11 Segment 31 RoadSegment 12 RoadSegment 22 RoadSegment 21 Node2 Node1 Node4 Node3

Mini case 1 Common only Exchange Requirements: Provided by: Common ontology, with: V-con consortium Classes Road, RoadSegment, RoadNode Property min_vehicle_capacity, Unit amount_per_hour Two onto layers, e.g. international and project specific Common dataset in Turtle 2 existing roads, 1 new road, 5 road segments, 6 road nodes Property: min_capacity = 1500 Import, export data in Turtle V-Con Solution Common Dataset in Turtle Export, import data in Turtle An ontology prescribed by V-Con A Software Application that knows the ontology prescribed by V-Con

Systems Engineering / Requirements Management Mini Case 1. Test Plan Based on template Olle Systems Engineering / Requirements Management VCS V-Con ontologies

Systems Engineering / Requirements Management Mini Case 1. Test Plan Based on template Olle Systems Engineering / Requirements Management VCS 5, 6 2, 3 4 1 Test case Purpose/description/comments/restrictions 1 Access Common Ontologies mc_onto_int and mc_onto_loc, and make visible in the VCS; so you can see what ontologies are in use (TC 5.1); and you can see the class and property structures of each ontology on data structure level (TC 5.2) Create database based on mc_onto_loc 2 Import data set, make accessible and visible in the VCS, including property values 3 Import updated data set with updated objects and/or properties 4 Export dataset 5 Access and modify dataset using SPARQL 6 Link a simple (txt) file to an object V-Con ontologies

Mini Case 1. Test Plan Minicase specification overview Test "environment" and issues (BS/TS) Efforts from Principal Efforts from vendor Test case Mini Case Purpose/description/comments/restrictions Transaction nr Technical challenge Input ontology Input format Data set ref Execution/Content (in VCS) Output ontology Output format Verif Data set Verification method Success criteria 1 Mini Case 1 Access Common Ontologies mc_onto_int and mc_onto_loc, and make visible in the VCS; so you can see what ontologies are in use (TC 5.1); and you can see the class and property structures of each ontology on data structure level (TC 5.2)   1.1, 3.1, 5.1, 5,2 OWL Turtle n/a common ontologies for roads (1) international: mc_onto_int (2) local: mc_onto_loc, (where (2) will use (1)) view ontologies in VCS common ontologies mc_onto_int and mc_onto_loc are visible (names, metadata); class & property structures of ontologies are visible 2 Create database based on mc_onto_loc 1.2 mc_onto_loc MC dataset #1 database based on mc_onto_loc view dataset mc1 in vcs 3 Import data set, make accessible and visible in the VCS, including property values 1.3, 5.3 common dataset with 2 existing roads and 1 new road 4 Import updated data set with updated objects and/or properties 1.4, 5.3 MC dataset #1a updated dataset with 1 added property view dataset mc1a in vcs 5 Export dataset 1.5 export dataset view stored dataset mc1a in vcs 6 Access and modify dataset using SPARQL 1.6 add/modify a property 7 Link a simple (txt) file to an object 1.7 link txt-file txt

Mini Case 2 & 3 Under Construction

Mini case 2. Common & context SE-application based on Common onto BIM-app based on Context onto Both apps read & write Turtle; no translations yet Context ontology Common ontology V-Con Solution mapping Common Dataset in Turtle Context In Turtle SE BIM/W3C Linked Data application (that can read/write Turtle) W3C Linked Data application BIM convertor

Mini case 2. Common & Context 2a: Common only – same as case 1! 2b: Link to context – new! Context ontology Common ontology V-Con Solution mapping Common Dataset in Turtle Context In Turtle SE BIM/W3C Linked Data application (that can read/write Turtle) W3C Linked Data application BIM convertor 2b 2a

Mini case 2A. Common & Context Anda Context ontology Common ontology V-Con Solution Linking Ontology Common Dataset in Turtle Context In Turtle SE Anda Linked Data application (that can read/write Turtle) W3C Linked Data application ANDA convertor 3 5 6 7 8 4 2 1

Mini case 2B. Common & Context Anda Context ontology Common ontology V-Con Solution Linking Ontology Common Dataset in Turtle Context In Turtle SE Anda Linked Data application (that can read/write Turtle) W3C Linked Data application ANDA convertor 3 5 6 7 8 4 2 1

Mini Case 2. Test Plan Based on template Olle 5, 6, 7, 8 Systems Engineering VCS 5, 6, 7, 8 2 1, 3, 4 V-Con ontologies Asset Management

Mini Case 3 Systems Engineering VCS 1 2 V-Con ontologies Asset Management

Mini case 2b. Link to Context Context ontology Common ontology V-Con Solution mapping Common Dataset in Turtle Context In Turtle SE BIM/W3C Linked Data application (that can read/write Turtle) W3C Linked Data application BIM convertor Actors: BIM-actor (designer/engineer) Process: Read data: objects: 2 existing roads, 1 new road property “road_#3.min_vehicle_capacity (node#1, node#2) := 1500 (amount per hour)” Add data: property “road_#3.vehicle_capacity (node#1, node#2) := 1700 (amount per hour)” c) d) ** shape… ** link – SameAs… Store data. c) This is again one way to model this property; other ways are possible too! By the way, this “vehicle_capacity” is (by default) an expected value. d) … And of course it can be more complicated, e.g. by saying: “road #3 has x lanes from north to south with width y, thus offering capacity of z”. 2b

Mini case 2b Link to Context Exchange Requirements Provided by (Common Ontology, see 1) V-Con (Common Dataset, see 1) Context Ontology (someday “owl-ized ifc/anda” – now only 2 objects) ContextRoad, ContextRoadNode Capacity (Node, Node) Context Dataset in Turtle ContextRoad (1, 2, 3) Capacity (Node#1, Node#2) Mapping Specification Contractor Converter “SameAs” …also a more advanced conversion? xxx

2a + 2b. Common & Context Actors: BIM-actor (designer/engineer) Context ontology Common ontology V-Con Solution mapping Common Dataset in Turtle Context In Turtle SE BIM/W3C Linked Data application (that can read/write Turtle) W3C Linked Data application BIM convertor Actors: BIM-actor (designer/engineer) SE-actor (project manager) Process: SE-actor specifies min capacity (case 1) SE-actor sends data to BIM actor BIM-actor specifies proposed (expected) capacity (case 2b) Exchange Requirements: See case 1 and 2b

Mini Case 3. Common – Context plus translation to non-linked data Context ontology Common ontology V-Con Solution mapping Common Dataset Context Anda application W3C Linked Data application “Linked-data” SE-application based on common onto “Non linked-data” BIM-application Intermediate data set, based on owl-ized BIM context ontology

Mini Case 3. Common – Context plus translation to non-linked data Context ontology Common ontology V-Con Solution mapping Common Dataset Context BIM application W3C Linked Data application = 3a plus 3b 3a: Conversion common – context, all Turtle => see 2! 3b: Translation Turtle –> SPFF, … and back 3b 3a

3b. Context: non-Linked Data to Linked data “Non Linked-data” BIM-application Translation to Context Dataset, according to owl-ized BIM ontology Context ontology Translation Specification Native structure Context Dataset in Turtle ANDA application ANDA data in SPFF Import, export SPFF (= translate SPFF <-> Turtle) V-Con Solution Owl-ized ANDA ontology translation 1 2

3b. Context: non-Linked Data to Linked data Exchange Requirements Ontologies Context Ontology: owl-ized BIM ontology (Native Structure: EXPRESS) Datasets Context Dataset in Turtle 2 BIM Datasets in SPFF Mappings Mapping Specification for Translation of SPFF Dataset into Turtle Dataset, and back Translation Translation of SPFF Dataset into Turtle Dataset, and back. Context ontology mapping Native structure Context Dataset in Turtle BIM application BIM data in SPFF Import, export SPFF (= translate SPFF <-> Turtle) V-Con Solution Owl-ized BIM ontology translation