| Assignment #1
Date of issue: 23 September |
Low-Power Testing for IP Core-Based SoC |
|---|---|
| Assignment answer presented by Team A | |
| Assignment critique presented by Team C | |
| Assignment #2
Date of issue: 7 October |
Transition Faults Testing Using 1149.1 Boundary Scan |
| Assignment answer presented by Team B | |
| Assignment critique presented by Team A | |
| Assignment #3
Date of issue: 28 October |
Approximate Scan Logic |
| Assignment answer presented by Team C | |
| Assignment critique presented by Team B |
A number of assignments are given with subjects originating in research problems with a set of typically elder references. Typically, these references will not suffice to solve the assignment, and the teams are encouraged to seek additional literature.
An appointed team of students will prepair a technical report in reply to each given assignment. The report is distributed to all participants, using inside (a.k.a. campusnet) including an appointed critique team. At a lecture, the authors present the subject, while the critique team opposes the work, i.e. the critique team is responsible for discussing the topics of the report including correcting errors in the work, the later typically in written form. It is the joint responsability of the author and the critique team to present and discuss the subject of the assignment to the audience. At the end of the lecture, the audience evaluate the effort of both teams. Each student participate in the preparation of one report as well as one assignment critique.