Abstract
This paper looks at the possibility of using fuzzy terms in a software requirements specification. Potential benefits are reviewed. Methods for testing whether a fuzzy specification is met are investigated. Ways of modeling criticality and rigidity of specifications using fuzzy approaches are also identified. An example based on query response times is used throughout the paper. The results of a pilot study to see whether computer response time requirements can be fuzzified are described.
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.
