1. The document discusses application development challenges for the Internet of Things (IoT), including heterogeneity of devices, large scale, lack of separation of concerns, and life-cycle issues.
2. It proposes a conceptual model that classifies IoT concepts and relates development concerns to promote reusability.
3. A multi-stage model-driven approach is presented using a set of modeling languages to abstract heterogeneity, scale, and support automation across development stages.
The slides defines IoT and show the differnce between M2M and IoT vision. It then describes the different layers that depicts the functional architecture of IoT, standard organizations and bodies and other IoT technology alliances, low power IoT protocols, IoT Platform components, and finally gives a short description to one of IoT low power application protocols (MQTT).
The slides defines IoT and show the differnce between M2M and IoT vision. It then describes the different layers that depicts the functional architecture of IoT, standard organizations and bodies and other IoT technology alliances, low power IoT protocols, IoT Platform components, and finally gives a short description to one of IoT low power application protocols (MQTT).
IoT which stands for Internet of Things is not a very new topic, but sensing its importance and growing demand, it's very important for one to understand what exactly is IoT. So, here is the file, which will help you know about it in a very easy manner.
Hope this will help you
Internet of Things means every household or handy device which is used to make our world easy and better and connected with IP which transmit some data.
This slide covers IOT description, OWASP Top 10 2014 & its recommendations.
Machine to machine (M2M) is a broad label that can be used to describe any technology that enables networked devices to exchange information and perform actions without the manual assistance of humans.
Primarily M2M and IoT are similar in upper layer such as hardware, networking or devices. But they differ in system architecture, types of applications and underlying Technologies.
This will be helpful for GTU IOT subject course understanding too!
If you like the video please subscribe to our channel and turn notifications on for future videos.
Follow us on:
Website: http://www.edtechnology.in/
Instagram: https://www.instagram.com/ed.tech/
Facebook: https://www.facebook.com/Edtech18/
The Internet of things describes physical objects that are embedded with sensors, processing ability, software, and other technologies that connect and exchange data with other devices and systems over the Internet or other communications networks.
The IoT is here to stay. As with any other trend in the history of computer software, it’s starting to produce a new generation of cloud platforms. This tech talk will identify and explain what to look for when evaluating an IoT cloud platform to ensure a successful deployment of IoT strategies.
The impact of emerging IoT Technology and BigData. This is the slide presentation I did at the http://globalbigdatabootcamp.com/speakers/sanjay-sabnis/
What are the characterstics of good IOT platform?Yoganand Rajala
As the hardware, network and computation costs keep going down new IOT use cases will emerge. IOT platform needs to be prepared to enable end to end solutions quickly at scale.
\
IoT which stands for Internet of Things is not a very new topic, but sensing its importance and growing demand, it's very important for one to understand what exactly is IoT. So, here is the file, which will help you know about it in a very easy manner.
Hope this will help you
Internet of Things means every household or handy device which is used to make our world easy and better and connected with IP which transmit some data.
This slide covers IOT description, OWASP Top 10 2014 & its recommendations.
Machine to machine (M2M) is a broad label that can be used to describe any technology that enables networked devices to exchange information and perform actions without the manual assistance of humans.
Primarily M2M and IoT are similar in upper layer such as hardware, networking or devices. But they differ in system architecture, types of applications and underlying Technologies.
This will be helpful for GTU IOT subject course understanding too!
If you like the video please subscribe to our channel and turn notifications on for future videos.
Follow us on:
Website: http://www.edtechnology.in/
Instagram: https://www.instagram.com/ed.tech/
Facebook: https://www.facebook.com/Edtech18/
The Internet of things describes physical objects that are embedded with sensors, processing ability, software, and other technologies that connect and exchange data with other devices and systems over the Internet or other communications networks.
The IoT is here to stay. As with any other trend in the history of computer software, it’s starting to produce a new generation of cloud platforms. This tech talk will identify and explain what to look for when evaluating an IoT cloud platform to ensure a successful deployment of IoT strategies.
The impact of emerging IoT Technology and BigData. This is the slide presentation I did at the http://globalbigdatabootcamp.com/speakers/sanjay-sabnis/
What are the characterstics of good IOT platform?Yoganand Rajala
As the hardware, network and computation costs keep going down new IOT use cases will emerge. IOT platform needs to be prepared to enable end to end solutions quickly at scale.
\
Competing with Software: It Takes a Platform -- Devops @ EMC Worldcornelia davis
Presentation at Devops @ EMC World event, 3 May 2015
In Mark Andreessen’s 2010 piece for the Wall Street Journal, in which he declared “Software is Eating the World,” he talked about well established, large enterprises loosing footing to small, nimble startup companies who are far better at bringing software to their consumers. In fact, it’s not as much that these upstarts are better at meeting customer demands, rather they are the cause of the increased expectations, providing consumers with things they didn’t even know they wanted. What are the factors behind their success? New development and operational approaches including extreme agile & test driven development, continuous delivery and devops practices all play a significant role, and while a part of the difference is cultural, tools matter. In this session we’ll look at why a software-driven enterprise needs platform. Google has one. Facebook has one. Netflix has one. Your enterprise needs one.
Talk on Industrial Internet of Things @ Intelligent systems tech forum 2014Ahmed Mahmoud
The Industrial Internet can be thought of as Intelligent Industrial Systems. A subset of Intelligent Systems per IDC’s taxonomy, these systems have extremely high value not just in terms of product and process optimizations, efficiency and cost savings but in the enablement of new business models such as mass customization in manufacturing. This session will focus on the state of Industrial Internet today, the efforts underway to make the Industrial Internet a reality, leading companies, technologies and products in the space, efforts at standardization, case studies of the Industrial Internet in action, and opportunities in the space.
Enabling High Level Application Development In The Internet Of ThingsPankesh Patel
The Internet of Things (IoT) combines Wireless Sensor and Actuation Networks (WSANs), Pervasive
computing, and the elements of the \\traditional" Internet such as Web and database servers. This leads to
the dual challenges of scale and heterogeneity in these systems, which comprise a large number of devices of
dierent characteristics. In view of the above, developing IoT applications is challenging because it involves
dealing with a wide range of related issues, such as lack of separation of concerns, need for domain experts to
write low level code, and lack of specialized domain specic languages (DSLs). Existing software engineering
approaches only cover a limited subset of the above-mentioned challenges.
In this work, we propose an application development process for the IoT that aims to comprehensively
address the above challenges. We rst present the semantic model of the IoT, based on which we identify
the roles of the various stakeholders in the development process, viz., domain expert, software designer,
application developer, device developer, and network manager, along with their skills and responsibilities.
To aid them in their tasks, we propose a model-driven development approach which uses customized lan-
guages for each stage of the development process: Srijan Vocabulary Language (SVL) for specifying the
domain vocabulary, Srijan Architecture Language (SAL) for specifying the architecture of the application,
and Srijan Network Language (SNL) for expressing the properties of the network on which the application
will execute; each customized to the skill level and area of expertise of the relevant stakeholder. For the
application developer specifying the internal details of each software component, we propose the use of a
customized generated framework using a language such as Java. Our DSL-based approach is supported by
code generation and task-mapping techniques in an application development tool developed by us. Our
initial evaluation based on two realistic scenarios shows that the use of our techniques/framework succeeds
in improving productivity while developing IoT applications.
Towards application development for the internet of things updatedPankesh Patel
The Internet of Things (IoT) integrates the physical world with the existing Internet, and is rapidly gaining popularity, thanks to the increased adoption of smart phones and sensing devices. One of the important challenges in this domain is to enable domain experts to easily specify applications for the IoT. As a
first step towards developing a suitable programming
abstraction, in this paper we present a domain
model for applications in the Internet of Things, based on a
survey of recently proposed IoT applications from the real
world that represent a wide class of behaviors found in IoT
use cases.
<p>
[데브멘토 동영상] Meego for Intel Atom Processor and AppUp Center 2부 최종
<p>
이진용 Intel Korea 차장(Application Engineer)</p>
<p>
전LG전자 소프트웨어센터 책임연구원</p>
<p>
전PalmPalm Technology 신임연구원</p>
<p>
전Nexen 선임연구원</p>
<p>
중앙대학교 컴퓨터공학과 대학원 분산 및 운영체제 전공</p>
(ATS4-GS03) Partner Session - Intel Balanced Cloud Solutions for the Healthca...BIOVIA
Healthcare/Pharmaceutical -IT departments, under constant pressure to do more with less, face an ever increasing volume of regulatory requirements, infrastructure challenges, and demands from clinical end-users to support applications anytime, anywhere, on any device. Healthcare/Pharma CIOs have a hard enough time “keeping the lights on” and find it difficult to drive strategic initiatives that improve patient care or support growth.
Cloud computing can improve the efficiency of IT, increase organizational agility, and control costs, but how do organizations adopt interoperable, scalable solutions while minimizing industry concerns such as vendor lock-in and data breach?
In this session, attendees will learn about the key trends that are driving healthcare organizations toward cloud solutions that “balance” compute, network and storage concerns based on open, scalable infrastructure. We will look at real-world examples of how healthcare organizations are using the cloud today. Finally, we will discuss how healthcare cloud solutions can be improved with Intel platform capabilities.
It is an exciting time in computing with the sea-change happening both on the technology fronts and application fronts. Networked sensors and embedded platforms with significant computational capabilities with access to backend utility computing resources, offer a tremendous opportunity to realize large-scale cyber-physical systems (CPS) to address the many societal challenges including emergency response, disaster recovery, surveillance, and transportation. Referred to as Situation awareness applications, they are latency-sensitive, data intensive, involve heavy-duty processing, run 24x7, and result in actuation with possible retargeting of sensors. Examples include surveillance deploying large-scale distributed camera networks, and personalized traffic alerts in vehicular networks using road and traffic sensing. This talk covers ongoing research in Professor Ramachandran’s embedded pervasive lab to provide system support for Internet of Things.
Hadoop World 2011: Security Considerations for Hadoop Deployments - Jeremy Gl...Cloudera, Inc.
Security in a distributed environment is a growing concern for most industries. Few face security challenges like the Defense Community, who must balance complex security constraints with timeliness and accuracy. We propose to briefly discuss the security paradigms defined in DCID 6/3 by NSA for secure storage and access of data (the “Protection Level” system). In addition, we will describe the implications of each level on the Hadoop architecture and various patterns organizations can implement to meet these requirements within the Hadoop ecosystem. We conclude with our “wish list” of features essential to meet the federal security requirements.
Similar to Application development for the internet of things (20)
This is user manual for IoTSuite. This contains description about how to setup IoTSuite on your PC for programming, how to use development environment provided by IoTSuite.
A step-by-step video guide is available at URL: https://www.youtube.com/watch?v=nS_Je7IzPvM
Towards application development for the internet of thingsPankesh Patel
Application development in the Internet of Things (IoT) is challenging because it involves dealing with a wide range of related issues such as lack of separation of concerns, and lack of high-level of abstractions to address both the large scale and heterogeneity. Moreover, stakeholders involved in the application development have to address issues that can be attributed to different life-cycles phases. when developing applications. First, the application logic has to be analyzed and then separated into a set of distributed tasks for an underlying network. Then, the tasks have to be implemented for the specific hardware. Apart from handling these issues, they have
to deal with other aspects of life-cycle such as changes in application requirements and deployed devices.
Several approaches have been proposed in the closely related fields of wireless sensor network, ubiquitous and pervasive
computing, and software engineering in general to address the above challenges. However, existing approaches only cover limited subsets of the above mentioned challenges when applied to the IoT. This work proposes an integrated approach for addressing the above mentioned challenges. The main contributions of this work are: (1) a development methodology that separates IoT application development into different concerns and provides a conceptual framework to develop an application, (2) a development framework that implements the development methodology to support actions of stakeholders. The development framework provides a set of modeling languages to specify each development concern and abstracts
the scale and heterogeneity related complexity. It integrates code generation, task-mapping, and linking techniques
to provide automation. Code generation supports the application development phase by producing a programming
framework that allows stakeholders to focus on the application logic, while our mapping and linking techniques together support the deployment phase by producing device-specific code to result in a distributed system collaboratively hosted by individual devices. Our evaluation based on two realistic scenarios shows that the use of our approach improves the productivity of stakeholders involved in the application development.
Cloud computing that provides cheap and pay-as-you-go computing resources is rapidly gaining momentum as an alternative to traditional IT Infrastructure. As more and more consumers delegate their tasks to cloud providers, Service Level Agreements(SLA) between consumers and providers emerge as a key aspect. Due to the dynamic nature of the cloud, continuous monitoring on Quality of Service (QoS)
attributes is necessary to enforce SLAs. Also numerous other factors such as trust (on the cloud provider) come into consideration, particularly for enterprise customers that may outsource its critical data. This complex nature of the cloud landscape warrants a sophisticated means of managing SLAs. This paper proposes a mechanism for managing SLAs in a cloud computing environment using the Web Service Level Agreement(WSLA) framework, developed for SLA monitoring and SLA enforcement
in a Service Oriented Architecture (SOA). We use the third
party support feature of WSLA to delegate monitoring and enforcement tasks to other entities in order to solve the trust issues. We also present a real world use case to validate our proposal.
Enabling high level application development for internet of thingsPankesh Patel
Application development in the Internet of Things (IoT) is challenging because it involves dealing with
a wide range of related issues such as lack of separation of concerns, and lack of high-level of abstractions
to address both the large scale and heterogeneity. Moreover, stakeholders involved in the application development have to address issues that can be attributed to different life-cycles phases when developing applications.
First, the application logic has to be analyzed and then separated into a set of distributed tasks for an underlying network. Then, the tasks have to be implemented for the specific hardware. Apart from handling these issues, they have to deal with other aspects of life-cycle such as changes in application requirements and deployed devices.
Several approaches have been proposed in the closely related fields of wireless sensor network, ubiquitous and pervasive computing, and software engineering in general to address the above challenges. However, existing approaches only cover limited subsets of the above mentioned challenges when applied to the IoT. This paper proposes an integrated approach for addressing the above
mentioned challenges. The main contributions of this paper are$\colon$ (1) a development methodology that separates
IoT application development into different concerns and provides a conceptual framework to develop an application,
(2) a development framework that implements the development methodology to support actions of stakeholders. The development framework provides a set of modeling languages to specify each development concern and abstracts the scale and heterogeneity related complexity. It integrates code generation, task-mapping, and linking techniques to provide automation. Code generation supports the application development phase by producing a programming framework that allows stakeholders to focus on the application logic, while our mapping and linking techniques together support the deployment phase by producing device-specific code to result in a distributed system collaboratively hosted by individual devices. Our evaluation based on two realistic scenarios shows that the use of our approach improves the productivity of stakeholders involved in the application development.
2. Outline
• Characteristics of IoT
• Application development challenges
• Related work
• Contribution
• Conclusion
• Ongoing and future work
3. Characteristics of ``things’’
• May have sensors attached
• May have actuators attached
• Can communicate with other
things
• Can be involved in the
information exchange between
``physical’’ and ``virtual’’ worlds
3
4. Marriage of sensor network and pervasive
computing
Sensor network Pervasive computing
Large
Scale Heterogeneity
Internet of things
5. Multiple levels[IoTSurvey]
Internet of
Things
Domain
…
Smart Health-care Transportation
Environment
Detecting
Application HVAC
Fire
Deployment
INRIA office Google Office
[IoTSurvey] L. Atzori, A. Iera, and G. Morabito. The Internet of Things: A Survey. Computer Networks, 54:2787–2805, 2010.
6. Outline
• Characteristics of IoT
• Application development challenges
• Related work
• Contribution
• Conclusion
• Ongoing and future work
7. Heterogeneity of the devices
• Different types of sensors and actuators
(e.g., temp. sensor, badge reader)
• Different implementations (e.g., Android,
iOS).
• Different interaction modes (pub/sub,
req./resp., command)
• Different data unit (e.g., ‘C, ‘F)
Ideally, it should not be the developer's responsibility to
handle this heterogeneity.
8. Large scale
• Hundreds to thousands of devices
equipped with sensors and actuators
• Reasoning such a scale is not
feasible/practical.
Need of adequate abstractions to present the large scale
in suitable manner .
9. No separation of concerns
Wide range of hardware Domain-specific
and software entities, Middleware specific features
running on specific features
platforms
All concerns are largely coupled
Internet of Things
Application into the application logic.
Need of separating all these concerns to enable
reusability.
10. Lots of glue code
• The stakeholders have to write lots of glue code
apart from an application logic:
– Interface hardware and software components
– Interface software components and middleware.
– mapping code for device and software component
Ideally, the glue code should be generated, allowing the
stakeholders to focus only on the application logic.
11. Life-cycle and future changes
– Development: The application logic has to be
analysed and separated into a set of distributed
tasks for the underlying network.
– Deployment : The tasks have to be implemented
for the specific hardware.
– Evolution: future changes in the infrastructure
and application requirements.
Covering application development life-cycle
12. Summary
• An approach
1. Covers all application development stages
2. Links IoT development concerns
3. Supports modeling language (abstracts
heterogeneity and scale)
4. Provides automations at all stages
13. Outline
• Characteristics of IoT
• Application development challenges
• Related work
• Contribution
• Conclusion
• Ongoing and future work
14. Related work
Approaches Motivation Examples Disadvantages
Database •Provide SQL-like interface, TinyDB, Cougar, SINA • Only for homogeneous
•Address scale for data- devices
collecting application • Missing development life-cycle
Library- or •Offer abstractions to Gaia with Olympus, •Lots of glue code,
toolkit based implement applications Context toolkit •No separation of concerns
• Address heterogeneity •Missing development life-cycle
partially
Model-driven •Raise the level of abstractions ATaG, Only cover a limited subset of
in program specifications (in DiaSuite, requirements
UML/textual language) and PervML
transforms into working
implementations
15. Outline
• Characteristics of IoT
• Application development challenges
• Related work
• Contribution
• Conclusion
• Ongoing and future work
16. Contributions…
Classification
of concepts
1 Conceptual model
Captures concepts and associations 2 Development concerns
to represent the IoT applications
• separation of concerns,
•Promotes re-usability
are specified
in
are combined
in
3 A set of modeling
languages
•Abstracts heterogeneity, A multi-stage model-driven
•Abstracts large scale, 4
•Parameterized with domain
approach for IoT
• Supports application development stages
• Links IoT development concerns
•Supports automations at all stages
17. Our IoT Conceptual Model (1/2)
It encapsulates system’s
functionalities, provides
interface. Communicates-with
Traditional 1..* 1 consumes 1..*
1 Software
Internet concepts Information
Component 1 generates 1
Extends
Extends Extends Extends
End-user Storage Computational
Driver
Application Service service
Interacts 1 1
Provides
Extends Extends
with access to
1 1..*
Sensor Actuator
User Store Driver Driver
``Things’’- oriented
concepts
17
18. Our IoT Conceptual Model (2/2)
Entity of Consists of Observes
Phenomenon
Interest
affects
Actuator Sensor
accesses
actuates
Resource Actuator Sensor
Hosts Driver Driver
Device
generates
consumes
Runs-on
Software
Component Command Sensor
Measurement
End-user Storage
Computational Driver
Application Service
Service
Information
User Store
18
19. IoT applications and its development
concerns
Domain Application
• Sensor, • Computational
• Actuator, Service,
• Storage IoT
• End-user application
Applications
Deployment* Infrastructure
• Device • Sensor Driver,
• Actuator Driver,
• Storage Service
This concerns describesinformation about howspecific to the application
This concern supply howconcepts that components are are grouped
This concerns the the software are the devices connected for
It refers to underlying platform specific-components.
domain (e.g., buildingapplication logic.
specifying the automation, transport)
and physically distributed.
* I am in process of identifying a suitable name. The name could be “physical”.
20. Actuator
Vocabulary Lang. Device
action
Affects
Phenomenon
(Domain)
(e.g., Heater)
Information/
Deployment
command Lang.
Architecture Lang.
Computational
Service
(Deployment)
Computational
Device
(Application)
Service
Computes
Information and
take decision Computational
(e.g., Calculate Avg) Sensor Service
Measurement
Observes
Phenomenon
Vocabulary Lang. Device
Sensor Storage Stores info.
(e.g., Temperature
Sensor )
(Domain) about
Phenomenon
(e.g., User’s Preferences) 20
21. Vocabulary Language (1/2)
As a first step of abstracting heterogeneity, sensing and actuating entities are
specified in high-level manner.
One resource description for
many implementations.
One resource description for many
structs:
instances.
TempStruct
tempValue : double;
unitOfMeasurement : String;
resources:
sensors:
TemperatureSensor
generate tempMeasurement : TempStruct;
actuators:
Heater
action Off();
action SetTemp(setTemp: TempStruct);
storages:
ProfileDB
generate profile : TempStruct accessed-by badgeID : String; 21
22. Vocabulary Language (2/2)
To address scalable operations within IoT system, hierarchical clustering should
be specified [SINA].
Building:03
regions:
Building : Integer;
Floor : Integer; Floor: 10 ... Floor: 15
Room : Integer;
Room: 5 Room: 6
Use of region construct:
• Enables system partition at logical level
• Defines scope from which software components will
produce/consume data
[SINA] Srisathapornphat, C. and Jaikaeo, C. and Shen, C. , Sensor information networking architecture and
applications, 2001
22
23. Architecture Language avgTemp In-region
: room
Room
AvgTemp
tempMeasurement
hops:0:Room
Scope of consuming Temperature
data. Sensor
RoomAvgTemp
Enables
consume tempMeasurement from hops : 0: Room ;
Hierarchical
generate avgTemp : TempStruct ;
Clustering
in-region : Room ;
Scope of
deployment
23
24. Deployment Language
Temperature-Sensing-Device : Device Name
region :
Building : 15 ;
Floor : 11;
Room : 0;
Attached sensor/
abilities : TemperatureSensor;
actuator/storage
type : sunspot;
with device
Badge-Scanner :
region :
Building : 15 ;
Floor : 11;
Room : 0;
abilities : BadgeReader ;
type : android;
24
31. Linking
1
2
Domain Vocabulary
Expert Specification Architecture Application
Specification Designer
5
Framework
Generator
Network Network
3 description Manager
4 Mapper
6
Application Application 7
Application
Developer Logic Framework Mapping
files
Device
Device Developer
Specify Drivers
8 Combines the generated code into
Input
System Linker the actual code to be deployed on
Refer
the real devices.
Output
31
32. Maintenance and evolution(1/2)
E.g., Adding a new applications in the existing infrastructure.
E.g., Moving an application from one deployment to other.
E.g., Implementing and plugging new device drivers.
Change in
Any requirements?
Defining Defining Defining Defining
Compiler
Domain Application deployment infrastructure
Concern concern concern concern
32
33. Maintenance and evolution(2/2)
1. Change in vocabulary specification
2. Change in architecture specification
3. Change in network specification
Preserves previous application
logic and replaces the generated
Implementation framework
(Application logic)
Spec. Initially generated Initially generated Change in Compile time Modified
framework framework Spec. errors Impl.
34. Outline
• Characteristics of IoT
• Application development challenges
• Related work
• Contribution
• Conclusion
• Ongoing and future work
35. Conclusion
Requirements Solved in our approach
Abstracting • Vocabulary language (Different types of resources , Different
Heterogeneity types of implementations)
• Architecture language ( different types of interactions)
Abstracting • Architecture and vocabulary lang. (system-level)
Scale • Scope constructs
Separation of concern • Conceptual model , capturing concepts and association
• Classification of development concerns (enabling reusability)
Automation in Code generation and task mapping techniques
development
Covering application • Links development concerns
development stages • Supports automation in software development
• Combines modeling languages
• Supports for each stage of application development
36. Outline
• Characteristics of IoT
• Application development challenges
• Related work
• Contribution
• Conclusion
• Ongoing and future work
37. End-user interactions with devices
• The end-user is going to play a major role in
the IoT applications.
– Originator: an user triggers an event or query to
the application.
– Recipient: an user is notified a final results by the
application.
– Intermediary: an user is prompted as required.
We will provide abstractions to specify these users’ interactions
with applications.
38. Mobility of devices**
• The current version of our modeling language
considers only static topology where the
devices do not move once they are deployed.
We will support mobile devices in our future version of modeling
languages.
** I am investigating this future challenge.
39. Evaluating expressiveness of modeling
languages
• It explores the subset of IoT applications
characteristics that may be suitably developed
in the framework.
What are the characteristics of IoT applications that can modeled
by our approach ?
40. Evaluating development effort in the
real-world
• It evaluates the time required to develop an
application.
• To measure the development effort, we plan
to give our framework to our lab members
with a suitable application.
• From this experiment, we will measure the
total time to develop an application.
41. Tentative time-line
Month TODO list
February (1) Journal paper submission
(2) Finish future work
March
April
May
June
Thesis Writing and Thesis submission
July
August
September Presentation preparation
October Thesis defense
What will an Intern do with the help of me ? (next slide)
42. What will an Intern do ?
1. The intern will implements different applications using our
framework.
– Outcomes:
• Expressiveness of our approach
• Bugs identification and fix
2. The intern will implement a wrapper between our framework
and a middleware.
– Outcomes:
• Prototype implementations in real-world.
3. The intern will write a documentation of our approach on web-
pages.
– Outcomes:
• It will guide the developers to develop IoT applications.
• It will help our future PhD students to further extend this work.