Evolving the way we create and test services for the Internet of Things presented at RCIS 2012 - the Sixth International Conference on Research Challenges in Information Science, Valencia, Spain, 16-18 May 2012

1. Evolving the way we create and test
services for the Internet of Things

2. Internet of Things:
leveraging trends that are already in motion
25/05/2012 RCIS 2012 2
2011:
7 billion people
13 billion devices
2000:
6 billion people
500 million devices
2020
7.6 billion people
50 billion devices!!!
(projection by Cisco)
Source:
Gérald Santucci,
Networked Enterprise
European Commission

3. 25/05/2012 3
IoT is best explained in the real world
Scenarios
are often
intertwined!
RCIS 2012

4. IoT Comic Book
Alexandra Institute, Denmark
http://www.alexandra.dk/uk/services/Publications/Documents/IoT_Comic_Book.pdf
Andy Stanford‐Clark’s (IBM) TEDxWarwick talk:
http://www.youtube.com/watch?v=s9nrm8q5eGg
European Commission / Digital Agenda videos:
http://www.youtube.com/playlist?list=PLD4B1B7AB8011CFB7
25/05/2012 RCIS 2012 4
clever overviews of IoT

5. IoT opportunities:
many scenarios across many domains…
25/05/2012 5
Transportation
Emergency
Smart City
Smart Factory
Smart Home
Supply Chain
Healthcare
Lifestyle
Retail
Agriculture
Culture & Tourism
User Interaction
Environment
Energy
…and a lot of requirements!
RCIS 2012

6. • current IoT architectures are often domain‐specific, limited
requirements
• provisioning of these business services are time and cost
extensive, very complex
• these are just today’s envisioned domains!
• if this is truly the IoT…
an IoT challenge:
get out of the domain‐specific silo!
25/05/2012 6RCIS 2012

7. Transportation
Emergency
Smart City
Smart Factory
Smart Home
Supply Chain
Healthcare
Lifestyle
Retail
Agriculture
Culture & Tourism
User Interaction
Environment
Energy
…then we have to think multi‐domain, multi‐sector!
25/05/2012 RCIS 2012 7
an IoT challenge:
get out of the domain‐specific silo!

8. IoT.est: bridging the gap!
Service Creation Environment (SCE)
• automated composition of business services based on
common IoT service and test components (re‐use)
• self‐management capable components, business services
• abstraction of the heterogeneity of underlying technology
(interoperability)

9. IoT.est in action
Service Lifecycle phases:
• the project distinguishes four
service life cycle phases belonging
either to design‐ or run‐time.
Our objective: a framework for
efficient and reliable service creation
and provision by integrating self‐
testing and self‐adaptation in all
service life cycle phases.
RCIS 2012

10. IoT.est in action
Modelling Phase:
Knowledge based methods derive
semi‐automatically services and
related tests from semantic
service descriptions based on
standard service interfaces and
re‐usable service and test
components.
RCIS 2012

11. IoT.est in action
Composition Phase:
A test‐aware IoT Service Creation
Environment supports
incremental service evolution by
regression tests. When adding
new functionalities, the service
components and system tests are
included to ensure backward
compatibility with previous
service releases.
RCIS 2012

12. IoT.est in action
Deployment Phase:
The framework forces service
validation tests in a sandbox
environment before deployment
in the service providers’
infrastructure, including
automated deployment
procedures based on semantics
for service resource requirements
and network capabilities.
RCIS 2012

13. IoT.est in action
Execution Phase:
Run‐time monitoring mechanisms
enable service adaptation to
environment changes and
adjustment of network
parameters. This adaptation can
result in reselection of involved
components at run‐time.
RCIS 2012

14. right now in IoT.est:
analysis of scenarios, use cases and requirements
25/05/2012 14RCIS 2012

15. • Business oriented scenario: It is a requirement that the use case is business oriented, and the use
cases should preferably be part of a business process
• Complex scenarios: It is a requirement that the use case consists of composed services leading to
more complex scenarios.
• Usage of devices: IoT‐enabled devices should be involved in the scenario.
• Implementable scenario: The scenarios should be realizable, meaning that it should be possible
to get access to the sensors, services etc.
• Service Composition: The scenario should consist of service composition, i.e., create context‐
aware business services (i.e., IoT enabled services) that are composed by high level services and
the low level IoT services.
• Service adaptation: The scenarios shall provide service adaptation use cases where services will
automatically switch or adapt to new conditions when network and environment variables
change.
25/05/2012 15
scenarios, use case and requirements analysis
criteria and evaluation
RCIS 2012

16. 25/05/2012 16
Transportation
Smart City
Smart Factory
Smart Home
Supply Chain
Lifestyle
Retail
Agriculture
Culture & Tourism
User Interaction
Environment
RCIS 2012
scenarios, use case and requirements analysis
criteria and evaluation

17. 25/05/2012 RCIS 2012 17
Emergency:
Smart Events
Scenario
Energy:
Energy Efficient
Buildings
Scenario
Healthcare:
Well Being
Scenario
right now in IoT.est:
analysis of scenarios, use cases and requirements

18. – Accuracy
– Adaptation
– Architecture
– Availability
– Deployment
– Interoperability
– IoT Management
– Management
– Monitoring
– Performance
– Pervasiveness
– Portability
– Reliability
– Scalability
– Security
– Service Creation
– Testing
– Usability
25/05/2012 18
scenarios and requirements analysis
requirements classification
RCIS 2012

19. 25/05/2012 19
scenarios and requirements analysis
requirements extraction
ID:R.3.1.6
Description:
Reusable IoT Services Components
Rationale:
Identify a software component design which enables reusage of IoT services
ID:R.3.1.15
Description:
IoT Services Catalogue comprising all reusable IoT Services that can be used to compose new
services
Rationale:
To ensure the visibility of available IoT Services that can be used to compose new services
ID:R.4.0.4
Description:
IoT.est SCE should assist the process of identifying the target environment.
Rationale:
IoT.est SCE should provide the means to the user in order to be able to easily provide the target
environment description.
RCIS 2012

20. Thank you!
Contact details:
James Ahtes (james.ahtes@atos.net)
www.ict‐iotest.eu
Internet of Things Environment for
Service Creation and Testing (IoT.est)