EEL6706
Fault-Tolerant Computer Architecture
Fall Term 2009, 3 Credits
Section #7747


OVERVIEW

Catalog Description: Prereq: EEL5764 Computer Architecture, CDA5155, or consent of instructor. Design and quantitative analysis of fault-tolerant architectures and dependable systems including fundamental issues, redundancy techniques, evaluation methods, design methodology, and applications.

Time and Place: MWF-6 (12:50-1:40pm), 330 Larsen Hall.

Course Objective: Students will gain fundamental knowledge and understanding of principles and practice in fault-tolerant computer architecture and computing, emphasizing both hardware and software challenges and the interactions between them, as well as exposure to research challenges in this field, through class lectures and discussions, reading assignments, homework, and a major research project.

Prerequisites by Topic: Topics covered in EEL5764, which include: fundamentals of computer design; performance and cost; instruction set principles, examples, and measurements; basic and advanced pipelining; superscalar and VLIW instruction-level parallelism; memory-hierarchy design; storage systems; and interconnect technology.

Required Textbook: Fault-Tolerant Systems, by Israel Koren and C. Mani Krishna, Morgan Kaufmann Pub. (2007), ISBN 978-0-12-088525-1. The authors also provide a set of small computer-based tools to support studies in FTCA. Readings from the textbook will be supplemented by readings from selected journal and conference publications.

Instructors:

Suggested Reference Texts: General Topics: Project: A major research project will be assigned in order to explore fundamental issues in fault-tolerant computer architectures, networks, services, systems, and applications. This project will span most of the semester and provide students the opportunity to more deeply explore fundamental issues in FTCA. Students will form small teams (e.g. two or three students) and propose then conduct a simulative and/or experimental research project on a topic in FTCA of their choosing (subject to professor approval). Each project will involve studies with hardware, software, information, and/or time redundancy. Testbed facilities to support these projects will be provided as needed and available via special resources in the professor's research laboratory. The culmination of each project will be a clear and concise technical report suitable for potential publication discussing project concepts, development, experiments, results, and analyses. The most important outcome of each project will be the research results that are achieved, analyses rendered, and conclusions drawn with demonstrable insight.


POLICIES

Grading Policy: Note: UF grading policy has recenty changed whereby both "+" and "-" grades are now included (i.e. A, A-, B+, B, B-, C+, C, etc.). More information on the new policy can be found here.

Deadline Policy: Much as you will often experience in your career after graduation, all assignments in this course will be given with a strict deadline, and students are required to submit their assignments on or before that deadline. In case of extenuating circumstances, students are advised to contact the professor immediately or as soon as practical.

Attendance Policy: A significant portion of the lectures in this course will be complementary but not duplicative of the textbook. Therefore, students are strongly advised to attend all lectures and take good notes. Tardiness for lectures is disruptive and thus NOT permitted.

Conduct Policy: We, the members of the University of Florida community, pledge to hold ourselves and our peers to the highest standards of honesty and integrity. All assignments are to be considered an individual effort unless otherwise specified by the instructor.

Academic Honesty: Your instructors in this course require the utmost degree of academic honesty and thus violations will be handled most seriously. All students admitted to the University of Florida have signed a statement of academic honesty committing themselves to be honest in all academic work and understanding that failure to comply with this commitment will result in disciplinary action. This statement is a reminder to uphold your obligation as a student at the University of Florida and to be honest in all work submitted and exams taken in this class and all others. If at any time questions arise regarding what is or is not appropriate, the student should ask the instructor for guidance or clarification before proceeding.

Accommodation: From the university regarding accommodations for students with disabilities: "Students requesting classroom accommodation must first register with the Dean of Students Office. The Dean of Students Office will provide documentation to the student who must then provide this documentation to the Instructor when requesting accommodation."


ASSIGNMENTS

READING ASSIGNMENTS TO DATE

ASSIGNED DESCRIPTION
08/24/09 Monday Intro: Textbook Chp. 1 [PDF], Chp. 1 Ref. #1 [PDF], Chp. 1 Ref. #17 [PDF], Supp. Ref. #1 [PDF]
08/26/09 Wednesday Textbook Chp. 2 (Sections 1-3)
09/09/09 Wednesday Textbook Chp. 2 (Sections 4-7), ByzAlg notes [PDF], Sharpe notes [PDF]
09/21/09 Monday Textbook Chp. 3 (Section 1)
10/02/09 Friday Textbook Chp. 3 (Sections 2-5), Supp. Ref. #1 [PDF]
10/19/09 Monday Textbook Chp. 4, Supp. Ref. #1 [PDF], Supp. Ref. #2 [PDF]
10/30/09 Friday Textbook Chp. 5, Supp. Ref. #1 [PDF], Class notes [PDF]
11/09/09 Monday Textbook Chp. 6, Supp. Ref. #1 [PDF], Class notes [PDF]
11/16/09 Monday Guest Lecture by Dr. Oscar Boykin, Class notes [PDF]

HOMEWORK/PROJECT ASSIGNMENTS TO DATE

NAME ASSIGNED DUE DESCRIPTION
HW #108/24/09 Monday09/04/09 FridayCarefully survey the literature then write a 4-6 page technical paper (single-spaced, 11-point font) in your own words about the history of ONE of the three (your choice) general areas of need for fault-tolerant computing: (a) critical applications (e.g. life-critical or wealth-critical systems, (b) harsh environments (e.g. space systems), or (c) highly complex systems (e.g. supercomputer with very many devices). Find and cite at least 5 scholarly references using the same citation format as used in our textbook. Based upon the material that you analyze, draw conclusions about the future.
Practice Problems #109/09/09 WednesdayN/AFirst installment, Chp. 2 Exercises: 1-2, 4-7, 9-10, 12-15. Second installment (9/21/09), Exercises 16, 18, 19, which relate to the latter half of Chapter 2.
HW #209/25/09 Friday10/02/09 FridaySee attachment [PDF]
Practice Problems #210/02/09 FridayN/AFirst installment, Chp. 3 Exercises: 1-4, 6-9. Second installment, TBD.
Class Project 10/05/09 Monday 10/21/09 Wednesday (proposal); 12/15/09 Tuesday (report) FTCA project assignment (see handout)
HW #310/28/09 Wednesday11/20/09 Friday This optional assignment consists of two parts, both for extra credit. In Part 1, each participating project team will select an important FT system (past or present), one that exemplifies significant concepts and methods in our course, and prepare/submit a technical presentation about that system, highlighting its attributes in terms of FTCA design and analysis. Teams are encouraged (but not required) to choose a system that relates to their class research project and thus leverage one activity for the benefit of the other. Each submission should be clearly cite all reference sources for all info and graphics used. The due date for Part 1 is Friday, 11/20/09. Afterwards, the best 1-3 submissions will be invited to participate in Part 2 of this assignment, a presentation to our class on Monday, December 7.
NOTE: Each homework and project assignment is due at the beginning of class on the designated date.

EXAM SCHEDULE

DAY AND TIME TYPE
10/14/09 Wednesday, in-class exam Exam #1
12/02/09 Wednesday, in-class exam Exam #2