This is not an assembly language, this is a machine language.
Machine language is anything that physically means something to the machine.
In the case of pocket computers, it's key presses, encoded into numbers in the machine. You don't give more information about this Electronika MK61 machine, so I'll give the example of the TI-57: the machine language used the number of the key given as column in the tens and line in the units. So for example, a program that would increment the memory 8 would be:
33 8 57 1 58 23
This is machine language: it's what's directly interpreted by the machine.
Assembly language would be the human readable text:
RCL 8
+
1
=
STO 8
To transform this text into the sequence of machine codes, you would need an assembler, which may be a program, or a human who would translate that text into the sequence of numbers.
The confusion is often done, because there's often a quite direct translation from the assembly language to the machine language, but this is not always an entirely direct translation: macro assemblers have powerful macros that may do a lot of work in the assembler and generate a lot of machine language instructions from a single assembly instruction. The mere translation of symbolic addresses may involve changing the op-code of the branch instructions (for example, when switching from short relative addressing to long relative or absolute addressing), so it's not always as direct as you'd think.
It's no longer advised to code directly to assembly. It was important during Nvidia FX5xxx/Radeon 9700 era. A very long time ago. Now all shaders are compiled by drivers to extract max performance out of the platform.
Use OpenGL shading language, or use Nvidia Cg to generate an assembly from C++ like code.
Best Answer
Your lecturer's statement is provably false. The Joint Strike Fighter's control code is written in C++. The 777 from Boeing uses 99%+ ADA. The JPL uses mostly C to drive spaceships.
I'm sure there are more examples but I suspect many are proprietary or classified.
Here is a paper that goes into some detail on the subject of testing avionics software on a more general level.