COMP SCI 3012 - Distributed Systems
North Terrace Campus - Semester 2 - 2017
General Course Information
Course Code COMP SCI 3012 Course Distributed Systems Coordinating Unit School of Computer Science Term Semester 2 Level Undergraduate Location/s North Terrace Campus Units 3 Contact Up to 2.5 hours per week Available for Study Abroad and Exchange Y Prerequisites One of COMP SCI 1007, COMP SCI 1009, COMP SCI 1103, COMP SCI 1203, COMP SCI 2103 or COMP SCI 2202 Assumed Knowledge COMP SCI 2000 & COMP SCI 3001 Course Description A selection of topics from the following: the challenges faced in constructing client/server software: partial system failures, multiple address spaces, absence of a single clock, latency of communication, heterogeneity, absence of a trusted operating system, system management, binding and naming. Techniques for meeting these challenges: RPC and middleware, naming and directory services, distributed transaction processing, 'thin' clients, data replication, cryptographic security, mobile code. Introduction to Java RMI.
Course Coordinator: Mr William Brodie-TyrrellCo-lecturer: David Milanese
The full timetable of all activities for this course can be accessed from Course Planner.
Course Learning OutcomesIn Distributed Systems this course, you will learn a range of fundamental and applied techniques in distributed systems. The learning objectives for Distributed Systems are:
- To develop and apply knowledge of distributed systems techniques and methodologies.
- To gain experience in the design and development of distributed systems and distributed systems applications.
- To gain experience in the application of fundamental Computer Science methods and algorithms in the development of distributed systems and distributed systems applications.
- To gain experience in the design and testing of a large software system, and to be able to communicate that design to others.
University Graduate Attributes
This course will provide students with an opportunity to develop the Graduate Attribute(s) specified below:
University Graduate Attribute Course Learning Outcome(s) Deep discipline knowledge
- informed and infused by cutting edge research, scaffolded throughout their program of studies
- acquired from personal interaction with research active educators, from year 1
- accredited or validated against national or international standards (for relevant programs)
1,2,3 Critical thinking and problem solving
- steeped in research methods and rigor
- based on empirical evidence and the scientific approach to knowledge development
- demonstrated through appropriate and relevant assessment
2, 3 Teamwork and communication skills
- developed from, with, and via the SGDE
- honed through assessment and practice throughout the program of studies
- encouraged and valued in all aspects of learning
2,3 Career and leadership readiness
- technology savvy
- professional and, where relevant, fully accredited
- forward thinking and well informed
- tested and validated by work based experiences
Required ResourcesYou can perform all the exercise work required for the course in the University computer Labs.
The programming language used is Java.
However, if you want to be able to work at home, you could consider installing Java on your own system.
For more information, go to the Java website --- simply Google "Java".
Recommended ResourcesReference books:
- Distributed Systems: Concepts and Design, G. Coulouris, Jean Dollimore and Tim Kindberg, Addison Wesley, 4th Edition
- Distributed Systems: Principles and Paradigms, A.S. Tanenbaum and M. Van Steen, Pearson, 2nd Edition
Online LearningMore information about the course can be found online on the Moodle forum of the school.
Learning & Teaching Activities
Learning & Teaching ModesThe course will be taught with lectures and collaborative sessions.
You are expected to attend the lectures and take part in the activities, and attempt collaborative sessions questions before the session.
All lectures will be attempted to be recorded, however attendance at the lectures is recommended, due to the large number of activities present in the lectures.
The information below is provided as a guide to assist students in engaging appropriately with the course requirements.The information below is provided as a guide to assist students in engaging appropriately with the course requirements.
You are expected to attend all scheduled lecture classes (2hrs per week), and, if scheduled, the collaborative sessions.
In addition to the schedule contact hours, you are expected to spend an additional 2-4 hours per week after each lecture to consolidate your understanding of it. You will need to allocate up to 7 hours per week on average to work on the assignments and work set in collaborative sessions.
Learning Activities SummaryThe topics taught in this course can be broadly classified as shown below. The list of topics and their schedule is available on the course web site.
Local and distributed synchronization
Remote Operations - latency hiding and reductions
Failure semantics in RPC
Distributed file systems
Distributed transactions and failures
2PC, 3PC, PAXOS
Specific Course RequirementsNote that COMP SCI 3001 is assumed knowledge for this course - this implies that students are familiar with Socket implementations (particularly in Java), and that students have an understanding of the idea of a protocol and the differences between TCP and UDP.
The University's policy on Assessment for Coursework Programs is based on the following four principles:
- Assessment must encourage and reinforce learning.
- Assessment must enable robust and fair judgements about student performance.
- Assessment practices must be fair and equitable to students and give them the opportunity to demonstrate what they have learned.
- Assessment must maintain academic standards.
Assessment SummaryThe assessment will comprise of two parts: practical programming assignments and collaborative session reports worth 30% and a final exam worth 70%.
Component Weighting CBOK Areas Assignments and Collaborative sessions 30% 1,2,4,7,8,9,11 Final Written Exam 70% 1,2,8
- Interpersonal Communication
- Societal Issues
- History & Status of the Discipline
- Hardware & Software
- Data & Information
- Human Computer Interfaces
- Systems Development
Details of the Australian Computer Society's Core Bode of Knowledge (CBOK) can be found in this document.
Assessment DetailMore information on the assessment is provided online on the course forum. The course has two forms of assessment: summative assessment, provided by the collaborative sessions, and formative assessment provided by the assignments and collaborative sessions' reports.
SubmissionAll practical assignments must be submitted using the School of Computer Science online Submission System.
Details are included in each assignment description on the course website. Collaborative practical reports are submitted via email to the course coordinator. The University policy on plagiarism applies on all submissions.
Grades for your performance in this course will be awarded in accordance with the following scheme:
M10 (Coursework Mark Scheme) Grade Mark Description FNS Fail No Submission F 1-49 Fail P 50-64 Pass C 65-74 Credit D 75-84 Distinction HD 85-100 High Distinction CN Continuing NFE No Formal Examination RP Result Pending
Further details of the grades/results can be obtained from Examinations.
Grade Descriptors are available which provide a general guide to the standard of work that is expected at each grade level. More information at Assessment for Coursework Programs.
Final results for this course will be made available through Access Adelaide.
The University places a high priority on approaches to learning and teaching that enhance the student experience. Feedback is sought from students in a variety of ways including on-going engagement with staff, the use of online discussion boards and the use of Student Experience of Learning and Teaching (SELT) surveys as well as GOS surveys and Program reviews.
SELTs are an important source of information to inform individual teaching practice, decisions about teaching duties, and course and program curriculum design. They enable the University to assess how effectively its learning environments and teaching practices facilitate student engagement and learning outcomes. Under the current SELT Policy (http://www.adelaide.edu.au/policies/101/) course SELTs are mandated and must be conducted at the conclusion of each term/semester/trimester for every course offering. Feedback on issues raised through course SELT surveys is made available to enrolled students through various resources (e.g. MyUni). In addition aggregated course SELT data is available.
- Academic Support with Maths
- Academic Support with writing and speaking skills
- Student Life Counselling Support - Personal counselling for issues affecting study
- International Student Support
- AUU Student Care - Advocacy, confidential counselling, welfare support and advice
- Students with a Disability - Alternative academic arrangements
- Reasonable Adjustments to Teaching & Assessment for Students with a Disability Policy
- LinkedIn Learning
Policies & Guidelines
This section contains links to relevant assessment-related policies and guidelines - all university policies.
- Academic Credit Arrangement Policy
- Academic Honesty Policy
- Academic Progress by Coursework Students Policy
- Assessment for Coursework Programs
- Copyright Compliance Policy
- Coursework Academic Programs Policy
- Elder Conservatorium of Music Noise Management Plan
- Intellectual Property Policy
- IT Acceptable Use and Security Policy
- Modified Arrangements for Coursework Assessment
- Student Experience of Learning and Teaching Policy
- Student Grievance Resolution Process
Students are reminded that in order to maintain the academic integrity of all programs and courses, the university has a zero-tolerance approach to students offering money or significant value goods or services to any staff member who is involved in their teaching or assessment. Students offering lecturers or tutors or professional staff anything more than a small token of appreciation is totally unacceptable, in any circumstances. Staff members are obliged to report all such incidents to their supervisor/manager, who will refer them for action under the university's student’s disciplinary procedures.
The University of Adelaide is committed to regular reviews of the courses and programs it offers to students. The University of Adelaide therefore reserves the right to discontinue or vary programs and courses without notice. Please read the important information contained in the disclaimer.