| Competences |
| Type A | Code | Competences Specific |
| CM10 | Have knowledge of the characteristics, functions and structure of operating systems and design and implementation of applications based on their services. | |
| Type B | Code | Competences Transversal |
| B8 | Be able to work in groups and in a multilingual and multidisciplinary environment. | |
| CT4 | Treballar de forma autònoma i en equip amb responsabilitat i iniciativa | |
| Type C | Code | Competences Nuclear |
| Learning outcomes |
| Type A | Code | Learning outcomes |
| CM10 |
Understand the structure and functioning of the subsystem of input/output. Design modules that implement the diverse interfaces of an operating system, especially for the input/output subsystem. Design software for integrating a device with the operating system. Understand the characteristics and functions associated with hardware drivers and their connection with the system bus and the exterior interface. Choose, install, configure and maintain a system of peripheral devices on the basis of specific requirements in terms of characteristics, costs, maintenance and integrability. | |
| Type B | Code | Learning outcomes |
| B8 |
Participates and collaborate actively in the team tasks, carries out personal contribution within the time allotted, takes into account the contributions of others and gives constructive feedback. | |
| CT4 |
Identify the role they play in the group and understand the group’s objectives and tasks Communicate and act within the group in such a way that they facilitate cohesion and performance. Commit to the group’s tasks and agenda. Participate in the group in a good working environment and help to solve problems. | |
| Type C | Code | Learning outcomes |
| Contents |
| Topic | Sub-topic |
| Introduction | Review of basic concepts of Operating Systems Fundamentals. |
| Operating System Kernel | Functionality, structure, and interfaces. Process Management. Memory Management. Input and Output Management. File System. Security. |
| Operating System Modules | Functionality, structure, and installation. Operating System Programming Interfaces. |
| Input/Output Module | Input and output devices. System calls. Device handlers. Input and output operations. Improving operation performance. |
| System Integration | Management of external devices. Virtualization. Cloud computing concepts. |
| Planning |
| Methodologies :: Tests | ||||||||||
| Competences | (*) Class hours |
Hours outside the classroom |
(**) Total hours | |||||||
| Introductory activities |
|
2 | 0 | 2 | ||||||
| Lecture |
|
24 | 24 | 48 | ||||||
| Laboratory practicals |
|
24 | 52 | 76 | ||||||
| Personal attention |
|
2 | 0 | 2 | ||||||
| Mixed tests |
|
4 | 10 | 14 | ||||||
| Practical tests |
|
4 | 4 | 8 | ||||||
| (*) On e-learning, hours of virtual attendance of the teacher. (**) The information in the planning table is for guidance only and does not take into account the heterogeneity of the students. | ||||||||||
| Methodologies |
| Description | |
| Introductory activities | Explanation of objectives, syllabus, and assessment process. |
| Lecture | The concepts and examples from the bibliography will be followed, clarified, expanded, and summarized (depending on the need) through the use of slides and a whiteboard to explain the theoretical concepts. There will be interaction with the students to encourage them to contribute their perspectives on different engineering problems and solution implementations. |
| Laboratory practicals | The implementation of a micro-Operating System will be carried out on a mobile device. The practical exercises are done in groups of up to four people, where each person is responsible for implementing a specific part of the operating system, which will later be integrated with the other parts. |
| Personal attention | Students can personally visit the professor's office during consultation hours to raise any doubts related to the theoretical or practical explanation, problem solving, practical exercises, and discuss their learning progress and difficulties. |
| Personalized attention |
| Description |
|
Students can personally visit the professor's office during consultation hours to raise any doubts related to the theoretical or practical explanation, problem solving, practical exercises, and discuss their learning progress and difficulties. |
| Assessment |
| Methodologies | Competences | Description | Weight | ||||
| Mixed tests |
|
Resolution of theoretical exercises and problems where the student must demonstrate their competence in the analysis, planning, design, and development of engineering problems. Resolution of various theoretical questions, possibly in a multiple-choice format and specific problems, which will be conducted during the semester related to the subject matter covered up to that point, including general questions from any role in the practical part. |
60 | ||||
| Practical tests |
|
Practices will be carried out in groups of up to 4 students. The tasks of the practices will be divided into 4 roles. The members of each practice group can distribute the roles as they see fit. There will be two phases that will be evaluated in the first examination period, one halfway through the semester and the other at the end. In the second examination period, both phases will be evaluated on the same day. In addition to implementing the required functionalities of the chosen role in the operating system, each person must also present a user program that runs on the implemented operating system. The user program must be adapted to the functionalities of each phase of the operating system, meaning that two versions of this user program will need to be presented. The evaluation flow for each phase will consist of three stages, which must be sequentially passed. The first stage is the presentation of the source code for the evaluated phase (OS + user program); the practice instructor will validate that it functions with a minimum level of correctness. If successful, the student can proceed to the second stage, which will be a multiple-choice test on the concepts involved in that phase of the practice. If a grade of 4 or higher out of 10 is obtained in the test, the practice can move on to the third stage, where the instructor will inspect the presented source code and adjust the test grade based on the quality of the source code. The adjusted grade may increase or decrease the test grade, but in general, it will never be lowered below 4 out of 10, except in cases of severe errors or plagiarism. Additionally, the maximum grade that can be obtained will depend on the number of integrated parts (the maximum grades and other weights for each section will be presented in the practice statement). |
40 | ||||
| Others |
| Other comments and second exam session | |||
|
If not otherwise stated, students will not be allowed to have access to communication and data transmission devices during the exams. To calculate the average between the theoretical and practical parts of the subject, a grade equal to or higher than 5 must be obtained in the weighted average of the evaluation tests for each part (weighted average of mixed tests for the theoretical part and average of the evaluation for each phase for the practical part). Additionally, to pass the practical part, a minimum grade of 4 must be obtained in each phase. In the second examination period, the grades obtained in the first examination period for each part will be retained. Therefore, it will only be necessary to recover the sections (theory or practice) that did not meet the minimum grade. In the theory part, there will be a single exam that will cover the entire syllabus. In the practical part, only the phases with a grade lower than 4 will need to be recovered. The same weights as in the first examination period will be applied. |
|||
| Sources of information |
| Basic |
TANENBAUM, ANDREW S., SISTEMAS OPERATIVOS, 3ª ED., 2009
SILBERSCHATZ, ABRAHAM, FUNDAMENTOS DE SISTEMAS OPERATIVOS, 7ª ED, 2006 |
||||||||
| Complementary | |||||||||
Any introductory book on LINUX/SOLARIS and/or UNIX. |
|||||||||
| Recommendations |
| Subjects that continue the syllabus | ||
|
||
| Subjects that it is recommended to have taken before | |||
|
|||
(*)The teaching guide is the document in which the URV publishes the information about all its courses. It is a public document and cannot be modified. Only in exceptional cases can it be revised by the competent agent or duly revised so that it is in line with current legislation.