Reference no: EM133697129

Project Report

Assessment overview

This task addresses the following Unit Learning Outcomes:

LO 1: Reflect on practice via the application of self- and peer-evaluation

LO 2: Find, organise, and evaluate information on a range of topics related to technology challenges

Individual assessment; While you may share data and visualisations within your project group, the submission report should be completed individually.

Assessment explanation

Gather evidence of how you have contributed to your project team. Present and discuss this evidence in an individual project report.

The goal of the report is for you to communicate how you have contributed to your project team in general, and to the solution to the project brief that your team has produced. Imagine you are applying for a promotion or having a progress review with your boss, and you want to make sure they understand the value you have added to the organisation.

For consideration
We are looking for the quality of contributions, not just the existence of contributions. High quality contributions (possibly backed up by references to good professional practices) and high quality evidence leads to a higher mark.

Task
The report should be around 3000-4000 words, excluding references. A word count should be included that excludes the title work
statements, table of contents and references. Reports over 4000 words will be assessed on the first 4000 words as determined b e assessor.

This is an individual task with a fixed deadline -- late penalties apply beyond the due date and no submissions will be accepted after the closing date.

Instructions

1. Before submitting, you must read the declaration
Note a cover page is not required, however please put your preferred name and student ID on at least the first page, ideally all pages.
A statement of who contributed to the work and how is required.

Generative Al tools used must be included in this statement -- note that output from generative Al tools is not permitted to be used for assessment and any sections identified as using them (by you or by the markers) will not be assessed.

2. As semester progresses, note down your contributions to and actions on the team project. This does not have to be in submittable form, however dated and in a document or folder is fine at this stage. A board (e.g., using Trello or a physical board) might also be helpful. Items that might be useful include:
Code snippets
VCS histories
Meeting minutes
Emails/digital chat messages from team mates
Towards the end of semester, start the final document. Sort your ideas into the relevant headings as noted below. If you have regularly tracked your contributions, this should be a straightforward task to create a story.

Proof-read and edit before you submit. I do recommend making use of LAS and Studiosity as well, but note these services might have a few day's turnaround time.

Use the following structure as a guide.
1. Introduction
Provide a brief overview of the report, the context of the project, and what you will discuss.

2. Contributions

The "Contributions" section should make up the bulk of your report, and contain technical details where appropriate (e.g., technical diagrams, code snippets).

2.1 Code Contributions
Describe and provide evidence for how you contributed to the code your team delivered. Include representative code snippets and explain how they work. Evidence of your contributions could include version control history, screenshots of emails or chats showing you sharing your work, or meeting minutes. Reflect on the value and quality of your contributions.

2.2 Design Contributions
Describe and provide evidence for how you contributed to the design of your team's solution. This could include but is not limited to
the user interface, software architecture, and database schema. Evidence of your contributions could include emails or chats showing you sharing your work, meeting minutes, or document edit histories. Reflect on the value and quality of your contributions.

2.3 Team Contributions
Describe and provide evidence for how you contributed to your team. This could include but is not limited to engagement vt - the project, attendance at meetings, punctuality, timely work completion, leadership roles, organisation, and other administrative activities. Evidence might include meeting minutes, chat messages or emails, testimonials from team members, or document edit histories. Reflect on the value and quality of your contributions.

3. Learning Outcome Reflection
Describe and provide evidence for how you have met each of the unit learning outcomes. Include one sub-section for each learning outcome. The learning outcomes are:
Assess the role of programming principles in a variety of settings
Reflect on practice via the application of self- and peer-evaluation
Apply knowledge of advanced programming fundamentals to technology challenges
Demonstrate the ability to work as an effective team member using simple project management tools
Find, organise, and evaluate information on a range of topics related to technology challenges
Consider and reflect upon social and cultural perspectives that impact on learning and working in a team

4. Summary
Provide a brief summary of the report and what you discussed.
References
A list of references you used. All references should be referred to in the main text of the report.

Referencing style: APA 7