Guiding the Construction of Textual Use Case Specifications

An approach for guiding the construction of use case specifications is presented. A use case specification comprises contextual information of the use case, its change history, the complete graph of possible pathways, attached requirements and open issues. The proposed approach delivers a use case specification as an unambiguous natural language text. This is done by a stepwise and guided process which progressively transforms initial and partial natural language descriptions of scenarios into well structured, integrated use case specifications. The basis of the approach is a set of linguistic patterns and linguistic structures. The former constitutes the deep structure of the use case specification whereas the latter corresponds to the surface structures. The paper presents the use case model, the linguistic basis and the guided process along with the associated guidelines and support rules. The process is illustrated with the automated teller machine (ATM) case study.

[1]  John Karat.  Scenario use in the design of a speech recognition system , 1995 .

[2]  John D. Gould,et al.  How to design usable systems , 1995 .

[3]  Hanspeter Mössenböck,et al.  Scene: using scenario diagrams and active text for illustrating object-oriented programs , 1996, Proceedings of IEEE 18th International Conference on Software Engineering.

[4]  Peter P. Chen.  English Sentence Structure and Entity-Relationship Diagrams , 1983, Inf. Sci..

[5]  Simon C. Dik,et al.  The theory of functional grammar , 1989 .

[6]  Branimir K. Boguraev,et al.  A note on a study of cases , 1987 .

[7]  P ? ? ? ? ? ? ? % ? ? ? ? , 1991 .

[8]  Morten Kyng,et al.  Creating contexts for design , 1995 .

[9]  T. Landauer,et al.  Handbook of Human-Computer Interaction , 1997 .

[10]  William E. Lorensen,et al.  Object-Oriented Modeling and Design , 1991, TOOLS.

[11]  Noam Chomsky,et al.  Deep structure, surface structure, and semantic interpretation , 1969 .

[12]  K. Koskimies,et al.  On the Role of Scenarios in Object-oriented Software Design on the Role of Scenarios in Object-oriented Software Design on the Role of Scenarios in Object-oriented Software Design , 1996 .

[13]  Boumediene Belkhouche,et al.  Semantic Case Analysis of Informal Requirements , 1993 .

[14]  John M. Carroll,et al.  Scenario-based design: envisioning work and technology in system development: john wiley & sons , 1995 .

[15]  Bonnie A. Nardi,et al.  The use of scenarios in design , 1992, SGCH.

[16]  Daniel A. Rawsthorne.  Capturing functional requirements through object interactions , 1996, Proceedings of the Second International Conference on Requirements Engineering.

[17]  John L. Bennett,et al.  Usability Engineering: Our Experience and Evolution , 1988 .

[18]  Stéphane S. Somé,et al.  Toward an Automation of Requirements Engineering using Scenarios , 1996 .

[19]  F. R..  Two Semantic Networks : Their Computation and Use for Understanding English Sentences , 2022 .

[20]  Emmon W. Bach,et al.  Universals in Linguistic Theory , 1970 .

[21]  David R. Dowty,et al.  Introduction to Montague semantics , 1980 .

[22]  Thomas Erickson,et al.  Notes on design practice: stories and prototypes as catalysts for communication , 1995 .

[23]  Peter Johnson,et al.  Rapid prototyping of user interfaces driven by task models , 1995 .

[24]  Kenji Takahashi,et al.  Inquiry-based requirements analysis , 1994, IEEE Software.

[25]  Robert L. Mack.  Discussion: scenarios as engines of design , 1995 .

[26]  Scott P. Robertson.  Generating object-oriented design representations via scenario queries , 1995 .

[27]  Kees Hengeveld,et al.  The Structure of the Clause , 1997 .

[28]  John F. Sowa,et al.  Conceptual Structures: Information Processing in Mind and Machine , 1983 .

[29]  Chris Dollin,et al.  Object-oriented development: the fusion method , 1994 .

[30]  Jakob Nielsen,et al.  Scenarios in discount usability engineering , 1995 .

[31]  Kevin Ryan,et al.  The role of natural language in requirements engineering , 1993, [1993] Proceedings of the IEEE International Symposium on Requirements Engineering.

[32]  Alistair Cockburn,et al.  Structuring Use Cases with Goals , 2000 .

[33]  Ivar Jacobson,et al.  The object advantage - business process reengineering with object technology , 1994 .

[34]  Björn Regnell,et al.  Improving the use case driven approach to requirements engineering , 1995, Proceedings of 1995 IEEE International Symposium on Requirements Engineering (RE'95).

[35]  Roger C. Schank,et al.  Computer Models of Thought and Language , 1974 .

[36]  Ivar Jacobson,et al.  Object-oriented software engineering - a use case driven approach , 1993, TOOLS.

[37]  Rebecca Wirfs-Brock,et al.  Designing objects and their interactions: a brief look at responsibility-driven design , 1995 .

[38]  Matthias Jarke,et al.  Scenario usage in system development: a report on current practice , 1998, Proceedings of IEEE International Symposium on Requirements Engineering: RE '98.

[39]  Ivar Jacobson,et al.  The use-case construct in object-oriented software engineering , 1995 .