Format and Structure
Once you have completed your workplace activity, you will need to write your final submission.
(Remember, you will need to have had your summary signed off by your DLC before completing your workplace activity, and writing and uploading your final submission.)
Your final submission should be text based and you should break down each learning area as listed in the Evidencing your knowledge, skills and behaviours step.
Your final submission can be written in one the following acceptable file formats: .pdf, .doc, or .docx.
The maximum file size is 750 MB.
You may include screenshots, diagrams, and other images as supporting evidence.
Your submission should also include:
- plans such as class diagrams.
- Java code.
- evidence of usage of Git.
- evidence of code review (e.g. screenshots or comments on GitHub).
- evidence of manual and unit testing in the form of a basic test plan and the associated results.
The following list is a reminder and checklist of what you should explain in the introduction section of your final submission.
- Description of the project.
- The approach.
- Project outcomes.
- How the KSBs are evidenced through your workplace activity.
- How the project was assigned to you.
- The stakeholders you liaised with for this.
- The key requirements.
- Other considerations e.g., budget.
- The way you interacted with various stakeholders.
You may be working in sensitive or restrictive environments, which means that you cannot share certain information. In cases like this, you can anonymise anything you complete.
It is also important for you to recognise where you should be redacting information when sharing evidence with third parties. This demonstrates good practice in security, and compliance with your company’s security policies.
When providing evidence during your apprenticeship journey, it is recommended that you use the STARRS method for each work task you are describing. This will provide you with a clear direction on how to structure the required evidence into the portfolio.
- What is the situation?
- What is the issue/problem that needs solving?
- What were you tasked with doing?
- What were your objectives?
- What did you do, and what did the task involve?
- Explain your tasks and responsibilities.
- What did you do?
- How did you do it?
- Who did you communicate with?
- What tools did you use? (This is where you can provide your screenshots/evidence.)
- What did you do after you completed your actions?
- Did anything need updating?
- Did you communicate with anyone?
- What was the conclusion?
- What did you do well?
- What didn’t go as well as you had hoped?
- In later stages, when you look to consolidate your portfolio, have you provided the best evidence from your apprenticeship work?
- Do you need to collate additional supporting evidence?
When you're ready, select Next to continue.
This Course provides you with information about how to get started and how to create, structure and submit your Apply stage activity evidence for Object Oriented Programming.
A world-leading tech and digital skills organization, we help many of the world’s leading companies to build their tech and digital capabilities via our range of world-class training courses, reskilling bootcamps, work-based learning programs, and apprenticeships. We also create bespoke solutions, blending elements to meet specific client needs.