Discussion topic: Management of Change with (e.g.) VCC (or annotated code in general)

Apr 28, 2010 at 1:10 PM
Edited Apr 28, 2010 at 1:11 PM
Hi, management of change (e.g. http://en.wikipedia.org/wiki/Change_management_(engineering) ) deals with processes that have to be executed when issues or new requirements with source code come up (e.g. in issue tracking tools, version control systems etc.). That one has to use change manamgement in standards such as e.g. for avionics DO-178B ( http://en.wikipedia.org/wiki/DO-178B ). VCC reasons about source code. What I want to ask is whether anyone is aware of guidelines on/processes for/papers on management of change where code annotations such as VCC of more generally other formal methods (say, Isabelle, PVS ...) are used for proving properties for source code. Management of change in this context would include updating properties and/or proofs once the underlying source code changes. (Yes, the question is not specific to VCC, but this forum seems an appropriate starting point to raise this question.) To be frank, the reason I am asking here is that a reviewer contested my statement that no well-established guidelines/processes exist (nor that much research had been done in the field. I'm also considering to post this question to broader/other forums, but this here seems a "first check"). Thanks, Holger