Re:Why Don't People Use Formal Methods?
by kiriakasis on Tuesday January 22, 2019 @06:43AM
(#18967585)
> it implies an often unrealistic separation between writing specs and writing implementations
I think that part of the problem is that small modification in the spec can lead to enormous changes in the proofs
think this is a bit of an overstatement, because it implies an often unrealistic separation between writing specs and writing implementations
Every government IT project that is years late and billions over budget is because of this
Re:Why Don't People Use Formal Methods?
by dragonwriter on Tuesday January 22, 2019 @03:50AM
(#18966949)
> Every government IT project that is years late and billions over budget is because of this
Well, that used to seem to be true before governments started experimenting with (methodologies which were notionally versions of) Agile, Lean, and related ideas. Then there were a whole new set of reasons for IT projects being years late and over budget.
Re:Why Don't People Use Formal Methods?
by aaaaaaaaaab on Tuesday January 22, 2019 @04:01AM
(#18967002)
False. Writing a waterfall-style “spec” on paper has nothing to do with formal methods.
I think this is a bit of an overstatement, because it implies an often unrealistic separation between writing specs and writing implementations. There may be several levels of each, and the middle levels may overlap.
For example, it may well be the case that the management on a project don't get heavily involved with the technical details and just specify "A needs to communicate with B" as part of the high level requirements. That doesn't mean the technical people responsible for implementing those requirement won't specify detailed protocols at a lower level and wouldn't benefit from formal methods to help ensure correct implementation.