微信服务号

微信订阅号

2025-4-16- 5
Home > Archive>Volume 20, Issue 2, 2009 >177-192
PDF HTML XML Export Cite reminder
Research on Dynamic Requirement Traceability Method and Traces Precision
Author:
Affiliation:

  • Article
    • | |
  • Metrics
    • |
  • Reference [57]
    • |
  • Related
    • |
  • Cited by
    • | |
  • Comments
    Reference
    [1] van Lamsweerde A. Requirements Engineering in the year 00: A research perspective. In: Proc. of the 22nd Int’l Conf. on Software Engineering (ICSE 2000). New York: ACM, 2000. 5-19.
    [2] Jr Brooks FP. No silver bullet: Essence and accidents of software engineering. IEEE Computer, 1987,20(4):10-19.
    [3] Nuseibeh B, Easterbrook S. Requirements engineering: A roadmap. In: Int’l Conf. on Software Engineering, Proc. of the Conf. on the Future of Software Engineering. New York: ACM, 2000. 35-46.
    [4] Gotel OCZ, Finkelstein ACW. An analysis of the requirements traceability problem. In: Proc. of the 1st Int’l Conf. on Requirements Engineering Conf. (RE’94). IEEE Computer Society, 1994. 94-101.
    [5] Gotel OCZ. Contribution structures for requirements traceability [Ph.D. Thesis]. London: Imperial College of Science, Technology and Medicine, University of London, 1995.
    [6] Jarke M. Requirement tracing. Communications of the ACM, 1998,41(12):32-36.
    [7] Ramesh B, Stubbs C, Powers T, Edwards M. Requirements traceability: Theory and practice. Annals of Software Engineering, 1997,3(1):397-415.
    [8] Aurum A, Wohlin C. Engineering and Managing Software Requirements. New York: Springer-Verlag, 2005.
    [9] Maletic A, Maletic JI. Recovering documentation-to-source-code traceability links using latent semantic indexing. In: Proc. of the 25th Int’l Conf. on Software Engineering. Washington: IEEE Computer ociety, 2003. 125-135.
    [10] Hayes JH, Dekhtyar A, Sundaram SK, Howard S. Helping analysts trace requirements: An objective look. In: Proc. of the 12th Int’l Requirements Engineering Conf. (RE 2004). Washington, 2004. 249-259.
    [11] Hayes JH, Dekhtyar A, Sundaram SK. Advancing candidate link generation for requirements tracing: The study of methods. IEEE Trans. on Software Engineering, 2006,32(1):4-19.
    [12] Cleland-Huang J, Settimi R, Duan C, Zou XC. Utilizing supporting evidence to improve dynamic requirements traceability. In: Proc. of the 13th IEEE Int’l Requirements Engineering Conf. (RE 2005). Washington: IEEE Computer Society, 2005. 135-144.
    [13] Pohl K, D?mges R, Jarke M. Towards method?Driven trace capture. In: Proc. of the 9th Int’l Conf. on Advanced Information Systems Engineering. London: Springer-Verlag, 1997. 103-116.
    [14] Spanoudakis G. Plausible and adaptive requirement traceability structures. In: Proc. of the 14th Int’l Conf. on Software Engineering and Knowledge Engineering. New York: ACM, 2002. 135-142.
    [15] Robinson WN, Pawlowski SD, Volkov V. Requirement interaction management. ACM Computing Surveys (CSUR), 2003,35(2): 132-190.
    [16] Ramesh B, Jarke M. Toward reference models for requirements traceability. IEEE Trans. on Software Engineering, 2001,27(1): 58-93.
    [17] Ramesh B. Factors influencing requirements traceability practice. Communications of the ACM, 1998,41(12):37-44.
    [18] Pohl K. Process-Centered Requirements Engineering. New York: John Wiley & Sons, 1997.
    [19] Gotel O, Finkelstein A. Contribution structures. In: Proc. of the 2nd Int’l Symp. on Requirements Engineering (RE’95). IEEE Computer Society, 1995. 100-107.
    [20] Jackson J. A keyphrase based traceability scheme. In: Proc. of the Tools and Techniques for Maintaining Traceability During Design, IEE Colloquium. London: IEEE Computer Society, 1991. 769-783.
    [21] Kaindl H. The missing link in requirements engineering. ACM SIGSOFT Software Engineering Notes, 1993,18(2):30-39.
    [22] Lefering M. An incremental integration tool between requirements engineering and programming in the large. In: Proc. of the IEEE Int’l Symp. on Requirements Engineering. IEEE Computer Society, 1993. 82-89.
    [23] IBM. Rational RequisitePro. http://www-306.ibm.com/software/awdtools/reqpro/
    [24] IBM. DOORS (dynamic object oriented requirements system). http://www.telelogic.com/index.cfm
    [25] Borland. Borland CaliberRM. http://www.borland.com/us/products/caliber/index.html
    [26] Change management & requirement tracing systems. http://www.bandwood.com/cms_exec_summary.htm
    [27] Pinheiro FAC, Goguen JA. An object-oriented tool for tracing requirements. IEEE Software, 1996,13(2):52-64.
    [28] Pohl K. PRO-ART: Enabling requirements pre-traceability. In: Proc. of the 2nd Int’l Requirements Engineering Conf. (RE’96). Washington: IEEE Computer Society, 1996. 76-84.
    [29] Hayes JH, Dekhtyar A, Osbourne J. Improving requirements tracing via information retrieval. In: Proc. of the 11th Int’l Requirements Engineering Conf. (RE 2003). Washington: IEEE Computer Society, 2003. 151-161.
    [30] Cleland-Huang J, Zemont G, Lukasik W. A heterogeneous solution for improving the return on investment of requirements traceability. In: Proc. of the 12th IEEE Int’l Requirements Engineering Conf. (RE 2004). Washington: IEEE Computer Society, 2004. 230-239.
    [31] D?mges R, Pohl K. Adapting traceability environments to project specific needs. Communications of the ACM, 1998,41(12): 55-62.
    [32] Antoniol G, Caprile B, Potrich A, Tonella P. Design-Code traceability for object oriented systems. Annals Software Engineering, 1999,9(1-4):35-58.
    [33] Antoniol G, Canfora G, Casazza G, de Lucia AD, Merlo E. Recovering traceability links between code and documentation. IEEE Trans. on Software Engineering, 2002,28(10):970-983.
    [34] Settimi R, Cleland-Huang J, Khadra OB, Mody J, Lukasik W, DePalma C. Supporting software evolution through dynamically retrieving traces to UML artifacts. In: Proc. of the 7th Int’l Workshop Principles of Software Evolution. Washington: IEEE Computer Society, 2004. 49-54.
    [35] Cleland-Huang J, Settimi R, Benkhadra O, Berezhanskaya E, Christina S. Goal-Centric traceability for managing non-functional requirements. In: Proc. of the 27th Int’l Conf. on Software Engineering (ICSE 2005). New York: ACM, 2005. 362-373.
    [36] Spanoudakis G, Zisman A, Pérez-Mi?ana E, Krause P. Rule-Based generation of requirements traceability relations. The Journal of Systems and Software, 2004,72(2):105-127.
    [37] Cleland-Huang J, Chang CK, Ge YJ. Supporting event based traceability through high-level recognition of change events. In: Proc. of the 26th Int’l Computer Software and Applications Conf. on Prolonging Software Life: Development and Redevelopment (COMPSAC). Washington: IEEE Computer Society, 2002. 592-602.
    [38] Cleland-Huang J, Chang CK, Christensen M. Event-Based traceability for managing evolutionary change. IEEE Trans. on Software Engineering, 2003,29(9):796-810.
    [39] Egyed A. A scenario-driven approach to traceability. In: Proc. of the 23rd Int’l Conf. on Software Engineering (ICSE 2001). Washington: IEEE Computer Society, 2001. 123-132.
    [40] Egyed A, Grüenbacher P. Automatic requirements traceability: Beyond the record and replay paradigm. In: Proc. of the 17th IEEE Int’l Conf. on Automated Software Engineering. Washington: IEEE Computer Society, 2002. 163-171.
    [41] Sun JJ, Cheng Y, Ding Q, Li JJ, Song LL, Ke Q. Information Retrieval. Beijing: Science Press, 2004 (in Chinese).
    [42] Deerwester S, Dumais ST, Furnas GW, Landauer TK, Harshman R. Indexing by latent semantic analysis. Journal of the Society for Information Science, 1990,41(6):391-4074.
    [43] Landauer TK, Foltz PW, Laham D. An introduction to latent semantic analysis. Discourse Processes, 1999,25:259-284.
    [44] Baeza-Yates R, Ribeiro-Neto B. Modern Information Retrieval. Addison Wesley, 1999.
    [45] Zou XC, Settimi R, Cleland-Huang J. Phrasing in dynamic requirements trace retrieval. In: Proc. of the 30th Annual Int’l Computer Software and Applications Conf. (COMPSAC 2006). Washington: IEEE Computer Society, 2006. 265-272.
    [46] Cysneiros LM, Leite JCSP. Nonfunctional requirements: From elicitation to conceptual models. IEEE Trans. on Software Engineering, 2004,30(5):328-350.
    [47] Gross D, Yu E. From non-functional requirements to design through patterns. Requirements Engineering Journal, 2001,6(1):18?36.
    [48] Chung L, Nixon BA, Yu E, Mylopoulos J. Non-Functional Requirements in Software Engineering. Springer-Verlag, 1999.
    [49] Cleland-Huang J, Schmelzer D. Dynamically tracing non-functional requirements through design pattern invariants. In: Proc. of the Workshop on Traceability in Emerging Forms of Software Engineering (TEFSE 2003). 2003.
    [50] Cleland-Huang J. Requirements traceability?When and how does it deliver more than it costs? In: Proc. of the 14th IEEE Int’l Requirements Engineering Conf. (RE 2006). Washington: IEEE Computer Society, 2006. 323.
    [51] Hayes JH, Dekhtyar A. A framework for comparing requirements tracing experiments. Int’l Journal Software Engineering and Knowledge Engineering (IJSEKE), 2005,15(5):751-781.
    [52] IBM. Purifyplus. http://www-304.ibm.com/jct03001c/software/awdtools/purifyplus/
    [53] Lin J, Lin CC, Cleland-Huang J, Settimi R, Amaya J, Bedford G, Berenbach B, Khadra OB, Duan C, Zou XC. Poirot: A distributed tool supporting enterprise-wide automated traceability. In: Proc. of the 14th Int’l Requirements Engineering Conf. (RE 2006). Washington: IEEE Computer Society, 2006. 356-357.
    [54] Hayes JH, Dekhtyar A, Sundaram SK, Holbrook EA, Vadlamudi S, April A. Requirements tracing on target (RETRO): Improving software maintenance through traceability recovery. Innovations System Software Engineering, 2007(3):193-202.
    [55] Li Y, Li J, Yang Y, Li MS. Requirement-Centric traceability for change impact analysis: A case study. In: Wang Q, Pfaho D, Raffo DM, eds. Proc. of the Int’l Conf. on Software Process (ICSP 2008). Berlin, Heidelberg: Springer-Verlag, 2008. 100?111.
    [56] Princeton University. WordNet. http://wordnet.princeton.edu/
    [57] Nuseibeh B. Weaving together requirements and architectures. Computer, 2001,34(3):115-117.
    Related
    Cited by
    Comments
    Comments
    分享到微博
    Submit
Get Citation

李引,李娟,李明树.动态需求跟踪方法及跟踪精度问题研究.软件学报,2009,20(2):177-192

Copy
Share
Article Metrics
  • Abstract:
  • PDF:
  • HTML:
  • Cited by:
History
  • Received:August 07,2007
  • Revised:April 15,2008
Links:Institute of Software, CASChina Computer FederationCASNSFC
You are the firstVisitors
Copyright: Institute of Software, Chinese Academy of Sciences Beijing ICP No. 05046678-4
Address：4# South Fourth Street, Zhong Guan Cun, Beijing 100190,Postal Code：100190
Phone：010-62562563 Fax：010-62562533 Email：jos@iscas.ac.cn
Technical Support：Beijing Qinyun Technology Development Co., Ltd.

Beijing Public Network Security No. 11040202500063