See, so, this is where the process experts come in.
Why go after an antiquated process? That we already know in advance doesn't meet modern security standards?
Here, look: controlling a process is expensive. The tighter you have to control it, the more expensive it gets
So, why not go the other way when you can? In this case, an open adversarial process yields the desired results, more quickly, more cheaply, and more efficiently than a streamlined but highly regulated one. The key words are checks and balances.
It can get very simple. When you go to vote - if you're a Republican, you get checked in by the Democrat election workers. Adversarial step #1. If you're a Dem, you get checked in by the Pubs.
Then, you have a same-party person give you your actual ballot, after checking that the opposite party properly did its job at check in. And you have someone from the opposite party watching when you place your ballot into the collection box.
These are deliberately adversarial process, it works, and it's cheap. But it has to be followed to the letter. So you need enforcers from each party watching the workers, and you need an oversupply of trained workers because you want everyone to be yankable at any time for any reason. (But attach a lot of legal paperwork to it, and a stiff penalty for abusing the process).
I can expound on this method in detail, if you wish. You can ask the Six Sigma people in the manufacturing world, or the Scrum type in the software world, how this all works and the wisdom of it.
The best systems are those that are self correcting and require no maintenance. Good luck finding one, but that's what we strive for.
As far as the programming - that too should be adversarial. Ask anyone at NASA how that works, they'll tell you about design reviews and functional reviews. Y'know, you have a bunch of engineers sitting in a room and one of em says "all we gotta do is put this switch on the front panel", and then some QA guy says "front panel's already full, where you gonna put it?", and the instant they hear THAT the ergonomic psychologists take over and don't let go till they've figured out the exact best location where a human being can access that switch in an emergency.
So like, if you're a Scrum boss trying to implement this, you don't have to worry about the "why's", that's already been decided in the context of a much larger adversarial process. Similarly, if you're an election worker, you shouldn't have to know about the "why's". In fact you shouldn't even be involved with them. Engineers on Scrum teams who question the requirements 'after the fact" generally don't last long. They're viewed as excuses for slipping the schedule.
Similarly, the QA guy follows the test plan. He doesn't write it, someone else does that. He only figure out how to test every unit so it meets the requirement.
A well designed process is worth an untellable fortune. Once you have some experience with mission critical processes (which is what voting is), you'll understand why the adversarial approach is so important and so beneficial (and in a partisan world, so natural). The last thing in the world we want is some partisan dictator determining our election processes, amirite? Done the adversarial way, there's little danger if that. There'll be a hundred adversarial alarm bells if even the smallest untoward event happens