Degree | Type | Year |
---|---|---|
Data Engineering | OT | 4 |
You can view this information at the end of this document.
For a full understanding of the contents of the subject it is necessary to have basic skills in programming and a good knowledge of how programs run on computers. To do this, you must have passed Advanced Programming, as well as Physical Basics for Data Acquisition to understand the principles of digitization of information. It is advisable to have completed Data Structures and Parallel Programming.
Embedded systems are responsible for very specific sets of functions that usually act as a high-level interface between applications and the physical world. Therefore, they deal with the treatment of data captured by sensors, some of their processing (edge computing), the transmission of processed data to the applications, and with the control of motors and actuators of all kinds, too. Currently, there are systems embedded in almost any "thing" and, if things are complex, they can carry many such as those that may be in a car.
Because embedded systems are closely related to the physical environment around them, the algorithms they implement must meet many requirements, often very stringent and contradictory to each other. For example, having a high performance and consuming little energy.
Thus, for the development of embedded systems it is necessary to design robust algorithms that can be verified to operate in critical environments and have a development and execution cost within the margins delimited by the requirements of the application.
The aim of this course is for students to achieve the following objectives:
Title | Hours | ECTS | Learning Outcomes |
---|---|---|---|
Type: Directed | |||
Problem-solving: Problem solution proposals and discussion | 12 | 0.48 | 2, 3, 5, 4 |
Project: Course project development | 12 | 0.48 | 2, 3, 5, 4 |
Theory: Attendance and participation in theory classes | 24 | 0.96 | 1, 2, 5, 4 |
Type: Supervised | |||
Project: Course project follow-up reporting | 6 | 0.24 | 2, 3, 5, 4 |
Tutoring: Additional problem-solving activities | 6 | 0.24 | 1, 2, 3, 4 |
Type: Autonomous | |||
Assignment: Project development and report writing | 12 | 0.48 | 1, 2, 3, 5, 4 |
Problem-solving: Reporting solutions to proposed problems | 24 | 0.96 | 1, 2, 3, 5, 4 |
Theory: Study | 26 | 1.04 | 2, 4 |
Teaching is structured in the following face-to-face activities:
Theory classes: Presentations of course contents, with a first part that is devoted to the dissemination of the necessary knowledge for the analysis and the design of cyber-physical systems, and to explain cases that situate in context the knowledge and the abilities that are acquired during the course. The second part will be devoted to the discussion of problems that will be dealt with in the corresponding seminars.
Problem-solving seminars: Discussion of small case studies (for example, control of a microwave oven) that serve to consolidate theoretical knowledge regarding the analysis and design of cyber-physical systems.
Laboratory practices: Team work at the laboratory, following a walk-through guide under the supervision of a teacher. Each session will deal with a specific aspect regarding the implementation of cyber-physical systems.
As in all areas of Engineering, the development of embedded systems involves making decisions based on often contradictory criteria. In the case studies, care will be taken to include ethical, social and environmental criteria. Similarly, the ability to adjust them to adapt to incidents in the development process and changes in specifications will be encouraged.
Annotation: Within the schedule set by the centre or degree programme, 15 minutes of one class will be reserved for students to evaluate their lecturers and their courses or modules through questionnaires.
Title | Weighting | Hours | ECTS | Learning Outcomes |
---|---|---|---|---|
Continuous assessment assignments | 25% | 10 | 0.4 | 1, 2, 4 |
Final exam | 25% | 2 | 0.08 | 1, 2, 4 |
Laboratory | 25% | 12 | 0.48 | 2, 3, 5 |
Make-up exam | 50% | 2 | 0.08 | 1, 2, 4 |
Midterm exam | 25% | 2 | 0.08 | 2, 3, 4 |
a) Procedure and assessment activities’ plan
The assessment is continuous with specific activities (exams and assignments) throughout the course. These assessment activities generate a series of grades that determine the final grade.
The calculation of the final grade n follows the following expression:
n = x·50% + p·25% + c·25%
where x is the grade for the exams; p, that for the laboratory project, and c, that for the continuous assessment.
If x < 5 or p < 5, the final grade n is, at most, a 4.5. In other words, the average of the exams and the project must be passed separately.
Exam grade x is the average of the midterm exam and the final exam.
Project grade p is obtained from the weighted average of the grades corresponding to each lab session. Six are planned. In case of non-attendance, the absent person will receive a 0 as the grade for the corresponding session.
Continuous assessment grade c is obtained from a weighted average of the problem-solving assignments completed throughout the course. There is no minimum and, therefore, the course can be passed with c = 0 as long as x·50% + p·25% ≥ 5.
b) Assessment activities schedule
The dates of all face-to-face activities, including assessment activities, and submission deadlines will be published on the virtual campus (CV) and may be subject to possible changes in programming for reasons of adaptation to possible incidents: they will always be previously informed through the CV since it is the usual mechanism for exchanging information between teachers and students outside the classroom.
c) Re-assessment procedure
In accordance with the coordination of the Degree and the deanship of the School of Engineering, the following activities are not recoverable:
- Project, 25% of the final grade
- Continuous assessment, 25% of the final grade
The average grade of the exams can be recovered with a specific make-up exam.
d) Assessment review procedure
Assessment activities can be reviewed any time after corresponding grades are published and before the deadline for the revision of the final exam.
Should the change of a grade be agreed upon, that grade may not be modified in a later review.
No reviews will be done after the closure of the reviews of the final exam, but for the make-up exam.
e) Grading
A “non-assessable” grade is assigned to students that have not participated in any assessment activity. In any other case, not participating in an assessment activity scores 0 in the weighted average computation.
Honors will be awarded to those who obtain grades greater than or equal to 9.0 in each part, up to 5% of those enrolled in descending order of final grades. They may also be granted in other cases if they do not exceed 5% and the final grade is equal to or greater than 9.0.
f) Irregularities, copies and plagiarism
Copies are evidence that the work or the examination has been done in part or in full without the author's intellectual contribution. This definition also includes attempts to copy in exams and reports, and violations of the norms that ensure intellectual authorship. Plagiarisms refer to the works and texts of other authors that are passed on as their own. They are a crime against intellectual property. To avoid plagiarism, quote the sources you use when writing the corresponding work reports or examinations.
In accordance with the UAB regulations, copies or plagiarisms or any attempt to alter the assessment result, for oneself or for others, like e.g. letting other copy, imply a final grade for the corresponding part (exam, continuous assessment or project) of 0 in the computation of the final score and failing the course. This does not limit the right to act against perpetrators, both in the academic field and in the criminal.
The use of Artificial Intelligence (AI) technologies as an integral part of the development of the work is permitted, but not recommended, provided that the result reflects a significant contribution by the student in the analysis and personal reflection. The student must clearly identify which parts have been generated with this technology, specify the tools used and include a critical reflection on how they have influenced the process and the result of the activity. The lack of transparency in the use of AI is considered a lack of academic honesty and entails a penalty in the grade of the activity, or greater sanctions in serious cases.
g) Assessment of repeaters
There is no differentiated treatment for repeaters, but they can take advantage of their own material from the previous year provided it is informed in the corresponding reports.
h) Single assessment
This course does not have a single assessment procedure.
Ll. Ribas Xirgo. (2014). How to code finite state machines (FSMs) in C. A systematic approach. TR01.102791 Embedded Systems. Universitat Autònoma de Barcelona. [https://www.researchgate.net/publication/273636602_How_to_code_finite_state_machines_FSMs_in_C_A_systematic_approach]
Explains a method to program state machines in C which resembles the one presented in the course.
Ll. Ribas Xirgo. (2011). “Estructura bàsica d’un computador”, Capítol 5 de Montse Peiron Guàrdia, Lluís Ribas i Xirgo, Fermín Sánchez Carracedo i A. Josep Velasco González: Fonaments de computadors. Material docent de la UOC. OpenCourseWare de la UOC. [http://openaccess.uoc.edu/webapps/o2/handle/10609/12901]
It describes the state-based machine model, the algorithmic machines, and the digital systems’ basic architectures that are used in the course from a different perspective, though.
Edward A. Lee and Sanjit A. Seshia. (2017) Introduction to Embedded Systems, A Cyber-Physical Systems Approach, Second Edition, MIT Press.
A full course on embedded systems with much more theoretical background. (See also: https://ptolemy.berkeley.edu/)
M. J. Pont. (2005). Embedded C. Pearson Education Ltd.: Essex, England.
It shows how embedded systems are programmed, topic also treated in the course problem-solving part and laboratory. Therefore, it’s an interesting complementary material.
Brian Bailey, Grant Martin and Andrew Piziali. (2007). ESL Design and Verification. A Prescription for Electronic System-Level Methodology. Elsevier.
It gives an overview of the embedded systems’ synthesis process and situates the course material, thus it’s a good complement.
Tim Wilmshurst. (2010). Designing Embedded Systems with PIC Microcontrollers. Principles and Applications (Second Edition). Elsevier.
Complementary information to that of the course on an embedded system for controlling a robot.
Oliver H. Bailey. (2005). Embedded Systems Desktop Integration. Wordware Publishing.
Complementary information about the hardware-software communication aspect of embedded systems.
CoppeliaSim, EDU Version, Coppelia Robotics [https://www.coppeliarobotics.com/]
ZeroBrane Studio, ZeroBrane [https://studio.zerobrane.com/]
Draw.io, diagrams.net [https://app.diagrams.net/]
Please note that this information is provisional until 30 November 2025. You can check it through this link. To consult the language you will need to enter the CODE of the subject.
Name | Group | Language | Semester | Turn |
---|---|---|---|---|
(PAUL) Classroom practices | 1 | Catalan/Spanish | second semester | afternoon |
(PLAB) Practical laboratories | 1 | Catalan/Spanish | second semester | afternoon |
(TE) Theory | 1 | Catalan | second semester | afternoon |