This task asks me to answer the questions. the template is in here. I think that would not be useful but, I have attached sample(last year's).
And I have to request you the most important thing. please write every sources what you see as a reference. I have been in trouble 2 weeks ago. I went to the faculty discipline committee and got 60% deduction penalty. I think Turnitin which is used by the instructors can catch someone's idea as well.
Request
1. please write every sources what you see and use and the reference has to be Harvard style.
2. please finish it before the deadline.
3. it is a Distributed Systems course. so, please no off-topic
4. please see every files what I have attached.
5. if you don't know send me your progress. I'll ask it to the instructor.
Assignment 1/Instruction.pdf COMP8110 Assignment 1 (20% of your final grade) Due: Friday Week 7 11:59 pm (10th Sep 2021). Where: Submit a document (PDF) which includes the answers for each problem in the submission box for Assignment 1 on iLearn. The document name must be of the format studentid_firstname_lastname.pdf In this assignment, you will be asked to write a technical report for a fictitious company called ITSEG Co. to help the company to build and release new products. 1 Assignment Background ITSEG Co., the software provider for highly integrated and ultra-simplified intelligence system (Hypothetical company you work at as a distributed systems developer) proposed the project. The project is to develop a trustworthy system for connected and autonomous vehicles (Internet of Vehicles). As shown in the week 1’s lecture, Internet of Vehicles indeed offers a lot of flexibilities (i.e., crash scenes re-routing, emergency vehicles giveaway). However, malicious users can also generate misleading information to jeopardize the entire system. ITSEG is looking into the blockchain technology to build the backbone for a trustworthy internet of vehicles system. Your job is to investigate the following: 1. Background questions (put in the Background section) - 6 marks What are the main (heterogenous) components in Internet of Vehicles? How these components communicate with each other? What are the attack scenarios in such distributed systems? To achieve fault tolerance in such distributed systems, Byzantine agreement is needed. What are some state-of-the-art Byzantine agreement protocols available for such distributed systems? What can these protocols achieve? What are the remaining gaps? 2. General questions (put in the Preliminary section) – 5 marks How does Blockchain work? How does Blockchain ensure security? How does Blockchain ensure non-repudiation? 3. Application specific questions (put in the Solution section) – 9 marks How can Blockchain reduce or even eliminate malicious users? What are the limitations of Blockchain when applied for Internet of Vehicles? What are the possible solutions to solve these limitations? You are required to complete a technical report addressing the above-mentioned questions in a specific IEEE latex format (Assignment1.zip). Your report shall be 6 pages in total (excluding references). For references, we recommend conferences and journals at CORE A/A* or Q1 ranking. CORE conference ranking: http://portal.core.edu.au/conf- ranks/, CORE journal ranking: http://portal.core.edu.au/jnl-ranks/, Journal ranking: https://www.scimagojr.com/journalrank.php. The report template (Assignment1-COMP8110-S22021.tex) contains the following sections which you need to fill in the answers: 1. Background section: where you answer the background questions 2. Preliminary section: where you answer the general questions 3. Solution section: where you answer the application specific questions 4. Conclusion section: concludes your findings How you will be assessed Each question is marked out of the total score allocated to each section. Here is how you can impress the markers: • Make it easy for the marker to find your answers to each part of a question / problem. • The aim is not "how much" you write, or "how many" sources you use. Aim for quality over quantity. • Have clearly formatted answers free from spelling and grammatical errors. Have clear and concise answers for all aspects outlined in each question. • Higher grades will mostly reflect the quality of your thinking that has gone in to your considered answers. This might mean that you start the first week of the assignment with reading and reviewing areas covered in the questions. This is not something you will want to leave to the last minute. http://portal.core.edu.au/conf-ranks/ http://portal.core.edu.au/conf-ranks/ http://portal.core.edu.au/jnl-ranks/ https://www.scimagojr.com/journalrank.php COMP8110 Assignment 1 (20% of your final grade) 1 Assignment Background __MACOSX/Assignment 1/._Instruction.pdf Assignment 1/Assignment1/.DS_Store __MACOSX/Assignment 1/Assignment1/._.DS_Store Assignment 1/Assignment1/fig1.png __MACOSX/Assignment 1/Assignment1/._fig1.png Assignment 1/Assignment1/IEEEtran_HOWTO.pdf JOURNAL OF LATEX CLASS FILES, VOL. 14, NO. 8, AUGUST 2015 1 How to Use the IEEEtran LATEX Class Michael Shell, Member, IEEE (Invited Paper) Abstract—This article describes how to use the IEEEtran class with LATEX to produce high quality typeset papers that are suit- able for submission to the Institute of Electrical and Electronics Engineers (IEEE). IEEEtran can produce conference, journal and technical note (correspondence) papers with a suitable choice of class options. This document was produced using IEEEtran in journal mode. Index Terms—Class, IEEEtran, LATEX, paper, style, template, typesetting. I. INTRODUCTION W ITH a recent IEEEtran class file, a computer runningLATEX, and a basic understanding of the LATEX language, an author can produce professional quality typeset research papers very quickly, inexpensively, and with minimal effort. The purpose of this article is to serve as a user guide of IEEEtran LATEX class and to document its unique features and behavior. This document applies to version 1.8b and later of IEEEtran. Prior versions do not have all of the features described here. IEEEtran will display the version number on the user’s console when a document using it is being compiled. The latest version of IEEEtran and its support files can be obtained from IEEE’s web site [1], or CTAN [2]. This latter site may have some additional material, such as beta test versions and files related to non-IEEE uses of IEEEtran. See the IEEEtran homepage [3] for frequently asked questions and recent news about IEEEtran. Complimentary to this document are the files1 bare_con f.tex, bare_jrnl.tex, bare_jrnl_comsoc.tex, bare_ conf_compsoc.tex, bare_jrnl_compsoc.tex and bare_ jrnl_transmag.tex, which are “bare bones” example (tem- plate) files of a conference, journal, IEEE Communications Society journal, IEEE Computer Society conference, IEEE Computer Society journal and IEEE TRANSACTIONS ON MAGNETICS paper, respectively. Authors can quickly obtain a functional document by using these files as starters for their own work. A more advanced example featuring the use of Manuscript created February 25, 2002; revised August 26, 2015. This work was supported by the IEEE. This work is distributed under the LATEX Project Public License (LPPL) ( http://www.latex-project.org/ ) version 1.3. A copy of the LPPL, version 1.3, is included in the base LATEX documentation of all distributions of LATEX released 2003/12/01 or later. The opinions expressed here are entirely that of the author. No warranty is expressed or implied. User assumes all risk. See http://www.michaelshell.org/ for current contact information. 1Note that it is the convention of this document not to hyphenate command or file names and to display them in typewriter font. Within such constructs, spaces are not implied at a line break and will be explicitly carried into the beginning of the next line. This behavior is not a feature of IEEEtran, but is used here to illustrate computer commands verbatim. optional packages along with more complex usage techniques, can be found in bare_adv.tex. It is assumed that the reader has at least a basic working knowledge of LATEX. Those so lacking are strongly encouraged to read some of the excellent literature on the subject [4]–[6]. In particular, Tobias Oetiker’s The Not So Short Introduction to LATEX 2ε [5], which provides a general overview of working with LATEX, and Stefan M. Moser’s How to Typeset Equations in LATEX [6], which focuses on the formatting of IEEE-style equations using IEEEtran’s IEEEeqnarray commands, are both available for free online. General support for LATEX related questions can be obtained in the internet newsgroup comp.text.tex. There is also a searchable list of frequently asked questions about LATEX [7]. Please note that the appendices sections contain information on installing the IEEEtran class file as well as tips on how to avoid commonly made mistakes. II. CLASS OPTIONS There are a number of class options that can be used to control the overall mode and behavior of IEEEtran. These are specified in the traditional LATEX way. For example, \documentclass[9pt,technote]{IEEEtran} is used with correspondence/brief/technote papers. The various categories of options will now be discussed. For each category, the default option is shown in bold. The user must specify an option from each category in which the default is not the one desired. The various categories are totally orthogonal to each other—changes in one will not affect the defaults in the others. A. 9pt, 10pt, 11pt, 12pt There are four possible values for the normal text size. 10pt is used by the vast majority of papers. Notable exceptions are technote papers, which use 9pt text and the initial submissions to some conferences that use 11pt. Be aware that IEEE Computer Society publications use “PostScript” (i.e., “big point”, bp) point sizes (i.e., 72bp = 1in) rather than the traditional typesetters’ point (i.e., 72.27pt = 1in). Also, “10pt” IEEE Computer Society journal papers actually use a slightly smaller, 9.5bp, font size (probably to compensate for the slightly wider nature of the Palatino font). IEEEtran will automatically tweak the selected font size as needed depending on the mode. 0000–0000/00$00.00 c© 2015 Michael Shell http://www.latex-project.org/ http://www.michaelshell.org/ 2 JOURNAL OF LATEX CLASS FILES, VOL. 14, NO. 8, AUGUST 2015 B. draft, draftcls, draftclsnofoot, final IEEEtran provides for three draft modes as well as the normal final mode. The draft modes provide a larger (double) line spacing to allow for editing comments as well as one inch margins on all four sides of the paper. The standard draft option puts every package used in the document into draft mode. With most graphics packages, this has the effect of disabling the rendering of figures. If this is not desired, one can use the draftcls option instead to yield a draft mode that will be confined within the IEEEtran class so that figures will be included as normal. draftclsnofoot is like draftcls, but does not display the word “DRAFT” along with the date at the foot of each page. Both draft and draftclsnofoot modes imply draftcls (which is a subset of the other two). When using one of the draft modes, most users will also want to select the onecolumn option. C. conference, journal, technote, peerreview, peerreviewca IEEEtran offers five major modes to encompass conference, journal, correspondence (brief/technote) and peer review pa- pers. Journal and technote modes will produce papers very similar to those that appear in many IEEE TRANSACTIONS journals. When using technote, most users should also select the 9pt option. The peerreview mode is much like the journal mode, but produces a single-column cover page (with the title, author names and abstract) to facilitate anonymous peer review. The title is repeated (without the author names