Guiding the construction of textual use case specifications

Data and Knowledge Engineering

Volumn 25, Issue 1-2, 1998, Pages 125-160

  Rolland, Colette ^a   Ben Achour, Camille ^a  

^a UNIVERSITÉ PARIS 1 PANTHÉON SORBONNE   (France)

Author keywords

Requirements elicitation; Textual scenario analysis; Use case specification

Indexed keywords

AUTOMATIC TELLER MACHINES; COMPUTATIONAL LINGUISTICS; FORMAL LANGUAGES; MATHEMATICAL MODELS; NATURAL LANGUAGE PROCESSING SYSTEMS;

LINGUISTIC PATTERNS;

HUMAN COMPUTER INTERACTION;

EID: 0032027719     PISSN: 0169023X     EISSN: None     Source Type: Journal    
DOI: 10.1016/S0169-023X(97)86223-4     Document Type: Article

References (48)

1. B. Belkhouche, J. Kozma, Semantic case analysis of informal requirements, Proc. of the 4th Workshop on the Next Generation of CASE Tools, Enschede, The Netherlands, (1993) 163-181.
2. B. Boguraev, K. Spark-Jones, A note on a study of cases, in Computational Linguistics, Vol 13, No. 1-2 (1987) 65-68.
3. J.M. Carroll, The scenario perspective on system development, in J.M. Carroll (ed.), Scenario-Based Design: Envisioning Work and Technology in System Development (1995).
4. P. P-S Chen, English sentence structure and Entity Relationship diagrams, in Information Sciences 29 (1987) 127-149.
5. N. Chomsky, Deep Structure, Surface Structure and Semantic Interpretation (Steinberg & Jakobovits, 1971) 183-216.
6. A. Cockburn, Structuring use cases with goals, Technical Report, Human and Technology, 7691 Dell Rd, Salt Lake City, UT 84121, HaT.TR.95.1, http://members.aol.com/acocburn/papers/usecases.htm (1995).
7. D. Coleman, P. Arnold, S. Bodoff, C. Dollin, H. Gilchrist, F. Hayes, P. Jeremaes, Object-Oriented Development: The FUSION Method (Prentice Hall, 1994).
8. B. Dano, H. Briand, F. Barbier, A use case driven requirements engineering process, In 3rd IEEE Int. Symp. On Requirements Engineering (RE'97), Antapolis, MD (IEEE Computer Society Press, 1997).
9. S.C. Dik, The theory of functional grammar, Part I: The structure of the clause, Functional Grammar Series (Fories Publications, 1989).
10. D.R. Dowty, R.E. Walls, S. Peters, Introduction to Montague Semantics (Reidel-Kluwer, 1981).
11. E. Dubois, P. Heymans, M. Jarke, K. Phol, K. Weidenhaupt, A. Sutcliffe, N.A.M. Maiden, Integration of scenario representations: Formalisation and examples, ESPRIT Reactive Long Term Research Project 21.903 CREWS, Deliverable W4: Knowledge Representation Working Group (1997).
12. T. Erickson, Notes on design practice: Stories and prototypes as catalysts for communication, in J.M. Carroll (ed.), Scenario-Based Design: Envisioning Work and Technology in System Development (John Wiley and Sons, 1995) 37-59.
13. C. Fillmore, The case for case, in Holt, Rinehart, Winston (eds.), Universals in Linguistic Theory (E. Bach & R. Harms, 1968) 1-90.
14. J.D. Gould, How to design usable systems, in M. Helander (ed.), Handbook of Human-Computer Interaction (Elsevier Science, 1988) 757-790.
15. I. Jacobson, M. Christerson, P. Jonsson, G. Oevergaard, Object Oriented Software Engineering: a Use Case Driven Approach (Addison-Wesley, 1992).
16. I. Jacobson, The use case construct in object-oriented software engineering, in John M. Carroll (ed.), Scenario-Based Design: Envisioning Work and Technology in System Development (John Wiley and Sons, 1995) 309-336.
17. I. Jacobson, M. Ericsson, A. Jacobscn, The Object Advantage, Business Process Reengineering with Object Technology (Addison-Wesley Publishing Company, 1995).
18. M. Jarke, K. Pohl, P. Haumer, K. Weidenhaupt, E. Dubois, P. Heymans, C. Rolland, C. Ben Achour, C. Cauvet, J. Ralyte, A. Sutcliffe, N.A.M. Maiden, S. Monicha, Scenario use in European software organisations - Results from site visits and questionnaires, ESPRIT Reactive Long Term Research Project 21.903 CREWS, Deliverable W1: Industrial Problem Capture Working Group (1997).
19. P. Johnson, H. Johnson, S. Wilson, Rapid prototyping of user interfaces driven by task models, in John M. Carroll (ed.), Scenario-Based Design: Envisioning Work and Technology in System Development (John Wiley and Sons, 1995) 209-246.
20. J. Karat, Scenario use in the design of a speech recognition system, in John M. Carroll (ed.), Scenario-Based Design: Envisioning Work and Technology in System Development (John Wiley and Sons, 1995) 109-135.
21. K. Koskimies, H. Mossenbock, Scene: Using scenario diagrams and active text for illustrating object-oriented programs, in Proc. of ICSE-18 (1995) 366-375.
22. K. Koskimies, T. Mannisto, T. Systa, J. Tuomi, On the role of scenarios in object-oriented software design, Technical Report, Series of Publications A (A-1996-1) (Dept. of Computer Science, Univerity of Tampere, Finland, 1996).
23. M. Kyng, Creating contexts for design, in J.M. Carroll (ed.), Scenario-Based Design: Envisioning Work and Technology in System Development (John Wiley and Sons, 1995) 85-107.
24. J.C.S. do Prado Leite, G. Rossi, F. Balaguer, A. Maiorana, G. Kaplan, G. Hadad, A. Oliveros, Enhancing a requirements baseline with scenarios, in 3rd IEEE Int. Symp. On Requirements Engineering (RE'97), Antapolis, MD (IEEE Computer Society Press, 1997) 44-53.
25. R.L. Mack, Discussion: Scenarios as engines of design, in J.M. Carroll (ed.), Scenario-Based Design: Envisioning Work and Technology in System Development (John Wiley and Sons, 1995) 361-387.
26. B.A. Nardi, The Use of scenarios in design, in SIGCHI Bulletin 24(4) (1992).
27. J. Nielsen, Scenarios in discount usability engineering, in J.M. Carroll (ed.), Scenario-Based Design: Envisioning Work and Technology in System Development (John Wiley and Sons, 1995) 59-85.
28. C. Potts, K. Takahashi, A.I. Anton, Inquiry-based requirements analysis, in IEEE Software 11(2) (1994) 21-32.
29. D.A. Rawsthorne, Capturing functional requirements through object interactions, in Proc. of ICRE '96 (IEEE, 1996) 60-67.
30. B. Regnell, K. Kimbler, A. Wessler, Improving the use case driven approach to requirements engineering, in 2nd IEEE Int. Symp. On Requirements Engineering, York, England (I.C.S. Press, March 1995) 40-47.
31. S.P. Robertson, Generating object-oriented design representations via scenarios queries, in J.M. Carroll (ed.), Scenario-Based Design: Envisioning Work and Technology in System Development (John Wiley and Sons, 1995) 279-308.
32. C. Rolland, C. Ben Achour, C. Cauvet, J. Ralyte, A. Sutcliffe, N.A.M. Maiden, M. Jarke, P. Haumer, K. Pohl, E. Dubois, P. Heymans, A proposal for a scenario classification framework, ESPRIT Reactive Long Term Research Project 21.903 CREWS, Deliverable I1: Initial Integration Workpackage (1997).
33. C. Rolland, C. Proix, A natural language approach for requirements engineering, in P. Loucopoulos (ed.), Advanced Information Systems Engineering (Springer Verlag, 1992) 257-277.
34. M.B. Rosson, J.M. Carroll, Narrowing the specification-implementation gap, in J.M. Carroll (ed.), Scenario-Based Design: Envisioning Work and Technology in System Development (John Wiley and Sons, 1995) 247-278.
35. K.S. Rubin, A. Goldberg, Object behaviour analysis, Comms. of the ACM 35(9) (1992) 48-62.
36. J. Rumbaugh, M. Blaha, W. Premerlani, F. Eddy, W. Lorensen, Object-Oriented Modeling and Design, (Prentice Hall, 1991).
37. J. Rumbaugh, Getting started, Journal of Object-Oriented Programming (7) (1994) 8-23.
38. J. Rumbaugh, G. Booch, Unified Method, Notation Summary, Version 0.8 (Rational Software Corporation, 1996).
39. B. Scalzo, UPROAR - User processes reveal objects and requirements, in Proc. of the OOPSLA '95 Workshop on Use Cases, (1995).
40. R. Schanck, Identification of conceptualisations underlying natural language, in Computer Models of Thought and Language (R.C. Shanck & K.M. Colby, Freeman, San Francisco, 1973) 187-247.
41. R. Simmons, Semantic networks: their computation and use for understanding English sentences, in Computer Models of Thought and Language (R.C. Schanck & K.M. Colby, Freeman, San Francisco, 1973) 63-113.
42. S. Somé, R. Dssouli, J. Vaucher, Towards an automation of requirements engineering using scenarios, Journal of Computing and Information 2(1), Special Issue, ICCI'96, 8th Int. Conf. of Computing and Information, Waterloo, Canada (1996), 1110-1132.
43. J.F. Sowa, Conceptual Structures, Information Processing in Mind and Machine (Addison-Wesley, The Systems Programming Series, 1984).
44. K. Weidenhaupt, K. Pohl, M. Jarke, P. Haumer, Scenario usage in system development: A report on current practice, ESPRIT Reactive Long Term Research Project 21.903 CREWS, Deliverable W1-D2 (1997).
45. J. Whiteside, J. Bennett, K. Holtzblatt, Usability engineering: Our experience and evolution, in M. Helander (ed.), Handbook of Human-Computer Interaction (Elsevier Science, Amsterdam, 1988) 791-818.
46. Y. Wilks, Good and bad arguments about semantic primitives, Report No. 42 (Dept. of Artificial Intelligence, University of Edinburgh, 1977).
47. R. Wirfs-Brock, Designing objects and their interactions: A brief look at responsability-driven design, in J.M. Carroll (ed.), Scenario-Based Design: Envisioning Work and Technology in System Development (John Wiley and Sons, 1995) 337-360.
48. K. Ryan, The role of natural language in requirements engineering, Proc. IEEE Int. Symp. on RE (San Diego, CA, 1993) 240-242.