| Unit name | Embedded Computing Systems |
|---|---|
| Unit code | EEME30001 |
| Credit points | 20 |
| Level of study | H/6 |
| Teaching block(s) |
Teaching Block 1 (weeks 1 - 12) |
| Unit director | Professor. Dahnoun |
| Open unit status | Not open |
| Units you must take before you take this one (pre-requisite units) |
None |
| Units you must take alongside this one (co-requisite units) |
None |
| Units you may not take alongside this one |
None |
| School/department | School of Electrical, Electronic and Mechanical Engineering |
| Faculty | Faculty of Engineering |
Why is this unit important?
This course familiarizes students with the principles of designing and assessing computational systems that engage with real-world physical processes. These systems find applications in a wide array of domains, such as medical devices, consumer electronics, recreational products, healthcare support, traffic management, automotive technology, industrial process control, energy efficiency, environmental regulation, aircraft management, communication networks, instrumentation, the oversight of essential infrastructure (like electricity, water resources, and communication systems), robotics, including distributed robotic applications like telepresence and telemedicine, manufacturing, and intelligent structural systems.
How does this unit fit into your programme of study
In this unit, students will delve into the integration of hardware and software using industry-standard tools to develop embedded computing systems. The curriculum will explore the technical nuances of hardware-software co-design trade-offs, offering a comprehensive understanding through extensive design examples. Additionally, broader engineering considerations will be emphasized throughout the learning process.
An overview of content
The unit provides an introduction to the theory and practical implementation of using embedded computers as the central control and organizational hub for both electronic and mechanical systems, with a specific focus on time-sensitive systems. The content will mainly cover embedded system architecture and programming model; embedded software development; hardware interfacing; communication protocols; real-time systems; and embedded system integration and testing.
How will students, personally, be different as a result of the unit
At the end of this unit the students will be able to model, design, and implement embedded computing systems for real-word applications.
Learning Outcomes
The unit will have a blended learning approach incorporating a combination of synchronous and asynchronous lectures, seminars, and practical classes, as well as several self-directed exercises. Several series of short lectures with related design problems (in some cases requiring practical realisation) will be used to integrate the various aspects of core knowledge being taught as well as practice in the relevant design and build processes
Tasks which help you learn and prepare you for summative tasks (formative):
The formative tasks will include regular quizzes and laboratory-based design exercises.
Tasks which count towards your unit mark (summative):
The unit will be assessed by a single coursework assessment carrying a 100% weight. For this assessment, each student will make an individual submission comprising embedded systems firmware source code and accompanying documentation. The coursework will assess all ILOs.
When assessment does not go to plan
Re-assessment takes the same form as the original summative assessment.
If this unit has a Resource List, you will normally find a link to it in the Blackboard area for the unit. Sometimes there will be a separate link for each weekly topic.
If you are unable to access a list through Blackboard, you can also find it via the Resource Lists homepage. Search for the list by the unit name or code (e.g. EEME30001).
How much time the unit requires
Each credit equates to 10 hours of total student input. For example a 20 credit unit will take you 200 hours
of study to complete. Your total learning time is made up of contact time, directed learning tasks,
independent learning and assessment activity.
See the University Workload statement relating to this unit for more information.
Assessment
The assessment methods listed in this unit specification are designed to enable students to demonstrate the named learning outcomes (LOs). Where a disability prevents a student from undertaking a specific method of assessment, schools will make reasonable adjustments to support a student to demonstrate the LO by an alternative method or with additional resources.
The Board of Examiners will consider all cases where students have failed or not completed the assessments required for credit.
The Board considers each student's outcomes across all the units which contribute to each year's programme of study. For appropriate assessments, if you have self-certificated your absence, you will normally be required to complete it the next time it runs (for assessments at the end of TB1 and TB2 this is usually in the next re-assessment period).
The Board of Examiners will take into account any exceptional circumstances and operates
within the Regulations and Code of Practice for Taught Programmes.
