APRES 2016: Requirements Engineering Toward Sustainable World pp 79-93 | Cite as
2-dip-dfs: Algorithm to Detect Conflict Between Two Goal Selection Criteria
Abstract
In the requirements elicitation stage of goal-oriented requirements engineering, there is often a conflict between two goal selection criteria. This conflict can be detected by analyzing all pairs of each goal selection criterion for each subgoal graph with two layers in a goal graph. In this study, we defined a conflict between two goal selection criteria as a situation in which the selected child goal of a parent goal is different between one goal selection criterion in the pair and the other. On this basis, we proposed a metric called 2-dip(g) for detecting conflicts. Based on 2-dip(g), we developed an algorithm that can detect all conflicts in a goal graph. Because the algorithm uses a depth-first search, we called it 2-dip-dfs. By applying the algorithm result to a real goal graph, we demonstrated that 2-dip-dfs functions as designed.
Keywords
Goal-oriented requirements engineering Requirements elicitation Goal selection criteria Conflict detectionReferences
- 1.Aho, A.V., Hopcroft, J.E., Ullman, J.D.: Data Structures and Algorithms. Addison Wesley, Amsterdam (1983)MATHGoogle Scholar
- 2.Alexander, I., Beus-Dukic, L.: Discovering Requirements. John Wiley & Sons, New York (2009)Google Scholar
- 3.Boehm, B.W.: Software Engineering Economics. Prentice Hall, Englewood Cliffs (1981)MATHGoogle Scholar
- 4.Giorgini, P., Mylopoulos, J., Sebastiani, R.: Goal-oriented requirements analysis and reasoning in the tropos methodology. Eng. Appl. Artif. Intell. 18, 159–171 (2005)CrossRefGoogle Scholar
- 5.Horkoff, J., Yu, E.: Analyzing goal models - different approaches and how to choose among them. In: Proceedings of the 11th SIGAPP ACM Symposium on Applied Computing (SAC 2011), pp. 675–682 (2011)Google Scholar
- 6.Kaiya, H., Horai, H., Saeki, M.: AGORA: attributed goal-oriented requirements analysis method. In: Proceedings of the 10th Anniversary IEEE Joint International Conference on Requirements Engineering (RE 2002), pp. 13–22 (2002)Google Scholar
- 7.Kaiya, H., Shinbara, D., Kawano, J., Saeki, M.: Improving the detection of requirements discordances among stakeholders. Requirements Eng. 10(4), 289–303 (2005)CrossRefGoogle Scholar
- 8.van Lamsweerde, A., Darimont, R., Letier, E.: Managing conflicts in goal-driven requirements engineering. IEEE Trans. Softw. Eng. (TSE) 24(11), 908–926 (1998). Special Issue on Managing Inconsistency in Software in Software DeveloptmentCrossRefGoogle Scholar
- 9.Mylopoulos, J.: Goal-oriented requirements engineering: Part II. In: Presentation Slides of the 14th IEEE International Requirements Engineering Conference (RE 2006) (2006). https://files.ifi.uzh.ch/rerg/arvo/events/RE06/ConferenceProgram/RE06_slides_Mylopoulos.pdf
- 10.Mylopoulos, J., Castro, J., Kolp, M.: Tropos: a framework for requirements-driven software development. In: Information Systems Engineering: State of the Art and Research Themes, pp. 261–273. Springer, Berlin (2000)Google Scholar
- 11.Nilsson, N.J.: Principles of Artificial Intelligence. Morgan Kaufmann Publishers, San Mateo (1980)MATHGoogle Scholar
- 12.Robertson, S., Robertson, J. (eds.): Mastering the Requirements Process: Getting Requirements Right, 3rd edn. Addison-Wesley Professional, Boston (2012)Google Scholar
- 13.Saito, S., Yamamoto, S.: An attributed-based goal selection analysis method. J. Jpn Soc. Manage. Inf. 15(3), 37–50 (2006). [in Japanese]Google Scholar
- 14.van Lamsweerde, A.: Requirements Engineering: From System Goals to UML Models to Software Specifications. John Wiley & Sons, Chichester (2009)Google Scholar
- 15.Yamamoto, S., Kaiya, H., Cox, K., Bleinstein, S.: Goal oriented requirements engineering trends and issues. IEICE Trans. Inf. Syst. E89-D(11), 2701–2711 (2006)Google Scholar
- 16.Yu, E., Giorgini, P., Maiden, N., Mylopoulos, J.: Social Modeling for Requirements Engineering. The MIT Press, Cambridge (2011)Google Scholar