A study of methods for textual satisfaction assessment

Empirical Software Engineering

Volumn 18, Issue 1, 2013, Pages 139-176

  Holbrook, Elizabeth Ashlee ^a   Hayes, Jane Huffman ^b   Dekhtyar, Alex ^c   Li, Wenbin ^b  

^a Lexmark   (United States)

^b UNIVERSITY OF KENTUCKY   (United States)

^c CALIFORNIA POLYTECHNIC STATE UNIVERSITY   (United States)

Author keywords

Methods for SQA and V V; Requirements specifications; Tracing; Validation

Indexed keywords

ASSESSMENT PROCESS; ASSESSMENT TECHNIQUE; AUTOMATICALLY GENERATED; DESIGN ELEMENTS; HIGH ASSURANCE; HUMAN LIVES; PROJECT COST; REQUIREMENTS ANALYST; REQUIREMENTS/SPECIFICATIONS; SEARCH SPACES; SOFTWARE DEVELOPMENT LIFE CYCLE; SOFTWARE PROJECT; TRACING; VALIDATION;

COMPUTER SOFTWARE; SOFTWARE ENGINEERING;

AUTOMATION;

EID: 84872338936     PISSN: 13823256     EISSN: 15737616     Source Type: Journal    
DOI: 10.1007/s10664-012-9198-8     Document Type: Article

References (37)

1. Altman DG (1991) Practical statistics for medical research. Chapman & Hall
2. Antoniol G (2002) Recovering traceability links between code and documentation. IEEE Trans on Software Engineering 28(10):970-983
3. Asplaugh TA, Antón AI (2008) Scenario support for effective requirements. Inf Softw Technol 50(3):198-220
4. Baeza-Yates R, Ribeiro-Neto B (2003) Modern information retrieval. Addison-Wesley
5. Cleland-Huang J (2002) Automating speculative queries through event-based requirements traceability. Joint Conference on Requirements Engineering
6. Cleland-Huang J, Settimi R, BenKhadra O, Berezhanskaya E, Christina S (2005) Goal-centric traceability for managing non-functional requirements. In: Proceedings of the 27th international conference on Software engineering (ICSE '05). ACM, New York, NY, pp 362-371. doi: 10.1145/1062455.1062525. http://doi.acm.org/10.1145/1062455.1062525
7. Cuddeback D, Dekhtyar A, Hayes JH (2010) Automated requirements traceability: the study of human analysts. In Proc. 18th International Conference on Requirements Engineering, Sydney, Australia
8. Di Lucca GA, Di Penta M, Antoniol G, Casazza G (2001) An approach for reverse engineering of web-based applications. BP - 231, Dipartimento di Informatica e Sistemistica
9. Diallo MH, Naslavsky L, Ziv H, Alspaugh TA, Richardson DA (2007) Evaluating software architectures against requirements-level scenarios. Workshop on the Role of Software Architecture for Testing and Analysis
10. Durán A, Ruiz A, Toro M (2001) An automated approach for verification of software requirements. Jornadas de Ingeniería de Requisitos Aplicada, Seville, Spain
11. GanttProject, http://ganttproject.biz/
12. Gotel OCZ, Finkelstein ACW (1996) Extended requirements traceability: a framework for changing requirements. Workshop on Requirements Engineering in a Changing World
13. Greenspan S, Mylopoulos J, Borgida J (1994) On formal requirements modeling languages: RML revisited. Proc. 16th International Conference on Software Engineering, p 135-147, Sorrento, Italy
14. Hayes JH, Dekhtyar A (2005) Humans in the traceability loop: can't live with 'em, can't live without 'em. Proc. of the 3rd International Workshop on Traceability in Emerging Forms of Software Engineering, Long Beach, California. TEFSE '05. ACM, New York, NY, 20-23
15. Hayes JH, Dekhtyar A, Osbourne J (2003) Improving requirements tracing via information retrieval. International Conference on Requirements Engineering
16. Hayes JH, Dekhtyar A, Sundaram S (2006a) Advancing requirements tracing: the study of methods. IEEE Trans Software Engineering 32(1):4-19
17. Hayes JH, Dekhtyar A, Sundaram S (2006) Advances in dynamic generation of traceability links. Tech Report, (TR 451-06)
18. Hayes JH, Dekhtyar A, Sundaram S, Holbrook A, Vadlamudi S, April A (2007) REquirements TRacing On target (RETRO): improving software maintenance through traceability recovery. Innovations in Systems and Software Engineering: A NASA Journal 3(3):193-202
19. Holbrook EA (2009) Satisfaction assessment of textual software engineering artifacts, PhD dissertation, Dept. of Computer Science., University of Kentucky, Lexington, KY
20. Holbrook EA, Hayes JH, Dekhtyar A (2009) Toward automating requirements satisfaction assessment. Requirements Engineering Conference, 2009. RE '09. 17th IEEE International, vol., no., pp 149-158
21. ISO9000:2000, Quality Standard, International Organization for Standardization
22. Lecceuche R (2000) Finding comparatively important concepts between texts. Automated Software Engineering (ASE'00). Washington, DC, 55
23. Letier E, van Lamsweerde A (2004) Reasoning about partial goal satisfaction for requirements and design engineering. SIGSOFT Softw Eng Notes 29(6):53-62
24. Marcus A, Maletic JI (2003) Recovering documentation-to-source code traceability links using latent semantic indexing. In: Proceedings of the 25th International Conference on Software Engineering (ICSE '03). IEEE Computer Society, Washington, DC, pp 125-135
25. Marcus MP, Santorini B, Marcinkiewicz MA (1993) Building a large annotated corpus of English: the Penn Treebank. Computational Linguistics 19:313-330
26. Marcus A, Maletic JI, Sergeyev A (2005) Recovery of traceability links between software documentation and source code. Int J Softw Eng Knowl Eng, World Scientific 15(5):811-836
27. Porter A, Votta L (1998) Comparing detection methods for software requirements inspections. Empir Softw Eng 3(4):355-379
28. Robinson WN (2005) Implementing rule-based monitors within a framework for continuous requirements monitoring. In: Proceedings of the Proceedings of the 38th Annual Hawaii International Conference on System Sciences - Volume 07 (HICSS '05), Vol. 7. IEEE Computer Society, Washington, DC, 188.1-. doi: 10.1109/HICSS.2005.306. http://dx.doi.org/10.1109/HICSS.2005.306
29. Robinson WN (2009) Seeking quality through user-goal monitoring. IEEE Software, pp 58-65
30. Robinson WN, Pawlowski S (1999) Managing requirements inconsistency with development goal monitors. IEEE Trans. on Software Eng
31. Salton G (1983) Introduction to modern information retrieval. McGraw-Hill
32. Shull G, Rus I, Basili VR (2000) How perspective-based reading can improve requirements inspections. IEEE Computer 33(7):73-79
33. Spanoudakis G, Zisman A (2005) Software traceability: a roadmap. In: Chang SK (ed) Handbook of Software Engineering and Knowledge Engineering, vol. 3: Recent Advancements. World Scientific Publishing
34. Spanoudakis G, d'Avila A, Garcez A, Zisman A (2003) Revising rules to capture requirements traceability relations: a machine learning approach. In: Proceedings of the 15th International Conference in Software Engineering and Knowledge Engineering (SEKE 2003), pp 570-577, San Francisco
35. Spanoudakis G, Zisman A, Pérez-Miñana E, Krause P (2004) Rule-based generation of requirements traceability relations. J Syst Softw 2(72):105-127
36. Spivey J (1988) Understanding Z. Cambridge
37. Sutcliffe A (1998) Scenario-based requirement analysis. Requir Eng 3(1):48-65. doi: 10.1007/BF02802920. http://dx.doi.org/10.1007/BF02802920