In this unit, you integrate and apply the knowledge and skills you have gained in your course to an industry-relevant team project. You will undertake a project as a team. Teams should be formed, and the project needs to be decided upon before the end of Week 1, with roles and responsibilities agreed upon at your project meeting in Week 2. Once the project, along with roles and responsibilities, are decided in week 2, a change of topic or team is only allowed in exceptional circumstances with approval from the Unit Coordinator (UC).  Further details of the unit are on the Moodle website. 

Technical Report Assessment: In this assessment, you will develop a solid plan to execute your selected project. The technical report will show the feasibility and capability of your team to execute the project at the end of the term. An updated version of this report will be part of your final report at the end of the semester. The report must include the following sections at a minimum, but you are welcome to have additional sections as you see fit for the project. 

• Detailed description of the project, which will overcome a business problem.
• Identify technical and reporting milestones/deliverables of the project. As different groups are undertaking different projects, you should discuss with your Project Mentor (tutor) the expected deliverables for your project.
• Review existing/competing products, solutions, or literature relevant to the project milestone and include them in the report.
• Specification of requirements, for example, functional, usability, reliability, performance, and security.
• Identify, select, and justify appropriate network and security technologies to solve the problem.
• Design a system model for the project to address the problem. This will be the design of your proposed solution to address the business problem. For example, the design description may detail network/security architectures, logical and/or physical network designs, required protocols, or algorithms involved in the design solution.
• Determine the role and responsibilities of each team member to complete the project. Include capabilities to support the role and responsibilities. Your role must match the available job responsibilities in the seek.com.au web portal.
• A draft budget in a table to show itemised costs and where the fund is coming from.
• Risk assessment and a plan to address those risks. The risk assessment must consider ethical and professional issues relevant to the project.
• List the technical hardware and software components you need to use to implement the proposed solution.

The assessment specification on your Moodle website will further detail the points above.

Format and Submission:

The report should be presented as a formal, technical document (e.g. with title, section headings, references, diagrams, tables). The report must be submitted as a Microsoft Word document. You are encouraged to use the Appendix section of your documents/files for different artefacts. For example, if your group has developed/adopted a risk assessment model to undertake a risk assessment, then the risk assessment model can be included in the appendix.  All group documents and technical artefacts must be stored on a Microsoft Teams channel created for your group by the Unit Coordinator and shared with your Project Mentor (tutor) and Unit Coordinator. With prior approval of the Unit Coordinator, a collaborative platform other than Microsoft Teams may be used. While documents are stored in Teams, they must be submitted on Moodle to receive a grade.

You may upload a draft copy of your submissions in your shared Microsoft Team folder two weeks before submission to get feedback from your mentor and UC. The draft will not be graded or mandatory but will help you get feedback for improvements, which may result in a better grade. The assessment specification on your Moodle website will further detail the draft submission in week 3.

Marking Criteria

Your Report will be marked based on the high-level criteria below. The assessment specification on your Moodle will further unfold the marking criteria below.

1. Problem definition. You should clearly and concisely describe the problem your project is trying to solve.
2. Approach. The methodologies, tools, and techniques you use to solve the problem must be appropriate.
3. Quality and depth. Your proposed project plan and solution design will need to show an investigation into significant depth, and the outputs will need to be of the quality expected of a graduate.
4. Evaluation of ethical and professional issues. Your evaluation must show that you understand the issues and identify the appropriate strategies for handling the problems.
5. Clearly articulates the team's roles, responsibilities, and capabilities.
6. Presentation. For example, formatting, grammar, and referencing.

This unit is 12 credit points and requires significant work every week with frequent assessment deadlines. Catching up will be very hard if you catch up and miss a deadline. Therefore, for all assessments, any late submissions more than seven (7) days after the original deadline will receive 0 marks.

Detailed marking criteria are available on Moodle.

Individual and Group Contributions

On the cover page, you must declare individual contributions ( even if you contributed equally) with specific details. If your report does not have an individual contribution declaration, you may receive a deduction as specified in the marking guide in Moodle. The project mentor or Unit Coordinator may seek further information from team members, including via interviews, to evaluate the contributions.

In this assessment, you will create a public e-portfolio project page, which will include your project details, including all reports and artefacts relevant to your project. The e-portfolio project page will also include weekly individual and group project progress reports. In this assessment,

• you will submit a public e-portfolio link covering and presenting your project details according to your technical reports. You can also include video and another form of presentation to make the project website useful to the public.
• you need to create a project progress reporting section in your e-portfolio project webpage where you will post weekly individual and group progress reports. There is no specific format to report your progress report, but it will marked based on clarity,  illustration ( for example, screenshots, video, or other forms), and consistency.

Expectations of Progress Reports: Each progress report must:

• explain your technical progress since the last report (or since the start of the project), with each student referring to at least one technical artefact that they have made significant contributions to
• report on the status of tasks completed since the previous progress report and any significant changes with respect to your Project Plan
• list the issues and challenges that have arisen and your approaches to addressing them
• list the priority tasks for the next phase of work (up until the next progress report and/or the end of the project)

You will be expected to answer questions about your progress report during week 9 consultation.

Contribution to Grade

• Quality of the project e-portfolio: 10%
• Individual and Group Progress Report: (5+5) = 10 %

Marking Criteria

Your e-portfolio will be marked based on:

1. Design to ensure the professional and promoting nature of the project e-portfolio site
2. Various media and artefacts like videos to explain your project, easy to find your project progress, plan and link to your project's GitHub page
3. Creativity and clarity of the design and information dissemination, respectively.

Your Project progress report will be marked based on:

1. Genuine and in-depth reflection on your experience of doing the project tasks.
2. Analysis of how this project experience will contribute to your future career goals.
3. Depth and quality of your technical contributions.
4. Ability to plan realistic and significant tasks and to complete planned tasks.
5. Identification of challenges in the project and practical approaches to deal with those challenges.

Failure to publish artefacts on Portfolium will result in 0 marks for the individual and group Project progress reports.

In this assessment, you will be able to submit a draft of your final report, which will present finalised form of the technical report submitted in assessment one with additional content about the solution you have come up with. For example, you may update your risk action plan based on your findings during the project, or you may have modified your system model ( or solution design) or logical and/or physical network designs based on your new findings while implementing the solution. The draft final report should include all the technical artefacts you have created to address the problem and implement the solution. In addition to your updated technical report content, you must include the following sections in your final report.

• Variations: what are the variations adapted in the solution since your original plan was submitted in assessment one? and why?
• Was your current skill set enough to perform responsibilities relevant to your role? why or why not?
• Explain the implementation details of your solution. This part must be written as a user manual so anyone can reproduce your work. Feel free to include video, screenshots, and other relevant information helpful to use and implement your solution in a diverse context.
• What difficulties have you encountered, and how did you address them?
• A report of security vulnerability assessment for risk score using DREAD Threat Modelling. You may also perform penetration testing or another form of security evaluation to achieve a DREAD-based risk score.
• Review the report of the e-portfolio of another group.

Draft Final Report: 20%

This assessment will be marked based on the following guidelines:

• Content quality and relevance. For example, there should be sufficient technical depth, appropriate contributions presented, interesting and clearly explained content, and reflections on learnings.
• Adhering to specifications detailed in the assessment document
• How well does the report the development since reporting in assessment one?
• Appropriateness of the solution to address the problem statements and project plan laid out in the document.
• Documentation aspect of the project for reproducing/implementing the solution by another team
• Quality and completeness of risk scoring for the proposed solution.
• Quality of the review report.

The assessment specification on your Moodle website will further detail each of the points above.

In this final assessment, you will submit the final version of the e-portfolio and report accompanying a demonstration and presentation in front of public audiences. Please submit the following material below via Moodle. 

• Final and complete version of the e-portfolio: 5%.
• Final report that addressed feedback and comments on your draft report: 5%.
• Upload PowerPoint slides and perform demonstrative presentation: (5+5) =10%.

 Updated Version of e-portfolio:

• Should report 12 weekly individual and group progress reports.
• Presented the project and state of artefacts to date upon completion.
• Clarity and professional presentation.

Final report:

• Need to address all feedback and comments from mentor and/or supervisor.
• Update the rest of the content if required based on the development of the project's solution implementation.

Upload PowerPoint and perform demonstrative presentation:

• Upload PowerPoint slides or any other materials like video demonstration.
• Present your project and demonstrate the solution live as per schedule.

You may receive a Zero (0) in this assessment If you fail to appear on the planned demonstration/presentation day. The assessment specification on your Moodle website will further detail each of the points above.

The e-portfolio will marked based on the criteria below.

• Completeness and clarity.
• Up to date content.
• Various artefacts and media will be used to make the project website useful to the general public.

Marking Criteria of Final Report:

• Does the report adhere to a formal reporting style, like a table of contents, labeling figures, and so on?
• Did the final report address all feedback and suggestions satisfactorily?

Marking Criteria of Final Presentation: It is a group presentation where all group members must present. All members will receive the same group score (unless there are exceptional circumstances, e.g., one member does not give). The score will be based on how you give your part and answer questions. Different students in your team may receive different individual scores. The presentation will be marked based on the following.

• Demonstration of prototype/system [Group]. For example, appropriate technologies are chosen and shown, demonstrating the application of knowledge and skills.
• Presentation organization and flow [Group]. For example, keeping to time limit, preparedness, visual aids, and quality of demonstrations.
• Presentation skills [Individual]. For example, speaking skills, confidence, responding to questions, and demonstrating understanding of the content.

The assessment specification on your Moodle website will further detail each of the points above.