Use Case Specification at Different Levels of Abstraction

Use cases are narrative description of interactions between users and a software system. They are primary used to specify functional system requirements. Despite the fact that use cases are narrative, there is no standard that specifies what textual specification of use case should like. However, the integration of use cases in a Model Driven Engineering process requires more rigorous specifications. The specification of use cases at different levels of abstraction is needed because of the large number of stakeholders involved in the software development process. We propose use cases specification at different levels of abstraction to promote better integration, communication and understanding among the involved stakeholders. We still discuss that base on this approach different software development artifacts such as domain model, system operations, user interface design can be automatically generated or validated.

[1]  João Saraiva,et al.  Integration of RE and MDE paradigms: the ProjectIT approach and tools , 2007, IET Softw..

[2]  Michal Smialek,et al.  Accommodating Informality with Necessary Precision in Use Case Scenarios , 2005, J. Object Technol..

[3]  Carlos Videira,et al.  A Linguistic Patterns Approach for Requirements Specification , 2006, 32nd EUROMICRO Conference on Software Engineering and Advanced Applications (EUROMICRO'06).

[4]  Ivar Jacobson,et al.  The Unified Software Development Process , 1999 .

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

[6]  Clay E. Williams.  Towards a Test-Ready Meta-model for Use Cases , 2001, pUML.

[7]  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.

[8]  Juan Llorens Morillo,et al.  Use Cases in Model-Driven Software Engineering , 2005, MoDELS.

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

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

[11]  Silvia Mara Abrahão,et al.  A systematic review of the use of requirements engineering techniques in model-driven development , 2010, MODELS'10.

[12]  Milos Milic,et al.  Language for Use Case Specification , 2011, 2011 IEEE 34th Software Engineering Workshop.

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

[14]  Stéphane S. Somé.  Supporting use case based requirements engineering , 2006, Inf. Softw. Technol..

[15]  Rui Silva,et al.  XIS-UML Profile for eXtreme Modeling Interactive Systems , 2007, Fourth International Workshop on Model-Based Methodologies for Pervasive and Embedded Software (MOMPES'07).

[16]  Fábio Levy Siqueira,et al.  An Essential Textual Use Case Meta-model Based on an Analysis of Existing Proposals , 2011, WER.

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

[18]  Hermann Kaindl,et al.  On confusion between requirements and their representations , 2010, Requirements Engineering.

[19]  Terence John Parr,et al.  ANother Tool for Language Recognition , 2005 .

[20]  Guy Genilloud,et al.  Use Cases, Actions, and Roles , 2005, MoDELS.

[21]  A. Silva,et al.  The ProjectIT-Studio , an integrated environment for the development of information systems , 2006 .

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

[23]  Stéphane S. Somé.  A Meta-Model for Textual Use Case Description , 2009, J. Object Technol..