How Can You Improve Your As-Is Models? Requirements Analysis Methods Meet GQM

  • Shoichiro Ito
  • Shinpei Hayashi
  • Motoshi Saeki
Conference paper
Part of the Lecture Notes in Computer Science book series (LNCS, volume 10153)


Context & motivation: To develop information systems providing high business value, we should clarify As-is business processes and information systems supporting them, identify the problems hidden in them, and develop To-be information systems so that the identified problems can be solved. Question/problem: In this development, we need a technique to support the identification of the problems, which can be seamlessly connected to the modeling techniques. Principal ideas/results: In this paper, to define metrics to extract problems of the As-is system, following the domains specific to it, we propose the combination of Goal-Question-Metric (GQM) with existing requirements analysis techniques. Furthermore, we integrate goal-oriented requirements analysis (GORA) with problem frames approach and use case modeling to define the metrics of measuring the problematic efforts of human actors in the As-is models. This paper includes a case study of a reporting operation process at a brokerage office to check the feasibility of our approach. Contribution: Our contribution is the proposal of using of GQM to identify the problems of an As-is model specified with the combination of GORA, use case modeling, and problem frames.


Goal-Question-Metric paradigm Goal-oriented requirements analysis Use case modeling Problem frames 



This work was partly supported by JSPS Grants-in-Aid for Scientific Research Number 15K00088.


  1. 1.
    Basili, V., Caldiera, C., Rombach, D.: Goal, question, metric paradigm. Encycl. Softw. Eng. 1, 528–532 (1994)Google Scholar
  2. 2.
    Beckers, K., Faßbender, S., Heisel, M., Paci, F.: Combining goal-oriented and problem-oriented requirements engineering methods. In: Cuzzocrea, A., Kittl, C., Simos, D.E., Weippl, E., Xu, L. (eds.) CD-ARES 2013. LNCS, vol. 8127, pp. 178–194. Springer, Heidelberg (2013). doi: 10.1007/978-3-642-40511-2_13 CrossRefGoogle Scholar
  3. 3.
    Bernárdez, B., Durán, A., Genero, M.: Empirical evaluation and review of a metrics based approach for use case verification. J. Res. Pract. Inf. Technol. 36(4), 247–258 (2004)Google Scholar
  4. 4.
    Bresciani, P., Perini, A., Giorgini, P., Giunchiglia, F., Mylopoulos, J.: Tropos: an agent-oriented software development methodology. Auton. Agent. Multi-Agent Syst. 8(3), 203–236 (2004)CrossRefzbMATHGoogle Scholar
  5. 5.
    Cockburn, A.: Structuring use cases with goals.
  6. 6.
    Guizzardi, R., Reis, A.N.: A method to align goals and business processes. In: Johannesson, P., Lee, M.L., Liddle, S.W., Opdahl, A.L., López, Ó.P. (eds.) ER 2015. LNCS, vol. 9381, pp. 79–93. Springer, Heidelberg (2015). doi: 10.1007/978-3-319-25264-3_6 CrossRefGoogle Scholar
  7. 7.
    Jackson, M.: Problem Frames. Addison-Wesley, Boston (2001)Google Scholar
  8. 8.
    Jin, Z., Liu, L.: Requirements analyses integrating goals and problem analysis techniques. Tsinghua Sci. Technol. 12(6), 729–740 (2007)MathSciNetCrossRefGoogle Scholar
  9. 9.
    Kaiya, H., Morita, S., Ogata, S., Kaijiri, K., Hayashi, S., Saeki, M.: Model transformation patterns for introducing suitable information systems. In: Proceedings of the 19th Asia-Pacific Software Engineering Conference, pp. 434–439 (2012)Google Scholar
  10. 10.
    Kaplan, R.S., Bruns, W.: Accounting and Management: A Field Study Perspective. Harvard Business School Press, Brighton (1987)Google Scholar
  11. 11.
    van Lamsweerde, A.: Requirements Engineering: From System Goals to UML Models to Software Specifications. Wiley, Hoboken (2009)Google Scholar
  12. 12.
    Mohammadi, N.G., Alebrahim, A., Weyer, T., Heisel, M., Pohl, K.: A framework for combining problem frames and goal models to support context analysis during requirements engineering. In: Cuzzocrea, A., Kittl, C., Simos, D.E., Weippl, E., Xu, L. (eds.) CD-ARES 2013. LNCS, vol. 8127, pp. 272–288. Springer, Heidelberg (2013). doi: 10.1007/978-3-642-40511-2_19 CrossRefGoogle Scholar
  13. 13.
    Rolland, C., Achour, C.B.: Guiding the construction of textual use case specifications. Data Knowl. Eng. 25(1–2), 125–160 (1998)CrossRefzbMATHGoogle Scholar
  14. 14.
    Supakkul, S., Chung, L.: Extending problem frames to deal with stakeholder problems. In: Proceedings of the ACM Symposium on Applied Computing, pp. 389–394 (2009)Google Scholar
  15. 15.
    Watahiki, K., Saeki, M.: Combining goal-oriented analysis and use case analysis. IEICE Trans. 87-D(4), 822–830 (2004)Google Scholar
  16. 16.
    Yang, J., Liu, L.: Modelling requirements patterns with a goal and PF integrated analysis approach. In: Proceedings of the 32nd Annual IEEE International Computer Software and Applications Conference, pp. 239–246 (2008)Google Scholar
  17. 17.
    Yu, E.S.: Social modeling and i*. In: Borgida, A.T., Chaudhri, V.K., Giorgini, P., Yu, E.S. (eds.) Conceptual Modeling: Foundations and Applications. LNCS, vol. 5600, pp. 99–121. Springer, Heidelberg (2009). doi: 10.1007/978-3-642-02463-4_7 CrossRefGoogle Scholar

Copyright information

© Springer International Publishing AG 2017

Authors and Affiliations

  1. 1.Department of Computer ScienceTokyo Institute of TechnologyMeguro-kuJapan

Personalised recommendations