计算机科学 ›› 2018, Vol. 45 ›› Issue (10): 183-188.doi: 10.11896/j.issn.1002-137X.2018.10.034

• 软件与数据库技术 • 上一篇    下一篇

基于多视角卡牌模型的需求缺陷检测

苏若, 吴际, 刘超, 杨海燕   

  1. 北京航空航天大学计算机学院 北京100191
  • 收稿日期:2017-09-20 出版日期:2018-11-05 发布日期:2018-11-05
  • 作者简介:苏 若(1990-),男,硕士,主要研究领域为软件需求,E-mail:csuruo@gmail.com;吴 际(1974-),男,博士,副教授,主要研究领域为软件安全性与可靠性等,E-mail:wuji@buaa.edu.cn(通信作者);刘 超(1958-),男,博士,教授,主要研究领域为软件测试等;杨海燕(1974-),女,硕士,讲师,主要研究领域为软件测试等。
  • 基金资助:
    民用飞机专项科研项目(MJ-S-2013-10)资助

Requirement Defect Detection Based on Multi-view Card Model

SU Ruo, WU Ji, LIU Chao, YANG Hai-yan   

  1. School of Computer Science and Engineering,Beihang University,Beijing 100191,China
  • Received:2017-09-20 Online:2018-11-05 Published:2018-11-05

摘要: 需求来源于不同利益相关方对现实系统的认识和期望。需求获取在整个软件产品的研发过程中至关重要,往往决定着软件产品的质量甚至成败。然而,由于各种复杂因素的影响,获取到的需求中往往存在不完整、不准确甚至冲突等缺陷。需求表达上的二义性、需求描述的不完整和不一致等是最常见的需求缺陷。文中提出一种基于多视角需求获取的卡牌模型和需求缺陷检测规则。在需求获取过程中,特别是在其初期,其能够发现来自各方需求信息中常见的不完整和不一致需求缺陷。最后,通过3组项目案例验证了方法的有效性。

关键词: 多视角卡牌模型, 需求获取, 需求缺陷检测

Abstract: Requirement stems from the understanding and expectations of different stakeholders on the real system.Requirement elicitation is crucial in the wholeprocess of software product development,and it often decides the quality of software product,even its success or failure.Due to the influence of various complex factors in the elicited requirements,there are some defects such as incompleteness,inaccuracy and conflict.The ambiguity of requirement expression and the incompleteness and inconsistency of requirement description are the most common requirement defects.This paper proposed a card model based on multi-view requirements and requirement defect detection rules.In the process of requirement acquisition,especially in the early period,the incomplete and inconsistent requirement defects from stakeholders can be found through requirement defect detection rules.Finally,the validity of this method is verified by the experiment on three project cases.

Key words: Multi-view card model, Requirement defect detection, Requirement elicitation

中图分类号: 

  • TP311
[1]DAVIS A M.Just Enough Requirements Management:Where Software Development Meets Marketing[M].New York:Dorest House,2005.
[2]WIEGERS K,BEATTY J.软件需求[M].北京:清华大学出版社,2016.
[3]TAO Y.Automatically Deriving a UML Analysis Model from a Use Case Model[D].Ottawia:Carleton University,2010.
[4]ROSS D T.Structured Analysis (SA):A Language for Communicating Ideas[M]∥Programming Methodology.Springer New York,1978:16-34.
[5]ROSS D T,JR K E S.Structure Analysis for Requirements Definition[J].IEEE Transactions on Software Engineering,1977,3(1):6-15.
[6]MULLERY G P.CORE-a method for controlled requirement specification[C]∥International Conference on Software Engineering.1979:126-135.
[7]LEITE J C S P,FREEMAN P A.Requirements Validation Through Viewpoint Resolution[J].IEEE Transactions on Software Engineering,1991,17(12):1253-1269.
[8]KRUCHTEN P.Architectural Blueprints-The “4+1” View Model of Software Architecture[J].IEEE Software,1995,12(6):42-50.
[9]KOTONYA G,SOMMERVILLE I.Requirements engineering with viewpoints[J].Software Engineering Journal,2002,11(1):5-18.
[10]SOMMERVILLE I,SAWYER P.Requirements Engineering:A Good Practice Guide[J].European Journal of Dental Education,1997,168(1):220-221.
[11]SOMMERVILLE I,SAWYER P,VILLER S.Viewpoints for Requirements Elicitation:A Practical Approach[C]∥Third International Conference on Requirements Engineering,1998.IEEE,1998:74-81.
[12]BALZER R.“Tolerating Inconsistency” revisited[C]∥International Conference on Software Engineering.Toronto:IEEE Computer Press,2001:665.
[13]GHEZZI C,NUSEIBEH B.Guest editorial:Introduction to the special section[J].IEEE Transactions on Software Engineering,1999,25(6):782-783.
[14]EASTERBROOK S,CHECHIK M.Int’l workshop on living with inconsistency[C]∥Internationa Conference on Software Engineering.Toronto:IEEE Computer Press,2001:749-750.
[15]ZHU X F,JIN Z.About inconsistency management in software requirements [J].Journal of Software,2005,16(7):1221-1231.(in Chinese)
朱雪峰,金芝.关于软件需求中的不一致性管理[J].软件学报,2005,16(7):1221-1231.
[16]CLARKE E,GRUMBERG O,LONG D.Verification tools for finite-state concurrent systems[C]∥REX School /Symposium on A Decade of Concurrency,Beflections and Perspectives.London:Springer-Verlag,1994:124-175.
[17]MCMILLAN L.Symbolic model checking [D].Pittsburgh:Carnegie Mellon University,1992.
[18]HOLZMANN J.The model checker SPIN[J].IEEE Transac- tions on Software Engineering,1997,23(5):279-295.
[19]LAMSWEERDE V,DARIMONT R,LETIER E.Managing conflict in goal-driven requirements engineering[J].IEEE Transactions on Software Engineering,1998,24(11):908-926.
[20]LAMSWEERDE V,LETIER E.Handling obstacles in goal- oriented requirements engineering[J].IEEE Transactionson Software Engineering,2000,26(10):978-1005.
[21]GLINZ M.A lightweight approach to consistency of scenarios and class models[C]∥Proceedings of the 4th Int’l Conference on Requirements Engineering.Schaumburg:IEEE Computer Press,2000:49-58.
[22]CARROLL J M.Scenario-based design:envisioning work and technology in system development[M].John Wiley & Sons,Inc.,1995:375-376.
[23]JARKE M,BUI X T,CARROLL J M.Scenario Management: An Interdisciplinary Approach[J].Requirements Engineering,1998,3(3/4):155-173.
[24]FANMUY G,FRAGA A,LLORENS J.Requirements Verification in the Industry[J].Complex Systems Design & Management,2012,13(169):145-160.
[25]YAN Y Q,LI S X,MEI X Y.Defect needs analysis and management model[J].Computer Science,2009,36(4):140-144.(in Chinese)
严玉清,李师贤,梅晓勇.缺陷需求分析与管理模型[J].计算机科学,2009,36(4):140-144.
[26]KOESTERS G.Coupling Use cases and Class Models as a Means for validation and verification of requirements Specification[J].Requirements Engineering,2001,6(1):3-17.
[27]LEITE J C S D P,HADAD G D S,DOORN J H,et al.Scenario Construction Process[J].Requirements Engineering,2000,5(1):38-61.
[28]Software Considerations in Airborne Systems and Equipment Certification:DO-178B/C[S].1982.
[29]IEEE.Recommended practice for software requirements specifications[S].1998.
[1] 鱼滨 张琛 郝克刚.
支持MDA的交互式需求获取方法及辅助工具

计算机科学, 2008, 35(8): 273-276.
Viewed
Full text


Abstract

Cited

  Shared   
  Discussed   
No Suggested Reading articles found!