A proposal for consolidated intentional modeling language

Intentional modeling (IM) focuses on intentions and motivations of software systems rather than behaviours. KAOS ("Knowledge Acquisition in autOmated Systems"), and i* ("Distributed Intentionality") are the two popular IM languages used in requirement engineering. Each of these languages are defined as a collection of intentional elements, and intentional properties. However, these intentional elements are fragmented across IM languages, and thus limited in supporting detailed requirement analysis. Our proposed solution is to combine these two languages into a consolidated modeling language using a Model Based Software Engineering (MBSE) language integration technique, in EMF-Ecore, and develop a graphical tool for the new modeling language. The graphical tool is applied on a case study to show that it supports detailed requirement analysis. The rationale behind this paper is to provide the Software Engineering Community with a richer but less cumbersome intentional modeling language that can support detailed requirement analysis, this can reduce the cost associated with incomplete requirement analysis during software development.

[1]  J. Zdravkovic,et al.  Goal support towards business processes modelling , 2008, 2008 International Conference on Innovations in Information Technology.

[2]  Xavier Franch,et al.  Definition and Uses of the i* Metamodel , 2010, iStar.

[3]  Brian Berenbach,et al.  Towards a unified Requirements Modeling Language , 2010, 2010 Fifth International Workshop on Requirements Engineering Visualization.

[4]  Julio Cesar Sampaio do Prado Leite,et al.  Comparing GORE Frameworks: i-star and KAOS , 2009, WER.

[5]  Elena Navarro,et al.  A Comparative of Goal-oriented Approaches to Modelling Requirements for Collaborative Systems , 2011, ENASE.

[6]  Axel van Lamsweerde,et al.  Managing Conflicts in Goal-Driven Requirements Engineering , 1998, IEEE Trans. Software Eng..

[7]  João Araújo,et al.  Mdgore: Towards Model-Driven and Goal-Oriented Requirements Engineering , 2010, 2010 18th IEEE International Requirements Engineering Conference.

[8]  João Araújo,et al.  Towards a Unified Goal-Oriented Language , 2011, 2011 IEEE 35th Annual Computer Software and Applications Conference.

[9]  Axel van Lamsweerde,et al.  Handling Obstacles in Goal-Oriented Requirements Engineering , 2000, IEEE Trans. Software Eng..

[10]  Alexei Lapouchnian,et al.  Goal-Oriented Requirements Engineering: An Overview of the Current Research , 2005 .

[11]  Markus Strohmaier,et al.  Exploring Intentional Modeling and Analysis for Enterprise Architecture , 2006, 2006 10th IEEE International Enterprise Distributed Object Computing Conference Workshops (EDOCW'06).

[12]  Oscar Pastor,et al.  From i* Requirements Models to Conceptual Models of a Model Driven Development Process , 2009, PoEM.

[13]  João Araújo,et al.  Model-Driven Development for Requirements Engineering: The Case of Goal-Oriented Approaches , 2012, 2012 Eighth International Conference on the Quality of Information and Communications Technology.

[14]  Eric S. K. Yu,et al.  Social Modeling and i* , 2009, Conceptual Modeling: Foundations and Applications.

[15]  Patrick Heymans,et al.  Comparing Goal Modelling Languages: An Experiment , 2007, REFSQ.

[16]  Roel Wieringa,et al.  Goal-Oriented Requirements Engineering and Enterprise Architecture: Two Case Studies and Some Lessons Learned , 2012, REFSQ.

[17]  Anthony Finkelstein,et al.  A UML profile to support requirements engineering with KAOS , 2002 .

[18]  Richard F. Paige,et al.  Taming EMF and GMF using model transformation , 2010, MODELS'10.