Managing Conflicts in Goal-Driven Requirements Engineering
IEEE Transactions on Software Engineering
Handling Obstacles in Goal-Oriented Requirements Engineering
IEEE Transactions on Software Engineering - special section on current trends in exception handling—part II
Goal-Oriented Requirements Engineering: A Guided Tour
RE '01 Proceedings of the Fifth IEEE International Symposium on Requirements Engineering
Exploring Intentional Modeling and Analysis for Enterprise Architecture
EDOCW '06 Proceedings of the 10th IEEE on International Enterprise Distributed Object Computing Conference Workshops
Comparing goal modelling languages: an experiment
REFSQ'07 Proceedings of the 13th international working conference on Requirements engineering: foundation for software quality
Mdgore: Towards Model-Driven and Goal-Oriented Requirements Engineering
RE '10 Proceedings of the 2010 18th IEEE International Requirements Engineering Conference
Taming EMF and GMF using model transformation
MODELS'10 Proceedings of the 13th international conference on Model driven engineering languages and systems: Part I
Towards a Unified Goal-Oriented Language
COMPSAC '11 Proceedings of the 2011 IEEE 35th Annual Computer Software and Applications Conference
REFSQ'12 Proceedings of the 18th international conference on Requirements Engineering: foundation for software quality
Model-Driven Development for Requirements Engineering: The Case of Goal-Oriented Approaches
QUATIC '12 Proceedings of the 2012 Eighth International Conference on the Quality of Information and Communications Technology
| Hi-index | 0.00 |
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.