Module NumberCSD2600Distributed Computingand NetworkingModule Handbook(This template is for use in the 2014/15 academic session. In it,text inplain font is for inclusion verbatim in the handbook, and text in italics isguidance or suggested text which must be replaced for each handbook.)Autumn/Winter term Sept start (24 week module)2017/18Dr F.KammuellerSchool of Science and Technology2Information in alternative formatsThis handbook can be found online at: http://unihub.mdx.ac.ukIf you have a disability which makes navigating the website difficult and you would like toreceive information in an alternative format, please contact, please contact Disability Supportat Disability@mdx.ac.ukWe can supply sections from this publication as: a Word document with enlarged type sent by email or supplied on a CD or memorystick printed copy with enlarged type printed copy on non-white paper as BrailleOther formats may be possible. We will do our best to respond promptly. To help us, pleasebe as specific as you can about the information you require and include details of yourdisabilityDisclaimerThe material in this handbook is as accurate as possible at the date of production howeveryou will be informed of any major changes in a timely manner.Other DocumentsYour module handbook should be read and used alongside your programme handbook andthe information available to all students on UniHub including the Academic Regulations andStudent Charter3ContentsContents .3Module Summary/Introduction..4Introduction.4The module teaching team ..4Contacting the Module Leader..4UniHelp.4KIS Teaching and Learning Data.4Module Aims..4Learning Outcomes.5Assessment Scheme 5Assessment Weighting..5Syllabus.5Reading Materials 5Study hours outside class contact.6Brief Guide to Web-based Module Material..6Coursework ..7Details of Coursework ..7Group Peer Review Form 10Teaching Plan14Useful Information.15MyUniHub 15Attendance Requirements .15Academic Dishonesty .15Plagiarism..15Appeals164Module Summary/IntroductionIntroductionThis module gives an introduction to Erlang, Concurrency and Distributed Computing on Networks..The module teaching teamInsert the names of all members of the teaching team for the modulePlease include Student Learning Advisers and/or Academic Assistants attached to the moduleContacting the Module LeaderYou can contact your module leader in the following ways:Office Hours Room No: TG03 Mo 11-12, We 2-3 Email F.Kammueller@mdx.ac.ukTelephone 020 8411 4930MyUniHub pages https://myunihub.mdx.ac.uk It is not necessary to book an appointment to see any of the module tutors during their office hoursyou just need to drop by.In the first instance problems should be dealt with by talking to your lecturer after the lecture. Queriesconcerning course content are particularly suitable for the MyUniHub Discussion Board.UniHelpOn the Hendon campus, UniHelp is located on the Ground Floor of the Sheppard Library Office Hours: Monday to Friday: Saturday and Sunday: 08.30 21.3011.00 18.00 KIS Teaching and Learning DataPlease include a simple chart which shows as a percentage the proportion of time a student on thismodule will spend in each of the following: Scheduled teaching Independent study Placement (if applicable)This should be in the same format as the data submitted for inclusion in the KIS but must beapplicable to the current academic year.For details on how to calculate these proportions please see the information on the staff intranetabout Key Information SetsModule AimsThe module provides a firm basis for planning, programming and running distributed systems: how todesign communicating processes using simple specification and graphical animation and how toprogram concurrent programs in Java. Learners on satisfactory completion of the module will have5knowledge of the main concepts of distributed systems like processes, communication, andsynchronization and their central properties like fault tolerance and security. They will understandtypical problems with distributed applications like deadlocks and mutual exclusion and will know theprinciples of networks and how distributed systems run on them.Learning OutcomesOn completion of this module students will be able to:Knowledge:1. Analyse distributed applications, identify concurrency issues, and devise practical solutionsSkills:1. Design solutions as labelled transition systems, textualise them as finite state processes,demonstrate them and implement them in Erlang on a Network.Assessment SchemeAll learning materials will be presented by using suitable multimedia presentation. There are weeklyone-hour lectures.Two-hour weekly seminar and two hours lab will alternate to enforce topics covered in lectures and toencourage both individual and group activity.Discussion, weekly activities, and project work will underpin the achievement of the relevant learningoutcomes. The project report needs to set out the ethical/legal/professional issues issues related tothe project (raised by the tech and the context of application) and how they have been addressed inthe project.Assessment WeightingCoursework OnlySyllabus Erlang Processes and Threads Concurrent Execution Mutual Exclusion Synchronization and Monitors Deadlock Safety and Liveness Properties Distributed Communication Networking Principles ActorsReading MaterialsYour online reading lists can be accessed from the My Study area of UniHub. They highlight essentialand recommended reading for all modules you are registered on.Reading list at:http://readinglists.mdx.ac.uk/lists/07E505DD-03F9-5B8F-31A8-DB0E4D6F2968.htmlfor more information on electronic reading lists:http://libguides.mdx.ac.uk/liaisonlibrarians.6Study hours outside class contactThe study hours for each credit point is 10 hours. For a 30-credit module this equates to 300 hours.Therefore, if a module has time-tabled activities i.e. lecture/seminar/lab, of 3 hours per week for a 24week period (total of 72 hours), then the out-of-class study commitment expected of students is 228hours in total.Brief Guide to Web-based Module MaterialAdditional material available on your MyUniHub page for CSD2600 which you can access viaURL. (https://myunihub.mdx.ac.uk )7CourseworkDetails of CourseworkBelow is an outline of the coursework.Preparation materials for the coursework is provided in labs and seminars.Deadlines and Percentages for Submission of CourseworkTest on Erlang (30%) in week 7 (resit (only 40% achievable) In week 8)Journal paper (40%) due date in week 17Group presentation (30% individual assessment) weeks 18, 20, 22COURSEWORK 1: Erlang TestTo test your understanding of Erlang and help you to find out where additional work needsto be done, the first coursework is a test on Erlang. There will be ten simple questions on basicprogramming with Erlang.COURSEWORK 2: Journal Paper on Concurrency and DropboxHint: It is strongly advised to follow the outline of the Seminars sheets (Seminar 4 and 5) and Labsheets (Seminar 4 and 5).Scenario for the assignment: Concurrency problems with cloud services; service example isDropbox; the problem to be considered is mutual exclusion.Simple example scenario: Two users have access to a shared Dropbox folder. Both want to read andwrite the same file. This may create a concurrency issue.A standard solution is to use a semaphore or a monitor.Assignment Requirements: The journal paper must describe the background of the project, i.e.Concurrency and Dropbox. The concurrency problem must be illustrated using Finite State Machines(FSM) or Finite State Processes (FSP), and Erlang. The solution (Mutex) must also be illustrated inFSM/FSP and implemented in Erlang. The background: Dropbox and Erlang The concurrency problem using some high level description like FSM or FSP. How does thismanifest itself in your Erlang implementation? What is your solution idea/algorithm? (Mutex probably) Solution in Erlang including some analysis (tests, problems encountered).Formal Journal Requirements: The report should demonstrate qualities in terms of writing skills, format, and contents. Maximum 5 pages NO plagiarism Your own words with the exception of quotations from other sources that should be highlightedin quotation marks and referenced The Journal must be written in the provided IEEE format (can be found in the Internet, latex orword) The Erlang source code must be submitted together with the paper as a tared or zippedcollection of ASCII files and will be marked for functional correctness and completeness(Solution/Evaluation).8Recommended General Journal Paper Structure Abstract Summary of your work very important !! (it is the most read) Introduction Places the work in the appropriate context, gently introduces the subject, introducesrelated approaches and concludes with a roadmap Background basic concepts and terminology to understand your work Possible approaches Various solutions Discussion Critically evaluate all solutions pros and cons Future works / improvements (if any) Conclusions Summaries and underlines major concepts References Look in google scholar IEEE and ACM digital libraries NOT JUST WIKIPEDIAMarking Scheme:9IEEE Paper Format: ExampleInvestigating Airplane Safety and Security againstInsider Threats Using Logical ModelingFlorian Kammuller Middlesex University Londonf.email@example.comManfred KerberUniversity of BirminghamM.Kerber@cs.bham.ac.ukAbstractIn this paper we consider the limits of formal modeling of infrastructures and the application of social explanationfor the analysis of insider threats in security and safety criticalareas. As an area of study for the analysis we take examples fromaviation, firstly since incidents are typically well-documented andsecondly since it is an important area per se. In March 2015, aGermanwings flight has crashed in the French Alps in whatis quite firmly believed to have been intentionally caused bythe copilot who has locked the pilot out of the cockpit andprogrammed the autopilot on constant descent. We investigatethe security controls and policies in airplanes against insiderthreats using logical modeling in Isabelle.I. INTRODUCTION AND OVERVIEWIn this paper, we take a critical look at logical methodsto model and analyse safety and security critical systems.In particular, we address recent advances in applying formalverification techniques, e.g. , in the context of severeincidents like the tragic crash of a Germanwings flight: OnMarch 24, 2015 Germanwings Flight 9525, a scheduled flightfrom Barcelona to Dusseldorf was hijacked by the co-pilot. 30 minutes after takeoff Andreas Lubitz locked himself in [the]cockpit when [the] captain went out for a rest. Then the copilot started to descend. [The] captain tried to communicatewith Lubitz, but he didnt reply. After 8 minutes of falling theairplane crashed in the Alps near the French village PradsHaute-Blone. There were 144 passengers and 6 crew memberson board. None of them survived the crash. In this paper, we first summarize the development of airplane security (Section II) before we model and analyse thespecific settings in passenger transport airplanes using theIsabelle Insider framework (Section III) leading to a discussionand conclusions (Section IV).It should be noted that with insider attacks there are twofundamentally different approaches. The first is based onprobabilistic reasoning and cost analysis. For instance, if in acompany there is a leakage in low-cost pens, since employeestake them home then the company must consider whetherimposing a strict control regime involving CCTV cameras iscost effective in eliminating the problem. The company mayconclude that cheaper measures minimize the overall cost oflost pens and measures to lose only few.The second approach is based on Boolean reasoning inwhich it is investigated whether certain attacks are possibleor not. That is, a model of a real world situation is built andthen it is checked or proved that a particular situation can occuror not, for instance, by checking whether a particular state isreachable from an initial state or not. Such an approach wouldbe applied, for instance, if a particular situation is unacceptableand has to be avoided at all cost. As a consequence, forairplane safety this will be the method of choice and isthe approach taken in the following. Of course, this doesnot mean that the approach gives 100% guarantees. Themain problem is that any model of a real world situationis necessarily incomplete since it abstracts from (hopefullyonly irrelevant) details. However, it is difficult to establish thatnothing essential has been overlooked.A. Related WorkWe consider here some main threads of work by otherswhile discussing the relationship of the contribution of thispaper to our own previous work in Section IV.The Insider threat patterns provided by CERT  use theSystem Dynamics models, which can express dependenciesbetween variables. The System Dynamics approach is alsosuccessfully being applied in other approaches to Insiderthreats, for example, in the modeling of unintentional insiderthreats . Axelrad et al.  have used Bayesian networks formodelling Insider threats in particular the human disposition.In comparison, the model we rely on for modeling the humandisposition in the Isabelle Insider framework is a simplifiedclassification following the taxonomy provided by . Onthe other side, compared to all these approaches, our workprovides an additional model of infrastructures and policiesallowing reasoning at the individual and organisational level.In the domain of rigorous analysis of airplane systems, workoften follows for practical and economic reasons a philosophyof using a mix of formal and systematic informal methods.An example from airplane maintenance procedures  usesa security evaluation methodology following the CommonCriteria and a formal model and verification with the modelchecker AVISPA. In comparison, we use a more expressivelogical model in the Isabelle Insider framework than theirAVISPA specification. Also, we believe that our work is thefirst to consider Insider threats within airplane safety andsecurity at least in a formal way.On the formal side within the Insider threat communityin general, the work by Bishop et al  is relevant to theIsabelle Insider framework since it also uses a formal modelto analyse Insider threats. Bishop and colleagues use the10COURSEWORK 3: Group PresentationImportant Note on group presentations: all group members MUST submit a Peer ReviewForm (see below). This is a mandatory component to achieve this part of the coursework. Thepeer reviews need to consistently show the contribution of all group members.This peer review also contributes to the individual assessement of the group presentation(20%)Peer review form: This following form should be copied and printed by each student.It must be submitted on the day of the presentation to the seminar tutor. If it is missingit will automatically imply that this group member has not contributed and will lead tofailure of that coursework part.Group Peer Review FormSeminar Day ________________________ Time: ____________________Group name: _____________________________Peer Reviewer (name and email): ____________________________ All MembersNamesincluding selfTheir Contribution tothe PresentationMark (out of 20) Other Remarks1 2 3 4 5 Note: Under no circumstances that you are allowed to have more than FIVE members pergroup including the group leader and/or less than 3 per group.Group Presentation Subjects and Marking Scheme:Possible subjects for a group presentation in groups of size of 4-5 students are the following:Network vulnerabilities, Java distribution, CORBA, RMI, Erlang applications, Network protocols (IPv6vs IPv4), Router configuration, Cloud computing, Cloud security.Other subjects may be chosen but need to be discussed with the seminar leader.11Marking Scheme for Group PresentationsGroup Name: __________________________Seminar Session: _________________Date:_____________________ Title: _____________________________Final mark: _______________ Tutor Initials: ______________ Element Max. Mark in % Comments MarkawardedClarity to present topic 10%Relevant and to the point 10%Ability to convince audience 10%Evidence of Team work (fromPeer review form)20%Supporting materials 10%Understanding of topic 20%Time Management 10%Report 10%TOTAL 100% 12Remarks on Academic WritingSometimes deadlines from different modules will come at the same time and it is important to planyour workload to meet these deadlines.BibliographyIn the Bibliography section list the books, journal articles and other sources used in the preparation ofthe report. (These are the sources that have helped you in the preparation of your report, but are notcited in your report.)ReferencesIn technical reports, a list of cited works is usually called References and comes at the end of your report.(These are the books, journals and other sources that you have paraphrased or quoted and are cited inyour report.)Correct citing of original material is very important. When you use information from a source you mustshow where you have got it from. This is called an in-text citation. In your report your in-text citations andreference list should use the Harvard style shown in Cite Them Right.Go to: http://ezproxy.mdx.ac.uk/login?url=http://www.citethemrightonline.comCite Them Right shows you how to cite the reference in the text of your report and how to write a correctreference at the end.Where to submitSubmission of coursework via your UniHub page. Please note that only electronic submissionof work is possible.Written assessed coursework must be submitted to UniHelp, Ground Floor, Sheppard Library. Youshould attach a coursework feedback form which will be dated and receipted. You should keep yourreceipt it is for your own protection.Do not submit hand written assessed coursework directly to your tutor, and do not submit it by emailto your tutor.Written work should normally be handed in on the campus at which the module is being taught; if forany reason you have to hand it in at another campus please point this out to UniHelp so that it can besent to the correct campus. If, in an emergency, you have to send in written assessed work by postyou must send it by recorded delivery to UniHelp, Sheppard Library, Middlesex University, TheBurroughs, London NW4 4BT and keep the Post Office receipt. It will be deemed to have beensubmitted on the date of the postmark.Receipts for this work and other work submitted outside opening hours can be collected from UniHelp.Group CourseworkWhen submitting group coursework please ensure all students contributing to the coursework areclearly identified on the coursework Feedback Form.In most cases, students hold the intellectual property rights in the work they produce for assessment.There are some exceptions such as where the work is commercially-sponsored, or the aim of themodule is to develop intellectual property, or where the student is sponsored or employed, or onplacement. Students are asked to read the Middlesex University Policy Statement IntellectualProperty Rights: https://myunihub.mdx.ac.ukFeedback to students on coursework The Erlang test will be marked and returned by the lab/seminar tutors Annotation and return of the journal paper in the Turnitin online system13 Marks on presentations given after the talks taking the peer review and electronic copiesinto account.The overall weighting of the course is roughly equal for all three parts: test 30%, journal 40%,presentation 40%. The course is entirely course work based. Thus we need a strict discipline on themarking. The courseworks have to be submitted in time. The test in week 7 must be done by everystudent (if students fail to show up or fail the test a resit is possible, see below). To guarantee this theteaching is organized so that there is always time (Seminars in Week 8, 16, 24) to catch up. If astudent fails the test in Week 7, the seminar in Week 8 gives a resit opportunity. The submission ofthe journal paper is via turnitin with a fixed system deadline. If students fail to submit in time, everyday of late submission subtracts 20% of the possible outcome. I.e., a student submitting his journalpaper on day three after the deadline is two days late and can only get 60% of possible points.Coursework returnCoursework is not normally returned to students, so you should keep a copy of what you submit.
Distributed Computing and Networking
Pssst…We can write an original essay just for you.
Any essay type. Any subject. We will even overcome a 6 hour deadline.
<< SAVE15 >>
Place your first order with code to get 15% discount right away!