3 ms·
In case studies with formal methods, specification languages like Z are used to make the requirements more clear. Such methods have shown to work pretty well wi
by nickpsecurity 10y ago
In case studies with formal methods, specification languages like Z are used to make the requirements more clear. Such methods have shown to work pretty well with both programmers and laypersons learning it easily. This means a separate methodology or whatever might not be necessary if we just needed a less, ambiguous language. Of which there are many with some having tool support.
Example of one methodology that uses Z in safety-critical field with low defect results:
http://www.sis.pitt.edu/jjoshi/Devsec/CorrectnessByConstruction.pdf http://www.sis.pitt.edu/jjoshi/Devsec/CorrectnessByConstruct...
- DanielBMarkham 10y agoI think perhaps you do not understand what I am saying. Yes, there are quite a few such tools which allow laypeople and coders to come to an agreement. My point was about coming to and maintaining that agreement. Not how exactly you would go about doing that. I could think of about half-a-dozen good ways to formalize a domain. But even if your process is nothing more than "come to this room and let's talk"? It's difficult to get many people with many other duties in such a situation as much as it would be required. Don't forget -- and I'm sure you haven't -- that it's not just formalizing a language and grammar. It's the fact that these change over time as participants become more absorbed in the domain and see the same concepts from various viewpoints.
- nickpsecurity 10y agoThanks for clarifying. Those are good points.
- polskibus 10y agoWhich tools would you recommend for achieving agreement ? Any particular technique or framework ?