292 karma · joined October 25, 2009
In the current environment - I would contact the TPOC - it could just be stuck in limbo.
Tool-wise - refactoring was a bit of a pain.
The ones I have worked with have no problem telling management to go pound sand when they are pushing schedule.
It's great for reviews where any given reviewer could be expected to have a misunderstanding of certain details or skip a section (RAG somewhat helps this) - but it's frustrating for artifact generation where missing details cascade through the project.
As great as the technology (right now) it seems so far from reliable business process automation.
The intent isn't to make your code bullet-proof. It's to move towards a subset of the language with well-defined semantics.
Any safety critical coding standard work I've done always had a waiver process for both MISRA and mccabe-like complexity requirements - the intent is there's always some point where there is diminish returns for compliance.