It seems to me that in your case the relevant part is engineering, the standards are the real thing and programming is there to support them. This is not the case in my experience, where programming involves creating a new web site, a new database schema, a new game. There is little to no engineering on these fields, every day you see a newfangled "architecture" or "framework" or "API". EE is a much more standards driven arena, CS is not, IMO.

Agreed.

Yet, the parent is talking about "programming", that is still the most important part (although still a part) of a Software Engineering project.

Software Engineering is a recognized discipline, and although I do work in an EE environment, I believe most software projects (which have a contractual obligation with a definite scope and a deadline) use it in a form or the other.

Why would you be doing that? That sounds awful. I hope you're being compensated well.

Consider spending some of your day to automate these tasks. It sounds easily automatable.

I wrote a script that checks that Python scripts conform to standards and it worked well and saved a lot of time. Perhaps something like that would save you a lot of time and allow you to spend your working day doing something more fullfilling.

I wish the best of luck to you sir!

SPMP - Software Project Management Plan?

SQAP - Software Quality Assurance Plan?

SCMP - Software Configuration Management Plan?

SRS - Software Requirements Specification?

I've seen "engineering" defined as "statics, dynamics, and thermodynamics", but what you've listed sounds much more like engineering to me.

Yup. IEEE 1558-2004.

I might be wrong, but I believe "Software Engineering" is a more common concept in Europe than US, since many "Computer Science" degrees are actually part of Engineering Universities curricula.

That is to say, many universities are more likely to offer a "Software Engineering" degree rather than a "Computer Science" one. But it might be only my experience.