This topic is very interesting to me since I have been in the systems business since the 60s and have had to estimate the cost of a system based solely on a system specification in order to bid on a contract.
Given that the correctness of the product depends upon the development environment (e.g., the different tools, libraries, and languages used at the different stages of refinement and their semantic compatability), what is the state-of-the-art in qualifying the development environment as a whole?
Given that the correctness by construction is with respect to the specified requirements and given that most disappointments in software-dependent systems have been rooted in requirements (esp. the transformation of user needs into formal requirements specifications), to what extent can “domain modeling” help? What is the state-of-the-art in leveraging domain modeling in conjunction with domain engineering to create correct-by-construction systems?