Reference no: EM133555198 , Length: word count:3400

Project Report

Report Details
While you may share data and visualisations within your project group, the individual project report should be completed individually.

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.

Your report should be 3000 - 4000 words, excluding references.

Sections and subsections should be numbered (e.g., 1. for the first main section, 1.1 for the first subsection).

Use the following structure:

1. Introduction
Provide a brief overview of the report, the context of the project, and what you will discuss.

2. Contributions

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 ContributionsDescribe and provide evidence for how you contributed to your team. This could include but is not limited to engagement with 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 o nthe value and quality of your contributions.

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:

• Have an understanding of programming
• Demonstrate reflective practice, and use self and peer evaluation
• Apply knowledge of programming fundamentals to technology challenges
• Learn collaboratively in a team environment
• Find, organise, and evaluate information on a range of topics related to technology challenges
• Demonstrate awareness of social and cultural perspectives that impact on learning and working in a team

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