CSRML: A Goal-Oriented Approach to Model Requirements for Collaborative Systems

  • Miguel A. Teruel
  • Elena Navarro
  • Víctor López-Jaquero
  • Francisco Montero
  • Pascual González
Part of the Lecture Notes in Computer Science book series (LNCS, volume 6998)


A collaborative system is software which allows several users to work together and carry out collaboration, communication and coordination tasks. To perform these tasks, the users have to be aware of other user’s actions, usually by means of a set of awareness techniques. In previous works, we found by means of empirical studies that the most suitable Requirements Engineering approach to specify the requirements of this kind of systems is the Goal-Oriented one, and more precisely i* approach. In this paper, CSRML (Collaborative Systems Requirements Modelling Language) is presented, an extension of i* to deal with the specification of the requirements of these systems in which the collaboration and the awareness of other users presence / actions are crucial. In order to validate this proposal, a case study has been carried out by modelling a jigsaw activity: a cooperative-learning technique in which students individually do some research in a proposed problem and then they teach each other what they have learned by sharing each individual view of the problem.


Collaborative systems Awareness Requirements Engineering Goal-Oriented i* CSRML 


Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.


  1. 1.
    Pressman, R.S.: Software engineering: a practitioners approach. McGraw-Hill Science/Engineering/Math (2009)Google Scholar
  2. 2.
    Pohl, K.: Requirements Engineering: Fundamentals, Principles, and Techniques. Springer, Heidelberg (2010)CrossRefGoogle Scholar
  3. 3.
    Gutwin, C., Greenberg, S.: A Descriptive Framework of Workspace Awareness for Real-Time Groupware. Computer Supported Cooperative Work 11, 411–446 (2002)CrossRefGoogle Scholar
  4. 4.
    Hochmuller, H.: Towards the Proper Integration of Extra-Functional Requirements. Australasian Journal of Information Systems 6, 98–117 (1999)CrossRefGoogle Scholar
  5. 5.
    Teruel, M.A., Navarro, E., López-Jaquero, V., Montero, F., González, P.: An Empirical Evaluation of Requirement Engineering Techniques for Collaborative Systems. In: 15th International Conference on Evaluation and Assessment in Software Engineering, Durham, UK (2011)Google Scholar
  6. 6.
    Kitchenham, B.: A methodology for evaluating software engineering methods and tools. In: Rombach, H., Basili, V., Selby, R. (eds.) Experimental Software Engineering Issues: Critical Assessment and Future Directions. LNCS, vol. 706, pp. 121–124. Springer, Heidelberg (1993)CrossRefGoogle Scholar
  7. 7.
    van Lamsweerde, A.: Goal-Oriented Requirements Engineering: A Guided Tour. In: Proceedings of the Fifth IEEE International Symposium on Requirements Engineering, pp. 249–263. IEEE Computer Society, Los Alamitos (2001)Google Scholar
  8. 8.
    Cockburn, A.: Writting Effective Use Cases. Addison-Wesley, Reading (2000)Google Scholar
  9. 9.
    Booch, G., Rumbaugh, J., Jacobson, I.: The Unified Modeling Language User Guide. Addison-Wesley, Reading (2005)Google Scholar
  10. 10.
    Finkelsetin, A., Kramer, J., Nuseibeh, B., Finkelstein, L., Goedicke, M.: Viewpoints: A Framework for Integrating Multiple Perspectives in System Development. International Journal of Software Engineering and Knowledge Engineering 2, 31–57 (1992)CrossRefGoogle Scholar
  11. 11.
    Teruel, M.A., Navarro, E., López-Jaquero, V., Montero, F., González, P.: A Comparative of Goal-Oriented Approaches to Modelling Requirements for Collaborative Systems. In: 6th International Conference on Evaluation of Novel Software Approaches to Software Engineering, Beijing, China (2011)Google Scholar
  12. 12.
    Cysneiros, L.M., Yu, E.: Non-Functional Requirements Elicitation (Perspectives on Software Requirements). Springer, Heidelberg (2003)Google Scholar
  13. 13.
    Castro, J., Kolp, M., Mylopoulos, J.: A requirements-driven development methodology. In: Dittrich, K.R., Geppert, A., Norrie, M.C. (eds.) CAiSE 2001. LNCS, vol. 2068, pp. 108–123. Springer, Heidelberg (2001)CrossRefGoogle Scholar
  14. 14.
    Google, Google Docs (2001)Google Scholar
  15. 15.
    Kavakli, E., Loucopoulos, P.: Goal Modeling in Requirements Engineering: Analysis and Critique of Current Methods. In: Information Modeling Methods and Methodologies, pp. 102–124 (2004)Google Scholar
  16. 16.
    Chung, L., Nixon, B., Yu, E., Mylopoulos, J.: No Non-Functional Requirements in Software EngineeringTitle. Kluwer Academic Publishers, Dordrecht (1999)Google Scholar
  17. 17.
    Noguera, M., González, M., Garrido, J.L., Hurtado, V., Rodríguez, M.: System Modeling for Systematic Development of Groupware Applications. In: International Conference on Software Engineering Research and Practice, pp. 750–756 (2006)Google Scholar
  18. 18.
    Pozzi, F.: Using Jigsaw and Case Study for supporting online collaborative learning. Computers & Education 55, 67–75 (2010)CrossRefGoogle Scholar
  19. 19.
    Gutwin, C., Greenberg, S., Roseman, M.: Workspace Awareness in Real-Time Distributed Groupware: Framework, Widgets, and Evaluation. In: Proceedings of HCI on People and Computers XI, pp. 281–298. Springer, Heidelberg (1996)Google Scholar
  20. 20.
    Fardoun, H., Montero, F., López-Jaquero, V.: eLearniXML: Towards a model-based approach for the development of e-Learning systems considering quality. Advances in Engineering Software 40, 1297–1305 (2009)CrossRefGoogle Scholar

Copyright information

© Springer-Verlag Berlin Heidelberg 2011

Authors and Affiliations

  • Miguel A. Teruel
    • 1
  • Elena Navarro
    • 1
  • Víctor López-Jaquero
    • 1
  • Francisco Montero
    • 1
  • Pascual González
    • 1
  1. 1.LoUISE Research Group, Computing Systems DepartmentUniversity of CastillaLa ManchaSpain

Personalised recommendations