Marginal notes on amethodical requirements engineering: What experts learned from experience

Proceedings of the 16th IEEE International Requirements Engineering Conference, RE'08

Volumn , Issue , 2008, Pages 105-114

  Sim, Susan Elliott ^a   Alspaugh, Thomas A ^a   Al Ani, Ban ^a  

^a 5226 Donald Bren Hall   (United States)

Author keywords

[No Author keywords available]

Indexed keywords

ENGINEERING; REQUIREMENTS ENGINEERING;

CUSTOMER VALUES; PROFESSIONAL DEVELOPMENTS; REQUIREMENTS DOCUMENTS; REQUIREMENTS ENGINEERS;

PROFESSIONAL ASPECTS;

EID: 58049185016     PISSN: None     EISSN: None     Source Type: Conference Proceeding    
DOI: 10.1109/RE.2008.52     Document Type: Conference Paper

References (28)

1. B. Al-Ani and S. E. Sim. So, you think you are a requirements engineer? (extended abstract for poster). In 14th Intl. Requirements Engineering Conference (RE'06), 2006.
2. J. Aranda, S. Easterbrook, and G. Wilson. Requirements in the wild: How small companies do it. In 15th Intl. Requirements Engineering Conference (RE'07), pages 39-48, 2007.
3. Aristotle. Nicomachean Ethics, 350 B.C. (trans.W. D. Ross.
4. H. Beyer and K. Holtzblatt. Contextual Design : Defining Customer-Centered Systems. Morgan Kaufman, 1997.
5. R. L. Campbell, N. R. Brown, and L. DiBello. The programmer's burden: Developing expertise in programming. In The Psychology of Expertise: Cognitive Research and Empirical AI, pages 269-294. Springer-Verlag, 1992.
6. M. Chechik, B. Devereux, S. Easterbrook, and A. Gurfinkel. Multi-valued symbolic model-checking. ACM Trans. Softw. Eng. Methodol., 12(4):371-408, 2003.
7. J. M. Corbin and A. C. Strauss. Basics of Qualitative Research: Techniques and Procedures for Developing Grounded Theory. Sage, 2007.
8. K. A. Ericsson, R. T. Krampe, and C. Tesch-Römer. The role of deliberate practice in the acquisition of expert performance. Psychological Review, 100(3):363-406, 1993.
9. J. Goguen and C. Linde. Techniques for requirements elicitation. Requirements Engineering, 1993., Proceedings of IEEE International Symposium on, pages 152-164, 1993.
10. L. Hagge and K. Lappe. Sharing requirements engineering experience using patterns. IEEE Software, 22(1):24-31, 2005.
11. D. J. Haraway. Modest Witness@Second Millenium. FemaleMan Meets OncoMouse: Feminism and Technoscience. Routledge, 1997.
12. A. M. Hickey and A. M. Davis. Elicitation technique selection: How do experts do it? In 11th IEEE Joint International Conference on Requirements Engineering (RE'03), pages 169-178, 2003.
13. Intuit, inc. http://www.intuit.com/.
14. J. Lofland and L. H. Lofland. Analyzing Social Settings: A guide to qualitative observation and analysis. Wadsworth, 1994.
15. W. G. Lutters and C. B. Seaman. Revealing actual documentation usage in software maintenance through war stories. Inf. and Software Technology, 49(6):576-587, June 2007.
16. N. Maiden, C. Ncube, and S. Robertson. Can requirements be creative? experiences with an enhanced air space management system. In 28th International Conference on Software Engineering (ICSE '07), pages 632-641, May 2007.
17. B. Nuseibeh and S. Easterbrook. Requirements engineering: A roadmap. In 22nd International Conference on Software Engineering (ICSE '00), pages 35-46, June 2000.
18. C. Potts. Requirements models in context. In Third IEEE International Symposium on Requirements Engineering (RE'97), pages 102-104, 1997.
19. B. Russell. Knowledge by acquaintance and knowledge by description. Proceedings of the Aristotelian Society, 11:108-128, 1910.
20. Reprinted in Russell, Bertrand, Mysticism and Logic, London: Allen and Unwin, 1963, 152-167.
21. M. Sabetzadeh and S. Easterbrook. View merging in the presence of incompleteness and inconsistency. Requirements Engineering, 11(3):174 193, June 2006.
22. A. G. Sutcliffe and N. A. M. Maiden. Analysing the novice analyst: Cognitive models in software engineering. Intl. J. of Man-Machine Studies, 36(5):719-740, May 1992.
23. S. K. S. Tan. The elements of expertise. Journal of Physical Education, Recreation and Dance, 68(2):30-33, 1997.
24. D. Truex, R. Baskerville, and J. Travis. Amethodical systems development: the deferred meaning of systems development methods. Accounting Management and Information Technologies, 10(1):53-79, 2000.
25. S. Viller and I. Sommerville. Social analysis in the requirements engineering process: From ethnography to method. In Fourth IEEE International Symposium on Requirements Engineering (RE'99), pages 6-13, 1999.
26. R. Wieringa and C. Ebert. Re'03: Practical requirements engineering solutions. IEEE Software, 21(2):16-18, 2004.
27. R.Wieringa, N. Maiden, N. Mead, and C. Rolland. Requirements engineering paper classification and evaluation criteria: a proposal and a discussion. Requirements Engineering, 11(1):102-107, 2006.
28. R. J. Wieringa. Methodologies of requirements engineering research and practice: Position statement. In First International Workshop on Comparative Evaluation in Requirements Engineering (CERE'03), Sept. 2003.