Setup for Project
We now need to setup your folder structure
In your folder "12DI - Your Name" Create the following folders
"Project Assets"
Then create each of the following folders for each assessment you are doing.
In your folder "12DI - Your Name" Create the following folders
"Project Assets"
Then create each of the following folders for each assessment you are doing.
|
Year 12:
"AS91897 - Advanced Outcome" (This one is compulsory) "AS91893 - Digital Media" "AS91891 - Design Concept" "AS91896 - Programming" |
Year 13:
"AS91907 - Complex Processes" (Compulsory) "AS91901 - Concept Design" "AS91903 - Digital Media" "AS91906 - Programming" |
Go to those pages and download the documentation templates into their folders
Project Timeline - Gantt Chart
For this task you will be creating a Gantt Chart based on how long your project will take.
In order to pass AS91897 and AS91907 this chart will be important
Click here to get started:
https://www.onlinegantt.com/#/gantt
In order to pass AS91897 and AS91907 this chart will be important
Click here to get started:
https://www.onlinegantt.com/#/gantt
|
Gantt charts are used to manage time lines for massive projects.
We can use a Gantt chart as part of your learning for AS91897 and AS91907. We as teachers need to see your project timelines for this, broken down into small sections. |
|
|
Change the colours to match what stage you are up to.
You can use the days to help organise time. |
|
Create dependencies if certain jobs need to be done before others.
Use the dependencies to help when you start and finish |
|
You will need to take into account school holidays, exam leave etc etc.
| ac_-_digital_innovation_y12.pdf |
| ac_-_digital_innovation_y13.pdf |
Important Dates for 2025
Event |
Date |
School starts |
10th Feb |
Term Break 1 |
12th April-27thApril |
Term Break 2 |
29th June-13th July |
Achieved hand in date |
10th September |
Term Break 3 |
20th September-4th October |
Hand in date |
17th October |
Remember that we also have Exam Week, Public holidays and you will get sick occasionally.
We will be dedicating one week to study for the exam.
We will be dedicating one week to study for the exam.
Relevant Implications (2 Lessons)
Year 12From the learning that we have done earlier. Complete the first columns of Relevant implications
You are not going to address the implications just yet If you need to fill in multiple sets of documentation for this, copy and past Documentation: AS91894 - Electronics Outcome AS91891 - Concept Design AS91893 - Media Outcome AS91897 - Digital Outcome (Compulsory) |
Year 13From the learning that we have done earlier. Complete the first columns of Relevant implications
You are not going to address the implications just yet If you need to fill in multiple sets of documentation for this, copy and paste Documentation: AS91901 - Concept Design AS91903 - Media Outcome AS91907 - Complex Processes AS91904 - Electronics |
Relevant Conventions/User Experience(3 Lessons)
Media Outcome and Concept Design Students Only
Year 12With an Idea, Potential End Users, Requirements and Specifications it is now time to complete your relevant implications document and research relevant conventions for your outcome.
Convention Definition: "The rules that are generally understood and accepted when producing a media text, in particular genre" 
In the case of this video game listing hearts or life points in a corner of the screen is a convention. Using hearts and the colour red to depict health is also a convention.
ou can use Chat GPT to help generate a list of conventions for your outcome. Research conventions for your outcome, have websites as sources for conventions for your outcome. Document Conventions: "AS91893 - Media Outcome: update documentation with conventions you are going to use when creating your art assets" "AS91891 - Concept Design - Complete the investigation part for relevant conventions" |
Year 13UX is its whole own area in the technology industry. User Experience experts study all aspects of usability, functionality, aesthetics and similar relevant implications to better understand how people use technology. With knowledge of how and why people use things we can better design our tech so that people can use it with little to no training, and hopefully also even enjoy using it.
Consider times that you have used an interface and found it frustrating/given up on it. What made you feel this way? Things like an interface being unintuitive, hard to use, or unresponsive will make users feel frustrated or even stupid. Ultimately, as creators of an interface/interactive system, we want our users to feel smart. Our goal is to create software (or hardware) that is so easy to use that people feel like experts. The Freyberg Digital UX page talks more about this from a web design point of view, but much of the content is relevant and is worth looking over. What you need to do throughout your project (both now and continuously) is consider how users use your game. Something bad can clearly be improved, but good things can always become better too. No matter how good and usable you think your game is, it can still become better and easier to use. Do some research about UX in game design and consider what kinds of things you will focus on in your project. Here are a few sites to get you started: https://indiegamehaven.com/good-vs-bad-game-design/ https://uxplanet.org/five-examples-of-terrible-game-ux-777fea291990 Documentation: AS91903 - Digital Media As91901 - Concept Design 
Good or bad UI? I'll let you decide.
|
Concept Design Assessment 5 Weeks
If you are working on the concept design Assessment, now is the point in which you have to complete this assessment.
You should be able to complete this in about 3-4 weeks.
Follow the page to complete this.
This can be marked and handed in, term 1.
Year 12 - AS91891
Year 13 -AS91901
You should be able to complete this in about 3-4 weeks.
Follow the page to complete this.
This can be marked and handed in, term 1.
Year 12 - AS91891
Year 13 -AS91901
Project Management Tools (3 Lessons)
Begin the project management tools section in the complex processes documentation. Choose 3 project management tools that you are going to use, set them up and learn to use them.
Documentation:
Yr12
AS91897 - Digital Outcome
Yr13
AS91907 - Digital Outcome
Documentation:
Yr12
AS91897 - Digital Outcome
Yr13
AS91907 - Digital Outcome
Skill Training (Max 3 Weeks)
Spend this time upskilling yourself on the skills that you lack, follow tutorials, ensure that you are mostly up to speed for your assessment when it occurs.
You will have to learn skills past this week. But you should have some idea of where to go from here.
You will have to learn skills past this week. But you should have some idea of where to go from here.
Create a Design - Electronics Only (1-2 Weeks)
Create a design for your circuit
Documentation
Create a design for your circuit
Explain how it works
Test and refine your design to create a new Design
Documentation
Create a design for your circuit
Explain how it works
Test and refine your design to create a new Design
Trialing Components - Digital Outcome, Electronics (4 Weeks)
Important note on iterative development: two of the achievement standards that we are using have iterative development requirements. You will start with AS91907/AS91897 Complex Processes as you iteratively develop your components. Later in the project you will iteratively develop your entire project in AS91903/AS91893 Digital Media. Focus on 91907/91893 first (over the next 4 weeks), then focus more on AS91903/AS91893 after you have a prototype.
Naturally there will be some overlap and it may make sense to add final component updates back to AS91907/AS91897 toward the end as well.
Tasks:
Break down your outcome into smaller components:
- Art assets, sound assets, scripts
- Update AS91907/AS91897 with the break down.
- Start creating your outcome.
Documenting the iterations of your components in the complex processes iterative documentation.
Year 13:
Remember: for Excellence in 91907 you need to include a synthesis of information from planning, testing and trialing components. You aren't necessarily "simplifying" information because this might mean losing information, a better way to think about it would be condensing multiple parts into a single more manageable part.
Make sure to clearly document any "synthesis statements" and evidence of how you address these. Show how you have incorporated user suggestions and feedback to improve the usability, aesthetics, and functionality to produce a high-quality outcome.
Documentation:
AS91907 Complex Processes - Testing and Trialling components
AS91897 - Advanced Processes - Testing and Trialling components
Naturally there will be some overlap and it may make sense to add final component updates back to AS91907/AS91897 toward the end as well.
Tasks:
Break down your outcome into smaller components:
- Art assets, sound assets, scripts
- Update AS91907/AS91897 with the break down.
- Start creating your outcome.
Documenting the iterations of your components in the complex processes iterative documentation.
Year 13:
Remember: for Excellence in 91907 you need to include a synthesis of information from planning, testing and trialing components. You aren't necessarily "simplifying" information because this might mean losing information, a better way to think about it would be condensing multiple parts into a single more manageable part.
Make sure to clearly document any "synthesis statements" and evidence of how you address these. Show how you have incorporated user suggestions and feedback to improve the usability, aesthetics, and functionality to produce a high-quality outcome.
Documentation:
AS91907 Complex Processes - Testing and Trialling components
AS91897 - Advanced Processes - Testing and Trialling components
Rough Prototype (4-6 Weeks)
Complete a rough prototype of your game, get everything working to an achieved level. Don't worry too much about the detail at this stage.
|
Year 12:
Programming: Ensure you have met the requirements for programming, have you included 2 arrays and are you changing data inside in them? Media: Have you used at least 2 advanced techniques? Electronics: Have you used at least 2 advanced techniques? |
Year 13:
Programming: Ensure you have met the requirements for programming, are you meeting the criteria tagged with red on the marking criteria? Media: How's your UX? Are you addressing it? Are you meeting the red tags on the marking criteria? |
Testing (2 Weeks)
Test your outcome and make according to the specifications and requirements.
Documentation:
AS91893/AS91903 Media: Testing
AS91894/AS91904 Electronics: Testing and Debugging
AS91896/AS91906: Programming
AS91897/AS9107: Testing based on requirements.
Documentation:
AS91893/AS91903 Media: Testing
AS91894/AS91904 Electronics: Testing and Debugging
AS91896/AS91906: Programming
AS91897/AS9107: Testing based on requirements.
Iterative Development (2-4 Weeks)
Once you have a completed prototype it is time to begin Iterative development
Gather feedback and complete different iterations of your project
Documentation:
AS91893/AS91903 Media: Iterative Development
AS91894/AS91904 Electronics: Iterative Development
Gather feedback and complete different iterations of your project
Documentation:
AS91893/AS91903 Media: Iterative Development
AS91894/AS91904 Electronics: Iterative Development
Addressing Relevant Implications (1 lesson)
Document how you addressed relevant implications (using screenshots).
Summaries (1 Week)
Write up the summaries for the assessments you need to.
Documentation: AS91907/AS91897 Digital Outcome - Summary
Documentation: AS91907/AS91897 Digital Outcome - Summary
