Abstract
At the risk of being condemned as a software engineering heretic, it seems to me that notions of accuracy and correctness of software have intuitive appeal, but are difficult if not impossible to achieve in practice. The search for this chimera of "correctness" has misled many highly intelligent and technically capable developers into the quest for rigour in design, rather than rigour in requirements. But what does rigour in requirements mean? If we believe, with Boehm and colleagues [1] that "There is no complete and well defined set of requirements ready to be discovered in system development", what then is the requirements correctness criterion? And furthermore what is the correctness criterion for an implemented software system.
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.
