3 ms·
Okay, so the software is now provably correct.. now what were the costs in doing so, both in additional time pre-writing definitions and other abstractions for
by tracker1 11y ago
Okay, so the software is now provably correct.. now what were the costs in doing so, both in additional time pre-writing definitions and other abstractions for the software itself? Also, how does one prove that said software actually meets the business needs behind said software?
In an academic environment, or something tied to physical devices, this approach isn't a bad one at all... These are settings where software is much more akin to an engineering discipline than it is a craft.
In most software development, which are in any number of business environments building/adapting or bridging custom software that will run in any number of environments... the additional time that this will take over current approaches will be simply unacceptable. Most people don't care if a software is provably correct.. and for that matter, most bugs aren't critical in nature, and don't lead to end of the world scenarios... since most systems don't actually touch personal medical information or financial data.
I think on an intellectual level that approaches like this for some systems make a lot of sense... The problem is rarely do you have well defined interfaces/algorithms for well defined problems... so, you build your system with provably correct software, then the proverbial moose's neck breaks, because you didn't know about the moose.
- Wayne17 11y agoIn the context of physical systems, companies in the Netherlands including ASML, FEI, Philips Healthcare and Ericsson, have found in the past 10 years that applying model-checking to concurrency logic in control systems reduces both costs and time-to-market while increasing reliability of the built software. Why reductions? Because concurrency bugs are removed at the earliest possible moment, hence they cost orders of magnitude less than if they were found during testing or (worse) at customer sites.