Modeling interactions using role-driven patterns

Great interest in model-driven approaches that are based on the automatic transformation of models has emerged. In this software development paradigm, the models and their transformations are specified at a high abstraction level supporting evolution, refinement and code generation. One of the benefits that these approaches try to achieve is improving the software quality through the reusability of well proven patterns. In order to achieve this goal, this paper presents an approach that defines patterns to transform use case models into interaction models. This approach uses roles to capture the linguistic abstractions on the use case text as well as to describe the corresponding interaction. The roles are defined as model elements to guarantee genericity. In this way, the transformation patterns are independent of a specific domain or a technological platform. The defined patterns have been validated. Some of the validation results are also presented in this paper.

[1]  Björn Regnell,et al.  Requirements Engineering with Use Cases - a Basis for Software Development , 1999 .

[2]  Bashar Nuseibeh,et al.  Requirements engineering: a roadmap , 2000, ICSE '00.

[3]  Ralph Johnson,et al.  design patterns elements of reusable object oriented software , 2019 .

[4]  Daniel Jurafsky,et al.  Automatic Labeling of Semantic Roles , 2002, CL.

[5]  Robert B. France,et al.  A Metamodeling Approach to Pattern-Based Model Refactoring , 2003, IEEE Softw..

[6]  Christopher G. Lasater,et al.  Design Patterns , 2008, Wiley Encyclopedia of Computer Science and Engineering.

[7]  Ivar Jacobson,et al.  Object-Oriented Software Engineering , 1991, TOOLS.

[8]  Axel van Lamsweerde,et al.  Requirements engineering in the year 00: a research perspective , 2000, Proceedings of the 2000 International Conference on Software Engineering. ICSE 2000 the New Millennium.

[9]  Takako Nakatani,et al.  A requirements description metamodel for use cases , 2001, Proceedings Eighth Asia-Pacific Software Engineering Conference.

[10]  Oscar Pastor,et al.  Integrating Natural Language Techniques in OO-Method , 2005, CICLing.

[11]  Robert B. France,et al.  A UML-based pattern specification technique , 2004, IEEE Transactions on Software Engineering.

[12]  Neil A. M. Maiden,et al.  Guiding use case authoring: results of an empirical study , 1999, Proceedings IEEE International Symposium on Requirements Engineering (Cat. No.PR00188).

[13]  Grady Booch,et al.  Object-oriented development , 1986, IEEE Transactions on Software Engineering.

[14]  Charles J. Fillmore,et al.  THE CASE FOR CASE. , 1967 .

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

[16]  Oscar Pastor,et al.  A specification pattern for use cases , 2004, Inf. Manag..

[17]  Robert B. France,et al.  A role-based metamodeling approach to specifying design patterns , 2003, Proceedings 27th Annual International Computer Software and Applications Conference. COMPAC 2003.

[18]  E. Insfrána,et al.  Requirements Engineering-Based Conceptual Modelling , .

[19]  Coln Atkinson,et al.  Object-oriented development: The fusion method , 1996 .

[20]  Vicente Pelechano,et al.  The OO-method approach for information systems modeling: from object-oriented conceptual modeling to automated programming , 2001, Inf. Syst..

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

[22]  Heinrich C. Mayr,et al.  Linguistic aspects of dynamics in requirements specifications , 2000, Proceedings 11th International Workshop on Database and Expert Systems Applications.