Criteria
| Achievement | Achievement with Merit | Achievement with Excellence |
| Use Complex processes to develop a digital technologies Outcome. | Use Complex processes to develop an informed digital technologies Outcome. | Use Complex processes to develop a refined digital technologies outcome. |
| Involves: | Involves meeting the Achieved criteria, plus: | Involves meeting the Merit criteria, plus: |
| Using recognised and appropriate Project management techniques to plan the development of a digital technologies Outcome. | Effectively using Project management techniques to manage development, Feedback, and/or collaborative processes. | Synthesising information gained from the planning, Testing, and Trialling of components. |
| Decomposing the digital technologies Outcome into smaller components. | Effectively Trialling multiple components and/or techniques. | Discussing how this information led to the development of a high-quality digital technologies Outcome. |
| Trialling components of the Outcome. | Effectively using information from Testing and Trialling to improve the functionality of the digital technologies Outcome. | |
| Testing that the digital technologies Outcome functions as intended. | ||
| Addressing relevant implications. |
Relevant Implications
Project Management Techniques
Can be but are not limited to.
- Agile, Kanban, or waterfall techniques
- version Control
- collaboration and communication
- managing assets
- code review
- Project Scheduling
Step-By-Step Guide
Understanding What Assessors Are Looking For
Achieved
You must show that you:
- Used recognised Project management techniques.
- Broke your Project into smaller parts.
- Tested your Outcome.
- Trialled important components.
- Addressed relevant implications.
- Developed a functioning Digital Outcome.
Merit
You must additionally show that you:
- Used Project management techniques effectively.
- Managed Feedback and development throughout the Project.
- Trialled multiple solutions.
- Used Testing and Trialling information to improve functionality.
Excellence
You must additionally show that you:
- Synthesised information from planning, Testing and Trialling.
- Explained how all this information worked together to create a high-quality Outcome.
- Produced a refined and high-quality final Outcome.
General Rules
For every section:
Use Evidence
Include screenshots of:
- GitHub commits
- Trello/Kanban board
- Testing records
- Trialling records
- User Feedback
- Design changes
- Working features
Do not just insert screenshots.
Always Explain:
- What the evidence shows.
- Why you did it.
- What was learned.
- How it affected your next steps.
This explanation is what earns Merit and Excellence.
Development Process Sections
The sprint sections are where you tell the story of your Project.
A good sprint write-up should include:
What was planned?
Example:
My goal for Sprint 1 was to create the database structure and establish communication between the front-end and back-end.
What was developed?
Example:
I created three database tables and wrote the initial connection scripts.
What Testing was completed?
Example:
I tested whether records could be added and retrieved correctly.
Problems encountered
Example:
Foreign key relationships were causing insertion errors because records were being added in the wrong order.
Changes made
Example:
I modified the database logic and introduced validation checks.
Evidence
Insert:
- GitHub commits
- Screenshots
- Testing evidence
- Trello tasks
Sprint 1
Focus on:
- Initial planning
- Requirements gathering
- Research
- Project setup
- Early prototypes
Questions to answer:
- What was your objective?
- What did you build?
- What did you learn?
- What problems emerged?
Sprint 2
Focus on:
- Core functionality development
- First major features
Questions:
- What requirements were implemented?
- What Testing occurred?
- What modifications resulted?
Sprint 3
Focus on:
- Expansion of features
- Integration of components
Questions:
- How did different parts work together?
- What challenges arose?
- What Testing informed improvements?
Sprint 4
Focus on:
- Refinement
- User Feedback
- Bug fixes
Demonstrate:
- Testing results
- Feedback collection
- Changes based on evidence
Sprint 5
Focus on:
- Advanced features
- Optimisation
Demonstrate:
- Improvements in quality
- Features added because of user needs
- Trialling different approaches
Sprint 6
Focus on:
- Final refinements
- Quality assurance
Demonstrate:
- Comprehensive Testing
- Final Bug fixes
- Preparation for deployment
Final Submission
Summarise:
What was completed?
Describe the final Outcome.
What improvements were made?
Show the evolution between the first and final versions.
What evidence demonstrates quality?
Examples:
- Testing records
- User Feedback
- Screenshots
- GitHub history
Project Management Techniques
Version Control (GitHub Log)
Insert screenshots showing:
- Multiple commits
- Regular development
- Feature development over time
Good evidence includes:
- Meaningful commit messages
- Development across multiple weeks
- Branches if used
Bad example:
Final version uploaded
Good example:
Added login validation
Fixed session Bug
Improved database Query efficiency
Kanban Board (Trello)
Insert screenshots showing:
- To Do
- Doing
- Done
Assessors want to see:
- Tasks being moved
- Progress being tracked
- Planning throughout development
Not just a finished board.
How Have You Used Project Management Techniques?
Describe:
Planning
How Trello helped organise work.
Development
How GitHub helped track changes.
Communication
If working in a team:
- meetings
- messages
- task allocation
Monitoring
How progress was reviewed.
A strong answer connects Project management tools directly to development decisions.
How Has Your Use Been Effective?
For Merit, Explain effectiveness.
Use phrases like:
Trello allowed me to Identify delayed tasks and reprioritise work.
GitHub helped me quickly revert broken code after Testing identified a Bug.
Feedback from users was converted into new Kanban tasks, ensuring improvements were tracked systematically.
Testing and Trialling
Many students confuse these.
Testing
Testing asks:
“Does it work?”
Examples:
- Login works
- Database stores Data
- Program produces correct output
Testing table should show:
| Feature | Test | Expected Result | Actual Result | Pass/Fail |
|---|---|---|---|---|
| Login | Enter valid credentials | User logs in | User logs in | Pass |
Include screenshots.
Trialling
Trialling asks:
“Which solution is best?”
Examples:
- Two navigation layouts
- Two database structures
- Two algorithms
- Two interface designs
You must compare alternatives.
Example:
| Option A | Option B |
|---|---|
| Simpler | More scalable |
Then Justify why one was selected.
This is essential for Merit.
How Did You Trial More Than One Way?
Structure:
Problem
What needed solving?
Option 1
Advantages and disadvantages.
Option 2
Advantages and disadvantages.
Evaluation
Which was better?
Decision
Explain why it was selected.
Example:
I compared storing user information in JSON files and a MySQL database. While JSON was simpler initially, MySQL offered better scalability and security, making it more suitable for the Project’s long-term requirements.
How Did Testing and Trialling Improve Functionality?
Do not say:
Testing found bugs.
Instead say:
Testing identified users could submit empty fields. I added validation to prevent incorrect Data entry, improving Reliability and user experience.
Show:
- What Testing revealed.
- What changes were made.
- How functionality improved.
High Quality Outcome
This section is crucial for Excellence.
How Did You Synthesise Information?
“Synthesise” means bringing multiple sources of information together.
Discuss:
Planning
What requirements existed?
Testing
What issues were found?
Trialling
What solutions were evaluated?
Feedback
What users suggested?
Then Explain how these informed one another.
Example:
User Feedback identified navigation issues. Trialling different menu designs indicated a sidebar layout was more efficient. Testing confirmed users completed common tasks more quickly, leading to implementation of the sidebar navigation System.
How Did This Lead to a High Quality Outcome?
Discuss quality indicators such as:
- Reliability
- Usability
- Accessibility
- Functionality
- Performance
- User satisfaction
- Appearance
Example:
The combination of Testing, user Feedback and Trialling resulted in a more intuitive interface, reduced navigation errors and improved overall Usability, contributing to a high-quality final Outcome.
For Excellence, your answer must link evidence directly to Outcome quality.
Relevant Implications
Choose THREE implications.
The strongest choices are usually:
- Privacy
- Accessibility
- Usability
- Intellectual Property
- Legal
- Functionality
Structure for Each Implication
What is the Implication?
Define it briefly.
Why is it relevant?
Explain why it mattered in your Project.
What actions did you take?
Provide specific examples.
What was the result?
Explain the impact.
Example: Privacy
My application stored user information, making privacy an important consideration. Passwords were not stored directly and sensitive Data was protected through authentication controls. This reduced the Risk of unauthorised access and helped Ensure user information remained secure.
Example: Accessibility
I used high-contrast colour schemes, clear navigation and readable font sizes. These decisions made the Outcome easier to use for users with visual impairments.
Example: Intellectual Property
All images were either self-created or sourced from Copyright-free repositories and appropriately attributed. This ensured compliance with Intellectual Property requirements.
Final Excellence Checklist
Before submission, make sure you can answer YES to all of these:
If you can Support all of these with evidence and detailed explanations, you will be providing strong evidence towards Excellence in AS 91907.
- I have evidence from six sprints.
- I included screenshots throughout.
- GitHub commits clearly show incremental development.
- Trello demonstrates ongoing Project management.
- Testing evidence shows functionality.
- Trialling evidence compares multiple solutions.
- I Explain how Testing changed my Outcome.
- I Explain how Trialling changed my Outcome.
- I Discuss effectiveness of Project management.
- I synthesise planning, Testing and Trialling information.
- I Explain how this led to a high-quality Outcome.
- I fully Address three relevant implications.
