Internet of Things Environment for Service Creation and Testing (IoT.est)
Internet of Things Environment for Service Crea5on and Tes5ng (IoT.est) Sep$miu Nechifor – Siemens CT (on behalf of IoT.est team)
IoT in short • Family of topics – RFID, M2M, SCADA, etc. – Call for “things to things”, “things to systems”, “things to person” – Subfamily of “distributed systems” • Trends & Standardiza$on – REST – ETSI M2M – IETF COAP – COSM (Pachube) – OGC 01/07/2012 2
IoT.est – a snapshot • IoT.est develop a test-‐driven service crea$on environment (SCE) for Internet of Things enabled business services. • The SCE will enable the acquisi$on of data and control/actua$on of sensors, objects and actuators. • The project will provide the means and tools to deﬁne and instan$ate IoT services that exploit data across domain boundaries; • IoT.est will facilitate run-‐$me monitoring and will enable autonomous service adapta$on to environment/context and network parameter (e.g. QoS) changes.
IoT.est – bridging the gap 01/07/2012 Enabling Process Automa$on from requirements and design goals to the product as well as to the underlying device sensor/actuator layer.
IoT.est: The Key issues • IoT enabled Business Services: Seman$c Descrip$on • Service Composi$on: A Knowledge based Approach • Service Components: Re-‐usable, Interoperable and Adap$ve • Abstrac$on: Mapping to Heterogeneous Pla`orms and Large Scale Deployment • Tes$ng (Design Time): Automated Genera$on of Tests • Monitoring (Run-‐Time): Context-‐aware Service Adapta$on
Test approach – ques$ons to answer • Modeling – Covering the spec? Automated deriva$on? – Test side eﬀects? Side eﬀects reversed and how? • Composi$on – Any reusable tests from modeling? • Deployment – Any dependencies to deploy test? • Execu$on – Which test should be run to prove the SLA?