<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<div class="moz-cite-prefix">On 14/07/2020 17:06, Brent Kimberley
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:1371833483.1056689.1594742761523@mail.yahoo.com">
<div class="ydp5bda0d9cyahoo-style-wrap"
style="font-family:Helvetica Neue, Helvetica, Arial,
sans-serif;font-size:16px;">
<div dir="ltr" data-setdir="false">>> <span>how are the
software developers to reason reliably about the physical
problem world where the important requirements are located
and defined, and will---or will not---be satisfied? </span><br>
</div>
<div><br>
</div>
<div dir="ltr" data-setdir="false">An automated World view
inquiry framework? <span>epistemology automation? </span>;)<br>
</div>
</div>
</blockquote>
<p>The way I suggested doing that when using Perfect Developer to
develop and (to some extent) verify the software requirements is
to include a model of the external physical system in the
requirements specification. It is then possible to reason and
construct proofs about the combined behaviour of the software +
physical system, including the effects of external inputs. This
approach is in principle applicable to other tool-supported formal
specification languages, for example Z.<br>
</p>
<p>Although this is conceptually simple, the problem lies in
constructing a model of the physical system and possible external
inputs that is sufficiently accurate and complete to make the
proofs meaningful and useful.</p>
<p>Cheers<br>
</p>
<pre class="moz-signature" cols="72">David Crocker, Escher Technologies Ltd.
<a class="moz-txt-link-freetext" href="http://www.eschertech.com">http://www.eschertech.com</a>
Tel. +44 (0)20 8144 3265 or +44 (0)7977 211486</pre>
<br>
</body>
</html>