DOC PREVIEW
UB CSE 486 - Introduction to Distributed Systems

This preview shows page 1 out of 4 pages.

Save
View full document
View full document
Premium Document
Do you want full access? Go Premium and unlock all 4 pages.
Access to all documents
Download any document
Ad free experience
Premium Document
Do you want full access? Go Premium and unlock all 4 pages.
Access to all documents
Download any document
Ad free experience

Unformatted text preview:

1CSE 4/586 Introduction to Distributed Systems Spring 2008 Course Description A distributed system is one in which components located at networked computers and devices communicate and coordinate their actions by message passing for sharing resources and for distributing computational workload. This course will address some of the fundamental challenges in the design, implementation and deployment of large scale distributed systems including connection establishment, event handling, inter-process communication, storage management, static and dynamic component configuration, concurrency and synchronization. It will also cover issues related to distributed objects such as mobility, scalability, security, naming and location. Reliability is a core issue that will be covered across all the topics discussed in the course. Possible solutions will be analyzed at various levels of granularity using objects, processes, services, components and frameworks. This course will focus on practical solutions over theoretical formalisms and server-side and middle-ware technology over client-side. Special attention will be given the emerging technology of Service-Oriented Architectures (SOA), Web Services and open standards-based system software development. Concepts studied will be applied to solve problems in various domains such as wireless world, embedded systems, electronic marketplace and application servers. Students will work on middleware-based projects in orchestrated groups of two. There will be a mid-semester assessment and a final exam. On completion of this course, a student will be able to design and implement a reliable distributed system, and will be able to analyze a distributed system for its architecture, algorithms, protocols and services. Students will have good understanding and working knowledge of reliable distributed systems. Course Information Website: http://www.cse.buffalo.edu/~bina/cse486/spring2008 Instructor: Bina Ramamurthy ([email protected]) Lecture Time: MWF: 9.00-9.50AM Lecture Location: NSC 210 Office: 127 Bell Hall Office Hours: WF: 10.00-11.30AM Recitation R1: M 10.00 – 10.50 AM, Clemens 119 Recitation R2: W 3.00 – 3.50 PM, Park 250 Textbook and other material Text book: Distributed Systems: Concepts and Design, by G. Coulouris, J. Dollimore and T. Kingberg, Fourth Edition, Addison-Wesley, 2005. Besides the main textbook we will use a number of other material print and Internet publications, the references for which will be given to you at appropriate time during the semester. J.A. Stankovic, "Distributed Computing," in Readings in Distributed Computing Systems,T.L. Casavant and M. Singhal, Eds., pp. 6--30. IEEE Computer Society Press, Los Alamitos, CA., 1994. Read here. Pre-requisites You will need to have taken CSE505/CSE305 or an equivalent course that gives you a background in programming language internals; you should have a good foundation in problem solving, design representation, and object-oriented design methodology and application and design and development in Java/C#. You should also be familiar with object-oriented modeling, modern code design and debugging practices.2Grading Distribution Final letter grades will be based on the (combined) overall percentage of all the items listed below. A (95 -- ), A- (90 -- 94), B+ (85 -- 89), B (80 -- 84), B- (75 -- 79), C+ (70 -- 74), C (65 -- 69), C- (60 -- 64), D+ (55 -- 59), D (50 -- 54), F (less than 50). This policy is subject to change. If needed, the individual components and the overall grades will be appropriately curved. Grades will consist of the following components: Component (Quantity) Points Pop quizzes (2) + attendance 100 Project (3) 100, 150, 200 Midterm (1) 100 Final (1) 100 Projects The due date for each project will be announced when it is assigned. All the source code, documentation, makefile, data files, and README files are to be submitted on-line. The details of how to submit given along with your first project. You will have to follow the rules for the other projects too. I reserve the right to change the project specifications at any point before the due date to address problems that may arise during the course of the project. If your design is modular the changes will not be difficult to implement. A detailed grading guideline will be given to you along with the project specification. Use this as a guide for your design and implementation. It is absolutely necessary to keep up with the programming projects in the class. There will be a 25 point deduction for each day the project is late after the due date. Develop your code using the Incremental Development technique. Do not try to sit down and code the entire assignment in one sitting. Instead, take one section at a time, implement, test it, back up the code, and move on to the next section. You will turn in each lab before 11:59 PM on the due date via the departmental submit command. You must also include appropriate testing programs to show the validity of your solution. In addition, you must include external documentation discussing the “how’s and why’s” of your design and implementation. You will be required to demonstrate your lab to your TA. The TA will also run test examples against your code to check your solution’s overall correctness. The TA will provide a demo schedule. It is your responsibility to demo your project, or you will receive a zero for that portion of the grade. When your grade is assigned for the lab, the TA will indicate critical areas that must be fixed in order to solve the next assignment. In general, solutions are not provided for the lab. It is not that we do not have them, or am unwilling to distribute them but it’s that there is no one answer to any project solution. Exams There will be a midterm that will be administered and graded before the resign date. Midterm material will cover all lecture and reading assignments before the exam, as well as concepts from the lab assignments. Pop-quizzes will cover any special material covered during the lectures. The final is a comprehensive exam, covering all lecture, lab, and homework areas. All exams are closed book, closed notes, and closed neighbor. We do not give make up exams for any reason. If you miss an exam, you will receive a zero for that portion of the grade. Attendance Policy You are responsible for the contents of all lectures and


View Full Document

UB CSE 486 - Introduction to Distributed Systems

Download Introduction to Distributed Systems
Our administrator received your request to download this document. We will send you the file to your email shortly.
Loading Unlocking...
Login

Join to view Introduction to Distributed Systems and access 3M+ class-specific study document.

or
We will never post anything without your permission.
Don't have an account?
Sign Up

Join to view Introduction to Distributed Systems 2 2 and access 3M+ class-specific study document.

or

By creating an account you agree to our Privacy Policy and Terms Of Use

Already a member?