Abstract
It is a paradigm of software engineering that a complete representation of the problem domain (called requirement theory) is repeatedly refined by correctness-preserving transformations into the program itself. The design of a requirement theory has to allow for such a design methodology. The authors argue that currently available languages intended to yield requirement theories fail to meet these demands. They present a logic-based requirement language, which can be used to specify the requirements for software systems under the emerging methodology. The language presented is based on first-order predicate logic but augments standard first-order logic by introducing hierarchies and exceptions to its generalisations, in order to allow for a more natural description of the problem domain.
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.
