You will undertake two (2) quizzes on Moodle throughout the term. Each quiz will cover topics leading up to that quiz and may include topics covered by previous quizzes. Typically, the quizzes will assess your knowledge of the lecture content and tutorial activities. Some questions may require you to use software, e.g., software demonstrated in lectures and/or used in tutorial activities. Each quiz will consist of multiple questions which may be of various types (e.g., multiple-choice, short answer, calculations, written text, upload a file). All quizzes are individual assessment.

Quiz 1 will be conducted online. You will have a set period of time during Week 6 to complete the quiz. There are time limits on the quiz. The quiz time limits, topics and open/close times can be found on Moodle.

Quiz 2 will be conducted in-class, in the 1st hour only, under the supervision of your tutor. You must attend your allocated tutorial class in Week 12 and use a lab computer to complete the quiz during class. Online students will undertake Quiz 2 in a Zoom session in Week 12 (during the scheduled Online tute). Online students will need access to a webcam, speakers, and microphone (e.g., headset).

You will not be allowed to take a quiz at any time outside of the specified open/close times unless an Assessment Extension Request is approved. In Quiz 2, if you arrive late for class, you will not be granted extra time. Changes to quiz times can only be granted with approval by the Unit Coordinator.

While quizzes will be open-book (e.g. you can use lecture slides), you will be expected to produce the answers yourself. That is, you are not allowed to communicate with others during the quiz (including other students or people online), and if you use online searches, forums or AI systems (e.g. StackExchange, ChatGPT), you are expected to write the answer in your own words. Advice on what resources can(not) be used may be provided before the start of each quiz.

You are assumed to have a working computer and Internet connection during term, and especially during times when attempting a quiz. Technical problems, such as a computer crash or loss of Internet connection, will not usually be a reason for an extra attempt or extension. You are expected to prepare your computer before the quiz starts. If problems outside of your control occur during a quiz, report immediately to your tutor, who may either extend the time or allow you to undertake the quiz at another time (with the Unit Coordinator's approval).

• Quiz 1: 10%
• Quiz 2: 25%

In most cases, quiz answers will be automatically marked, with marks awarded based on the correctness of the answer within the context of topics covered in unit. Questions may be worth different marks, with the marks shown in the quiz. If quiz answers are manually marked (e.g., explanation style questions), then marks will be awarded based on the correctness and clarity of the answer.

It is important you answer the questions within the context of this unit. There are sometimes different meanings of terms in networking and cyber security. You will be expected to use the terms as covered in the lecture materials and tutorial activities.

As results and solutions may be released shortly after the due date, late submissions are not accepted. Making no attempts before the due date will result in a score of 0.

You will keep a journal throughout the unit that captures your tutorial activities and project contributions. Each tutorial has a set of tasks: the workings, results, answers and discussion arising from those tasks must be captured in your journal.

You must contribute to your journal every week, preferably during or shortly after each tutorial. Examples of content that may be included are:

• Screenshots capturing results of using software to complete tasks;
• Commands used to complete tasks, and the output of those commands, e.g., copy-and-paste from PowerShell;
• Network diagrams and other illustrations you develop;
• Links to websites/papers/software you used to solve problems or find information;
• Answers to questions in the tutorial activities, or relevant questions posed by your tutor or other students;
• Notes on how to use software, perform a calculation or solve a problem;
• Files you created or produced by software in conducting tutorial activities, e.g., web pages.

Tutorial activities may specify what must be included in your journal for a particular task. You should also use your journal to document your individual contributions to your project. As a general guide, include items in your journal that:

1. Provide evidence that you completed a tutorial task or made a contribution to the project (e.g., screenshots, output, commands, files, diagrams);
2. Demonstrate understanding and competence of the knowledge and skills taught (e.g., written insights, summary of concepts, reflections on what went wrong);
3. Will be helpful for you later in the unit, or in future units, to refer back to (e.g., notes, steps you took, links to websites and other instructions).

You will have to maintain your journal such that there is evidence of regular (at least weekly) contributions. Your journal must be created in a GitHub repository created using GitHub Classroom. As this is your own journal, you should not share with other students. The journal should use basic Markdown formatting (using just plaintext or uploading a Word document is insufficient). Details of creating the GitHub repository can be found on Moodle.

You are required to submit your journal early in the term (Journal Part 1) so you can gain feedback on the suitability of your entries so far. The entire journal is then submitted towards the end of term (Journal Part 2).

Your journal is an individual assessment worth 35% of the unit assessment, split as follows:

• Journal Part 1: 10%, covering contributions from Weeks 1 to 3
• Journal Part 2: 25%, covering contributions from Weeks 4 to 10

You will receive marks for:

• Each weekly entry, e.g., does your entry demonstrate completion and understanding of the tutorial activities? does your entry include genuine insights (e.g., suitable focused and adequate elaboration)?
• Professionalism in preparing the journal, e.g., weekly entries relevant to the topics; the data (e.g. screenshots, drawings) are your own and not shared with others; genuine individual reflections; submission in the correct format; presented in a professional manner.

There are minimum expectations for the journal and if you do not meet them you may receive 0 marks for that component. This includes:

• 0 marks for a weekly entry and professionalism if your entry includes identical data as another student when that data should be specific to you (e.g., you and another student submit an identical screenshot).
• 0 marks for professionalism if the submission is in the wrong format (e.g., ZIP file not submitted).
• 0 marks for professionalism if no evidence of regularly (weekly) entries (e.g., based on GitHub commits).
• 0 marks for entire submission if GitHub and markdown is not used (e.g., you simply upload a Word document).
• 0 marks for tasks that were submitted into a different week than specified in the published tutorial instructions for that term (e.g., submitting week 3 task 4 in week 2 entry)

While the journal will be maintained on GitHub, on Moodle you must submit a ZIP of the journal as well as PDF of each weekly entry. This is necessary so that a permanent record of your contribution is available in Moodle (in case the online platform is not available in the future). Late penalties are calculated based on your final submission in Moodle, not activity in GitHub. Instructions for producing the ZIP and PDF files are provided in Moodle.

You will conduct a project involving network design and cyber security analysis. You will apply the knowledge and skills you have learnt in the unit to propose a networking and cyber security solution for a small/medium sized organisation. You will also identify and reflect on professional and ethical issues that may arise as a result of the project. Details of the project tasks can be found on Moodle.

This is a group project consisting of two (2) students from the same class (or with the Unit Coordinators permission, three students, e.g., when an odd number of students in the class). Students should form their own groups, but if not formed within reasonable time, the Unit Coordinator may allocate students to a group. Generally, a change of groups is not allowed once the project starts. If a student is not contributing to the project (e.g., they are absent or not responding to communications), the other student must inform the Unit Coordinator as soon as possible.

Students must use a GitHub repository to track their project contributions (e.g., drafts, design files, code). Details of creating the GitHub repository can be found on Moodle. Your contributions on GitHub may be taken into account when determining your overall contribution to the project.

You will produce written reports on the project, as well as a presentation at the end of the project. The presentation will be via a recorded video. Details of the presentation format and duration can be found on Moodle.

Your project assessment is worth 30% of the unit assessment, split as follows:

• Project Part 1: 12%. A written report covering the network design phase.
• Project Part 2: 18%. A written report and presentation covering the entire project.

The report in both parts will be marked based on the quality of the work, the application of knowledge and skills taught in the unit, and professionalism of the report (including regular contributions to the project throughout the term, as evidenced by GitHub contributions and contributions during tutorials). The presentation will be marked based on the ability to offer genuine, personal reflections on the project, and to clearly explain aspects of the project.

While this is a group project, some parts may be individually assessed. For example, some tasks are to be completed by the group and generally each student will receive the same marks, while some tasks may be assigned to individuals and each student will receive a mark for their assigned task. Even for the group tasks, different marks may be given to students in a group when there is a significant difference in contributions (e.g., as evidenced by GitHub contributions and contributions during tutorials).

There are minimum expectations for the project and if you do not meet them you may receive 0 marks for that component. This includes:

• 0 marks for a component of the assessment if files/data related to that component are not submitted or submitted in the correct format (e.g., an Excel spreadsheet is required but not submitted).
• 0 marks for a component of the assessment if you include identical data to another group when that data should be specific to your group (e.g., you and another group include an identical screenshot).
• 0 marks for multiple components of the assessment if no evidence of regularly (weekly) contributions to the project (e.g., based on GitHub commits).
• 0 marks for multiple components of the assessment if one or multiple parts of the submission are in the wrong format (e.g., no ZIP submission, video submitted wrongly).
• 0 marks for entire submission if GitHub and markdown is not used (e.g., you simply upload a Word document).
• 0 marks for an individual student if that student does not make any reasonable contributions via GitHub.

Detailed marking criteria specifying these and other minimum expectations, as well as the components, is available on Moodle.

While the project will be maintained on GitHub, on Moodle you must submit a ZIP of the project as well as PDF of each relevant Markdown page. You must also submit a video for Project Part 2. This is necessary so that a permanent record of your contribution is available in Moodle (in case the online platform is not available in the future). Late penalties are calculated based on your final submission in Moodle, not activity in GitHub. Instructions for producing the ZIP, PDF files and video are provided in Moodle.