ABSTRACT
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.
- Fernanda M. Alencar, Beatriz Marin, Giovanni Giachetti, Oscar Pastor, Jaelson Castro, and Joao Henrique Pimentel. From i* requirements models to conceptual models of a model driven development process. In PoEM, pages 99--114, 2009.Google ScholarCross Ref
- Carlos Cares, Xavier Franch, Lidia Lopez, and Jordi Marco. Definition and uses of the i* metamodel. In Jaelson Brelaz de Castro, Xavier Franch, John Mylopoulos, and Eric S. K. Yu, editors, Proceedings of the 4th International i* Workshop, Hammamet, Tunisia, June 07--08, 2010, volume 586 of CEUR Workshop Proceedings, pages 20--25. CEUR-WS.org, June 2010.Google Scholar
- A. Edirisuriya and J. Zdravkovic. Goal support towards business processes modelling. In Innovations in Information Technology, 2008. IIT 2008. International Conference on, pages 208--212, dec. 2008.Google ScholarCross Ref
- Wilco Engelsman and Roel Wieringa. Goal-oriented requirements engineering and enterprise architecture: Two case studies and some lessons learned. In REFSQ, pages 306--320, 2012. Google ScholarDigital Library
- W. Heaven and A. Finkelstein. Uml profile to support requirements engineering with kaos. Software, IEE Proceedings -, 151(1):10--27, feb. 2004.Google ScholarCross Ref
- J. Helming, M. Koegel, F. Schneider, M. Haeger, C. Kaminski, B. Bruegge, and B. Berenbach. Towards a unified requirements modeling language. In Requirements Engineering Visualization (REV), 2010 Fifth International Workshop on, pages 53--57, sept. 2010.Google ScholarCross Ref
- Jennifer Horkoff, Yu Eric, and Gemma Grau. istar quick guide, 2006.Google Scholar
- Dimitrios S Kolovos, Louis M Rose, Saad Bin Abid, Richard F Paige, Fiona AC Polack, and Goetz Botterweck. Taming emf and gmf using model transformation. In Model Driven Engineering Languages and Systems, pages 211--225. Springer, 2010. Google ScholarDigital Library
- Alexei Lapouchnian. Goal oriented requirement engineering: An overview of the current research, 2005.Google Scholar
- Raimundas Matulevicius and Patrick Heymans. Comparing goal modelling languages: An experiment. In REFSQ, pages 18--32, 2007. Google ScholarDigital Library
- R. Monteiro, J. Arau andjo, V. Amaral, and P. Patri andcio. Mdgore: Towards model-driven and goal-oriented requirements engineering. In Requirements Engineering Conference (RE), 2010 18th IEEE International, pages 405--406, 27 2010-oct. 1 2010. Google ScholarDigital Library
- R. Monteiro, J. Araujo, Vasco Amaral, M. Goulao, and P. M. B. Patricio. Model-driven development for requirements engineering: The case of goal-oriented approaches. In Ricardo Machado Joao Pascoal Faria, Alberto Silva, editor, 8th International Conference on the Quality of Information and Communications Technology (QUATIC 2012), number 8 in Quality of Information and Communications Technology, pages 75--84. IEEE Computer Society, 09 2012. Google ScholarDigital Library
- Pedro Patricio, Vasco Amaral, Joao Araujo, and Rui Monteiro. Towards a unified goal-oriented language. In COMPSAC, pages 596--601, 2011. Google ScholarDigital Library
- Respect-IT. A kaos tutorial, 2007.Google Scholar
- Miguel A. Teruel, Elena Navarro, Víctor López-Jaquero, Francisco Montero Simarro, and Pascual González. A comparative of goal-oriented approaches to modelling requirements for collaborative systems. In ENASE, pages 131--142, 2011.Google Scholar
- A. van Lamsweerde. Goal-oriented requirements engineering: a guided tour. In Requirements Engineering, 2001. Proceedings. Fifth IEEE International Symposium on, pages 249--262, 2001. Google ScholarDigital Library
- A. van Lamsweerde, R. Darimont, and E. Letier. Managing conflicts in goal-driven requirements engineering. Software Engineering, IEEE Transactions on, 24(11):908--926, nov 1998. Google ScholarDigital Library
- Axel van Lamsweerde and Emmanuel Letier. Handling obstacles in goal-oriented requirements engineering. IEEE Transactions on Software Engineering, 26:978--1005, 2000. Google ScholarDigital Library
- Vera Maria Bejamim Werneck, Antonio de Padua Albuquerque Oliveira, and Julio Cesar Sampaio do Prado Leite. Comparing gore frameworks: i-star and kaos. In Ibero-American Workshop of Engineering of Requirements, Val Paraiso, Chile, July 2009.Google Scholar
- E. Yu, M. Strohmaier, and X. Deng. Exploring intentional modeling and analysis for enterprise architecture. In Enterprise Distributed Object Computing Conference Workshops, 2006. EDOCW'06. 10th IEEE International, pages 32--32. IEEE, 2006. Google ScholarDigital Library
- Eric S. K. Yu. Social modeling and i*. In Conceptual Modeling: Foundations and Applications, pages 99--121, 2009.Google ScholarDigital Library
Recommendations
Requirements elicitation with business process modeling
PLoP '14: Proceedings of the 21st Conference on Pattern Languages of ProgramsRequirements Elicitation is the area of Requirements Engineering that deals with identifying system requirements. The paper documents a pattern showing how to elicit functional requirements for a software product in the form of User Stories through ...
Requirements management within a full model-based engineering approach
In this paper we show how the Property-Based Requirements (PBR) theory can be used to fully integrate Requirements Engineering (RE) into a Model-Based Systems Engineering (MBSE) method using OMG UML and its SysML profile. The objective is to avoid “in-...
A family of experiments to evaluate the understandability of TRiStar and i* for modeling teleo-reactive systems
An i* extension for teleo-reactive (TR) systems named TRiStar.A novel approach to modeling software requirements of TR systems using TRiStar.An empirical proof of the higher efficiency of TRiStar vs i* for TR systems.An empirical proof of the higher ...
Comments