Get Instant Help From 5000+ Experts For

Writing: Get your essay and assignment written from scratch by PhD expert

Rewriting: Paraphrase or rewrite your friend's essay with similar meaning at reduced cost

Editing:Proofread your work by experts and improve grade at Lowest cost

And Improve Your Grades
Phone no. Missing!

Enter phone no. to receive critical updates and urgent messages !

Attach file

Error goes here

Files Missing!

Please upload all relevant files for quick & complete assistance.

Guaranteed Higher Grade!
Free Quote
Internet of Things (IoT) Prototyping: Design, Implementation, and Security Considerations


1. Critically evaluate the strengths, weaknesses, and resource constraints of IoT computing systems in comparison to traditional computing models;

2. Design and implement a connected prototype IoT software system that utilises sensor data;

3. Implement industry standard IoT messaging protocols. 

This assignment requires you to propose the design and implementation approaches for an Internet of Things (IoT) prototype that is well considered regarding the functionality and interaction it provides users. The work you do will be assessed through two distinct and unrelated components: i) a substantial written report and ii) basic IoT connectivity code. The technical report will describe the design and implementation choices for an IoT prototype for the Smart Home environment – there is no code development required for this. The security implications of such a prototype will also be critiqued in the report. The IoT connectivity code piece of work is a smaller piece of work for the assessment and will demonstrate simulated sensor data sent to cloud services for storage and consumption – to be clear, the MXChip board is not to be used for this assessment. Note that the two assessment components are not dependent upon each another in any way, they are completed independently.

The assessment will require you to produce the following two components of work, please note the weighting of each, clearly you should spend most of your time on the technical report first.

i) Technical report for proposed IoT prototype (80% of assessment marks)

ii) IoT Connectivity code (20% of assessment marks)

The two required components are now outlined. 

The technical report is focused on detailing the design and implementation choices of an IoT prototype for the Smart Home environment. To help you generate ideas for your prototype, choose from a smart home device theme below:

Connected fridge-freezer with various sensors such as temperature, and capability to auto-order items

Security camera with two-way audio and video

Smart thermostat to control heating and hot water based on household consumption behaviours

Smart speaker system

Smart bulb with audio capability and connectivity to other smart home devices 

When you have selected a smart home device theme from the above list you can then begin thinking of the design of such a system in terms of the user interactions, followed by the types of cloud services you will need, as well as the security considerations.  This will all be included in the report as described below.


The report will contain five sections that provide a discussion and critique of your proposed IoT prototype. The required sections are i) Background, ii) Design, iii) Implementation, iv) Security considerations, and v) References. It is a mandatory requirement to use these main sections in the report, do not use your own. The content for each section is outlined below as well as some guidance on length.

i) Your background section should state your proposed IoT prototype’s scope, which smart home device theme you selected, and your motivation as to why feel the prototype would be useful as part of smart home environment. You should discuss other relevant smart home applications and supporting academic literature in the IoT smart home space. (~2 pages pages) ii) The design section should outline the proposed infrastructure of the IoT prototype, including the requirement of a basic diagram* to provide a simple overview of the components of the prototype, see figure 1 for an example. Your design should propose the cloud services as a bullet list at this stage, that will support your IoT Prototype. Additionally, you must also discuss how the individuals in the home environment will interact with the proposed IoT protype and what those features are. (~ 3 pages) iii) The implementation section should discuss the core cloud services that are required for the prototype, these are the services you proposed as a list in the design section and you should discuss each one in adequate detail in terms of its role and functionality in supporting the prototype. For example, you can discuss and critique the types of cloud storage that could be used for the proposed sensor data that will be generated, as well as any other core or supporting services such as cloud functions and IoT hubs (~3 pages)

iv) You must discuss the security considerations of the IoT prototype being deployed in a home environment in terms of threat modelling and STRIDE. (~2 pages)

v) The References section should contain a fully referenced list (Harvard style) for all academic and other relevant sources you have cited.

Your IoT connectivity code must only implement the following basic services on Azure which will in turn use the simulated sensor data, do not do any additional development work than set out below and in the CRG, please refer to the CRG for specific marking criteria:

1. Create and deploy an IoT hub to receive and ingest the simulated sensor data which is then saved to a suitable cloud data storage service (Cosmos DB) by creating an IoT Hub trigger. You will have already deployed and configured these services if you completed the relevant cloud tasks in workshops 4 and 5, so you can reuse them for this part. You must include your IoT Hub Device Connection String in the C# console app SimulatedDevices.cs file programmatically, as shown in workshop 10; 

2. The use of a ONE cloud HTTP Trigger function to enable third party access to the simulated sensor data stored in the cloud data storage service (from item 1 above). HTTP Trigger function must be RESTful and use an HTTP GET method. You will have already deployed and configured a basic version of an HTTP Trigger function if you completed the relevant cloud task in workshop 6, so you can reuse it for this part. You need to write the HTTP trigger function code so that only the JSON data for the simulated temperature sensor is returned, no other sensor data must be returned. The function must be coded in C# only. You must include your HTTP Trigger function URL in your submission and screenshot of returned data, see detailed submission instructions at tend of this document. You are free to reuse and modify code supplied in the workshops or any other public domain source.  

sales chat
sales chat