Towards the Integration of UML- and textual Use Case Modeling

In this paper, we present a metamodel for textual use case descriptions, structurally conforming to the UML, to specify the behavior of use cases in a flow-oriented manner. While being primarily targeted at supporting requirements engineers in creating consistent use case models, the metamodel defines a textual representation of use case behavior that is easily understandable for readers, who are unaware of the underlying metamodel. Hence, the known benefits of natural language use case descriptions are preserved. Being formalized, consistency between UML-based use case representations and their textual descriptions can be automatically ensured. With NaUTiluS we present an extensible, Eclipse-based toolkit, which offers integrated UML use case modeling support, as well as editing capabilities for their textual descriptions.

[1]  Claus Bossen,et al.  Executable use cases: requirements for a pervasive health care system , 2004, IEEE Software.

[2]  Ivar Jacobson,et al.  Object Oriented Development in an Industrial Environment , 1987, OOPSLA.

[3]  Kurt Bittner,et al.  Use Case Modeling , 2002 .

[4]  Mordechai Ben-Menachem,et al.  Writing effective use cases , 2001, SOEN.

[5]  Martin Glinz,et al.  SCENT: A Method Employing Scenarios to Systematically Derive TestCases for System Test , 2000 .

[6]  Klaus Pohl,et al.  The ScenTED Method for Testing Software Product Lines , 2006, Software Product Lines.

[7]  Wolfgang Weber,et al.  Specifying Use Case Interaction: Types of Alternative Courses , 2003, J. Object Technol..

[8]  Daryl Kulak,et al.  Use cases: requirements in context , 2000, SOEN.

[9]  Armin Eberlein,et al.  Requirements engineering for time-to-market projects , 2002, Proceedings Ninth Annual IEEE International Conference and Workshop on the Engineering of Computer-Based Systems.

[10]  Amit M. Paradkar,et al.  Toward Engineered, Useful Use Cases , 2005, J. Object Technol..

[11]  Colin J. Neill,et al.  Requirements Engineering: The State of the Practice , 2003, IEEE Softw..

[12]  Liwu Li,et al.  Translating use cases to sequence diagrams , 2000, Proceedings ASE 2000. Fifteenth IEEE International Conference on Automated Software Engineering.

[13]  Ivar Jacobson,et al.  Use cases – Yesterday, today, and tomorrow , 2004, Software & Systems Modeling.

[14]  Vladimir Mencl,et al.  Improved Processing of Textual Use Cases: Deriving Behavior Specifications , 2007, SOFSEM.

[15]  Andreas Paepcke,et al.  Conference proceedings on Object-oriented programming systems, languages, and applications , 1991, Conference on Object-Oriented Programming Systems, Languages, and Applications.

[16]  Deepali Kholkar,et al.  Visual specification and analysis of use cases , 2005, SoftVis '05.

[17]  Martin Glinz,et al.  Problems and deficiencies of UML as a requirements specification language , 2000, Tenth International Workshop on Software Specification and Design. IWSSD-10 2000.

[18]  Jon Whittle,et al.  Generating Hierarchical State Machines from Use Case Charts , 2006, 14th IEEE International Requirements Engineering Conference (RE'06).

[19]  J. Michael Spivey,et al.  The Z notation - a reference manual , 1992, Prentice Hall International Series in Computer Science.

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