Can Rev-Trac ensure developers are not unintentionally changing an object currently being tested in QAS?

Yes. Rev-Trac extends SAP's own locking concept beyond the time of transport release, and extends the SAP locking concept to include configuration as well as workbench objects. Rev-Trac's extended locking system ensures that a developer who starts to change an object or configuration that is currently awaiting testing in QAS is notified that the object or configuration is locked to a particular Rev-Trac request, and that all changes to this this object or configuration should be recorded against the same Rev-Trac request.

A mechanism exists to loosen this restriction in specific circumstances, or on a case-by-case basis, if required. Locks are dropped when a change reaches production.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.