Evaluating the effectiveness of a goal-oriented requirements engineering method

Fourth International Workshops on Comparative Evaluation in Requirements Engineering, CERE'06

Volumn , Issue , 2006, Pages 8-19

  Al Subaie, Huzam S F ^a   Maibaum, Tom S E ^b  

^a KING'S COLLEGE LONDON   (United Kingdom)

^b MCMASTER UNIVERSITY   (Canada)

Author keywords

[No Author keywords available]

Indexed keywords

DATA REDUCTION; ERROR CORRECTION; PROBLEM SOLVING; STATISTICAL METHODS;

GOAL ORIENTED REQUIREMENTS ENGINEERING (GORE); KAOS METHOD; OBJECTIVER TOOLS; RE OBJECTIVES (REO);

REQUIREMENTS ENGINEERING;

EID: 34547558651     PISSN: None     EISSN: None     Source Type: Conference Proceeding    
DOI: 10.1109/CERE.2006.3     Document Type: Conference Paper

References (47)

1. th Anniversary of international IEEE RE conferences and symposium, http://www.re02.org/, Germany 2002.
2. E. Kavakli, "Goal-Oriented Requirements Engineering: A Unifying Framework". Requir. Eng. 6(4): 237-251 (2002).
3. th REFSQ'98, Italy, 1998.
4. th ACM SIGSOFT, ACM Press, South Carolina, 2002.
5. A. Lapouchnian, "An Overview of the Current Research", Department of Computer Science, University Of Toronto, 2005.
6. th International Conference "Software & Systems Engineering and their Applications, Paris - 2003.
7. R Darimont, "Requirements Engineering with Objectiver from Goal Analysis to Automatically Derived Requirements Documents", RE'03, California, USA,2003.
8. A. Dardenne, S. Fickas and A. van Lamsweerde, "Goal- Directed Concept Acquisition in Requirements Elicitation", Proc. IWSSD-6, Como, 1991.
9. A. Dardenne, A. van Lamsweerde and S. Fickas, "Goal Directed Requirements Acquisition," Science of Computer Programming, vol. 20, 1993.
10. R. Darimont, "Process Support for Requirements Elaboration", PhD Thesis, Universite catholique de Louvain, Dept. Ingenierie Informatique, Louvain-la-Neuve, Belgium, 1995.
11. A. Davis, "Software Requirements: Objects, Functions and States", Prentice Hall, 1993.
12. A. Davis, Software Requirements: Analysis and Specification, 2nd Edition, Prentice Hall, 1993.
13. st International Conference on RE, pages 94-101, 1994.
14. IEEE, "A Compilation of IEEE Standard Computer Glossaries", New York, 1990.
15. IEEE Recommended Practice for Software Requirements Specifications, IEEE Std. 830-1998.
16. I. Jureta, "Engineering Requirements for Information Systems using KAOS and Request frameworks", FUNDP - Institution - Belgium .2005.
17. E. Letier, "Reasoning about Agents in Goal-Oriented Requirements Engineering", PhD thesis, Université catholique de Louvain, Belgium, April 2001.
18. B. Kitchenham, "DESMET: A method for evaluating Software Engineering methods and tools", TR96-09, Dep. of Computer Science, University of Keele, U.K., 1996.
19. I. Sommerville and G. Kotonya, "Requirements engineering with viewpoints", Software Engineering Journal, Jan. 1996.
20. th REFSQ'99, Heidelberg, Germany 1999.
21. K Laitinen, "Estimating understandability of software documents", ACM SIGSOFT, Software Engineering Notes, Vol. 21, No. 4, July, 1996.
22. nd ICSE 2000.
23. A. van Lamsweerde, "Goal-Oriented Requirements Engineering: A Guided Tour", IEEE Transactions of Requirement Engineering, 2001.
24. A. van Lamsweerde, R. Darimont and E. Letier, "Managing Conflicts in Goal-Driven Requirements Engineering", IEEE Trans, on Software Engineering, 1998.
25. A KAOS tutorial, www.objectiver.com, 2003.
26. B. Boehm, "Verifying and validating software requirements and design specifications", IEEE Software, 1984.
27. B. Nuseibeh, S.Easterbrook, "Requirements engineering: a roadmap", the future of Software engineering, Limerick, Ireland, 2000.
28. th IWSSD'96, IEEE Computer Society Press, 1996.
29. Web site of Objectiver, www.objectiver.com, 2003.
30. Department of Computing Science and Engineering, Université catholique de Louvain, Belgium, http://www.info.ucl.ac.be/Research/Areas/ SoftwareE/GoalOrientedRE.php.
31. G. REGEV, "A Systemic Paradigm for Early IT System Requirements Based on Regulation Principles: The Lightswitch Approach", Ph.D thesis no. 2810, EPFL 2003.
32. W.N., Robinson, "Integrating Multiple Specifications Using Domain Goals", Proc. IWSSD-5, IEEE, 1989.
33. C. Rolland, N. Prakash: "From conceptual modelling to requirements engineering", Ann. Software Eng. 10: 151-176, 2000.
34. th edition, Addison- Wesley, 2000.
35. I. Sommerville and G. Kotonya, "Viewpoints for requirements definition", Software Engineering Journal 7, 1992.
36. I. Sommerville and G. Kotonya, "Requirements Engineering Processes and Techniques", John Wiley & Sons, 1998.
37. National Institute Of Standards And Technology, Guidelines, Information Quality Standards, and Administrative Mechanism, www.nist.gov/director/ quality_standards.htm, 2002.
38. Wikipedia encyclopedia, Version 1.2 http://en.wikipedia.org/wiki/ Ambiguity, 2002.
39. Williams, G. Lloyd, Assessment of safety-critical specifications. IEEE Software, 11(1):51-60, 1994.
40. K. Yue, "What does it mean to say that a specification is complete?", Proceedings of IWSSD'87, 1987.
41. D. Zowghi, V. Gervasi, "On the Interplay Between Consistency, Completeness, and Correctness in Requirements Evolution", the Journal of Information and Software Technology, Volume 45, Issue 14, 2003.
42. th Annual International Symposium on Systems Engineering, Seattle, 1998.
43. F Cioch, "Measuring software misinterpretation. Journal of Systems and Software", 14(2): 85-95, 1991.
44. R. Darimont, "Requirements Engineering with Objectiver: from Goal Analysis to Automatically Derived Requirements Documents", RE02, 2000.
45. J. You, "Goal-Oriented Requirements Engineering: Promising or Falling", Department of Computer Science, University of Toronto, 2004.
46. K. Wiegers, "First Things First: Prioritizing Requirements" Software Development, Vol. 7, No. 10, Oct. 1999.
47. R. Yin, "Case study research: Design and methods", 2nd ed., Beverly Hills, CA: Sage Publishing (1994).