What I am almost positive about, but will have to check (and I’ll tell you why that is interesting to me privately), is that their toolset does support triggers that enforce the existence of, status of, other artifacts. Such as – compilation without warnings, etc, etc. So, enforcing a ‘pass’ on static checking should be possible.

It’s been a while since I was involved in configuring and supporting the toolset and since then they have, I have heard, been busy with improvements and enhancements. Recently I have been told there are some new updates coming to their web site that will better represent the latest round of improvements.

FWIW: this is the paradigm upon which the culture and processes that enabled the team with the most rewarding project (yes, that one!) of my career to be and do what they were and did.

They were created, and progressively improved as he moved on, by someone I worked with at the second enterprise who eventually started a company to make available to more enterprises as a commercially available set of tools the latest in the evolution of these excellent CM/SW Project Management tools.

I could expound at length on the unique set of abilities his tool paradigm – the result of the requirements of developing reliable switching software – possess that make sense and contribute to the sanity (and quality) of mission critical software projects, but not here, and not now.

I strongly suggest taking a peek at the company’s web site, though: http://www.neuma.com/index.html