An empirical study of requirements model understanding: Use Case vs. Tropos models

Visual modelling languages are commonly used to support software requirements analysis and documentation. A variety of languages are available, based on different conceptual paradigms. They can be roughly divided into two main groups: goal-oriented approaches and scenario-based approaches. In the last ten years, numerous works developed case studies that illustrate the effectiveness and limitations of goal-oriented and scenario-based approaches. A few works even suggest coupling these approaches in order to capture requirements from different perspectives. However, experimental comparisons of these approaches have been rarely addressed. This paper presents the design and preliminary results of an empirical study that compares two state of the art requirements modelling methods: Use Cases, which is a scenario-based approach, and Tropos, which is a goal-oriented approach. The objective is to evaluate different levels of comprehension of requirements models expressed in both methods, as well as to estimate the time required to perform simple analysis tasks using both methods. Preliminary results show that Tropos models seem to be more comprehensible, although more time consuming, than Use Case models to novice requirements analysts.

[1]  John Mylopoulos,et al.  Information Modeling in the Time of the Revolution , 1998, Inf. Syst..

[2]  Colette Rolland,et al.  Experience with goal-scenario coupling in requirements engineering , 1999, Proceedings IEEE International Symposium on Requirements Engineering (Cat. No.PR00188).

[3]  Stephen Fickas,et al.  Goal-Directed Requirements Acquisition , 1993, Sci. Comput. Program..

[4]  A. van Lamsweerde Goal-oriented requirements enginering: a roundtrip from research to practice [enginering read engineering] , 2004 .

[5]  Alistair G. Sutcliffe,et al.  Scenario-based requirements engineering , 2003, Proceedings. 11th IEEE International Requirements Engineering Conference, 2003..

[6]  V. Kumar,et al.  Goal-oriented or scenario-based requirements engineering technique - what should a practitioner select? , 2005, Canadian Conference on Electrical and Computer Engineering, 2005..

[7]  Ivar Jacobson,et al.  The Unified Modeling Language User Guide , 1998, J. Database Manag..

[8]  Bashar Nuseibeh,et al.  Requirements engineering: a roadmap , 2000, ICSE '00.

[9]  John Mylopoulos,et al.  Towards requirements-driven information systems engineering: the Tropos project , 2002, Inf. Syst..

[10]  Axel van Lamsweerde,et al.  Requirements engineering in the year 00: a research perspective , 2000, Proceedings of the 2000 International Conference on Software Engineering. ICSE 2000 the New Millennium.

[11]  Evangelia Kavakli,et al.  Goal-Oriented Requirements Engineering: A Unifying Framework , 2002, Requirements Engineering.

[12]  Eric S. K. Yu,et al.  Agent/goal Orientation versus Object Orientation for Requirements Engineering: A Practical Evaluation Using an Exemplar , 2005, WER.

[13]  Ivar Jacobson,et al.  The Unified Modeling Language user guide second edition , 2005 .

[14]  Fausto Giunchiglia,et al.  Tropos: An Agent-Oriented Software Development Methodology , 2004, Autonomous Agents and Multi-Agent Systems.

[15]  Eric Yu,et al.  Modeling Strategic Relationships for Process Reengineering , 1995, Social Modeling for Requirements Engineering.

[16]  Marco Torchiano,et al.  The Role of Experience and Ability in Comprehension Tasks Supported by UML Stereotypes , 2007, 29th International Conference on Software Engineering (ICSE'07).

[17]  Miroslaw Staron,et al.  An empirical study on using stereotypes to improve understanding of UML models , 2004, Proceedings. 12th IEEE International Workshop on Program Comprehension, 2004..

[18]  Axel van Lamsweerde,et al.  Goal-oriented requirements enginering: a roundtrip from research to practice [enginering read engineering] , 2004, Proceedings. 12th IEEE International Requirements Engineering Conference, 2004..

[19]  Claes Wohlin,et al.  Experimentation in software engineering: an introduction , 2000 .

[20]  Sooyong Park,et al.  Managing requirements conflicts in software product lines: A goal and scenario based approach , 2007, Data Knowl. Eng..

[21]  Ivar Jacobson,et al.  Unified Modeling Language User Guide, The (2nd Edition) (Addison-Wesley Object Technology Series) , 2005 .