Annotating Goals with Concerns in Goal-Oriented Requirements Engineering
In goal-oriented requirements analysis, goals specify multiple concerns such as functions, strategies, and non-functions, and they are refined into sub goals from mixed views of these concerns. This intermixture of concerns in goals makes it difficult for a requirements analyst to understand and maintain goal refinements. Separating concerns and specifying them explicitly is one of the useful approaches to improve the understandability of goal refinements, i.e., the relations between goals and their sub goals. In this paper, we propose a technique to annotate goals with the concerns they have in order to support the understanding of goal refinement. In our approach, goals are refined into sub goals referring to the annotated concerns, and these concerns annotated to a goal and its sub goals provide the meaning of its goal refinement. By tracing and focusing on the annotated concerns, requirements analysts can understand goal refinements and modify unsuitable ones. We have developed a supporting tool and made an exploratory experiment to evaluate the usefulness of our approach.
KeywordsGoal-oriented requirements engineering Concern Goal refinement
This work was partly supported by JSPS Grants-in-Aid for Scientific Research (#15K00088 and #15K00109).
- 3.Giorgini, P., Rizzi, S., Garzetti, M.: Goal-oriented requirements analysis for data warehouse design. In: Proceedings of the 8th ACM International Workshop on Data Warehousing and OLAP (DOLAP 2005), pp. 47–56 (2005)Google Scholar
- 5.van Lamsweerde, A.: Goal-oriented requirements engineering: a guided tour. In: Proceedings of the 5th IEEE International Symposium on Requirements Engineering (RE 2001), pp. 249–263 (2001)Google Scholar
- 6.van Lamsweerde, A.: Requirements Engineering: From System Goals to UML Models to Software Specifications. Wiley, Hoboken (2009)Google Scholar
- 7.Makino, N., Suzuki, T.: Convenience stores and the information revolution. Jpn. Echo 24(1), 44–49 (1997)Google Scholar
- 8.Moreira, A., Rashid, A., Araujo, J.: Multi-dimensional separation of concerns in requirements engineering. In: Proceedings of the 13th IEEE International Conference on Requirements Engineering (ICSE 2005), pp. 285–296 (2005)Google Scholar
- 9.Munro, S., Liaskos, S., Aranda, J.: The mysteries of goal decomposition. In: Proceedings of the 5th International i* Workshop (iStar 2011), pp. 49–54 (2011)Google Scholar
- 10.Mylopoulos, J., Chung, L., Nixon, B.: Representing and using non-functional requirements: a process-oriented approach. IEEE Trans. Softw. Eng. 6(4), 489–497 (1992)Google Scholar
- 11.Saeki, M., Hayashi, S., Kaiya, H.: A tool for attributed goal-oriented requirements analysis. In: Proceedings of the 24th IEEE/ACM International Conference on Automated Software Engineering (ASE 2009), pp. 670–672 (2009)Google Scholar
- 12.Tanabe, D., Uno, K., Akemine, K., Yoshikawa, T., Kaiya, H., Saeki, M.: Supporting requirements change management in goal oriented analysis. In: Proceedings of the 16th IEEE International Requirements Engineering Conference (RE 2008), pp. 3–12 (2008)Google Scholar
- 13.Tarr, P., Ossher, H., Harrison, W., Sutton Jr., S.M.: N degrees of separation: multi-dimensional separation of concerns. In: Proceedings of the 10th International Conference on Software Engineering (ICSE 1999), pp. 107–119 (1999)Google Scholar
- 14.Yu, E.: Towards modeling and reasoning support for early-phase requirements engineering. In: Proceedings of the 3rd IEEE International Symposium on Requirements Engineering (RE 1997), pp. 226–235 (1997)Google Scholar