Replicating the CREWS use case authoring guidelines experiment

Empirical Software Engineering

Volumn 5, Issue 3, 2000, Pages 245-267

  Cox, Karl ^a   Phalp, Keith ^a  

^a BOURNEMOUTH UNIVERSITY   (United Kingdom)

Author keywords

[No Author keywords available]

Indexed keywords

COMPUTER AIDED SOFTWARE ENGINEERING; COMPUTER PROGRAMMING LANGUAGES; ENGINEERING RESEARCH; NATURAL LANGUAGE PROCESSING SYSTEMS; SEMANTICS; STANDARDS; SYSTEMS ANALYSIS;

COOPERATIVE REQUIREMENTS ENGINEERING; NATURAL LANGUAGE TEXT; UNIFIED MODELING LANGUAGE; USE CASE AUTHORING GUIDELINES;

REQUIREMENTS ENGINEERING;

EID: 0034316468     PISSN: 13823256     EISSN: None     Source Type: Journal    
DOI: 10.1023/A:1026542700033     Document Type: Article

References (21)

1. Ben Achour, C. 1998. Guiding scenario authoring. Proc. 8th European-Japanese Conference on Information Modeling and Knowledge Bases. Finland, 181-200.
2. Ben Achour, C., Rolland, C., Maiden, N., and Souveyet, C. 1998. Guiding use case authoring: Results of an empirical study. Proc. Fourth IEEE Int. Symposium on Requirements Engineering University of Limerick, Ireland. Version taken from the CREWS web site: http://sunsite.informatik.rwth-aachen.de/CREWS/reports.htm. Report Number: 93-31.
3. Ben Achour, C., and Maiden, N. 1999. Empirical study of use case authoring: Experimental material. Internal Report. Centre de Recherche en Informatique, Universite de Paris 1-Sorbonne. http://panoramix.univ-paris1.fr/CRINFO/users/benachour/ESEM/.
4. Booch, G., Rumbaugh, J., and Jacobson, I. 1999. The Unified Modelling Language User Guide. Reading, MA: Addison-Wesley.
5. Cockburn, A. 1997. Using goal-based use cases. Journal of Object-Oriented Programming Nov-Dec.
6. Cockburn, A. 2000. Writing Effective Use Cases: Part One. In Print. Addison-Wesley.
7. Cox, K., and Phalp, K. T. 2000. A case study implementing the unified modeling language use-case notation version 1.3. Proc. Sixth Int. Workshop on Requirements Engineering: Foundation for Software Quality. Stockholm, Sweden.
8. Ericksson, H., and Penker, M. 1993. UML Toolkit. Wiley.
9. Fowler, M., and Scott, K. 2000. UML Distilled Second Edition: A Brief Guide to the Standard Object Modelling Language. Reading, MA: Addison-Wesley.
10. Greene, J., and D'Oliveira, M. 1982. Learning to Use Statistical Tests in Psychology: A Student's Guide. Bury St Edmunds, Suffolk: Open University Press.
11. Harwood, R. 1997. Use case formats: Requirements, analysis and design. Journal of Object-Oriented Programming January: 54-66.
12. Jacobson, I. 1987. Object-oriented development in an industrial environment. Proc. OOPSLA'87. Special Issue of SIGPPLAN NOTICES 22(12): 183-197.
13. Jacobson, I., Christerson, M., Jonsson, P., and Oevergaard, G. 1992. Object-Oriented Software Engineering: A Use Case Driven Approach. Addison Wesley.
14. Jarke, M., Pohl, K., Haumer, P., Weidenhaupt, K., Dubois, E., Heymans, P., Rolland, C., Ben Achour, C., Cauvet, C., Ralyte, J., Sutcliffe, A., Maiden, N., and Minocha, S. 1997. Scenario use in European software organisations - Results from the site visits and questionnaires. Taken from the CREWS web site: http://sunsite. informatik.rwth-aachen.de/CREWS/reports.htm. Report Number: 97-10.
15. Nardi, B. 1992. The use of scenarios in design. SIGCHI Bulletin 24(4): 13-14.
16. Pooley, R., and Stevens, P. 1999. Using UML: Software Engineering with Objects and Components. Reading, MA: Addison-Wesley.
17. Rational Software Corporation. 1997. UML notation version 1.1. http://www.rational.com/uml
18. Robson, C. 1993. Real World Research. Blackwell.
19. Rosenberg, G., with Scott, K. 1999 Use Case Driven Object Modeling with UML: A Practical Approach. Reading, MA: Addison Wesley.
20. Swan, M. 1980. Practical English Usage. Oxford University Press.
21. Weidenhaupt, K., Pohl, K., Jarke, M., and Haumer, P. 1998. Scenarios in System Development: Current practice. IEEE Software March/ April: 34-45.