Page Comparison

...

Steps to develop IoT applications using TQL:

Design

Model-led approach

1. Start by writing models (DataModels and ThingModels) - you can leave the ThingModels without ThingFacets at this time. The idea is the get a list of relevant entities in your domain and start to construct your domain logic. This approach gives you an overall picture before detailed implementation.

2. Add ThingFacets where you get access to actual devices or service APIs. For each ThingFacet you write and combined with a ThingModel, you can deploy and test with a few queries (Create queries, Find queries and Subscription Queries in some cases).

3. Create inter-model relationships. Sometimes you need to build business logic between different models. 

References (including Smart References)

Cherry-picking

Queries

Subscriptions

Thing-led approach

ThingFacets and ThingModels

Other Models and Model facets

Create queries or subscriptions

Simulate

Deploy and test

Write queries

TQLStudio

   You can use your account to login into TQLStudio. TQLStudio provides the complete development lifecyle for IoT application development

   Model → Deploy → Instantiate → Use

   Using Model editor, you can create appModels, ThingModels and DataModels.

   Using ThingSpace→Deploy, you can manage engines and deploy projects containing models.

   ThingSpace→Instantiate allows you to create new instances of things or entities.

    ThingSpace→Runtime

Eclipse

XMLEditorThe development lifecycle of TQL applications consist of four main steps:

1. Model

Define models and model facets to define the structure and behaviors of the things and the business domain (e.g. sensor model, zone models, greenhouse model)

2. Deploy

Deploy the models (model definitions) to the TQLEngine(s)

3. Run & test

Including three steps

(1) Instantiate: provide instance data to the TQLEninge, and the TQLEngine will automatically create model instances

(2) Activate: if not already done in (1), provide or modify instance data to the model attributes associated with actions or workflows, thereby activate the actions or workflows

(3) Interact: run any quries or create any subscriptions against model instances

4. Create apps

Use queries or subscriptions for various apps