Journal Paper on Concurrency and Dropbox Hint: It is strongly advised to follow the outline of the Seminars sheets (Seminar 4 and 5) and Lab sheets (Seminar 4 and 5). Scenario for the assignment: Concurrency problems with cloud services; service example is Dropbox; the problem to be considered is mutual exclusion. Simple example scenario: Two users have access to a shared Dropbox folder. Both want to read and write 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 in FSM/FSP and implemented in Erlang. • The background: Dropbox and Erlang • The concurrency problem using some high level description like FSM or FSP. How does this manifest 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 highlighted in quotation marks "…" and referenced • The Journal must be written in the provided IEEE format (can be found in the Internet, latex or word) • The Erlang source code must be submitted together with the paper as a tared or zipped collection of ASCII files and will be marked for functional correctness and completeness (Solution/Evaluation). Recommended 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, introduces related 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 WIKIPEDIA Marking Scheme: