Automatic Comprehension of Textual User Requirements and their Static and Dynamic Modeling

Requirements engineering is the most important activity in software engineering, and is concerned with the gathering and understanding of user requirements written in natural language (NL). There is a gap between the textual description of the software to be developed, and the software UML models abstracting the static or dynamic views of the software. Our research is aimed at filling this gap by automatically extracting from text a more universal (graphical) hybrid model to present the variety of knowledge that can be found in textual requirements written in unlimited NL. The advantages of a hybrid diagram include its ability to illustrate, in a way which is graphical and simple to perceive, both the static and dynamic view of the system to be developed. The hybrid diagram serves as a source for an automatic inspection of the requirements text, and will provide timely feedback to the user on the actual content of the requirements he/she has written. Such feedback will enable correction and clarification of the text before it is delivered to the software developers, thereby helping them to avoid incorrect interpretation of the requirements. The hybrid diagram also allows for automatic generation of scenario-based black-box test cases for ensuring the final quality of the software.

[1]  Dong Liu,et al.  UCDA: Use Case Driven Development Assistant Tool for Class Model Generation , 2004, SEKE.

[2]  Colette Rolland,et al.  Guiding the Construction of Textual Use Case Specifications , 1998, Data Knowl. Eng..

[3]  J. F. M. Burg,et al.  The Impact of Linguistics on Conceptual Models: Consistency and Understandability , 1995, Data Knowl. Eng..

[4]  Daniel Amyot,et al.  Use case maps for the capture and validation of distributed systems requirements , 1999, Proceedings IEEE International Symposium on Requirements Engineering (Cat. No.PR00188).

[5]  Olga Ormandjieva,et al.  Automatic Transition of Natural Language Software Requirements Specification into Formal Presentation , 2005, NLDB.

[6]  Christian Kop,et al.  From textual scenarios to a conceptual schema , 2005, Data Knowl. Eng..

[7]  Nik Boyd,et al.  Using Natural Language in Software Development , 1999, J. Object Oriented Program..

[8]  Colette Rolland From Conceptual Modeling to Requirements Engineering , 2006, ER.

[9]  Heinrich C. Mayr,et al.  From Scenarios to KCPM Dynamic Schemas: Aspects of Automatic Mapping , 2003, NLDB.

[10]  Walter Daelemans,et al.  MBT: A Memory-Based Part of Speech Tagger-Generator , 1996, VLC@COLING.

[11]  Beum-Seuk Lee,et al.  Automated conversion from requirements documentation to an object-oriented formal specification language , 2002, SAC '02.

[12]  Vangalur S. Alagar,et al.  Automated test generation from object-oriented specifications of real-time reactive systems , 2003, Tenth Asia-Pacific Software Engineering Conference, 2003..

[13]  Vladimir Mencl DERIVING BEHAVIOR SPECIFICATIONS FROM TEXTUAL USE CASES , 2004 .

[14]  Daniel Amyot,et al.  Generating scenarios from use case map specifications , 2003, Third International Conference on Quality Software, 2003. Proceedings..