0% found this document useful (0 votes)
34 views25 pages

Unit Iii

The document outlines the steps in an IoT design methodology: 1. Define the purpose and requirements of the system. This includes the system behavior, requirements, and what problem it aims to solve. 2. Specify the processes and use cases of the system based on the requirements. 3. Develop a domain model showing the relationships between physical and virtual entities of the system. 4. Specify the information model including the attributes and relationships of the virtual entities.

Uploaded by

ELAKYA R INT
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
34 views25 pages

Unit Iii

The document outlines the steps in an IoT design methodology: 1. Define the purpose and requirements of the system. This includes the system behavior, requirements, and what problem it aims to solve. 2. Specify the processes and use cases of the system based on the requirements. 3. Develop a domain model showing the relationships between physical and virtual entities of the system. 4. Specify the information model including the attributes and relationships of the virtual entities.

Uploaded by

ELAKYA R INT
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
You are on page 1/ 25

IT 18503 Internet of Things

UNIT-III
IoT platforms Design methodology

IoT Design Methodology- Purpose & Requirements


Specification, Process Specification ,Domain Model
Specification, Information Model Specification, Service
Specifications , IoT Level specification,Functional View
Specification , Operational View Specification , Device &
Component Integration , Application Development , Case
Study on IoT System for Weather Monitoring.
IoT Platform
Internet of Things platform is a group of technologies that provide the building blocks for developing
your product.

IoT platforms provide the “infrastructure” you use to create the specific features of your solution.

The goal of an IoT platform is to provide all the generic functionality for your application so you can
focus on building features that differentiate your product and add value for your customers.

An IoT platform manages connectivity of the devices and allows developers to build new mobile
software applications. It facilitates the collection of data from devices and enables business
transformation. It connects different components, ensuring uninterrupted flow of communication
between the devices.
Design Methodology
1. Design methods are procedures, techniques, aids, or tools for designing.What methods to use to design
a product /service.
2. The key to design methodology is finding the best solution for each design situation
3. IoT systems comprise of multiple components ,deployment tiers ,system levels suited for different
applications.
4. Designing IoT system is complex and challenging ,it involves interactions among various
components .
5. It is difficult to evaluate the available alternatives.
6. IoT designers keep in mind specific services/products so designs are tied leading to lock-in and
unsatisfactory customer.
7. Updating design becomes tough and may require complete redesign.
8. Generic IoT design methodology proposed for IoT system design independent of specific
product,service or PL.
9. This avoids extra design,testing and maintenance time and cost and makes comparing alternatives for
IoT system components more easier.
Step 1: Purpose & Requirements Specification

The first step in IoT system design methodology is to define the purpose and
requirements of the system. In this step, the system purpose, behavior and
requirements are captured.

The purpose of this _________________(System name) is to ____________ (understand?


Describe? Develop? Discover?) the ____________(central element being developed ) for
__________ (the participants, such as the individual, groups, organization) at
____________(research site) using ____________________________.

The behaviour ,system Management requirements,data analysis requirement,deployment


requirements and security requirements has to be mentioned.
Step 2: Process Specification
The use cases of the IoT system are formally described based on and derived
from the purpose and requirement specifications.
Step 3: Domain Model Specification
A domain model is a conceptual model of the domain that incorporates both behaviour and data.
It is a model that shows the real-world flow, relationships between entities,objects ,attributes , and concepts.
Designer will get idea about the IoT system that need to be developed.
Domain model includes
1. Physical entity ,a discrete and identifiable entity in physical world.Eg room,light ,appliance .
2. Virtual entity,a representation of physical entity in digital world.
3. Device provide a medium of interaction between PE and VE .Devices are attached to physical entities
and are used to gather information about physical entity.,perform actuation upon PE or identify PE.
4. Resources - S/w components on board or network resources .
5. Services provide a interface for interacting with the PE .They access the resource on the device or
network resource to obtain info about PE or perform actuation.
Eg: Setting mode,setting status ,controller service.
Information Model Specification
1. a "semantic" modelling technique
2. An Information Model is an organizational framework that you use to categorize your
information resources.
3. Defines structure of all information in the system.
4. eg.Attributes of Entities and relationships .
5. List the virtual entities from domain model add more details by defining their attributes
and relationships.
6. A strong, effective Information Model solves the problems described when it is designed
in the context of a content-management system.
7. .The model labels information according to the ways it will be accessed. In fact, the
information can be reorganized in many ways, depending upon who is doing the looking.
Service Specification
Defines the services in the IoT system like service type,service input and
output ,endpoints,schedules ,preconditions and effects.

Services are derived from process specification and information model.

From process specification and information model we identify states and attributes

For each state and attribute define service.Services can either change the state or
attribute value or retrieve the current value.

Mode service -set mode to manual or auto else retrieve the current mode.

State service -set the appliance on/off or get the current state.

Controller service monitors the light level in auto mode and updates the status in
the database.
Define the IoT level of the System.
7.Functional view specification
Defines the functions of the IoT systems grouped into various functional groups.

Each FG provides functionality for interacting with instances of concept defined in domain model. Or
provides info related to these concepts.

FG are

Devices- All devices for monitoring and control.

Communication- includes commn protocols,API

Services- services like device monitoring ,control services,publishing ,device discovery.

Management - Configuration and management of IoT system.

Security- all security mechanism

Application - that provide interface to the users to control & monitor or view syste
8.operational view specification
Various options pertaining to IoT system deployment and operations are defines
such as hosting options ,storage,device options,application hosting.
Step :9 Device and component Integration
10.Application Development

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy