Name: Prof. Azer Bestavros Email: firstname.lastname@example.org Office: MCS-175, 111 Cummington Mall (ext: 3-9726) Hours: Tue 05:00pm-06:30pm Wed 09:30am-11:00am or by appointment
Name: Prof. Renato Mancuso Email: email@example.com Office: MCS-201A, 111 Cummington Mall (ext: 8-8537) Hours: Wed 01:00pm-02:00pm Wed 05:40pm-06:40pm or by appointment
Name: Showan Esmail Asyabi Email: firstname.lastname@example.org Office: Undergrad Lab Room 302 at 730 Commonwealth Ave Hours: Mon 12:00-02:00pm Fri 12:00-02:00pm or by appointment
Name: Wil Koch Email: email@example.com Office: Undergrad Lab Room 302 at 730 Commonwealth Ave Hours: Thu 12:00-03:00pm or by appointment
Room: KCB-101 Where: http://www.bu.edu/classrooms/classroom/kcb-101/ When: Tue/Thu 3:30pm-4:45pm
A2: Wed 1:25pm-2:15pm(in MCS-B19) A3: Wed 2:30pm-3:20pm(in MCS-B19) A4: Wed 3:35pm-4:25pm(in MCS-B19) A5: Wed 4:40pm-5:30pm(in MCS-B19) A6: Wed 5:45pm-6:35pm(in MCS-B19)
Drop Date: Last day to drop class without a W grade is Tue 2/26 W Date: Last day to drop class with a W grade is Fri 4/05 Midterms: In-class exam dates are Thu 3/7 and Thu 4/25 Final: End-of-semester exam date is Thu 5/09
Portal: http://www.cs.bu.edu/~best/courses/cs350/S19 Piazza: http://piazza.com/bu/spring2019/cs350 Hangouts: https://meet.google.com/kqo-sezd-kzb Blackboard: http://learn.bu.edu/ Gradescope: http://www.gradescope.com/courses/37949 Facebook: http://www.facebook.com/groups/bucs350
Schedule of Lectures and Assignments
Changes to the schedule will be announced in class if need be
This course is a required sophomore/junior-level Computer Science course. It covers the fundamental concepts underlying the design and implementation of computing systems.
The philosophy underlying the design of this course is that students should be familiarized with problems that reoccur in software systems, and should be acquainted with the set of classical algorithms/techniques for solving such problems. In particular, it is important to develop the ability to recognize standard problems in different wordings and within unusual context, and match them with appropriate solutions.
Rigorous treatment of invariant concepts, algorithms, and performance evaluation methods underlying computing systems design. Topics include modeling and analysis of concurrent processing, computational resource scheduling and consumption, and performance evaluation techniques.
Recommended Follow-up Courses:
The following courses build on knowledge assimilated in CS-350. They are natural follow-up courses in decreasing order of relevance (more or less).
CS-451: Distributed Systems and Cloud Computing
Function in the Curriculum:
As a core undergraduate course, CS-350 does not focus on particular implementations or specific technologies. On the contrary, it stresses the fundamental concepts and basic algorithms that have survived (and are likely to survive) the evolution of computer software systems in general, and operating systems in particular.
This course is significantly different in purpose and coverage from CS-210 (Computer Systems) and CS-410 (Software Systems). CS-210 and CS-410 introduce computer systems to sophomores using a hands-on approach by examining the "mechanics" and/or the "plumbing" of modern (or typical) computer operation through exposure to various interfaces between architecture, compilers, loaders, linkers, and run-time systems. CS-350 does not focus on a particular interface or a particular technology, rather it deals with fundamental notions and algorithms that are common to computing systems in general and to software systems in particular.
This course is required or strongly recommended for the following advanced courses: CS-552 (Advanced Operating Systems), CS-550 (Advanced Computer Architecture), CS-551 (Parallel Computing Architectures and Models), CS-455/655 (Data Communications), CS-460/660 (Databases), and CS-470/670 (Performance Analysis). In that respect, this course covers basic notions that we expect students (graduates and undergraduates alike) enrolling into these classes to have mastered. For example, it is inconceivable that a student who is interested in taking a database or an operating systems class, not to have been exposed to the notion of concurrent processing and mutual exclusion. Similarly, it is unconceivable for a student enrolled in a networking, database, or operating systems class, not to have been exposed to performance analysis using simple queuing systems, for example.
The topics covered in this class could be grouped under 4 general themes:
The first half of the semester will be devoted to the coverage of the first two of the above themes, whereas the second half of the semester will be devoted to the coverage of the other two themes.
Class Meetings and Communication Forums
Attending lectures is
mandatory and will account for up to 5% of the final class grade. To take attendance,
frequent one-question quizzes (at some point during a randomly selected set of
lectures) will be given.
You are responsible for ALL the materials covered in the lectures including any topics not in the notes or references.
Class participation and questions are very welcome during the lectures. There is no such thing as a "stupid question". Failure to ask a simple question might result in the inability to follow the rest of the lecture (and even following lectures).
Up to 10 minutes at the beginning of every class may be devoted to answering questions related to topics discussed in previous lectures. This is a particularly good time to ask if you have questions.
If you are taking this class then you have signed up for a weekly 50-minute discussion session. Please check the course web page for the coordinates of your teaching fellow and of the place/time of the discussion sections.
The teaching fellow(s) will be leading the discussion sessions. Materials covered in the discussion sessions will be elaborations on materials covered in the lectures. In some of the discussion sections (especially at the beginning of the course), the teaching fellow(s) will be covering background/prerequisite materials that many students typically do not master. Also, the discussion sessions will be the venue used to answer any questions (or provide clarifications) regarding the homework assignments.
If (for some reason) you miss (or cannot make) the discussion section for which you are signed up, then please make sure to attend another one in the same week.
You should come to the Instructor and/or Teaching Fellow(s) office hours with your questions well-thought out. Office hours are NOT meant to be tutoring sessions; they are meant to answer specific questions about the material covered in the lecture, discussion section, and lecture notes.
Questions like "could you repeat your explanation of ..." or "I do not understand section ... of the lecture notes" should be asked in the lecture and/or discussion sections.
On-line Forums and Facebook Group Usage:
The class communication forums (e.g., Piazza, Blackboard, and Facebook) are for you to use as channels for asking questions and seeking clarifications, whether from the instructor, teaching fellow, or classmates. However, like any broadcast medium, you should be careful not to abuse these channels. This means that "one-liners" and "cute" commentaries should be avoided.
You will be held responsible for any inappropriate postings on these forums.
In an effort to make things a bit more dynamic during lectures and sections,
the instructor and the teaching fellow may occasionally award "Bonus"
credit points for student participation. Also, as a further
motivation to read the notes thoroughly, bonus points will be
awarded to students who discover technical "bugs" in the lecture
notes, or who provide significant contributions. Such bonus points will count as extra credit points for the
homework that is due next and will be capped at 10 points per homework. Any points above the maximum
grade for the homework will not count (i.e. if your grade in a homework is
100/100 and you get 10 extra points, your grade for the homework will continue
to be 100/100).
Azer Bestavros & Renato Mancuso, Lecture Notes on Fundamentals of Computing Systems.
These notes are a book that has been perpetually "in-progress", and
hence they are
Note: These Lecture Notes will be made available from the class home page and Piazza. They are all in PDF format, so you will need access to an Acrobat Reader.
Homework assignments constitute an important part of this course. They are designed to help you understand the materials covered in lectures and in assigned readings. It is only by doing the homework that you really learn the material.
Nature, Frequency, and Grading:
There will be 8 homework assignments handed out throughout the semester (subject to change). Each assignment will consist of a set of (typically 3) "pencil and paper" problems as well as a one "coding" problem. Each homework assignment will be worth 100 points.
Homework Assignments will be worth 30% of the final grade. In calculating the overall homework grade, the assignment with the lowest grade will be dropped.
As detailed above, some of the problems in the homework assignments will require programming using Java.
Homework assignments may be fairly long, each taking an average of 4 hours to complete (assuming that you are caught up with readings and are fluent in programming), although the time required will vary quite a bit from student to student and assignment to assignment. Always allow more time than you think you will need!
Electronic Submission Process:
Homework assignments will be posted on-line at the end of the week (typically on Fridays). As a tree-friendly practice, no hardcopies will be distributed or made available, and all solutions will be handed in electronically (on-line).
For the non-coding "pencil and paper" components of the assignments, solutions will be managed using Gradescope (http://www.gradescope.com). For the coding component of the assignments, solutions will be handled using gsubmit (www.cs.bu.edu/teaching/hw/gsubmit/) which allows for auto-grading.
If applicable, please follow special instructions regarding submission and documentation of your work (especially code). Typically, homework assignments will span at least two weekends.
If your homework solutions (or parts thereof) are handwritten, you will need to scan your write-up and upload that electronically. Scanning capabilities are available at various university libraries and also through the main CS office on the first floor of MCS (during normal business hours, office staff can help you email a scanned copy of your work to yourself). Please take this into consideration so that you don't get stuck having to do this at the last minute.
Grades for assignments will be returned (also on-line) in a timely fashion. It is the student's responsibility to make sure that the grade they received for each homework is properly recorded by the instructor and/or teaching fellow. This can be done by periodically checking your grades on-line through the Gradescope and Blackboard portals.
For full credit, your homework must be submitted electronically by the deadline. There will be a hefty penalty of 25% for a homework submitted one class late. You may submit part of the homework by the deadline to avoid the penalty on that part. No homework will be accepted if late by more than one class. There will be no exceptions to this policy, except for certified medical excuses. In such cases, extensions will be granted only if (and until) the homework solutions are posted (hopefully, about 1 week after the original due date).
Exams and Quizzes
Attendance Quizzes and Piazza Polls:
Throughout the semester, I will be posting simple polls on Piazza to serve as attendance/participation quizzes. As such, some of these polls will be assigned and must be answered during the class (please make sure you bring your smart phone or personal computer along), whereas others will be assigned online and must be answered within 48 hours. Each poll will consist of a single (easy) question mostly to check your understanding of material covered in lecture. You are allowed to miss one attendance quiz without being penalized.
Attendance quizzes and on-line polls will go towards the 10% of the final grade for class participation.
Interim (Midterm) Exams:
There will be two in-class exams. These exams (combined) will be worth 30% of the final grade, and will cover the material presented from the beginning of the semester (or from the previous in-class exam) and up to the last lecture before the exam. Please check the class schedule for the specific dates of these exams.
The course final exam is worth 30% of the final grade, and will cover the material offered throughout the semester. Please check the class schedule for date and time. The place for the final exam is typically the same as that of the lecture (and will be announced in due time, if different).
Policy on Missed Exams:
Please mark the exam dates on your calendar (and remember them when
you make your recess and end-of-semester travel plans!) There will be
absolutely no make-up exams, except for medical emergencies. For medical
emergencies, you must provide a letter from a doctor, specifying the period of
time during which you were unable to attend an exam.
The final class grade will be broken down as follows:
Grading (except for the final exam) is done by a number of class graders, under the direct supervision of the Teaching Fellow(s). If you have an issue with a grade (homework or exam), please contact the Teaching Fellow(s). If your issue is not resolved, then (and only then) please contact the instructors. In doing so, please note that (to ensure fairness and grading consistency) it is seldom the case that Teaching Fellow(s) decisions are overruled.
This class is not graded on a curve, i.e., there is no prescribed proportions for specific grades. This means that if everybody's performance in the class deserves an A, then everybody will get an A. The converse is also true! Therefore, don't be satisfied with an "average" grade because that average could well be less than what you expect. Being a "gateway" to all other (more advanced) CS "systems" classes, you should expect this class to be competitive. Thus, make sure you work hard from the very beginning.
In previous years, the average grade for this class was around B/B-. The minimum grade for this course to count towards the CS concentration is C.
An instructor is not allowed to give W (withdrawal) grades. One can get such a grade only by dropping this class by the deadline specified by the registrar office for withdrawals with or without a W grade (check the registrar's office calendar for the exact date). Also, an instructor is not allowed to give an I (incomplete) grade except if a student misses completing assignments and/or misses taking tests due to circumstances beyond their control.
Academic Code of Conduct
In addition to the normal and well-understood strictures against cheating on exams, altering transcripts, and etc., there are other varieties of academic misconduct described in the BU Academic Conduct Code and which you must be aware of when working on assignments.
The most relevant section of the Academic Code of Conduct for the assignments in this class relates to Plagiarism.
Plagiarism. Any attempt by a student to represent the work of another as his or her own. This includes:
Policy on Collaboration:
There is nothing wrong in principle about discussing the topics covered in the course with your friends and colleagues. However, there are severe consequences to plagiarism. In particular, when you submit a homework with your name on it, you are claiming that the work contained therein is your own; it is Plagiarism to submit work under your own name in which:
The above is nothing less than plagiarism and will be punished accordingly.
If you are in a situation whereby you have collaborated with a student on a homework problem, or obtained homework solutions (or parts thereof) from some other source, then you should clearly and unambiguously disclose this in your write-up. Failure to do so constitutes plagiarism.
If you are caught cheating in a test or plagiarizing a homework, you will automatically receive an F and the matter will be reported to CAS Academic Conduct Committee, who recommends sanctions to the Dean of the College.
Handing in your own assignment a day or two late will affect your grade far less than turning in a copy of someone else's work on time!
is William Fairfield Warren Distinguished Professor in the CS Department at Boston University, which he joined in 1991 and
chaired from 2000 to 2007. He is the Founding Director of the BU Hariri
Institute for Computing, set up in 2011 to support "a community of
scholars who believe in the transformative potential of computational
perspectives in research and education." He pursues research in networking,
distributed computing, and high-assurance systems. His currently active
projects seek to develop multi-party computation platforms for
privacy-preserving data analysis at scale, cloud-based open platform for
smart-city applications, and game-theoretic mechanisms for cloud
Mancuso is an Assistant Professor in the CS
Department at Boston University, which he joined
after completing his Ph.D. from the University of Illinois at
Urbana-Champaign in 2017. His research focuses on real-time and embedded
systems, with a particular focus on OS-level multi-core resource
management for high-performance, safety-critical avionics
and automotive systems. He is also interested in applications and
methodologies for design, deployment and analysis of cyber-physical
systems, real-time cloud computing, embedded systems security, and
systems technologies for UAVs.
Esmail Asyabi is a PhD student in the CS Department at Boston
University, advised by Professor Bestavros. His research currently
focuses on designing and building system software to enhance utilization
and/or mitigate energy consumption of cloud data centers. He is mainly
interested in distributed systems, operating systems, and cloud
Wil Koch is a PhD student in the CS Department at Boston University advised by Professor Bestavros. His research focuses on improving multi-rotor drone flight performance. Also, he has conducted research in cyber-security, focusing on developing defenses for automated attacks. Before returning to academia, he was involved in a few start-ups and worked as a software engineer in the aerospace industry.