Teachers
Person in charge
- Josep Llosa Espuny ( josepll@ac.upc.edu )
Others
- Carlos Alvarez Martinez ( calvarez@ac.upc.edu )
- Enric Morancho Llena ( enricm@ac.upc.edu )
- Josep Ramon Herrero Zaragoza ( josepr@ac.upc.edu )
- Miquel Moretó Planas ( mmoreto@ac.upc.edu )
- Pedro José Martínez Ferrer ( pedro.martinez.ferrer@upc.edu )
- Pol Garcia Recasens ( pol.garcia.recasens@upc.edu )
- Teresa Monreal Arnal ( teresa@ac.upc.edu )
- Victor Soria Pardos ( victor.soria.pardos@upc.edu )
Weekly hours
Theory
2
Problems
1
Laboratory
1
Guided learning
0.4
Autonomous learning
5.6
Competences
Common technical competencies
- CT2.3 - To design, develop, select and evaluate computer applications, systems and services and, at the same time, ensure its reliability, security and quality in function of ethical principles and the current legislation and normative.
- CT2.4 - To demonstrate knowledge and capacity to apply the needed tools for storage, processing and access to the information system, even if they are web-based systems.
- CT3.6 - To demonstrate knowledge about the ethical dimension of the company: in general, the social and corporative responsibility and, concretely, the civil and professional responsibilities of the informatics engineer.
- CT5.2 - To know, design and use efficiently the most adequate data types and data structures to solve a problem.
- CT6.2 - To demonstrate knowledge, comprehension and capacity to evaluate the structure and architecture of computers, and the basic components that compound them.
- CT7.1 - To demonstrate knowledge about metrics of quality and be able to use them.
- CT7.2 - To evaluate hardware/software systems in function of a determined criteria of quality.
- CT7.3 - To determine the factors that affect negatively the security and reliability of a hardware/software system, and minimize its effects.
- CT8.1 - To identify current and emerging technologies and evaluate if they are applicable, to satisfy the users needs.
- CT8.4 - To elaborate the list of technical conditions for a computers installation fulfilling all the current standards and normative.
Sustainability and social commitment
- G2.2 - To apply sustainability criteria and the deontological codes of the profession in the design and evaluation of technological solutions. To identify the necessity to apply the legislation, regulations and normatives, specially the ones affecting the technical informatics engineer profession. To analyse and evaluate the environmental impact of the technical solutions in the ICT field.
Objectives
-
Students shuldbe able to translate routines and high-level code fragments to assembly of a real machine (IA32) and link routines in assembler with a high-level language (C) using the Linux Application Binary Interface
Related competences: CT5.2, -
Students should be able to describe the internal structure and operation of the main components of the memory hierarchy and the techniques to improve their performance.
Related competences: CT8.1, CT7.2, CT6.2, -
Students should be able to describe the operation and to use the main mechanisms for error detection and correction.
Related competences: CT7.3, CT2.3, -
Students should be able to describe the structure and operation of data storage systems and evaluate their reliability.
Related competences: CT8.1, CT7.2, CT7.3, CT6.2, CT2.4, -
Students should be able to describe the taxonomy of instruction sets ​​(ISA) and the characteristics of the different paradigms (such as RISC-CISC).
Related competences: CT7.2, CT6.2, -
Students should be able to describe the techniques used in computer design based on parallelism (such as pipelining, superscalar processors, VLIW processors, vector SIMD extensions, multithreading processors, multiprocessors and multicomputers) and their principles of operation.
Related competences: CT7.2, CT6.2, CT2.3, -
Students should be able to evaluate the performance of code fragments and/or applications (both in assembler and high level) taking into account components such as: memory hierarchy, storage systems, instruction set architecture (ISA) and the main processor design techniques based on parallelism.
Related competences: CT7.1, CT7.2, CT6.2, CT5.2, CT2.3, -
Students should be able to assess the impact on power and energy consumption of code fragments and/or applications (in both assembler and high level) taking into account components such as: memory hierarchy, storage systems, the design of the instruction set architecture (ISA) and the main processor design techniques based on parallelism.
Related competences: G2.2, CT7.1, CT7.2, CT6.2, CT8.4, CT3.6, -
Students should be able to apply simple optimizations to code fragments to improve their performance and/or power consumption taking into account: the memory hierarchy, storage systems, the design of the instruction set architecture (ISA) and the main processor design techniques based on parallelism.
Related competences: CT7.1, CT5.2,
Contents
-
Fundamentals of computer design and evaluation
-
High-level / assembler language interface
-
Memory Hierarchy
-
Storage Systems
-
Instruction Set Architecture Design
-
Pipelining and parallelism in computer design
Activities
Activity Evaluation act
Theory
2h
Problems
1h
Laboratory
1h
Guided learning
0h
Autonomous learning
4h
Documental "The E-Waste Tragedy" + debat
Theory
0h
Problems
0h
Laboratory
0h
Guided learning
2h
Autonomous learning
1h
Teaching methodology
Theory lectures interleaved with small problems. In the theory classes homework will be assigned to students for the next practice class.Problem-solving classes are based on group activities. Using problems solved individually at home, students will work together in small groups to resolve the doubts that may have emerged. Because the methodology used in practice classes it is recommended that students do not enroll to courses that overlap with this one.
The laboratory classes support the theory. Students have the documentation available before each practice session. It is mandatory that students prepare the session beforehand (read the documentation, study the concepts used, etc.). It is also recommended, once the session ends, to review the concepts seen. Students have to prepare a preliminary work that will be delivered at the beginning of each session. The lab sessions are performed on-site and used to produce the lab grade, so it is essential that there is no overlap of the laboratory with any other course.
Evaluation methodology
The course grade is based on the two tests (C1 and C2), the laboratory grade (LAB) and the practice class activity (AP).The final grade (NF) is calculated (with a single decimal and rounded to nearest even) as:
NF = 0,3*C1 + 0,4*C2 + 0,2* LAB + 0,1* AP
Students can only be evaluated of LAB and AP if they ATTEND THE GROUP where THEY ARE ENROLLED.
Bibliography
Basic
-
Computer architecture: a quantitative approach
- Hennessy, John L.; Patterson, D,
Elsevier, Morgan Kaufmann,
2019.
ISBN: 9780128119051
https://discovery.upc.edu/discovery/fulldisplay?docid=alma991004117509706711&context=L&vid=34CSUC_UPC:VU1&lang=ca
Complementary
-
Computer systems: a programmer's perspective
- Bryant, R.E.; O'Hallaron, D.R,
Pearson,
2016.
ISBN: 9781292101767
https://discovery.upc.edu/discovery/fulldisplay?docid=alma991004062589706711&context=L&vid=34CSUC_UPC:VU1&lang=ca -
Computer organization and design: the hardware/software interface
- Patterson, D.A.; Hennessy, J. L,
Elsevier Morgan Kaufmann,
2014.
ISBN: 9780124077263
https://discovery.upc.edu/discovery/fulldisplay?docid=alma991004000499706711&context=L&vid=34CSUC_UPC:VU1&lang=ca