A Method to Deal with the Type of Lexical Ambiguity in a Software Requirement Specification Document

Md. Rizwan Beg, Qamar Abbas, Alok Joshi
{"title":"A Method to Deal with the Type of Lexical Ambiguity in a Software Requirement Specification Document","authors":"Md. Rizwan Beg, Qamar Abbas, Alok Joshi","doi":"10.1109/ICETET.2008.160","DOIUrl":null,"url":null,"abstract":"SRS is the agreement between the client and the developer, it is a document which specifies the clientpsilas requirement and also validates the final product. In various surveys it was found that approximately 20-25% of the project time is allocated for the requirements definition and major part of its time is wasted in making the requirement specification unambiguous, to avoid the conflict in future. Conflict arises because of more than one interpretation of a requirement, this lead to misinterpretation of design constraints, functionality, and external interfaces or in any further enhancements. In our proposed system requirements are documented in natural language. The system checks whether the written requirements are valid requirements or not and also checks for the lexical type of ambiguities, especially the ambiguity related to homonyms, heteronyms and homographs.","PeriodicalId":269929,"journal":{"name":"2008 First International Conference on Emerging Trends in Engineering and Technology","volume":"27 1","pages":"0"},"PeriodicalIF":0.0000,"publicationDate":"2008-07-16","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":"10","resultStr":null,"platform":"Semanticscholar","paperid":null,"PeriodicalName":"2008 First International Conference on Emerging Trends in Engineering and Technology","FirstCategoryId":"1085","ListUrlMain":"https://doi.org/10.1109/ICETET.2008.160","RegionNum":0,"RegionCategory":null,"ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":null,"EPubDate":"","PubModel":"","JCR":"","JCRName":"","Score":null,"Total":0}
引用次数: 10

Abstract

SRS is the agreement between the client and the developer, it is a document which specifies the clientpsilas requirement and also validates the final product. In various surveys it was found that approximately 20-25% of the project time is allocated for the requirements definition and major part of its time is wasted in making the requirement specification unambiguous, to avoid the conflict in future. Conflict arises because of more than one interpretation of a requirement, this lead to misinterpretation of design constraints, functionality, and external interfaces or in any further enhancements. In our proposed system requirements are documented in natural language. The system checks whether the written requirements are valid requirements or not and also checks for the lexical type of ambiguities, especially the ambiguity related to homonyms, heteronyms and homographs.
一种处理软件需求说明文档中词汇歧义类型的方法
SRS是客户端和开发人员之间的协议,它是指定客户端需求并验证最终产品的文档。在各种调查中发现,大约20-25%的项目时间分配给了需求定义,大部分时间浪费在使需求规范明确,以避免未来的冲突上。冲突的产生是因为对需求的多种解释,这将导致对设计约束、功能、外部接口或任何进一步增强的误解。在我们建议的系统中,需求是用自然语言记录的。系统检查所写的需求是否为有效需求,并检查歧义的词汇类型,特别是与同音异义词和同形异义词相关的歧义。
本文章由计算机程序翻译,如有差异,请以英文原文为准。
求助全文
约1分钟内获得全文 求助全文
来源期刊
自引率
0.00%
发文量
0
×
引用
GB/T 7714-2015
复制
MLA
复制
APA
复制
导出至
BibTeX EndNote RefMan NoteFirst NoteExpress
×
提示
您的信息不完整,为了账户安全,请先补充。
现在去补充
×
提示
您因"违规操作"
具体请查看互助需知
我知道了
×
提示
确定
请完成安全验证×
copy
已复制链接
快去分享给好友吧!
我知道了
右上角分享
点击右上角分享
0
联系我们:info@booksci.cn Book学术提供免费学术资源搜索服务,方便国内外学者检索中英文文献。致力于提供最便捷和优质的服务体验。 Copyright © 2023 布克学术 All rights reserved.
京ICP备2023020795号-1
ghs 京公网安备 11010802042870号
Book学术文献互助
Book学术文献互助群
群 号:481959085
Book学术官方微信