Four paradigms of information systems development
Communications of the ACM
Agile Project Management: Creating Innovative Products
Agile Project Management: Creating Innovative Products
| Hi-index | 0.00 |
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.