|
ASSESSMENT 3 BRIEF
|
|
Subject Code and Title
|
GPF104: Game Production Foundations
|
|
Assessment
|
Assessment 3 - Arcade Game - Milestone 2 (Functional Game
|
|
Individual/Group
|
Individual or Group
|
|
Length
|
Playable game with win/lose condition.
|
|
Learning Outcomes
|
a) Develop a game from concept to completed work through a command of scripting, game design
and audio-visual asset generation and
implementation. Iterate and evaluate game mechanics and design to enhance user
experience, playability and game feel.
b) Identify & iterate key elements of user
experience, playability, desirability, credibility, and usability.
c) Plan and manage a project through agile methodology and related tools.
d) Develop an understanding of how audio-visual elements synthesise with game mechanics and design to influence user experience.
|
|
Submission
|
Milestone 2: Polished Arcade Game -
By 11:55pm AEST/AEDT Sunday of Module 10 (Week 10)
|
|
Weighting
|
Milestone 2 - 35%
|
|
Total Marks
|
Milestone 2 - 100 marks
|
Assessment Overview:
This summative is a direct continuation of a game that was previously proposed and planned in Assessment 1. It will be delivered across two separate Milestone (Assessment) submissions.
The Milestones will form. the basis for the expected deliverables for each Assessment. Projects are encouraged to be developed and iterated as their designs progress. These changes should be evolutions from previous states, not completely new ideas.
At submission, the game should be playable with a clear communication of progression paths, win/loss states and any other specific gameplay mechanisms. Artwork should be contextually relevant to the game, supporting the gameplay experience and the context. Audio should contribute to the user experience and context of the game while communicating interaction and relationships with the environment and other game entities. GUI should be providing a quality user experience.
The final game should be a completed work with a level of content appropriate to the design.
Additionally, the product should be polished to a high standard in terms of art, audio and gameplay. Your project should meet or exceed the expected deliverables by each respective due-date with clear adherence to your agile project structure. This will be demonstrated by regular updates tracking the progress of your project.
Milestone 2 - Functional Arcade Game (Week 10)
Overview:
For this Milestone, students are asked to further develop their prototype, and submit a fully functional product based on their milestone two (2) deliverables.
By the time of submission, the game should be playable with a clear communication of progression paths, win/loss states and any other specific gameplay mechanisms. Artwork should be contextually relevant to the game, supporting the gameplay experience and the context. Audio should contribute to the user experience and context of the game while communicating interaction and relationships with the environment and other game entities. GUI should be providing a quality user experience.
The final game should be a completed work with a level of content appropriate to the design.
Additionally, the product should be polished to a high production standard in terms of art as well as gameplay. Each aspect of the game should reflect on-going user testing, feedback and iteration.
In summary - the game experience should be complete from end to end.
Instructions / Submission:
Game:
• To be eligible for assessment, the game needs to be fully functional and should be submitted as a working executable.
• Submission should include both the executable and the project files, should be archived and named as requested in submission filename section.
Agile Project:
• Links to an accessible cloud-based project plan which reflects consistent weekly updates in- line with agile development.
• Testing logs and data from at least two play-test sessions. Testing data should be
accompanied by an analysis of the results and evidence of how they influenced the project development (approx. 300-500 words).
All group members will receive the same mark unless the project plan reflects a significant derivation from the expected workload for each individual.
Attribution & 3rd Party Content
All content derived from third party sources must be referenced using APA 6th Edition and relevant licenses must be included with project.
The (core’ of the game must not be based on complete game templates. Engine extensions are allowed. Speak with your lecturer if you need clarification.
General file structure & naming convention
Lastname_FirstName_Subjectcode_Assessment2_Milestone_2.zip
- Lastname_FirstName_Subjectcode_A2_M2_Build.zip
- Lastname_FirstName_Subjectcode_A2_M2_Project.zip
- Lastname_FirstName_Subjectcode_A2_M2_Documentation.pdf/docx
Note : If your executable requires a platform. other than Windows 10 or any peripherals other than a keyboard, mouse or gamepad then you must confirm with your lecturer the availability of these for assessment of your submission.