Abstract
In all models of the software life-cycle, the requirements specification phase, i.e., the phase when the user requirements are elicited and expressed formally, plays a critical role. Two key properties of specifications are completeness (i.e., their ability to capture all the user requirements) and minimality (i.e., their ability to capture nothing but the user requirements). The paper describes a system that helps specifiers check these properties on specifications that are written in some predefined relational form.
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.
