🛠️ DTSP K22: The Engineer’s Toolkit | UML, Testing & Debugging

Welcome to the core skills series for the Digital and Technology Solutions Professional (DTSP) Degree Apprenticeship.
I'm Sam, your Lead Tutor.
In this session, we tackle Knowledge 22 (K22): Principles of development techniques and artefacts.
We move from the process (SDLC) to the tools. Learn how to use UML, Unit Testing, and Debugging to create the professional artefacts that prove your engineering rigour.
IN THIS VIDEO:
Technique vs. Artefact: Understanding the difference between the action and the evidence.
UML Explained: Class, Sequence, and Use Case diagrams.
Unit Testing: Why coverage matters and how to evidence it.
Debugging: Moving beyond guessing to systematic fault finding.
Frameworks & Architecture: How to structure your projects professionally.
Role-Specific Guides: How Software Engineers apply these tools daily.
Workplace Action: Simple tasks to generate artefacts tomorrow.
Portfolio & EPA: The STARR template to showcase your toolkit.
Major Project: Which diagrams and reports you must include.
ADDITIONAL DETAILS:
Your problem, solved! Find the exact answers you need below:
Slide 2: What is an artefact?
Slide 3: When should I use UML?
Slide 4: What is a Unit Test?
Slide 5: How do I document debugging?
Slide 10: How do I write the K22 STARR reflection?
Slide 11: What diagrams do I need for my Major Project?
➡️ Download the full presentation slides and transcript from our EPA Hub:
www.mentorinai.com/epahub/
Timestamps:
00:00 Welcome! The Craftsman’s Workshop
01:30 Decoding K22: Technique vs. Artefact
03:00 Technique 1: UML (Unified Modeling Language)
04:15 Technique 2: Unit Testing
05:30 Technique 3: Debugging
06:45 Technique 4: Frameworks & Libraries
08:00 Technique 5: Software Architecture
09:15 Pathway Specific Application
10:30 Workplace Application: How to Start
11:45 Portfolio Evidence: The STARR Method
13:00 Implementing K22 in Your Major Project
14:15 Summary & Next Steps
EPA Checklist: The K22 "What, How, Why"
What: Did I identify the technique (e.g., UML)?
How: Did I produce the artefact (e.g., The Diagram)?
Why: Did I explain how this technique improved quality or understanding?
Affiliate Links:
Enhance your Technical skills with these recommended courses:
Udemy: UML and Object-Oriented Design for Beginners
Pluralsight: Unit Testing with JUnit/NUnit
(We may earn a commission if you sign up through these links).
Join our newsletter for weekly tips: www.mentorinai.com
Need help? Book a Mock Interview or Portfolio Review today!