Abstract
This document proposes one answer to the question: how does one measure and communicate progress in code verification? The question is addressed within the scope of verifying the order-of-accuracy of codes that solve partial differential equations. A process is described whereby order-verification exercises may be conducted within software development projects. The process entails domain-definition, test-suite construction, and test-suite demonstration phases. Progress measures are proposed to monitor the latter two phases particularly with regard to how close they are to completion. A fitness measure is introduced which measures the verification-fitness of a code relative to a given application.
Sign-in/Register to access full text options 
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Schedule a callDisclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.
