School of Computing

Schedule and Deliverables

Notes and Advice

●    The Extenuating Circumstances procedure is there to support you if you have had any circumstances (problems) that have been serious or significant enough to prevent you from attending, completing or submitting an assessment on time. If you complete an Extenuating Circumstances Form (ECF) for this assessment, it is important that you use the correct module code, item number and deadline (not the late deadline) given above.

● ASDAC are available to any students who disclose a disability or require additional support for their academic studies with a good set of resources on the ASDAC moodle site

●    The University takes any form of academic misconduct (such as plagiarism or cheating) seriously, so please make sure your work is your own. Please ensure you adhere to our Code of Student Behaviourand watch the video  on Plagiarism.

●    Any material submitted that does not meet format or submission

guidelines, or falls outside of the submission deadline could be subject to a cap on your overall result or disqualification entirely.

●     If you need additional assistance, you can ask your personal tutor, student engagement officer ana.ba[email protected], academic tutor [email protected]or your lecturers.

●     If you are concerned about your mental well-being, please contact our Well-being service

Internet of Things Coursework (M30226)

The goal of this coursework is to apply your knowledge and practical skills to design and build an IoT application. The deliverables consist of three artifacts:

A final report with details of the design. A demo of your application (a 3 minute video recording) along with implementation source code.

Your final report should address but not limited to the following parts:

Introduction: Define the application scenario and the problem -- justify why the IoT solution is needed, propose your design and the main functionality, decompose the design into smaller tasks, and give a basic outline of what you proposed to implement. The main tasks and the logic flow should be well justified.

Details of the design: Include any essential components: tools, sensors, modules, protocols, platforms, pseudo code, and diagrams -- anything that is necessary to clearly explain your IoT system/steps. You are free to go further beyond what you have been provided with for your practical exercises. You need to compare the useful components/sensors/modules before you adopt any of them for your design.

Browse the Internet, look for more sensors, identify their operating/working conditions, and include them in your design. Describe the communication protocols and application protocols that you will use, with detailed data flow and pseudo code. Even though some sensors/functions will not be implemented due to the limited resources, a consistent representation of them in data flow and pseudo code is expected across all stages. If you are considering using a commercial platform. as a public broker/server, name the one you want to use and provide evidence of testing the platform. Besides the technical issues, the cost of your design should be quantitatively evaluated. Justify all your choices for this part.

Implementation: You could implement only some parts of your design. It is acceptable for you to have a sophisticated design but without an implementation of the entire design due to the limits on available tools or resources.

Here are the basic and advanced requirements for your implementation:

•   The system operates without errors (basic)

•   Hardware components are properly connected (basic)

•   The design/function logic is clearly defined (basic)

•   The code is well written (basic)

•  Implementing machine learning algorithms to enable sensory feedback in the project (advanced)

Discussion and conclusions: Summarise the main insights into your design and map your solutions to the defined scenario and problems. Discuss the potential drawbacks, advantages and disadvantages of your design and how your design could be improved. Identify clearly which part you implemented as a tangible output and why the rest are not implemented.

Grading

Grading will be based on the quality of the design (for example: originality, thoroughness, extent of analysis, justification), the clarity of the written report, and the implementation quality based on the demo and code. Ideally, you are encouraged to try something novel or apply ideas out of our workshops to the problems given. You can get a good grade for the design even if your innovative ideas do not work out well, as long as your final report shows evidence of extensive analysis and exploration, provides sound justification for your choices of modules / sensors / methods / platforms, and provides thoughtful reviews / reflections / comparisons on the existing solutions.

Originality check

The design and implementation should be done all by yourself independently. Your marks will be capped if the implementation has been proved to have not been done on your own.

The marking criteria below apply for both the design, implementation, report and demo

● Introduction 12%

○     Understanding of your application scenario and problem

○     Justification of the need of an IoT solution to your problem

○     Presentation of the motivation of your design and justification

○     Design decomposition into subsystems/submodules

○     Integration of innovative ideas into the design process

● Details of the design 35%

○     Clear description of the chosen solutions/tools for each subsystem/submodule

○     Justification behind the chosen solutions/tools, highlighting their suitability for the given scenario

○     Comparison with alternative modules/sensors/protocols considered

○     Clear citations & references of the sources for the tools/sensors, modules, protocols, platforms, etc.

○     Utilisation of pseudo code or code snippets with syntax to illustrate the functions in each

subsystem/submodule (applied to all subsystems/submodules, including those not implemented)

○     Incorporation of flowcharts/diagrams to visually depict the logic and data flow (control commands + actuator signals) of the final design

○     Specification of the working conditions of the design

○     Demonstrated innovation and practicality in the design approach

○     Cost estimation of your design/implementation

● Implementation of your design 38%

○     Implementation of either the entire design or a portion thereof

○     Error-free functionality in the implementation

○     Proper connection of hardware components without any evident issues

○     Clarity in the logic of functions during the demonstration

○     Ability to provide clear explanations of the code during the demo

○     Implementation beyond simple execution of previously provided code

○     Integration of innovative elements in the implementation, such as data fusion, human factors, and user interface enhancements

● Discussion 15%

○     Summary of your design

○     Alignment of solutions with the provided scenario and problem

○     Identification of potential pitfalls, along with advantages and disadvantages

○     Presentation of alternative solutions and recommendations

○     Suggestions for future enhancements or directions to enhance existing solutions

○

How to submit

Upload a single compressed file with your student ID as the file name (for example UP123456.zip) to the submission link before the 12th May, 2025. The submission link on the Moodle will be disabled on the deadline (12th May, 2025 by 16:00) and only the content submitted will be marked: The single submitted compressed file (zipped file) must contain the following:

●     The final report which must be a PDF file saved inside a “Report” folder.

●     The source code which must be saved in the “Source” folder.

●     A 3-minutes demo video which must be saved in the “Video” folder. The report should be in the IEEE journal format. A template is available on Moodle for your reference.