Embedded Systems and the Internet of Things EEE_6_ESI
- Subject Code :
EEE-6-ESI
Assessment Brief
Read this assessment brief carefully, it tells you how you are going to be assessed, how to submit your assessment on-time and how (and when) youll receive your marks and feedback.
|
Module Code |
EEE_6_ESI |
|
Module Title |
Embedded Systems and the Internet of Things |
|
Module Leader |
Stavros Dimitriou |
|
Assessment Type |
Assignment (Formal Report) |
|
% of Module Mark |
16% of Module Mark |
|
% of CW Mark |
40% of CW Mark - Subcomponent 2 (SC2_40) |
|
Distributed |
21 February 2025 |
|
Assignment Window |
10 weeks |
|
Submission Method |
Submit online via Modules Moodle site (VLE) |
|
Submission Deadline |
Tuesday 6 th May 2025 by 9pm |
|
Release of Feedback |
Feedback will be available from 28th May 2025 |
|
Release of Marks |
Provisional marks will be available in the Gradebook on Moodle VLE from 28th May 2025 |
Assessment Title:
IoT-Based Smart Traffic Management System
(Controlling Using Open-Source Tools for Simulation and Optimization)
This is your Embedded Systems and the Internet of Things assignment (Formal Report) . Your formal report should include title, contents, abstract (no more than 150 words), Introduction, Main body (answer clearly to the above problem including your implemented designs, programs/simulations), Conclusion (no more than 200 words), References, Appendix. Find below indicative report guidelines. These guidelines are generic and may vary.
REPORT GUIDELINES
A project results in a detailed written technical report. The project report should be neat, readable, and self-contained. Also, it should be written with the readers in mind.
Any class member should be able to understand your report, and benefit from the results you obtain. Therefore, you should include adequate references and/or background materials and you should use tables, diagrams, graphs, figures, and portions of printouts to enhance readers' comprehension of your project.
The following format is suggested. You don't have to follow it exactly. Some sections may not be needed, or additional sections may be necessary. In all cases, please type and paginate your report!
- It comes first in your report, but you write it last.
- Gives succinct information on the aims, objectives, scope, purpose, methods and expected results and outcomes.
- Briefliterature Include background material and discuss the scope and limitations of your project.
- Results and Discussion. The body of your report. This includes the methodology Be sure to fully describe any figures, tables or diagrams you include.
- Recommendations,especially for future work and unsolved
- References(must always be included), annotated if
- Appendices,including supporting material as
Do not submit complete computer outputs. Relevant excerpts from program listings or output should be included but reduced to the size of the rest of the report and containing either as figures or tables in the text or as an appendix.
Project Overview
This project requires you to design and simulate an IoT-enabled Traffic Management System to optimize urban traffic flow, reduce congestion, and prioritize emergency vehicles. The entire project will be developed using only open-source software, ensuring accessibility for all.
You will analyse traffic patterns, implement smart traffic light control, and propose improvements using simulated IoT sensors, data analytics, and real-time monitoring techniques.
Project Goals & Expected Outcomes
By the end of this project, you will:
- Understand how IoT can be applied to smart city infrastructure (e.g., smart traffic systems).
- Develop and simulate a smart traffic management system using open-source
- Process and analyse traffic data to optimize signal timings and traffic
- Use IoT communication protocols (MQTT) for smart device
- Propose improvements for urban mobility based on their simulation
Project Breakdown & Implementation
Step 1: Research and System Design
- Research existing IoT applications in traffic management (e.g., smart traffic lights, congestion monitoring, emergency vehicle prioritization).
- Definethe problem statement : How can IoT improve traffic flow and reduce congestion?
- Designa conceptual system architecture , showing how IoT devices (sensors, actuators, communication protocols) interact in a smart city environment.
- Forclarity, the system consists of three main elements:
- SUMOsimulates traffic flow and
- IoTsensors (virtual in SUMO) detect congestion levels and send
- MQTT(Mosquitto) transmits this data to Node-
- Node-REDprocesses the data and optimizes traffic signals
- Thisensures that traffic light control is adjusted based on real-time
- Selectan open-source IoT platform for data
Deliverable:
???? Section in the Report: Introduction, Background & System Architecture.
Step 2: Software Setup and Simulation Tools
You must install and familiarize yourself with the following open-source tools (all freely available):
|
Software |
Purpose |
Download Link |
|
SUMO (Simulation of Urban Mobility) |
Traffic simulation |
https://www.eclipse.dev/sumo/ |
|
Node-RED |
Visual programming for IoT |
https://nodered.org/ |
|
Eclipse Mosquitto MQTT Broker |
IoT communication protocol |
https://mosquitto.org/ |
|
ThingsBoard |
IoT data visualization |
https://thingsboard.io/ |
|
Python + Jupyter Notebook |
Data analysis & automation |
Deliverable:
???? Section in the Report: Software Selection, Setup, and Justification.
Step 3: IoT Sensor Simulation & Traffic Data Collection
You will simulate IoT sensors (traffic cameras, vehicle counters, emergency vehicle detection) inside SUMO:
In SUMO, virtual IoT sensors can be implemented using 'induction loop detectors' at intersections to measure vehicle flow, waiting time, and congestion levels. These sensors detect passing vehicles and transmit data.
Example: In SUMO, go to 'Add Detector' ? Select 'Induction Loop' ? Place at an intersection to measure waiting times
SUMO (Simulation of Urban Mobility)
- Definea simple road network (one intersection or a small grid).
- Add simulated vehicles with varying speeds and
- Implement virtual sensors to detect traffic conditions (waiting time at intersections, congestion levels).
Eclipse Mosquitto (MQTT Communication)
- Simulatereal-time traffic data
- Sensorswill send data via MQTT messages , which will be processed in Node-RED .
Deliverable:
???? Section in the Report: Traffic Data Collection, IoT Sensor Simulation.
Step 4: Smart Traffic Light Control
You will implement an adaptive traffic light system that changes based on real-time congestion:
Node-RED (Visual Programming for IoT Control)
- Createan IoT dashboard to control traffic
- Uselogic-based rules to change traffic signal timings dynamically based on vehicle flow.
Python + Jupyter Notebook (Traffic Flow Analysis)
- ProcessSUMO traffic data to find congestion
- Apply basic optimization techniques to improve traffic
Deliverable:
???? Section in the Report: Implementation of Smart Traffic Light Control.
Step 5: Data Analysis & Optimization
- Use Python (Matplotlib, Pandas) to visualize traffic
- Compare:
o Fixed-time traffic lights vs. IoT-based adaptive control.
You must compare metrics such as vehicle waiting time, number of stops per vehicle, and congestion levels before and after implementing the IoT-based adaptive traffic control. Suggested metrics include:
Example Table for Analysis:
|
Metric |
Fixed-Time Control |
IoT-Based Adaptive Control |
Improvement (%) |
|
Average Vehicle Waiting Time |
45 sec |
25 sec |
44% |
|
Number of Stops per Vehicle |
4 stops |
2 stops |
50% |
|
Congestion Level (%) |
70% |
40% |
30% |
o Congestion levels before and after optimization.
- If time allows, propose further improvements (e.g., machine learning for predictive traffic control ).
Deliverable:
???? Section in the Report: Results & Discussion.
Step 6: Future Work & Conclusion
- Summarize
- Discuss limitations (e.g., real-world deployment challenges).
- Propose future improvements (e.g., integrating AI for traffic prediction).
Deliverable:
???? Section in the Report: Conclusion & Recommendations.
Project Deliverables
You will submit:
- A 10-15 page formal report with a main body of 1600 words (from Introduction to Conclusion), excluding the cover page, content page, references, and appendices including:
- ????Title, Abstract, Introduction, Background
- ????System Design & Architecture
- ????Simulation Implementation & Analysis
- ????Results & Future Work
- ????References
- Screenshotsof SUMO, Node-RED, and Python
- Graphsdemonstrating traffic optimization
- Final submission in PDF format on Moodle VLE as explained in section Assessment Details.
Before submitting your report, use this checklist to ensure all required elements are included:"
- Screenshotsof SUMO, Node-RED, and Python
- Aclear explanation of how MQTT is used for
- Comparisonof fixed-time and adaptive traffic control using relevant
- Adiscussion of at least one potential improvement for future smart traffic
Proposed (Indicative) Report Structure (1600 Words)
|
Section |
Approximate Word Count |
Page Allocation |
|
Title Page |
(Not included in word count) |
1 page |
|
Abstract |
150 words |
page |
|
Introduction |
250 words |
1 page |
|
Background & Literature Review |
300 words |
2 pages |
|
System Design & Architecture |
250 words |
1.5 pages |
|
Implementation & Simulation |
300 words |
2 pages |
|
Results & Discussion |
250 words |
1.5 pages |
|
Conclusion & Future Work |
100 words |
1 page |
|
References |
(Not included in word count) |
1 page |
|
Appendices (if needed) |
(Not included in word count) |
1 page |
Total: 1600 Words (~10-15 Pages)
Indicative Project Timeline (32 Work Hours)
|
Week |
Tasks |
Estimated Workload |
|
Week 1 |
Research, Literature Review, Concept Design |
4 hours |
|
Week 2 |
Install and Set Up Open-Source Software |
4 hours |
|
Week 3 |
Implement IoT Traffic Sensors in SUMO & Node-RED |
6 hours |
|
Week 4 |
Develop Traffic Light Control System |
6 hours |
|
Week 5 |
Perform Data Analysis & Optimization |
5 hours |
|
Week 6 |
Write Report (Results, Discussion, Conclusion) |
7 hours |
Total Work Hours: 32
Assessment Details:
|
Type: |
Formal Report |
|
Resources: |
Lecture material. Core and optional books as published in the Module Guide. |
|
Word Count: |
As a guide, aim for about 1,600 words (ideally 1,500 to 1,700 words. The maximum word limit is 1,700 words. This is for the main body of the word-processed report. The main body of the report includes the chapters from Introduction to Conclusion and Recommendations . Footnotes will not count towards word count totals but must only be used for referencing, not for the provision of additional text. The bibliography will not count towards the word total. Assessed work should not exceed the prescribed length. If the total word limit is exceeded, you will be penalized as described below: If you exceed the specified maximum length by less than 10% the mark will be reduced by 5%, but the penalised mark will not be reduced below the threshold pass mark (30%): marks already at or below the threshold pass mark will not be reduced. For example, if you write between 1,701 and 1,869 words, you will lose 5% so a mark of 71% would be reduced to 66%, a mark of 33% would be reduced to 30% but a mark of 29% or below would not be reduced. Similarly, if you exceed the specified maximum length by 10% (1,870 words) or more the mark will be reduced by 10%. Minimum Length: Please note there is no automatic penalty for under-length essays providing there is sufficient suitable content |
|
Presentation: |
Work must be referenced, and a bibliography provided Work must be submitted as a Word document (.doc/docx) or pdf document. Save your final copy as a word or pdf document using the following naming convention: Student ID Number_ EEE-6-ESI_Report (e.g. 1234567_EEE-6-ESI_Report ) Course work must be submitted using Arial font size 11 or Times New Roman/Calibri font size 12 (or larger if you need to), with a minimum of 1.15 line spacing Your student number must appear at the front of the |
|
coursework. Your name must not be on your coursework. |
|
|
Referencing: |
Harvard Referencing should be used, see your Library Subject Guide for guides and tips on referencing. |
|
Regulations: |
Make sure you understand the University Regulations on expected academic practice and academic misconduct. Note in particular: Your work must be your own. Markers will be attentive to both the plausibility of the sources provided as well as the consistency and approach to writing of the work. Simply put, if you conduct the research and reading yourself and write the report independently while citing your sources properly, you will ensure that your work meets academic integrity standards, leaving no reason for markers to question its authenticity. All quotations must be credited and properly referenced. Paraphrasing is still regarded as plagiarism if you fail to acknowledge the source for the ideas being expressed. TURNITIN: When you upload your work to the Moodle site it will be checked by anti-plagiarism software. Aim for a Turnitin score up to 10%. |
Ensuring Academic Integrity in Your Work
This assignment requires hands-on implementation and real simulation results, meaning it cannot be completed using AI tools alone . While AI can assist in understanding concepts or debugging code, your submission must reflect your own work and critical thinking . To ensure academic integrity:
- Include simulation screenshots from SUMO and Node-RED as proof of your implementation (already required in the submission checklist).
- Write a reflection section discussing the challenges you faced and how you solved them. This demonstrates your problem-solving approach and personal engagement with the project.
- Ensure originality in data analysis by explaining your specific simulation results rather than relying on generic IoT Your traffic data, comparisons, and optimizations should be based on your unique implementation.
- Be aware of plagiarism detection tools (e.g., Turnitin) , which will check for AI- generated content and copied material. Using AI-generated text without critical engagement or personal analysis may result in academic misconduct.
By following these guidelines, you will develop real IoT engineering skills while maintaining academic honesty in your submission.
Learning Outcomes
This assessment will fully assess the following learning outcomes for this module.
Design and Innovation:
- Select hardware and software tools to design and evaluate applications for embedded systems and IoT, including the design and build of a simple sensor network based on IoT, smart applications and the use of embedded and IoT operating systems (C5, C6).
This assignment requires you to select hardware and software tools to design and evaluate applications for embedded systems and IoT. This includes designing and building a simple sensor network based on IoT principles, implementing smart applications, and utilizing embedded and IoT operating systems. By tasking you with designing and explaining in detail how to access and monitor Smart IoT Devices, you are directly addressing the learning outcomes related to design and innovation (C5, C6).
The Engineer and Society:
- Appraiseand analyse the legal and ethical requirements to deploy IoT components with minimal impact to the environment and society and illustrate awareness of the need to design an IoT system that is secure and reliable (C7, C8, C10).
Your assignment prompts you to appraise and analyse the legal and ethical requirements associated with deploying IoT components, ensuring minimal impact to the environment and society. Additionally, it requires you to illustrate awareness of the need to design IoT systems that are secure and reliable. By emphasizing the importance of considering legal, ethical, environmental, security, and reliability factors in IoT system design, your assignment aligns well with the learning outcomes related to the engineer's role in society (C7, C8, C10).
This assignment would be assessed by a formal report.
Assessment Criteria and Weighting
LSBU marking criteria have been developed to help tutors give you clear and helpful feedback on your work. They will be applied to your work to help you understand what you have accomplished, how any mark given was arrived at, and how you can improve your work in future.
How to get help
This assignment brief provides comprehensive guidance to students, ensuring they understand the task, know how to structure their report, and are aware of the criteria for assessment.
We will discuss this Assessment Brief in class. However, if you have related questions, please contact me [name and email] as soon as possible.
Resources
Lecture material. Core and optional books as published in the Module Guide.
APPENDIX A: SOFTWARE LEARNING RESOURCES
This project requires the use of open-source software tools. Below are learning resources to help you get started with each tool.
SUMO (Simulation of Urban Mobility)
Purpose: Traffic simulation and sensor data collection. Getting Started: http://sumo.dlr.de/docs/Getting_Started.html
http://sumo.dlr.de/docs/Tutorials.html
Node- RED
???? Purpose: IoT automation and smart traffic light control.
???? Getting Started:
Eclipse Mosquitto (MQTT Broker)
???? Purpose: IoT messaging between devices.
???? Getting Started:
ThingsBoard
???? Purpose: IoT data visualization and dashboards.
???? Getting Started:
- https://thingsboard.io/docs/getting-started-guides/
- https://thingsboard.io/docs/user-guide/ui/visualization/
Python & Jupyter Notebook
???? Purpose: Data analysis and traffic trend visualization.
???? Getting Started:
|
Criteria |
Feedforward comments |
|||||||
|
100- 80% |
79- 70% |
69- 60% |
59- 50% |
49- 40% |
39- 30% |
29- 0% |
||
|
5% |
1. Research |
Extensive independent relevant |
Extensive independent relevant |
Wide range of relevant |
A range of sources |
Limited research |
Some evidence of |
Little or no |
|
Systematic identification |
research evidenced by quality and |
research evidenced by quality |
sources identified and used. |
identified and |
identified and used. |
research but |
research |
|
|
and use of academic and |
quantity used. Ability to draw on |
and quantity used. Some |
Very little guidance needed. |
used. Limited |
Some guidance |
insufficient amount. |
presented. Needs |
|
|
relevant resources |
own research and that of others. |
autonomous research. |
guidance needed. |
needed to complete |
Needs support to |
significant support |
||
|
research tasks. |
develop research |
to develop |
||||||
|
skills. |
research skills. |
|||||||
|
20% |
2. Subject Knowledge |
Shows sustained breadth, |
Shows breadth, accuracy and |
Accurate and extensive |
Accurate |
Understanding of key |
Some evidence of |
Little or no |
|
Understanding and |
accuracy and detail in |
detail in understanding key |
understanding of key aspects |
understanding of |
aspects of subject. |
superficial |
evidence of |
|
|
application of subject |
understanding key aspects of |
aspects of subject. Contributes |
of subject. Evidence of |
key aspects of |
Some evidence of |
understanding of |
understanding of |
|
|
knowledge. Contribution to |
subject. Contributes to subject |
to subject debate. Some |
coherent knowledge. |
subject. Evidence |
coherent knowledge. |
subject. |
subject. |
|
|
subject debate. |
debate. Awareness of ambiguities |
awareness of ambiguities and |
of coherent |
Inaccuracies. |
Inaccuracies. |
|||
|
and limitations of knowledge. |
limitations of knowledge. |
knowledge. |
||||||
|
25% |
3. Critical Analysis |
Very high-quality analysis |
Sustained evaluation and |
Evaluation and synthesis of |
Evaluation and |
Some attempt at |
Limited evaluation of |
Little or no |
|
Analysis and interpretation |
developed independently. |
synthesis of resources. Use of |
resources. Use of evidence- |
synthesis of |
evaluation and |
resources. Limited |
evaluation of |
|
|
of sources, literature |
Sustained evaluation and |
evidence-based arguments. |
based arguments. Identifies |
resources. Use of |
synthesis of |
use of evidence- |
resources. Very |
|
|
and/or results. Structuring |
synthesis of resources. Use of |
Thoroughly identifies trends, |
trends, inconsistency, |
evidence-based |
resources. Some |
based arguments |
little use of |
|
|
of issues/debates. |
evidence-based arguments. |
inconsistency, congruence, and |
congruence, and states the |
arguments. |
use of evidence- |
evidence-based |
||
|
Thoroughly identifies trends, |
states the implications. |
implications. |
based arguments. |
arguments. |
||||
|
inconsistency, congruence, and |
||||||||
|
states the implications. |
||||||||
|
30% |
4. Testing and Problem- |
Autonomous creation and novel |
Almost entirely autonomous |
Mainly autonomous creation |
Some autonomy to |
Exploration of |
Limited exploration of |
Little or no |
|
Solving Skills |
implementation. Adapts to |
creation and implementation. |
and implementation. Adapts |
create and |
possible solution(s). |
possible solution(s) |
exploration of |
|
|
Design, implementation, |
unforeseen practical and |
Adapts to unforeseen practical |
to unforeseen practical and |
implement. Some |
Use of established |
using established |
solution(s). |
|
|
testing and analysis of |
theoretical challenges to achieve |
and theoretical challenges to |
theoretical challenges to |
adaption made to |
approaches to |
approaches to |
Question or |
|
|
product/process/system/ |
identified goals. |
achieve identified goals. |
achieve identified goals. |
unforeseen |
resolve practical and |
resolve practical and |
problem |
|
|
idea/solution(s) to |
practical and |
theoretical problems. |
theoretical problems. |
unresolved. |
||||
|
practical or theoretical |
theoretical |
|||||||
|
questions or problems |
challenges to |
|||||||
|
achieve identified |
||||||||
|
goals. |
||||||||
|
5% |
5. Practical Competence |
Consistently applies |
Applies comprehensive practical |
Applies practical and/or |
Applies practical |
Applies a sufficient |
Applies some |
Limited application |
|
Skills to apply theory to |
comprehensive practical and/or |
and/or technical skills which |
technical skills very well and |
and/or technical |
level of practical |
aspects of the |
of some aspects of |
|
|
practice or to test theory |
technical skills which reflect the |
reflect the correct application of |
with careful application of |
skills correctly and |
and/or technical skills |
practical and/or |
the practical and/or |
|
|
correct application of theory to |
theory to context. |
theory to context. |
with some |
but with some errors. |
technical skills but |
technical skills. No |
||
|
context. |
application of |
Limited application of |
these are incomplete |
application of |
||||
|
theory to context |
theory to context. |
or contain important |
theory to context. |
|||||
|
with only minimal |
errors. Very limited |
|||||||
|
errors. |
application of theory |
|||||||
|
to context. |
||||||||
|
10% |
6. Communication and |
Communication is entirely clear, |
Communication is clear, |
Communication is clear, |
Communication is |
Communication is |
Communication is |
Communication is |
|
Presentation |
persuasive and compelling with |
persuasive and compelling with |
mostly persuasive and |
clear, with skilful |
mostly clear and |
unclear because |
very unclear |
|
|
Clear intention in |
very skilful use of the presentation |
very skilful use of the |
compelling with skilful use of |
use of the |
presentation format |
presentation format |
because |
|
|
communication. Audience |
format. Presentation addresses |
presentation format. |
the presentation format. |
presentation |
is adequate. |
is not used |
presentation |
|
|
needs are predicted and |
fully the needs of the audience. |
Presentation addresses fully the |
Presentation addresses the |
format. |
Presentation may |
adequately and/or |
format is not used |
|
|
met. Presentation format |
needs of the audience. |
needs of the audience. |
Presentation takes |
sometimes not take |
the needs of the |
adequately, and |
||
|
is used skilfully. Work is |
into account the |
into account the |
audience are not |
the needs of the |
||||
|
well structured. |
needs of the |
needs of the |
taken into account. |
audience are not |
||||
|
audience. |
audience. |
taken into account. |
||||||
|
5% |
7. Academic Integrity 1 Acknowledges and gives credit to the work of others follows the conventions and practices of the discipline including appropriate use of referencing standards for discipline. |
Consistent, error free application of relevant referencing conventions with great attention to detail. |
Consistent, error free application of relevant referencing conventions. |
Consistent application of relevant referencing conventions with few errors. |
Application of relevant referencing conventions, with some errors and / or inconsistencies. |
Generally correct application of relevant referencing conventions, with some errors and / or inconsistencies. |
Limited application of referencing conventions and / or errors. |
Very limited or no application of referencing conventions, and/or multiple errors. |
